ECC emergency mode officially ends
ECC declared the end of emergency mode, and the NU5 retrospective will begin in four weeks.
Agenda summary 6
ECC update: end of emergency mode and ECC focus and decentralization
Electric Coin Company · Zooko
- ECC officially declared the end of emergency mode, since all three wallets using the wallet SDK have shipped new versions based on SDK 2.0, giving users access to their funds.
- The Zashi UI is being iteratively improved, and private beta testers are being recruited. On the product side, ECC is helping other parties take over the full-node maintenance role for exchanges and mining pools.
- ECC introduced its 'Focusing ECC, Decentralizing Zcash' stance.
- The focus areas are PoS, the SDK and Zashi, and it was explained that a lot of effort goes into getting others to take over things ECC did alone eight years ago, such as the z.cash website and operating full nodes for exchanges.
Zebra 1.4.0 update
Zcash Foundation · Teor
- Zebra 1.4.0, with Teor as release manager, will come out next week. About 12 mining RPCs, typically getblocktemplate, are provided in the production build.
- Like zcashd, the Sapling and Sprout verification parameters were built into the zebrad binary. A separate parameter file download is no longer needed, and the files can be deleted after upgrading.
- With the Rust crates being published, API documentation is provided on docs.rs, and the public API documentation on the old doc.zebra website will no longer be updated.
- The team is considering reducing the roughly 7 docker tags per release to an exact version tag and a latest tag, and asked people to say if they need any tags.
Trailing Finality research progress
Electric Coin Company · Nate, Daira
- The goal of consistently revising the TFL book to fit Crosslink has not yet been achieved, and a coherent version introducing Crosslink will come out by Monday. The Crosslink definitions currently on HackMD will also be merged into one document.
- Work continues on the two security arguments for the Crosslink construction, liveness and safety. The next big goal is improving the Python simulator so it can run multiple security scenarios.
- Daira implemented the Crosslink and Snap-and-Chat abstractions in the simulator, and a draft PR is up for the BFT protocol abstraction. Next, Streamlet, a BFT protocol designed for teaching, will be implemented.
- TFL is a hybrid approach that layers PoS on top of PoW to finalize transactions; finalized transactions cannot be rolled back, which helps with bridge and DEX integrations. The key point of the analysis is not to get only the security of the weaker of the two protocols.
FROST update
Zcash Foundation · Teor
- The FROST audit report was published on the NCC website.
- Cleanup work for the FROST Rust release candidate is underway, and work has begun on adding network communication to the demo.
ZSA update: move to Zebra and regulatory response discussion
QEDIT · Jon (QEDIT), Teor, Daira
- QEDIT is working on getting the ZSA, which was demonstrated on Zcashd, running again on Zebra.
- A test platform is being written that creates ZSA transactions in a pseudo-v6 format and runs them on Zebra, and it can also be used to test Orchard transactions.
- The testnet purpose is hardcoded in Zebra, so a separate network must be run for ZSA. Teor said that forking the current testnet and adding a network upgrade is easy, but a separate network from genesis needs scheduling.
- The NU6 scope was described as a process in which the ZIP editors gather the ready ZIPs and decide after community input from ECC and ZF, after which the editors create the transaction format and the implementation teams incorporate it.
- Jon proposed a working group to discuss features for responding if ZSA is misused, to prepare for regulatory risk, and mentioned the November 30 ZK policy event in Washington.
- Daira said existing regulation-compatible proposals harm privacy greatly and that better ideas are needed.
NU5 retrospective format and topics
Daira, Jack Gavigan, Nate, Str4d, Teor, Kris
- With ECC's emergency mode over, the NU5 retrospective can begin. It was decided to hold the first retrospective in the late slot in four weeks, and to continue general updates in the early slot. Long meetings will include breaks.
- Jack Gavigan created a shared document organizing topics. They include schedule, scope and complexity, external constraints, a sandblasting post-mortem, and meta and cross-cutting issues.
- Daira and Str4d said the sandblasting post-mortem should be done first, separately from the NU5 retrospective, and its results fed into the retrospective's cross-cutting discussion. The questions of who responds to attacks and who is responsible for network monitoring will also be covered.
- Teor said they should also discuss how schedule changes happened, external constraints such as the halving, and the split between work before and after activation. Teor will facilitate, Daira will contribute opinions, and the existing note-takers will keep the record.
- There was an opinion that the retrospective and future upgrade planning should be kept separate. The next Arborist Call is the general update in the early slot on November 16.
This summary is based on the original meeting notes; check them for exact details.