Thanks for the feedback @nuttycom, makes complete sense to me. I’ve made sure to pass this on to the rest of our team as well.
Hi everyone, I’m back with another update on our maintenance efforts:
WebZ.js + MetaMask Snap — February + March 2026
- Internal monitoring upgrades
- Completed core functionality gaps in zcash_client_memory by implementing incoming Sapling/Orchard transaction storage, transparent address metadata tracking, and several previously-stubbed WalletRead API methods (list_addresses, get_last_generated_address_matching, utxo_query_height).
- Optimized received note lookups from O(n) linear scans to O(1) indexed lookups and fixed balance calculation bugs around expired unmined transactions and unscanned range filtering.
- Hardened both zcash_client_memory and zcash_client_backend’s block scanner by replacing all .unwrap()/assert!()panics with proper Result error propagation — critical for WASM targets where panics are unrecoverable.
Hi Zcash community, ChainSafe is nearing the end of it’s runway with our current maintenance grant for WebZjs and the Zcash Metamask Snap. We’ve just created a new grant application to extend maintenance funding for another year. You can review the application here. Please let us know if you have any questions or feedback!
Apologies if this has been covered before, but I’m wondering how much work it would be to introduce FROST support on web via wasm, for example for payment escrow.
Thank you for your submission. After consideration from ZCG and sufficient time for the community to provide feedback on the forum, the committee has decided to reject this proposal.
The committee appreciates your grant submission efforts and encourages you to continue as an active member of the Zcash community going forward!