[TPP Draft] Revocation of Remaining TPP-18 Capped Minters
Status
Draft Proposal – Request for Community Feedback
This proposal is submitted for discussion before any formal on-chain vote.
I welcome feedback from delegates, Matter Labs, the ZKsync Foundation, and the broader community.
Summary
This proposal requests that the Token Assembly exercise the authority explicitly reserved under TPP-18 to revoke all remaining monthly capped minters that have not yet been distributed.
This is not a proposal to reverse past distributions, nor is it intended to oppose continued development of ZKsync or Matter Labs.
Rather, it asks whether the assumptions under which TPP-18 was approved continue to justify automatic monthly treasury allocations.
If governance concludes that additional funding remains appropriate, Matter Labs should always be free to submit a new proposal with updated justification, milestones, and accountability.
Background
TPP-18 explicitly states:
“The Token Assembly retains the right to revoke any future monthly minter at any time.”
That safeguard was included for a reason.
Governance recognized that a twelve-month funding commitment should not become irreversible if circumstances changed.
This proposal asks the Token Assembly to exercise that authority because, in my view, the circumstances surrounding TPP-18 have materially changed since it was approved.
Why Reconsider TPP-18?
1.The roadmap and assumptions have materially changed
When TPP-18 was presented, one of its central justifications was that institutional adoption would ultimately contribute to protocol activity and governance-controlled fee mechanisms.
Since then, Matter Labs has explained that previously anticipated fee mechanisms remain deferred and subject to future governance decisions, without a committed timeline or defined activation criteria.
As a result, the connection between institutional growth and direct token-holder value accrual remains uncertain.
Institutional deployments also have different technical and commercial requirements than originally envisioned.
Whether those engineering decisions were correct is not the question before governance.
The governance question is simpler:
Should an automatic twelve-month treasury allocation continue unchanged after the strategic assumptions supporting it have evolved?
I believe governance should reassess that commitment.
2. Commercial success changes the funding discussion
Matter Labs has publicly explained that its enterprise business generates commercial revenue through managed services, enterprise deployments, licensing, and Prividium.
A successful commercial business is positive for the ecosystem.
However, it is reasonable for governance to ask whether the development of commercially monetized products should continue to rely on recurring treasury issuance to the same extent once those products generate independent revenue.
As commercial activity matures, funding those efforts increasingly from commercial revenues rather than continued token issuance may represent a healthier long-term alignment between the company and token holders.
This proposal is not an argument against Matter Labs earning revenue.
It is an argument that treasury funding should evolve alongside the project’s commercial maturity.
3.Governance should reassess recurring dilution
Each remaining monthly capped minter increases the circulating supply of ZK.
Governance accepted that trade-off when approving TPP-18.
However, recurring dilution should remain justified by current circumstances—not only by assumptions made months earlier.
The purpose of the revocation mechanism was to allow governance to make exactly that reassessment.
4. Accountability is stronger than automatic funding
If Matter Labs requires additional funding to continue developing ZKsync, governance can evaluate new proposals based on the current roadmap rather than past expectations.
Those proposals could include:
Updated budgets.
Clearly defined milestones.
Transparent reporting.
Measurable deliverables.
An updated explanation of how requested funding benefits both the protocol and long-term token holders.
This proposal does not seek to eliminate future funding.
It seeks to ensure future funding reflects current realities and receives fresh governance approval.
Why Act Now?
Every month another capped minter becomes available under TPP-18.
If governance believes the original assumptions should be revisited, delaying that discussion simply allows additional allocations to proceed before the community has exercised the authority that TPP-18 intentionally reserved.
The revocation mechanism exists so governance can respond when circumstances evolve.
This proposal asks the community whether now is the appropriate time to do so.
Proposed Action
If supported by the community, a formal governance proposal would:
-
Revoke all remaining TPP-18 capped minters that have not yet been activated.
-
Leave previously distributed allocations unchanged.
-
Preserve Matter Labs’ ability to request future funding through new governance proposals.
-
Encourage future funding requests to include updated milestones, reporting, and justification reflecting the current roadmap.
Questions for the Community
I would appreciate feedback on the following:
-
Have the assumptions underlying TPP-18 changed sufficiently to justify exercising the Token Assembly’s revocation authority?
-
If not, what specific milestones or conditions should governance wait for before reconsidering the remaining monthly allocations?
-
Should future protocol funding rely more heavily on milestone-based governance approvals rather than recurring allocations?
-
Are there additional accountability mechanisms that should accompany future funding proposals?
Conclusion
TPP-18 deliberately preserved the Token Assembly’s authority to revoke future monthly minters.
That safeguard exists because governance should retain the ability to reassess long-term funding commitments when circumstances materially change.
This proposal asks the community whether that moment has arrived.
I look forward to constructive feedback from delegates, Matter Labs, the Foundation, and the broader ZKsync community.