The ZIP Process and the Principle of Consent

Recently, several community members have shared draft or proposed ZIPs, which as drafted, would impose implicit obligations on ZF.

The primary purpose of ZIPs is to describe changes to the Zcash protocol (as implemented in network upgrades).

While ZIP 1014 defines certain obligations that apply to ZF, ECC and the Bootstrap Project, it is important to note that each organization entered into those obligations voluntarily, and in the context of receiving a slice of the Dev Fund (e.g. transparency and reporting obligations, the restrictions on how ZF may disburse the Major Grants slice).

It is unreasonable to seek to impose an arbitrary requirement on a person, group or entity through the ZIP process without their consent. Nor is it reasonable to seek to coerce a person, group, or entity to follow a specific course of action by imposing conditions on the receipt of funds that do not reasonably relate to the purpose and intent of the funding.

It is reasonable for potential Dev Fund recipients to decline conditions that they consider to be inappropriate or unreasonable. For example, during the process that led to the adoption of ZIP 1014, ZF indicated that it would not accept funding if it were the sole recipient of funding, and ECC indicated that it would decline its funding slice if the community opted to impose a USD-denominated funding cap or volatility reserve.

As the Zcash community seeks to reach consensus on whether a new ecosystem funding mechanism should replace the Dev Fund, ZF encourages community members to respect the independence of the people, groups and entities involved in the Zcash ecosystem—and to aim for collaboration over coercion.