v0.4.11
Critical bugfix release!
This release fixes a critical bug (see #392)! It's imperative to upgrade to this release before NU5 activates!
Since NU5 has already activated on testnet, please follow this procedure to deploy this release on testnet. Also follow this procedure for mainnet if NU5 has already activated (scheduled to be May 31, 2022, at approximately 1600 UTC).
Note, if this procedure causes too much downtime, see alternate instructions below to minimize downtime.
- Stop the running lightwalletd (it's not necessary to stop the local
zcashd) - Remove the lightwalletd cache directory (these are the default locations, your installation may have them in a different path)
- testnet:
rm -r /var/lib/lightwalletd/db/test - mainnet:
rm -r /var/lib/lightwalletd/db/main
- Start lightwalletd
It will take 2 or 3 hours for the lightwalletd to recreate the cache directory, depending on your system's CPU performance.
To minimize downtime (mainnet), this can be done on the same system as your production lightwalletd is running:
- Start a separate temporary instance of the new lightwalletd (v0.4.11) using a different port number (9069, of it's in use, try another), for example:
./lightwalletd --no-tls-very-insecure --log-file /dev/stdout --grpc-bind-addr 127.0.0.1:9069 --data-dir /tmp/lwd-data-dir - Let it sync; this will take 2 or 3 hours, the "adding block" messages will stop and you'll begin to see only "waiting for block" messages
- Stop the temporary lightwalletd (control-C)
- Stop the production lightwalletd and upgrade it to the new release (v0.4.11)
- Copy
/tmp/lwd-data-dir/db/main(or the 2 files within) to the production cache (see filesystem paths above) - Start the production lightwalletd as usual