Future of Zcash dev funding — high signal, low noise

[sonya]

Final edit: This forum thread is now deprecated! Please refer to the ZIP process website and the Zcash Foundation’s governance page for future information and updates. Forum discussion will continue in the protocol subcategory.

To see past edits of this post:

---

This thread will remain locked. It’s intended as a reference, not a discussion venue. It will be updated whenever we (the Zcash community) move the ball forward.

For details and discussion, consult the megathread.

Note: the merged ZIPs include some editorial changes. They supercede both the original pull requests, and the draft proposals on the forum threads. If you are a ZIP author and see a change that doesn’t reflect your intent, please contact @daira.

Draft ZIPs

• Keep the block distribution as initally defined. 90% to miners

  • Merged as ZIP 1001
  • Original pull request on GitHub
  • Advocate: @mistfpga

• A genuine opt-in protocol level, development donation option

  • Merged as ZIP 1002
  • Original pull request on GitHub
  • Advocate: @mistfpga

• 20% split between the ECC and the Foundation, and a Voting System Mandate

  • Merged as ZIP 1003
  • Original pull request on GitHub
  • Advocate: @aristarchus

• Miner Directed Dev Fund (was: 20% to any combination of ECC, Zfnd, Parity, or “burn”)

  • Merged as ZIP 1004
  • Original pull request on GitHub
  • Advocate: @amiller

• ZIP proposal: ZCFS (Zcash Community Funding System)

  • Merged as ZIP 1005
  • Original pull request on GitHub
  • Advocate: @anon16456014

• Blocktown Development Fund Proposal: 10% to a 2-of-3 multisig with community involved Third Entity

  • Merged as ZIP 1006
  • Original pull request on GitHub
  • Advocate: @Blocktown

• Dev Fund Supplemental Proposal: enforce devfund commitments with legal charter

  • Merged as ZIP 1007
  • Original pull request on GitHub
  • Advocate: @lex-node

• Kek’s proposal: fund ECC for 2 more years

  • Merged as ZIP 1008
  • Original pull request on GitHub
  • Advocate: @kek

• Five-Entity Strategic Council

  • Merged as ZIP 1009
  • Original pull request on GitHub
  • Advocate: @avichal

• A Grand Compromise/Synthesis ZIP Proposal

  • Merged as ZIP 1010
  • Original pull request on GitHub
  • Advocate: @acityinohio

• Decentralizing the Dev Fee

  • Merged as ZIP 1011
  • Original pull request on GitHub
  • Advocate: @mhluongo

• Dev Fund to ECC + Zfnd + Major Grants

  • Merged as ZIP 1012
  • Original pull request on GitHub
  • Advocate: @tromer

• Keep It Simple, Zcashers: 10% to ECC, 10% to ZF

  • Merged as ZIP 1013
  • Original pull request on GitHub
  • Advocate: @gojomo

ZIP Process

ZIP = Zcash Improvement Proposal

Writing and submitting a ZIP is how you formally suggest changes to the Zcash protocol, or a decision about Zcash’s future that you want to be recognized and recorded.

@sonya

After forum discussion, the next step is creating and submitting a formal Zcash Improvement Proposal. The ZIP process is defined in ZIP 0.

• GitHub repo
• issues
• pull requests

Help

• Guide to writing your first ZIP
• ZIP-writing suggestions and examples by @mistfpga
• Proposal authors, please read: Help making ZIPs by @nathan-at-least

NU4 deadlines:

Event	Date
ZIP draft submission deadline	Aug 31, 2019
Feature selection done	October 31, 2019
Testnet beta code release	March 31, 2020
Testnet activation	May 31, 2020
Mainnet activation	October 2020

Proposals for NU4 must be submitted as draft ZIPs by August 31.

The active ZIP editors are @daira, representing the Electric Coin Company, and George Tankersley, representing the Zcash Foundation.