← All calls
ARBORIST#37

ZIP 317 fee parameters revealed

The ZIP 317 logical action formula and the 5000 zat per action fee parameters were introduced in detail for the first time.

Agenda summary 4

  1. Zebra update - release candidate and audit preparation

    Zcash Foundation · Deirdre

    • The team is preparing to tag a release candidate, and once tagged it will be handed to the security audit and the Zcash spec conformance audit. There were many dependency updates and CI adjustments.
    • Work in progress remains, such as getblocktemplate support and RPC improvements for the lightwalletd front end. The team is fixing a problem where, because of large mainnet blocks, RPC froze for several minutes or more while blocks were applied to state.
    • The team is working on state changes that write unconfirmed blocks on a separate thread and parallelize it, aiming for zebrad to stay responsive even when many queries pile up.
  2. Zcashd update - 5.3.0 and Halo 2 recursion

    Electric Coin Company · Steven

    • Work on mobile SDK fast sync is nearly done and will come out over at least two SDK updates. Sync is expected to be faster even than before the mid-June load.
    • The focus of 5.3.0 is optimizing concurrent memory usage. The team improved areas exposed as increased parallelism made it use more resources, and said OOM will go away in the recommended memory configuration.
    • Halo 2 recursion is proceeding in parallel on three tracks: the front-end API, back-end split accumulation, and circuit changes for full-width scalar multiplication.
    • For ZIP 317, the team thoroughly analyzed past fees and transaction profiles and began implementation. It is adding an abstraction layer so fees can be changed easily later when moving to an EIP 1559-style mechanism.
  3. ZIP 317 parameter selection and analysis

    Electric Coin Company · Steven, Kris

    • Steven thanked Adi for writing the ZIP, Kris and Daira for building the initial model, Nate for researching the mechanism, and Greg for building the analysis scripts.
    • Fee calculation uses logical actions. It is the sum of the larger of transparent inputs and outputs, twice the Sprout joinsplits, the larger of Sapling inputs and outputs, and the Orchard actions, and a 2-in 2-out is 2.
    • The proposed parameters are a marginal fee of 5000 zat and 2 grace actions. The fee for a 2-logical-action transaction is 10,000 zat, which amounts to returning to the standard fee before ZIP 313.
    • As design motivation, Kris cited making fees proportional to the load placed on the chain and not disadvantaging any of the Transparent, Sapling or Orchard protocols.
    • Splitting a transaction gives the same total, so the fee cannot be circumvented. Sending a 2-logical-action transaction once per block is 1,152 transactions a day for $6.91, up from the previous $0.69. A ZEC price of $60 was assumed.
    • In Greg's analysis, sandblasting transactions with more than 300 outputs averaged 704 per day, with an average of 1,102 logical actions. Doing this every day would cost about $69,000 a month, a large rise from the previous $12 a month.
  4. Fee roadmap and consultation with wallet developers

    Electric Coin Company · Nate, Steven, Daira

    • Nate explained the background of the fee change: performance improvements alone will not reduce overuse, and fees are the only solution.
    • There could be an impact on mining pools, donation recipients and small businesses with many inputs and outputs. They estimated that even Dev Fund organizations receiving a deposit every block would see costs rise by about $200 a month.
    • Since hardcoded parameters are a limitation, they said they want to move later to a method adjusted dynamically with demand, such as an EIP 1559-style or Bitcoin-style fee market.
    • They said they would call in shielded wallet developers that day to explain and hear concerns. The plan is to have wallets use the new fees first before consensus enforcement, and track rollout progress with Greg's analysis.
    • Daira said that since a ZIP, unlike an RFC, is easily amended, PRs or drafts can be shared with wallet developers even before it is finalized, and that this ZIP could be published almost immediately.
    • A ZIP starts as a PR, is merged as a draft, and then becomes active or final, and Daira said this ZIP should become active once it is implemented in more than one wallet.

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