Hello everyone! This will be the thread for the next standing Proposal Review call that will take place on Wednesday, July 22nd.
Proposal authors of active or developing proposals can request time to present & discuss their proposals with the community. These calls are also a time to shared and discuss ecosystem updates.
I will update this forum post the day of the call with a proposed agenda based on results from the forum. I will use that agenda as a guide to help facilitate the call.
Looking forward to seeing all of your shining faces after a break from calls!
Your Gov Experience gal- Shelby
TENTATIVE AGENDA
Proposal Updates
[ZIP-16] ZKsync v31 Upgrade - Voting live, ends Thu July 23. This protocol upgrade enables Priority Mode for ZKsync OS chains settling directly on L1, protocol-contract compatibility improvements for ZKsync OS, and a direct upgrade path for ZKsync Era from protocol version 29 to version 31. Matter Labs team members will join the call to discuss and answer questions about the proposal.
ZKsync Token Program Minter Overview & Deployment Interfaces - After a round of initial feedback and testing, ScopeLift is in the process of making a few updates and improvements to the interfaces, specifically on the minter deployment pages. Please feel free to share feedback on the interfaces / missing resources or instructions as you use them!
I have an active draft proposal, “[TPP Draft] Revocation of Remaining TPP-18 Capped Minters,” and would like to request time on the agenda to present it to delegates and the community.
I also don’t use Google Calendar. Could you let me know how I can register for the call or obtain the meeting link without subscribing through Google Calendar?
Hey @Anwar - Noting that everyone is welcome to join the Proposal Review Calls. However, presentation timings are reserved for either active onchain proposals or formal proposal drafts on the forum.
The post you mention above is labelled and formatted as a RFC with a list of questions and roadmap requests. At the moment, this is not a formal proposal based on the TPP Guidelines & template found on the docs. You are welcome to join the call to ask specific questions to present Delegates you have at this time.
Matter Labs, the Foundation, and the Governance Team are regular attendees, and the v31 proposal currently onchain is part of the agenda.
I’m struggling to reconcile your response with the published process.
The call announcement written by you above states that “proposal authors of active or developing proposals can request time to present & discuss their proposals with the community.” My proposal is explicitly a developing draft intended to gather community feedback before an on-chain submission.
In addition, the TPP Guidelines specifically contemplate forum-stage cancellation proposals before an on-chain proposal is submitted. That is precisely what this proposal is.
You have now introduced a different standard by saying my proposal is not a “formal proposal.” Could you please point me to the specific provision in the published TPP Guidelines that my proposal fails to satisfy?
If there are additional eligibility requirements for presentation slots beyond the published guidelines, they should be clearly documented and applied consistently rather than introduced on a case-by-case basis.
Based on the published announcement and TPP Guidelines, I believe my proposal is eligible for a presentation slot. Unless you can identify a published rule that excludes it, I ask that you reconsider your decision and reserve time for me to present it to delegates.
Hey @Anwar - As I mentioned above, the Proposal Review Call is open to all Delegates so you’ll be able to hear about the v31 proposal and ask questions around scope and roadmap during the call. I’ve added your topic to the agenda for discussion.
Your response still leaves an important point unclear.
The call is tomorrow, so I need confirmation on whether I have been allocated time to present my proposal or whether my topic has only been added for general discussion.
I did not request time to discuss v31. I requested a presentation slot for my developing TPP proposal, as described in the call announcement.
The proposal has a clear objective and is straightforward to present. I do not require significant agenda time, but I do need clarity on whether I should prepare to present it to delegates and what format that presentation will take.
Please confirm the format, timing, and whether I should prepare to present the proposal to delegates.
Check out the video description for timestamps on different discussion topics. Given we have the recording, notes will be kept very brief. Please watch the recording for full context!
Governance & Ecosystem Updates
ZKsync Token Program Minter Overview & Deployment Interfaces - After an initial round of user feedback and testing, ScopeLift is working on implementing changes and improvements to the zkminter interfaces. Please keep this in mind if you are planning to play around with them over the coming 1-2 weeks.
Matter Labs Q2 2026 Deliverables Report: The report outlines key highlights of work completed in Q2, including new developments in enterprise deployments and compliance, a shift to prioritize private interop after receiving clear signals from Prividium clients, expansions on access to the ZK token and protocol performance improvements.
Prividum Now Extends to Hyperledger Besu: Hyperledger Besu underpins approximately 35 percent of enterprise permissioned blockchain deployments globally. With this new support, the path to ZK-proven privacy and direct Ethereum interoperability is now open for all of them.
Onchain: [ZIP-16] V31 Interop Bundles Upgrade - ZIP-16 has met quorum. Voting ends on July 23rd at 19:50 UTC. This protocol upgrade enables Priority Mode for ZKsync OS chains settling directly on L1, protocol-contract compatibility improvements for ZKsync OS, and a direct upgrade path for ZKsync Era from protocol version 29 to version 31. Matter Labs team members will join the call to discuss and answer questions about the proposal.
Steven from Matter Labs joined the call to review the scope of the v31 upgrade and provide context for the changes from the original forum draft. He noted partner feedback heavily influenced the decision to reprioritize private interop for Prividium chains, with public interop implementation being postponed.
Question: What would you like to see from the community involvement on v31 or the protocol upgrades? Chime in on the forum, let us know what you would like to see.
Forum Draft: [TPP Draft] Revocation of Remaining TPP-18 Capped Minters - Aims to revoke TPP-18 capped minters 1 month after program start due to claimed material changes to the roadmap. Argues the reprioritization of private interop over public interop based off of Prividium partner feedback/demand is a material change. There was a discussion on the call with Steven (Matter Labs), where he pointed out private & public interop are both noted in Stream 1 of TPP-18, and that by following partner feedback better helps achieve TPP-18 goal “to execute the 2026 Prividium roadmap and convert the active institutional pipeline into deployed chains and a growing institutional network.” It was also clarified that any deployed protocol fee mechanisms, whether related to private or public interop, are under control of the governance system. Next steps TBD.