andyceo / docker-zcash

Zcash docker image

Image Badges

Download zcash parameters

sudo docker run --rm -v /data/zcash/.zcash-params:/root/.zcash-params:rw -v /data/zcash/.zcash:/root/.zcash:rw --entrypoint zcash-fetch-params andyceo/zcash

Run

sudo docker run -d -v /data/zcash/.zcash-params:/root/.zcash-params:ro -v /data/zcash/.zcash:/root/.zcash:rw -h zcash --name zcash andyceo/zcash

Check hashrate

time ~/zcash/src/zcash-cli zcbenchmark solveequihash 10


time solveequihash NUM_ITERS [NUM_THREADS]

The result will be something like

real    1m15.879s
user    0m0.000s
sys     0m0.004s

where the first number is the real time taken. Divide 10 by this value (converted into seconds) and you have your hashrate in hashes per second. Of course the advantage to this method is that you can easily run 100 or 1000 loops to average out the run times.

• see How do i check my hashrate?
• https://forum.z.cash/t/how-to-check-mining-hashrate-with-zcash-built-in-miner/2810
• https://forum.z.cash/t/monitor-zcashd-hash-rate-in-daemon-mode/4531/12
• https://www.cryptocompare.com/mining/calculator/zec
• https://steemit.com/mining/@takenbtc/how-mining-zcash

Releases

Will be the same as Zcash releases: https://github.com/zcash/zcash/releases

Volumes

Previously, this image had two volumes: /root/.zcash-params and /root/.zcash. To simplify volume management, and add ability to store user history with zcash-cli and other cli tools, it has been changed to just /root.

• /root/.zcash-params - contains zcash parameters, that could be obtained with zcash-fetch-params command.
• /root/.zcash - this is the zcash.conf location, also wallet data, blockchain data, etc.

docker-zcash's Issues

Use a Custom Address

I see that a wallet.dat gets created during the launch of zcash:

• Host system: /root/.zcash/wallet.dat

I'm sure that's needed for syncing information with the network. What I'm wondering is:

• Does your docker image make use of the mineraddress parameter? If so, how?

I've combed through your DockerFile and scripts and I don't see it explicitly referenced. I'm thinking I'll try adding it to the conf file and report back.

README Errors

I found an issue with your README. I would submit a PR, but I'm not sure if I hacked around it or I configured something bad. It seems like it was just an older config that needed updating; maybe?

I changed the volume mount from:

• -v /data/zcash/.zcash:/root/.zcash:rw

to:

• -v /root/.zcash:/root/.zcash:rw

Check Hashrate

Can you be more specific on the command you supplied; maybe even create a wiki with more details?

time ~/zcash/src/zcash-cli zcbenchmark solveequihash 10

However, after cloning zcash and running the command, I get No such file or directory:

~$ git clone https://github.com/zcash/zcash.git
Cloning into 'zcash'...
remote: Counting objects: 63842, done.
remote: Total 63842 (delta 0), reused 0 (delta 0), pack-reused 63842
Receiving objects: 100% (63842/63842), 46.13 MiB | 6.06 MiB/s, done.
Resolving deltas: 100% (48154/48154), done.
~$ time ~/zcash/src/zcash-cli zcbenchmark solveequihash 10
bash: /home/vertigoray/zcash/src/zcash-cli: No such file or directory

real    0m0.001s
user    0m0.000s
sys     0m0.004s

I did confirm that there doesn't appear to be a file/directory in that path of the repo.

Thoughts?

Connection reset?

Fresh install, mainnode, getting:

2018-11-28 15:48:07 socket recv error Connection reset by peer (104)
2018-11-28 15:48:08 Misbehaving: <IP>:<PORT> (0 -> 1)
2018-11-28 15:48:08 ProcessMessages(reject, 43 bytes) FAILED peer=2
2018-11-28 15:48:08 Misbehaving: <IP>:<PORT> (1 -> 2)
2018-11-28 15:48:08 ProcessMessages(ping, 8 bytes) FAILED peer=2

With the last two lines repeating for tons of IPs. Rejected on every peer? Any idea? Clients work fine outside of docker.