Orchard ZSA spec completion report
Qedit said Orchard ZSA is complete by the spec and will go into review soon.
Agenda summary 8
Zebra update
Zcash Foundation · Conrado
- Orchard and Sprout fields were added to the getrawtransaction RPC, and missing fields were filled in to complete the z_gettreestate RPC.
- Configuration was changed to a layered approach, so Zebra can be configured with environment variables in addition to the existing TOML file.
- This makes deployment and CI easier.
- Sapling bundle verification was replaced with a call to a librustzcash function, removing a considerable amount of duplicate code in Zebra.
- The longer-term goal is to switch the transaction types to librustzcash's as well.
- Items missing from the RPC spreadsheet are being identified and worked on, and CI refactoring is also in progress.
- The plan is then to focus on supporting Zallet and Zaino.
ECC core update (librustzcash, P2SH, Zallet)
Electric Coin Company · Daira Emma, Kris, Str4d, Pacu
- A draft of the specification for generating the P2SH multisig address needed for NU 6.1 (ZIP 48) was sent to Keystone developers, who gave positive feedback.
- RPC calls were implemented for the Zallet alpha, and problems in the Zaino and Zebra stack were worked around.
- In the Zallet alpha, z_viewtransaction and z_listunspent handle both transaction lookup and unspent output lookup.
- This makes it possible to retire zcashd's confusing gettransaction and listunspent.
- New engineer Mischell is implementing the long-standing task of separating anchor height selection from the confirmations requirement, and a mobile SDK update is expected to let Zashi, Edge and others spend change notes sooner.
- Pacu's send max feature was merged into zcash_client_backend, and the in-memory wallet implementation built by ChainSafe was also merged, so it is no longer neglected.
- It will be supplemented under a maintenance grant ChainSafe is about to start.
- The NU 6.1 protocol specification changes were completed in the PR, and only one of the disbursement addresses has yet to be generated.
Zaino update
Zingo Labs · Za
- The grant proposal work was finished and the requested features were passed to the Zallet developers; the many issues they filed are being triaged by priority so the Zallet alpha can come out within a few weeks.
- A good part of the architecture redesign, which promotes internal types into the type system to get compiler guarantees, has also been done.
- The goal is to finish the upgrade supporting NU 6.1 within this week.
zcashd retirement update
Electric Coin Company, Zcash Foundation, Zingo Labs · Pacu, Str4d, Daira Emma, Alfredo
- Initial feedback is being gathered from partners such as exchanges for the network upgrade friction survey.
- It is used to gauge the scope of transaction changes and to put together an RFP if needed.
- Alfredo announced a test framework that runs against the Zebra RPC codebase, which is expected to speed up feedback on repetitive RPC work.
- Bugs from the integration process are also being triaged.
- Str4d said that for features that will not be offered in Zallet, the next zcashd release may additionally mark them as deprecated but still enabled by default.
- The changed semantics will be documented and updated on the book page.
- Zallet documents its RPC with OpenRPC, and Alfredo said it would be good for Zebra and Zaino to use it too, giving unified RPC documentation.
- Zebra currently uses Swagger.
- Pacu explained that the first principle is not a one-to-one replacement of zcashd but avoiding carrying technical debt over to the new system.
ZSA update (Orchard ZSA, transaction v6)
Qedit · Pablo
- Orchard ZSA is spec complete.
- SIGHASH versioning and the issuance key change added by the ZIP editors were incorporated, and after finishing touches to reduce the diff the PR will be switched to ready for review within a few days.
- The review can be parallelized across three areas.
- They are the ZSA circuit, unchanged since the audit half a year ago, the Python reference implementation, and the Orchard crate, which builds both ordinary Orchard bundles for v5 and ZSA bundles for v6.
- After discussion with Daira Emma and Str4d, they decided to extend the v6 transaction implementation to spec complete in line with ZIP 230, including the NSM field and fee changes.
- A draft librustzcash PR has also been opened.
- Zebra has a working version with a global state and DB table tracking the supply and finalized status of issued assets, and the issuance consensus rules.
- It is not the final version because Orchard and v6 are not yet finalized.
- Adding a GET-style health endpoint for Docker to Zebra is being discussed with ZF, and the plan is to submit it as a PR separate from ZSA.
- The Python reference implementation is a test vector generator rather than production code, and Str4d explained that it is for verifying that parser implementers handle every transaction encoding.
Network Sustainability Mechanism (NSM) update
Shielded Labs · Mark
- A small PR fixing CI was merged so the NSM test vector PR can be merged.
- Once the test vectors are merged, work will return to Zebra to handle the ZIP 233 PR.
- ZIP 233, ZIP 234 and ZIP 235 are unchanged.
- Daira Emma opened a PR renaming the CSF simulation repository to NSM and asked for review.
Crosslink update (Trailing Finality Layer)
Shielded Labs · Nate
- At last week's Milestone 3 workshop, several participants connected to the network and synced, and a demo showed that rollback to before the finality point is prevented.
- There were connection and audio problems and persistent bugs, but they did not block the overall progress.
- PoS is added starting with Milestone 4.
- Because it is a big task, Milestone 4.1 comes first, building an easy-to-join testnet and a good guide.
- It also includes registering arbitrary weights on the roster through a Zebra RPC.
- The plan is to hold a smoother workshop within a month, then introduce the first staking mechanisms, such as bonding and unbonding transactions, in 4.2.
- A blog post on the user-facing effects of staking is also coming soon.
- Rigorous analysis of the economic mechanisms will be done after the prototype stage at the end of the year.
- The current design is simplified, with no edge-case rules such as slashing.
- For privacy, the team is considering quantizing delegation and release times and having an unbonding period.
- A delegation position reveals the amount and the delegate, which makes it different from a turnstile.
Open announcements and discussion
Str4d, Nate, Daira Emma, Pablo
- Str4d said they had tried to test Zallet at the weekly zcashd retirement meeting but a blocking bug got in the way, and that they will try again soon.
- Anyone who wants to take part can let the Zcash R&D Discord know.
- Daira Emma suggested that Crosslink staking draw on Penumbra's private staking design.
- The approach is to start with transparent delegation and later add private delegation through a simple change to the value-conversion circuit.
- Nate said they would put this forward as a post-1.0 candidate.
- Daira Emma is working on a draft of a long-term custody protocol (reservoir) built from simple cryptography, and also noted that a post-quantum protocol is needed.
- For the quantum-resistance ZIP, the prerequisite changes in the protocol spec work were resolved, so a draft can be written soon.
- Str4d said it is a change to how notes are constructed on the consumer side, not a consensus change, and that shipping it with NU 7 would be convenient.
- Daira Emma argued for making the new note plaintext format mandatory from NU 7, while Str4d, citing the ZIP 212 experience and the risk that wallets would not comply, said to discuss it in a separate R&D meeting.
This summary is based on the original meeting notes; check them for exact details.