Mood leans toward holding off ZSA mainnet activation
On the NU7 vote results, the direction discussed for ZSA was to keep it behind a feature flag and on testnet.
Agenda summary 10
Discussion of NU 7 polling results
Jason, Pili, Jon, Pacu, Kris
- Jason said this is the first call since the polling results and put an agenda item on aligning interpretations of the NU 7 scope, zcashd deprecation and the NU 7 activation schedule.
- Pili summarized that most items were agreed but a few were split.
- Qedit's Jon interpreted the forum discussion as showing that the urgency of activating ZSA immediately had decreased, and that there was a consensus to verify ZSA's usefulness on a testnet rather than on main Zcash.
- So the idea is to keep ZSA in the codebase behind a feature flag, make it usable on the testnet, and defer the decision on mainnet activation.
- Pili said ZF also supports merging behind a feature flag so that the ZSA investment is not wasted.
- Jon said Qedit's ZSA team will focus going forward on maintaining a feature testnet with just the flag turned on, and do more of other work such as the Tachyon audit.
- Pacu said that, aligned with zcashd's end-of-support (16-week cycle), the earliest time deprecation is possible is September 2, and that it must be re-evaluated since time has passed.
- Because deprecation is hard to reverse, Pacu started creating a document in the zcashd book laying out the order of deprecation.
- Kris said the ZIP editors group is putting together, in consultation with the major development players, an NU 7 proposal that is minimal yet complete and leaves room for quick extension.
- They said a proposal explaining the rationale will be presented to the community soon, and that some people want to put it out within next week.
Zebra update
Zcash Foundation · Marek
- The Python QA framework was removed, and the mempool transaction filter was matched to zcashd (an external contribution).
- The team fixed a verification bug for transactions that use inputs from both the chain and the mempool and a peer connection metrics bug, and simplified the Read state service implementation.
ZODL update
ZODL · Kris, Hazel
- In Zallet the shielded coinbase implementation is progressing through to the backend stack.
- It fixed an earlier problem where coinbase maturity was not handled properly, and is also integrating P2SH support for importing the P2SH key components of zcashd wallets.
- The integration test repository, which Str4d created by splitting ZF's integration test work out of the Zebra repository, builds Zebra, Zaino and Zallet together and runs the legacy zcashd RPC tests.
- It is now possible to identify feature gaps in Zallet and add support if needed.
- When Hazel asked why all tests pass for the draft Zallet chain index migration PR 336, Kris answered that it is because the parts that do not work are not tested and failing tests need to be added.
Zaino update
Zingo Labs · Hazel
- This is the fourth Zaino release candidate, and the hope is that it is the last.
- No additional code is needed and only the release process remains, and it can be tested as is.
- The subtree roots API for Zallet is an untested draft PR, so it is left out of this release and will go into a minor release shortly after.
- Kris said they would depend on that patch version if needed.
zcashd deprecation update
Electric Coin Company, Zcash Foundation, Zingo Labs · Pacu
- It is a quiet period without much outreach until a new alpha is released.
- The Zallet contributor board is being tidied, and because community contributions are numerous the open issues have run out, so new issues are being screened and prioritized.
- The team is also helping with Zaino development.
ZSA update
Qedit · Vivek
- The ZIPs have been stable for a month, and minor fixes were merged.
- It restored the ZSA activation flag in the Orchard specification that was dropped during a merge, and limited the value burn field for asset burns from U64 to U63.
- It finished internal replies to Str4d's comments on Orchard upstream PR 471, and the ball will soon be back in Str4d's court.
- For zcash-test-vectors, PRs 112 and 114, which split out the formatting changes, were approved by Alfredo.
- The ZSA changes in standalone PR 108 are also awaiting review.
- In librustzcash the ZIP 233 amount field is included in the test vectors and run behind a feature flag, and the gap with upstream is being reduced.
- In Zebra, state management that stores issued assets in a separate map is nearly done.
- A blockchain cache feature was added to the transaction tool to avoid a full resync when restarting the testnet, and the single-node testnet continues to run.
Network Sustainability Mechanism (NSM) update
Shielded Labs · Jason
- The PR that combined ZIP 234 and 235 was split into separate PRs.
- ZIP 233 and 235, which burn 60% of fees, will proceed first, and ZIP 234, which deals with flattening issuance, can be deferred while community and coinholder discussion continues.
- In the polling results, burning transaction fees received broad support from both coinholders and the community panel.
- The distribution mechanism that flattens the issuance curve was strongly supported by the community panel but not by coinholders.
Crosslink update (Trailing Finality Layer)
Shielded Labs, ZODL · Mark
- The prototype phase wraps up at the end of this month, followed soon by the first seasonal incentivized testnet.
- Rewards are based on activities that help mainnet, such as running a DNS seeder, and will continue beyond the second quarter.
- The official roadmap will also be posted on the site soon.
- The team built an internal tool, deploy link, that deploys a testnet from a commit hash of a monorepo that bundles Zebra, Zaino and librustzcash as Git subtrees.
- A demo can be set up for other teams that need feature testing.
- Starting from Crosslink's need for fast block sync, it is researching a networking stack that uses the Noise protocol and UDP.
- It is collaborating with the Zcash Foundation, Nym and Tachyon teams and also pursuing compatibility with Nym's UDP tunneling.
Dynamic fees
Shielded Labs · Mark
- There are no meaningful updates since the last call.
- The team is reviewing the ZIP and discussing the design internally.
Open presentation: Zebra chain tip bug, a Kusama idea for Zcash
Hazel, Mark
- Hazel reported a problem where the getblockchaininfo RPC returns the tip of the non-finalized state while the read state service returns the tip of the finalized state, a 99-block difference.
- It is unclear whether it is a Zebra bug or a Zaino handling problem, and they agreed to check separately with Marek.
- Mark proposed the idea of building a canary network for Zcash with real economic value, like Polkadot's Kusama.
- They asked anyone interested in an informal, lightweight working group to contact them individually.
This summary is based on the original meeting notes; check them for exact details.