NSM "burn" terminology dispute
A terminology dispute arose over what NSM's "burn" does to the supply cap.
Agenda summary 11
Zebra update
Zcash Foundation · Marek
- The JSON RPC server was migrated to a new framework in place of the old framework, which is no longer developed.
- A verification optimization was implemented so that a transaction already in the mempool is not verified again when it appears in a new block.
- The getblock and getrawtransaction RPCs were brought closer to zcashd's output, and several bugs related to getblock transactions were also fixed.
ECC update: zcashd 6.1.0 / 6.2.0
ECC · Str4d, Pili
- zcashd 6.1.0 was released last week, and since 6.0.0 loses support with less than two weeks left, ECC-built nodes must be updated before then.
- 6.1.0 is a maintenance release, and the flag that marks RPC methods as deprecated goes into the next release, 6.2.0, for lack of time.
- The plan is to implement 6.2.0 as quickly as possible and release it soon.
ECC update: transparent address scanning and zcash devtool
ECC · Str4d
- After the Keystone-related work landed in Zashi just before Christmas, a few follow-up bug fixes came in.
- Kris generalized transparent address gap limit scanning in the Rust crates, so that importing a transparent-only seed phrase can still find existing transparent funds and shield them.
- The missing funds of users who imported a Ledger-based seed phrase into Keystone are due to it currently looking only at the first transparent address.
- The team is still tracking down a rare edge-case bug in the note commitment tree, and if it cannot be found it will write code to forcibly work around it.
- The published zec-sqlite-cli was renamed zcash devtool and made into a multitool for wallet developers that absorbs the old zcash inspect tool.
- PCZT-related features are also in this tool, and the new wallet mentioned late last year saw no change over the holidays.
zcashd retirement: outreach and a Zaino regtest error
Zcash Foundation, Zingo Labs · Pacu, Marek, Pili
- Pacu is contacting API providers such as CoinMarketCap and CoinGecko but responses are slow, so they asked anyone with a direct contact to say so.
- Usage is being collected through a Google survey instead of email, and there have been a few responses but nothing notable.
- At the Zingo team's request Pacu looked at the Zaino regtest error, and said the problem is mainly on the test tooling side and there is no evidence of a problem in Zebra regtest.
- Marek said they merged a PR allowing, in regtest, the consensus rule that forbids transparent outputs in transactions spending coinbase outputs.
- zcashd may also break the rule banning spending of coinbase within 100 blocks in regtest, so allowing it for regtest only is under consideration.
FROST DKG and audit plan
Conrado, Pili
- Running DKG through the FROST server is complete, leaving only use of the broadcast channel required for security.
- An audit is to be run soon, the start date is not yet set, and code cleanup and documentation improvements will come before it.
- Pili said that once the audit is done they will look for developers to try integrating and help them.
Trailing Finality / Crosslink update
Shielded Labs · Zooko, Nate, Jason McGee
- Zooko had just returned from vacation and said they had nothing to report.
- Nate tested Zebra locally and tried to replicate the Zebra team's CI, but is considering substituting a simple setup that only runs cargo test in the early prototype stage.
- Jason McGee said hiring has progressed, with two offers currently out, and that they hope two engineers will start by February 1.
NSM: ZIP 233 burn and ZIP 234 issuance smoothing
Shielded Labs · Jason McGee, Paul Dann, Conrado
- Following Kris's forum comment, a revision was proposed to state explicitly in ZIP 233 that burning permanently reduces total supply below the 21 million cap.
- ZIP 234 is a mechanism that systematically issues ZEC into future block rewards, and there is no direct relationship between burned coins and newly issued coins.
- Without a mechanism like ZIP 234, burning would permanently reduce total supply, and this proposed revision is awaiting the ZIP editors' answer.
- On the forum, Jason McGee responded to Conrado's alternative that keeps halvings and asked for opinions on the importance of ZIP 234 and halvings.
- Paul Dann explained that the current implementation does not track deposits separately and computes issuance only from the money reserve, max money minus chain value.
- Conrado said they were confused about what must be tracked when burning from the transparent pool, and Paul Dann answered that a burn is equivalent to an input with no output.
NSM terminology dispute: burn
Dodger, Nate, Jason McGee, Str4d, Zooko, Paul Dann
- Dodger repeatedly asked to use a different term, because burn means permanent removal of coins and could make people think the 21 million cap shrinks.
- Nate said it is just a common term also used in Ethereum's EIP 1559, that they are not especially attached to it, and that a miner not claiming a reward is also an implicit burn.
- Dodger countered that in Ethereum burning and issuance are separate, whereas in NSM the burned amount is directly tied to later issuance.
- Str4d said that rather than the term, the ZIP should make clear whether this mechanism affects circulating supply or maximum supply.
- Zooko said that only if ZIP 235 goes into an actual network upgrade can its intent be called Zcash's intent.
- When Jason McGee relayed that Kris's suggestion was retraction, Dodger said it was a good term.
Zcash Shielded Assets (ZSA) update
QEDIT · Vivek
- Open issues were resolved and the description of the consensus rules was rewritten to match the specification PDF, so the upstream PR is ready for the next ZIP editor review.
- Computation of the row fields for action groups, reference notes and issuance notes was added, and the implementation was reflected in Orchard, librustzcash and the test vectors.
- In Zebra, duplicate code with Orchard is being reduced and asset state management is being worked on, and a demo was shown at the community call before the holidays.
- The first testnet is nearly ready and is being finished so people can easily run it themselves with GitHub Actions.
- The Least Authority audit report is broadly positive, and the recommendations will be settled after discussion with ECC.
- The asset swap ZIP must be revised to match the ZSA ZIP changes, and for user control and trade acceptance a draft ZIP was prepared as an internal PR and a grant was also proposed to ZCG.
NU7 discussion
Jason McGee, Dodger, Pili
- The plan to include an NU7 survey in the ZCG vote was pushed to mid-to-late January, and the question wording has been coordinated transparently.
- Jason McGee argued that the current wording makes clear that the burn is not permanent and is reissued as future rewards.
- Dodger told Jason McGee to think about alternative terms, and there is no update yet on the timing of the survey.
- Pili said that if everything cannot go into NU7 or it exceeds the complexity budget, priorities can be set after seeing the survey results.
Public announcements: ZIP editors meeting and the ZconVI call for talks
Str4d, Pili, Nate
- The ZIP editors meeting is due to resume next week for the first time this year, though the schedule may be adjusted because it overlaps with the ZCon summit.
- The next tasks are reviewing non-semantic changes to candidate ZIPs, reviewing the semantic changes related to action groups in the ZSA ZIPs, and defining the v6 transaction format and signature hash.
- The deadline for ZconVI talk submissions is this Sunday.
- Nate posted a quick poll on X prompted by the terminology discussion.
This summary is based on the original meeting notes; check them for exact details.