← All calls
ARBORIST#96

NU7 config flag convention discussed

The account metadata key ZIP 325 and the config flag approach for NU7 were discussed.

Agenda summary 15

  1. Housekeeping: calendar file and ecosystem partner mailing list

    Zcash Foundation · Dodger

    • There is no Arborist call on March 6, the week of ZconVI.
    • A new calendar file with the correct schedule can be downloaded from zcasharborist.org, but it is a simple file that does not reflect canceled or skipped calls.
    • Opinions were asked on whether to create a public Google calendar to which people can subscribe for the Arborist call and the community call.
    • A Google Groups mailing list was created so ecosystem partners can receive news of software changes and deprecations.
    • The group is moderated so only approved mail is posted, and people can subscribe by email without a Google account.
  2. Zebra update: results of work in progress since the last call

    Zcash Foundation · Alfredo, Daira Emma

    • The Dockerfile and entrypoint refactoring was finished, and the internal finalized-state functions needed for the invalidateblock and reconsiderblock RPCs were completed by Arya and an external contributor.
    • The feature that tracks peers sending bad information with a scoring system and bans them was finished, and work adding inbound connections to the getpeerinfo RPC is done up to the pre-merge stage.
    • Replacing Zcash script is being done by Conrado, alongside their FROST work, and replacing sinsemilla by Natalie.
    • Daira Emma said that if the banning mechanism is not documented it could be abused to drive off legitimate nodes, so documentation is needed for analysis.
    • Alfredo will write the documentation for the score-based banning.
  3. Zebra update: recent RPC changes and work in progress

    Zcash Foundation · Alfredo

    • getblockchaininfo was extended to return more data, and at Zaino's request a new network kind was applied to regtest transparent addresses.
    • A block commitment field was added to the getblock output, and for compatibility with zcashd, sendrawtransaction accepts an extra parameter but does nothing with it.
    • Verbose support was added to getrawmempool, and the getinfo RPC was extended to return more information.
    • Negative height support is being added to some RPCs, and a fix aligning the getblocktemplate coinbase output order with zcashd and the implementation of invalidateblock and reconsiderblock are in progress.
    • They added that high-quality external contributors are sending a lot of code, which is good news for the ecosystem.
  4. ECC update: librustzcash crate release and ZIP 325

    ECC · Str4d, Daira Emma, Kris

    • The team concentrated on organizing and releasing the changes of the past few months, and finished the lower-stack changes so Keystone can ride on the public versions without pinned dependencies.
    • The transparent change recovery work changes how wallets sync transparent funds substantially, so it was left out of this release and will ship as a separate breaking release.
    • After the release it will be brought into the mobile SDKs so Zashi, Edge, Unstoppable and others can test it, and Zallet will also be able to add transparent-related RPC keys.
    • ZIP 325 defines a common account metadata key tree that encrypts the off-chain metadata a wallet creates so it can be recovered from the seed phrase backup alone.
    • When a hardware wallet exports a UFVK it can also export this key, so it can be used without separate derivation, and it covers things such as address books, transaction annotations, exchange rates and tax-related records.
    • Kris reported considerable progress on the v6 transaction format ZIP among the NU7 ZIPs.
  5. ECC update: submitting transactions over Tor

    ECC · Str4d, Daira Emma

    • The mobile SDK now fetches and submits transactions over Tor, and once the Swift bindings are done it goes out in the next release.
    • Applying it to transaction submission first cuts the connection by which lightwalletd directly observes who submitted a transaction.
    • Looking up the same information right after submission could create a timing correlation, so wallets must design their request patterns carefully.
    • Daira Emma said Tor is not designed to stop global surveillance but is quite effective against compromised infrastructure.
    • Str4d said that as a stronger step, mixnets such as NYM are also of interest.
  6. FROST audit and demo

    Conrado, Kris, Dodger

    • Least Authority sent its audit report on the FROST client and the frostd tool; there were no serious problems, and the minor issues will be handled this week or early next week.
    • The FROST server was demonstrated at the community call the day before; the demo had errors, so it will be re-recorded and posted.
    • Small tasks such as PCZT integration remain, and the next step is for wallets and software to try integrating FROST.
    • Kris proposed offering the reference implementation as a zcash devtool command, and Conrado said they would schedule it.
    • Dodger said the current priorities are zcashd retirement and merging ZSA into Zebra.
  7. Crosslink hiring and roadmap discussion

    Shielded Labs · Nate, Daira Emma, Dodger

    • Shielded Labs has hired a few people and one is joining soon; next week the team meets in person to sort out the Crosslink implementation roadmap and code design.
    • The first milestone is a demo anyone can run, containing part of the Crosslink functionality in a Zebra fork, and the team wants to complete it by the end of March.
    • It will not replicate the Zebra CI as is but build a new automated CI for the Crosslink prototype, and is considering getting full CI feedback through draft PRs when needed.
    • The Zebra team held a community call that day introducing its CI setup.
    • Daira Emma said the Crosslink security analysis is still incomplete and that they want to finish the finite-event Python model, and Nate answered that it is needed after the first milestone.
  8. NSM update

    Shielded Labs, Eiger · Jason McGee, Str4d, Kris

    • ZIP 233 removed the feature flag and added NU7 to the v6 transaction format, and ZIPs 234 and 235 were implemented with two separate feature flags.
    • The feature flag in librustzcash was also removed and NU7 put into the v6 format, and the Zcash test vectors were updated for v6.
    • All PRs except the librustzcash PR were rebased onto the latest upstream, and because Zebra does not use the latest librustzcash, the librustzcash PR kept its December 2024 code.
    • Str4d said rebasing right after the upcoming crate release would be smoothest.
    • The team meets Eiger on Tuesday to discuss the work needed before the upstream merge.
  9. ZSA off-chain metadata: asset desc design change

    ECC · Daira Emma, Str4d, Kris, Nate

    • The ZIP editors proposed encoding the asset description string, asset desc, on chain only as a hash.
    • If wallets display asset desc as is, it can mislead, and users need to know metadata such as the issuer's reputation, value, security issues and whether a wrapping claim is genuine.
    • Such information requires an off-chain protocol that relies on reputation, and with a hash it can still be verified once the original description is received.
    • Nate introduced an approach in which wallets subscribe to curated lists, like Ethereum MetaMask's token list.
    • Str4d said that even with a hash, disclosure of the original cannot be forced, the same as with the original string approach, and that the memo bundle can be put in the first issuance transaction to publish it.
    • Kris said that showing an on-chain description to users is itself an anti-pattern and that it should be obtained only through an off-chain protocol the user has explicitly chosen.
  10. Public announcement: ZconVI schedule

    Zcash Foundation · Dodger, Daira Emma

    • ZconVI will be held fully online from March 4 to 7, and information is at zfnd.org.
    • Daira Emma introduced their talk on quantum-resistant Zcash.
  11. Open discussion: livestreaming the Arborist call on X

    Jason McGee, Daira Emma, Dodger, Str4d, Conrado

    • Jason McGee proposed livestreaming the Arborist call on the Zcash X account and elsewhere. YouTube videos struggle to pass 150 views, and the aim is to publicize open development and increase participation.
    • Daira Emma strongly objected, saying X is a platform that excludes transgender people and that risk for participants could increase; they said they would take part as a protest, but could skip if the risk grows.
    • Dodger said their position is that Zcash should be politically neutral and that they would decide pragmatically, as with running Zoom, and asked anyone who wants to skip to tell Dodger privately.
    • Str4d said they should first weigh the real benefit of livestreaming, why X, and the moderation burden.
    • The streaming would leave the Zoom session as it is and only rebroadcast the video to another platform.
    • Conrado said the Twitter Space on the Dev Fund last August had 305 listeners, and expected the effect to be small.
  12. Open discussion: ZIP 231 encrypted memo bundle

    ECC, Zcash Foundation · Alfredo, Kris, Str4d, Daira Emma

    • Alfredo said that reading ZIP 231 they found it hard to see how the requirement of being able to tell whether a memo exists without full decryption is met.
    • Str4d explained that if the memo key is all zeros anyone can decrypt it, and all ones is used to indicate there is no memo.
    • ZIP 231 is not yet implemented and remains a proposal until a reference implementation exists; Kris worked on an implementation and then stopped for other work.
    • The consensus part was reviewed in the ZIP editors' discussion late last year, and the sighash is being defined by the ZIP editors together with other ZIPs.
    • Daira Emma said there is an interaction with ZIP 302, the legacy memo format ZIP, which may need to be updated or withdrawn.
    • Alfredo will leave the ambiguous points as comments on the ZIP.
  13. Open discussion: ways to limit asset desc, and FROST and CT logs

    ECC · Conrado, Kris, Str4d, Daira Emma

    • Conrado proposed restricting asset desc to allowed characters, like usernames, since each wallet will display it arbitrarily.
    • Kris explained that an on-chain description can be abused to imitate a famous asset and deceive with a different issuer key, or when an issuer key is stolen.
    • Kris said arbitrary strings can also be used for offensive content or exposing personal information and stay on chain permanently, and told people to read the motivation of PR 975.
    • Str4d answered that FROST is indistinguishable from a single signature so it has no advantage for outside verification, and that the blockchain itself serves the role of a CT log, so a CT log is not needed.
  14. Open discussion: proposal for an ecosystem-wide config flag

    ECC · Kris, Daira Emma, Str4d

    • The existing zcash_unstable = zfuture flag has the limitation that multiple of the same identifier cannot be enabled at once, so an ecosystem-wide zcash_unstable = NU7 config was proposed.
    • Within each crate, features such as the memo bundle and ZSA are introduced under this config flag as ordinary Rust feature flags, so that turning them all on gives the NU7 features.
    • Str4d said feature flags are additive, so a config flag is necessary in order not to affect consensus, and that a second config flag convention should be left open for non-additive changes.
    • Daira Emma said this config flag should indicate that it is not the standard mainnet consensus mode, and that where a node needs both the new and old circuits, duplicate code is unavoidable.
    • Mainnet and testnet are global consensus networks, so code goes in without flags, and changes for private testnets are managed behind flags or in parallel repositories.
  15. Open discussion: how config flags apply, and agreement

    Zcash Foundation, ECC · Alfredo, Str4d, Daira Emma, Dodger, Arya

    • When Alfredo asked how the config flag behaves when pulling libraries from Zebra, Str4d answered that it is specified with --cfg in RUSTFLAGS and is completely separated by a separate build.
    • RUSTFLAGS handling improved in Rust 1.85, making caching more stable, and in CI it is good to check a build with this flag on first at warning level.
    • Dodger suggested writing the proposal up as a document so newcomers and the Zebra team can review it easily.
    • The NSM changes have already moved to the config flag, and some can be changed back to feature flags depending on context, but the top-level config flag stays.
    • Str4d said that for ZSA, the note encryption change was merged without a flag, but the Halo 2 and Orchard changes will be put behind the config flag in the first integration.
    • Arya said this plan will help ZSA integration, and the next regular call is on March 20 at a late time slot.

This summary is based on the original meeting notes; check them for exact details.