Missing Params Bug Notes

gistfile1.txt

root@bd56a513c246:~# /home/zcash/src/zcashd -printtoconsole





Zcash version v1.1.2-6b9c96272 (2018-07-30 03:46:37 -0700)
Using OpenSSL version OpenSSL 1.1.0h  27 Mar 2018
Using BerkeleyDB version Berkeley DB 6.2.23: (March 28, 2016)
Default data directory /root/.zcash
Using data directory /root/.zcash/testnet3
Using config file /root/.zcash/zcash.conf
Using at most 125 connections (1048576 file descriptors available)
Using 4 threads for script verification
scheduler thread start
Error: Cannot find the Zcash network parameters in the following directory:
"/root/.zcash-params"
Please run 'zcash-fetch-params' or './zcutil/fetch-params.sh' and then restart.
Error: Cannot find the Zcash network parameters in the following directory:
"/root/.zcash-params"
Please run 'zcash-fetch-params' or './zcutil/fetch-params.sh' and then restart.
libevent: getaddrinfo: address family for nodename not supported
Binding RPC on address ::1 port 18232 failed.
HTTP: creating work queue of depth 16
No rpcpassword set - using random cookie authentication
Generated RPC authentication cookie /root/.zcash/testnet3/.cookie
HTTP: starting 4 worker threads
Using wallet wallet.dat
init message: Verifying wallet...
CDBEnv::Open: LogDir=/root/.zcash/testnet3/database ErrorFile=/root/.zcash/testnet3/db.log
Bound to [::]:18233
Bound to 0.0.0.0:18233
Cache configuration:
* Using 2.0MiB for block index database
* Using 120.0MiB for chain state database
* Using 328.0MiB for in-memory UTXO set
init message: Loading block index...
Opening LevelDB in /root/.zcash/testnet3/blocks/index
Opened LevelDB successfully
Opening LevelDB in /root/.zcash/testnet3/chainstate
Opened LevelDB successfully
LoadBlockIndexDB: last block file = 0
LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=1, size=1700, heights=0...0, time=2016-10-28...2016-10-28)
Checking all blk files are present...
LoadBlockIndexDB: transaction index disabled
LoadBlockIndexDB: hashBestChain=05a60a92d99d85997cce3b87616c089f6124d7342af37106edc76126334a2c38 height=0 date=2016-10-28 09:47:13 progress=0.000001
init message: Rewinding blocks if needed...
init message: Verifying blocks...
Shutdown requested. Exiting.
Shutdown: In progress...
StopRPC: waiting for async rpc workers to stop
scheduler thread interrupt
StopNode()
Shutdown: done
root@bd56a513c246:~# ls -la /root/.zcash-params/
total 888864
drwxr-xr-x 2 root root      4096 Aug  1 04:51 .
drwx------ 1 root root      4096 Aug  3 17:31 ..
-rw-r--r-- 1 root root 910173851 Mar  3 19:32 sprout-proving.key
-rw-r--r-- 1 root root      1449 Mar  3 20:02 sprout-verifying.key
root@bd56a513c246:~# sha256sum /root/.zcash-params/*
8bc20a7f013b2b58970cddd2e7ea028975c88ae7ceb9259a5344a16bc2c0eef7  /root/.zcash-params/sprout-proving.key
4bd498dae0aacfd8e98dc306338d017d9c08dd0918ead18172bd0aec2fc5df82  /root/.zcash-params/sprout-verifying.key
root@bd56a513c246:~#

I noted the possibility of an error log:

root@db9fb7f3c5ed:/# ls -la !$
ls -la /root/.zcash/testnet3/db.log
-rw------- 1 root root 0 Aug  3 18:03 /root/.zcash/testnet3/db.log

That turned out to be empty.

I ran with "-P" to ensure port exposure.
The actual docker run command:

docker run -P -it --entrypoint=/bin/bash alpinezcashbuilder:latest

I searched via duckduckgo for this pattern:

Error: Cannot find the Zcash network parameters in the following directory:"/root/.zcash-params"

That had several interesting results:

1. I studied this issue (DDG result): zcash/zcash#2787
   I decided this issue was not the same because I saw this in it:

2017-12-02 13:20:15 Loading verifying key from /root/.zcash-params/sprout-verifying.key
2017-12-02 13:20:15 Loaded verifying key in 0.004999s seconds.

2. I investigated this URL (DDG result):
   zcash/zcash#2709
   WAIT WHAT? Insight, how can my "scratch" image be ~153MiB if the params file is ~911MiB?
   ANSWER: The scratch based image is ~ 1.06GiB, mostly /root/.zcash-params/sprout-proving.key

I have checked the path name. It's not the case that I have it wrong, it's:

/root/.zcash-params/

followed by basenames that fetch-params.sh supplied. Therefore I rule out this issue as the same.

3. I studied this issue (DDG result): zcash/zcash#2214

   This seems to be a test of the behavior of the system when one tries to start zcashd during parameter download. That's not the case I am in.

4. I studied this issue (DDG result): HorizenOfficial/zencash-swing-wallet-ui#64

   First, this is a zencash issue, second "reindex" is invoked, so it seems different than mine.