
When Allocations Become Provisional: Zcash’s Treasury Reallocation Precedent Changing future funding and redirecting funds already received are different exercises of governance. Zcash’s latest development-fund proposal raises a substantive precedent question because it attempts both. The proposal from Sean Bowe, Zooko Wilcox, and Jason McGee would end Zcash Community Grants’ 8% funding stream at a network upgrade after NU7. For the remainder of the stream’s term, that allocation would flow into a new Future Dev and Legal Defense Fund Lockbox, inaccessible until a later ZIP establishes disbursement rules. Separately, it would require a 50,000 ZEC contribution from ZCG’s existing treasury to the Network Sustainability Mechanism. The first change concerns future issuance. The second reopens the disposition of assets already received under previously approved arrangements. That distinction deserves to be central to the debate. Restricted funds, established expectations ZCG’s treasury is not an unrestricted pool available for any purpose that later attracts community support. ZIP 1015 requires the Financial Privacy Foundation, which receives and administers ZCG funds, to recognize the allocation as a restricted-fund donation. It specifies permitted uses: grants to qualifying external parties or autonomous entities operating under FPF, along with expenses reasonably related to administering the grants program. These restrictions distinguish the treasury from an ordinary holder’s assets—but also from a general-purpose community reserve. The new draft proposes amending ZIP 1015 to permit the NSM contribution. Whether that amendment can authorize the use of previously received restricted funds has already been disputed publicly. In the forum discussion, Zcash developer Jack Grigg questioned whether changing the ZIP could alter restrictions attached to funds already received. Bowe responded that FPF had reviewed the proposal and concluded that the transaction was possible and legal. Those are competing positions in a public discussion, rather than a published legal determination resolving the issue. Even if the contribution is legally permissible, the governance question remains: What expectations should attach to an allocation once it has been received? A donation with a governance mandate Under the draft, the ZCG committee would instruct FPF to transfer 50,000 ZEC within 30 days of the proposal’s acceptance. The funds would go to an unspendable address. Upon activation, the protocol would credit that value to the NSM, allowing it to return to circulation through future block subsidies. The draft’s treasury snapshot places the contribution at roughly 55% of ZCG’s ZEC holdings. This would not reverse the transactions that originally funded ZCG. Nor would the proposal itself seize the treasury’s private keys. It relies on the responsible parties executing a new transfer. But the absence of a cryptographic seizure does not eliminate the precedent concern. A transfer described as a donation can still be the subject of substantial governance pressure. The relevant question is whether the custodian is exercising discretion within an established mandate or being pressed to surrender assets because influential participants now prefer another allocation. The distinction matters for institutional credibility. If approved allocations can be reopened whenever their market value becomes politically uncomfortable, recipients must treat those allocations as contingent on continued approval. Finality has more than one meaning The strongest objection should be stated precisely. Blockchain transaction finality does not guarantee that an organization will never spend, donate, or otherwise dispose of assets it has received. A subsequent authorized transfer does not invalidate an earlier one. The concern here is the durability of governance commitments.


