Zebra rc.1 and security audit preparation
Zebra released 1.0.0-rc.1, its second release candidate, to be sent to the security audit.
Agenda summary 4
Zebra 1.0.0-rc.1 release
Zcash Foundation · Deirdre
- The team released the second release candidate, Zebra 1.0.0-rc.1. All dependencies were updated, and this candidate will likely be sent to the security audit. If it passes the audit, it becomes the long-term-support 1.0 stable.
- The first implementation of the getblocktemplate RPC went in, but it does not yet fill in all live data. getblockhash and getblockcount were also added, and guidance on Prometheus and Grafana metrics is in the repository.
- The mempool was fixed to reject transactions with an outpoint or nullifier that has already been used. The problem of shielded parameter downloads breaking on Rust 1.64 was resolved, so for those who build it themselves, 1.64 is supported again.
- The team released ed25519-zebra 3.1.0, the ed25519 verification crate with ZIP 215 consensus rules. Thanks to a contributor, it supports no-std and can be used with core alone.
- The audit firm has been shortlisted but not yet confirmed.
Zcashd update - mobile SDK fast sync and memory optimization
Electric Coin Company · Steven, Pacu, Daira
- Since NU5 activation, ECC has focused only on performance and scalability, releasing 5.1.0, 5.2.0 and 5.3.0. They said there have been no problem reports yet for 5.3.0's OOM improvements.
- Mobile SDK fast sync will ship in two or three stages. The first stage is under internal testing and Android follows in about a week. The first stage includes the DAGSync foundation and unified address support.
- Pacu said the iOS alpha has reached 0.17.0-alpha 3 and that alphas may break compatibility with each other, so use the latest. They asked for feedback on the API preview and plans to submit PRs to help partners adopt it.
- The SDK's UA syncs Transparent and Sapling and does not yet support Orchard. The original plan was Orchard support and SDK hardening, but the order was changed because of load, and the UA is a pattern designed to keep working smoothly as pools are added.
- Daira said zcashd holds the block header tree of the entire chain in memory, and because an Equihash solution is 1344 bytes, the total comes to about 2.3GB. The next optimization reads this from LevelDB only when needed.
ZIP 317 progress and ecosystem coordination
Electric Coin Company · Steven, Adi
- In zcashd, the team is building a general-purpose fee abstraction that can accommodate ZIP 317 and even EIP 1559-style fees. The next step is to discuss implementation with ecosystem partners.
- Adi invited Zcash developers and service providers to the November 10 ZIP 317 meeting. The team is spreading word through social media and direct contact with developers (DMs, email).
- 5.3.0 is rolling out across the ecosystem. Steven said 5.1.0 was halted and some are running older versions they compiled themselves. Memory and block propagation optimizations will be added in 5.3.1 or 5.4.0.
Open discussion - review of the draft ZSA ZIPs
Zcash Foundation · Deirdre, Daira
- At the ZIP sync, the team looked at the draft ZSA ZIPs and the ZSA issuance PR in the Orchard crate, and wanted to ask QEDIT whether there are differences between the code and the draft, but no one from QEDIT attended this meeting.
- The transfer and burn documents were reviewed a few months ago, and the issuance draft was skimmed for the first time this time, so there is feedback. Daira will contact Daniel.
This summary is based on the original meeting notes; check them for exact details.