Zallet alpha released
The Zallet alpha is out and can be installed as a Docker image or Debian package.
Agenda summary 7
Zebra update
Zcash Foundation · Alfredo
- The missing Orchard fields in getrawtransaction were completed, and the getaddresstxids RPC now accepts string arguments as well as object arguments.
- The getmempoolinfo RPC is also being worked on by external contributors cseri and Conrado.
- Tests verifying the NU 6.1 disbursement were added, and a Zcash unstable feature variant was added to the network upgrade so other teams can develop future upgrades.
- Sapling code was replaced with the upstream sapling-crypto crate, removing a large amount of duplicate code, and the contributor guidelines were updated.
- Arya implemented backing up the latest 100 blocks of the non-finalized chain to a file, so on restart Zebra can resume right from where it stopped.
- Gustavo's CI refactoring made CI simpler and more stable, so PRs merge faster.
- The guidelines now state a policy of not adding features that belong to Zaino or Zallet to Zebra and moving them to those repositories instead.
- The Flyclient support PR is such a case, and an external contributor is also working on getnetworkinfo.
- Marek is back and is expected to resume work on the ZIP 213 PR supporting shielded coinbase addresses for miners.
- Several approaches to the health endpoint were proposed and the team is converging on one.
ECC core update (Zallet alpha and more)
Electric Coin Company · Kris, Str4d
- The Zallet alpha was released.
- Documentation is at zcash.github.io/wallet, and a Docker Hub image and a Debian package are provided.
- Str4d urged feedback, noting that as an alpha, changes may require recreating wallets from scratch and there will be many edge cases.
- Some zcashd RPCs will not be supported because better alternatives exist.
- The differences are listed on the documentation site, and people were asked to say so if there is a method they truly need.
- Cross-chain payments through NEAR became possible with Zashi's cross pay, and the reverse swap, bringing any coin into Zashi, is nearing completion.
- Kris tried it themselves, scanning a QR code in MetaMask to swap ETH for ZEC.
- The Rust implementation of the Zcash script interpreter has progressed considerably, and two PRs are to be merged for the last feature needed for key generation for NU 6.1 mainnet.
Zaino update
Zingo Labs · Za
- Get transaction status and get snapshot methods are being worked on to support the Zallet release and are awaiting review.
- In line with ZF guidelines, Zaino's own deserialization and the local cache tied to it are being retired in favor of the get snapshot API implemented by Hazel.
- Dependency problems were sorted out and the NU 6.1 upgrade finished; all work is grouped in a GitHub project aiming to finish next Friday, and it is on track.
ZSA update
Qedit · Pablo
- The SIGHASH versioning implementation was shown to ECC and feedback was received.
- Hashing per action group is needed for future swaps, so this is preparation, and it will also apply to Sapling and transparent as the ZIP editors decide.
- For the Orchard ZSA review, the team recommended freezing the related ZIPs (except bug fixes) and pausing Orchard changes unrelated to ZSA during the review period.
- Qedit is waiting for ECC to start its review.
- They discussed with Str4d how far to catch up the upstream librustzcash PRs in order to put the NSM field into the v6 transaction format.
- A wallet subgroup started by Kris meets every two weeks to discuss ZSA wallet integration and fee changes, including reflecting the issue bundle.
- Qedit's Zebra fork is catching up with upstream changes; the remaining core tasks are state management and the consensus rules that depend on it.
- For the health endpoint, a crate was replaced by a fork upstream, so it will be resubmitted with the new version.
Network Sustainability Mechanism (NSM) update
Shielded Labs · Mariusz, Jason
- zcash-test-vectors PR 101 has addressed all comments and is waiting to be merged.
- The ZIP 233 Zebra PR was rebased onto the latest librustzcash.
- The all-features CI test fails because it turns on v6 features without the NU 7 unstable flag.
- Kris and Str4d explained an approach of separating CI for the unstable flag and not blocking merges when it fails.
- Alfredo will open an issue in Zebra.
- Jason asked when work on ZIP 234 and 235 would start.
- Kris replied that nothing remains on the librustzcash side apart from Marek's coinbase PR.
- Nate proposed a cross-organization roadmap meeting to address the overlap of transaction types in Zebra and librustzcash.
- Zebra plans to move to the librustzcash types but has put that off until the Qedit code is merged.
Crosslink update (Trailing Finality Layer)
Shielded Labs · Nate
- Milestone 4 was split into smaller pieces of 4 to 6 weeks each.
- The first piece is a change moving the special message for BFT roster registration into an ordinary Zcash transaction, because of the design invariant that all PoS state changes happen through ordinary transactions.
- Fixes for configuration file confusion and improvements to CI and continuous deployment should make the next workshop run more smoothly.
- The next workshop is targeted for early-to-mid October and will not use Discord.
- The next milestone is minimal staking that ties roster state to testnet ZEC, and later in 4c, restriction rules such as time and amount quantization and lockup periods will be added.
- Design adjustments are being considered based on feedback on the blog post.
- Pablo said the problem is that the protocol is implemented redundantly in Zebra, Orchard and librustzcash, and that ZF also has plans to unify them.
- They agreed to postpone the unification in order to prioritize ZSA.
Open discussion: Crosslink tokenomics
Shielded Labs · Jason, Pablo, Zooko, Str4d, Nate, Mark
- Jason explained the current design.
- Staking takes place inside the Orchard pool and is delegated to a Finalizer, and the total amount staked is public.
- Amounts are quantized in exponential units such as 10, 100 and 1000, and timing at 10-day intervals, and release carries a 30-day unbonding period.
- The 30-day unbonding serves a security purpose, giving time to detect malicious behavior, and a privacy purpose, keeping some ZEC liquid in Orchard.
- However, investor feedback revealed a liquidity problem, so they said they would iterate on it as an initial design.
- Zooko shared historical examples, 30 days for the hard fork at the DAO hack, 8 days for the Steem soft-fork freeze, and 14 days for a hard-fork split, along with Coinbase Prime's comparison table of staked coins.
- Str4d said the purpose of staking is network security, not yield, and urged not to lean too heavily on the opinions of wealthy investors.
- They suggested that if shorter periods are wanted, a privacy cost or different yields by period could be considered.
- Zooko laid out the trade-offs among privacy, security, long-termism, usability and liquidity, and release speed, and Nate described the stall mode conceived by Daira Emma (if BFT stalls for long, PoW is restricted to coinbase only).
- They asked for opinions on the approach of shipping quickly and improving afterward.
This summary is based on the original meeting notes; check them for exact details.