Now it will be renamed to z4… 
1 Like
July 18th.
Hello! Another week, another Zcash Z3 development update!
This is the last update of the series. Today we reached Zcashd EOL block height at 3417100. As Josh says on his X post “The consensus rules zcashd pioneered live on. The chain it started keeps producing blocks, on infrastructure built for the next decade rather than adapted from the last one.”
As the last Zcashd peers fade out of the network a new Zcash era begins. This is not an art of chance. It is deliberate hard work that Zcash foundation developers have been doing for years with the support of the rest of the core developers.
Zcash has been able to turn the page and can begin to run at a higher pace thanks to not having to cope with the burden of tech debt inherited by Bitcoin core C++ code from many years ago and not having to support technical decisions that were not ours to make but Bitcoin’s.
The sun is rising and it’s going to be a bright day.
Congratulations to you all.
Onward.
Outreach
Status: unwinding
We completed the Zcashd EOL outreach and we are monitoring the situation.
Zebra
ZF Engineers released Zebra 6.1.0 and 6.2.0 along with Zakura developers (a Zebra Fork) releasing 1.0.0 and 1.0.1.
ZF Zebra and Zakura both support Zcashd-compat mode which helps the ecosystem hold on a bit longer to Zcashd APIs until they can do the full switch.
Zaino (ZingoLabs)
- Status: released 0.5.1
Zaino Engineers are working on storage optimizations and lean verification alongside Hahn.
Zallet full node wallet
- Status: 1.0.0-beta.1 released
tracking work on this repository and collaboration opportunities tracked on this board.
ZODL engineers released Zallet 1.0.0-beta.1 which contains most of the features needed for exchanges to work and we are receiving feedback from miners and exchanges to keep improving while there’s an audit on the way which will be ready before Ironwood activation.
Thanks for reading.
7 Likes
Hello pacu, I am running the Z3 stack and zallet db keeps getting corrupted.
I started with the repo https://github.com/ZcashFoundation/z3 and got it running with docker compose --env-file .env.regtest up , running some commands like z_getnewaccount, z_listunspent, z_getaddressforaccount, z_getbalanceforaccount, z_getbalances was successful. After some back and forth development period, calling on z_listunspent would throw error of WalletDb::get_memo failed`
Here’s the full command:
docker exec z3-regtest-zallet-1 zallet-zebra --config /etc/zallet/zallet.toml --datadir /var/lib/zallet rpc z_listunspent
2026-08-15T12:49:04.954981Z INFO zallet_core::commands: Loading configuration config=/etc/zallet/zallet.toml
ERROR:
JSON-RPC request failed: ErrorObject { code: ServerError(-20), message: “WalletDb::get_memo failed”, data: Some(RawValue(“Invalid UTF-8: invalid utf-8 sequence of 1 bytes from index 5”))`.
Initially, I thought it might a bug in that version (image: {Z3_ZALLET_IMAGE:-zodlinc/zallet:v0.1.0-beta.1@sha256:1849b4469875dc0165942c06d15fa6a7da76b2d43bade578cc8e5903a639869d})** of Zallet used in the Z3 repo, so I updated it to the latest (**image: {Z3_ZALLET_IMAGE:-zodlinc/zallet:latest}) inside of docker-compose.yml.
I restarted the container, everything looked good (for a while) till calling z_listunspent to confirm the result after a note was sent out produces the `JSON-RPC request failed: ErrorObject { code: ServerError(-20), message: “WalletDb::get_memo failed”, data: Some(RawValue(“Invalid UTF-8: invalid utf-8 sequence of 1 bytes from index 5”)) }`
Thanks for a solution.
1 Like
Can you file a GitHub issue in the Z3 repository?
I have done so - Zallet reports incorrect insufficient balance and wallet DB has invalid UTF-8 memo · Issue #794 · zcash/zallet · GitHub. Thanks
1 Like