Matter Labs | Q2 2026 Deliverables Report

Summary

In Q2 2026, we moved from institutional proof points to production-grade Prividium deployments, product-readiness work, and network formation. The quarter was defined by three themes: Prividium entered production with multiple live deployments, institutional demand centered on private interoperability, and ZKsync governance and token participation strengthened the protocol foundation that funds and coordinates the network build.

Highlights included:

  • Prepared the Cari Network production environment for launch as Cari expanded to a bank-governed network with more than 30 institutions representing approximately $10T in combined assets
  • Supported Memento’s Atlas-upgraded mainnet launch, a second production deployment path for Prividium with institutional participation
  • Supported Real Finance as it launched a ZKsync-powered confidential execution layer for institutional RWA workflows
  • Completed the SOC 2 Type I examination for Prividium, with the Type II audit underway
  • Extended Prividium support to Hyperledger Besu, allowing institutions and financial market infrastructure providers to add ZKsync privacy and Ethereum settlement to chains they already operate
  • Completed the technical foundations for private atomic interoperability, including selective disclosure and multi-prover proof-of-concept work
  • Progressed the v31 upgrade while reducing legacy surface area through the ZKsync Lite sunset and deprecation of legacy Gateways
  • Passed and executed the ML Funding TPP, allocating 67M ZK per month for 12 months to fund protocol and network development
  • Expanded $ZK access through Revolut and Bitstamp, reaching more than 19M potential users, and closing Season 1 of the staking pilot with approximately 350M ZK staked and 1.2B ZK in active governance delegation

Together, these milestones move ZKsync from isolated institutional deployments toward connected, private, Ethereum-settled infrastructure for regulated finance.

1. Enterprise Infrastructure & Compliance

Enterprise readiness improved sharply this quarter. Prividium moved further from bespoke deployments toward an institutional platform designed to support bank-grade requirements for privacy, auditability, and compliance.

  • SOC 2 Type I Completed for Prividium: We completed a SOC 2 Type I examination for the Prividium platform, covering security, availability, confidentiality, and privacy. This is a key enterprise-readiness milestone for institutions that require evidence of mature operational controls before moving to production. The SOC 2 Type II audit is now underway.
  • Cari Network Production Environment Preparation: We continued preparing the Cari Network environment for production launch, supporting bank-governed tokenized deposit infrastructure as Cari expanded to more than 30 institutions with approximately $10T in combined assets.
  • Operational Hardening: Work continued on production operations, including alerting, support readiness, audit logs, multi-organization controls, and richer auditability. These capabilities are essential for regulated financial institutions operating shared infrastructure.
  • Hyperledger Besu Support: Prividium now supports Hyperledger Besu chains, expanding the addressable market from greenfield deployments to the installed base of institutional chains. Institutions and FMIs running Besu can now add ZK-proven privacy and Ethereum settlement without replacing infrastructure they already operate.

2. Prividium: From Production Deployments to Network Demand

This quarter reinforced that Prividium is addressing the right institutional problem. Customer demand and public market signals pointed to the same requirements: privacy, interoperability, and Ethereum settlement.

  • Cari Network: We continued preparing Cari’s environment for production launch, with work focused on production readiness, auditability, and hardened support. Cari remains a leading example of a bank-governed tokenized deposit network built on Prividium.
  • Memento Atlas-Upgraded Mainnet: Memento launched its Atlas-upgraded mainnet in Q2, providing a second production deployment path for Prividium beyond Cari. This deployment puts Prividium to work across institutional digital asset workflows.
  • Real Finance Confidential Execution Layer: Real Finance launched a ZKsync-powered confidential execution layer for institutional RWA markets. It targets workflows such as wealth and asset management, balance sheet operations, and tokenized deposits.
  • Institutional Demand: We focused commercial efforts on the institutional use cases where privacy, interoperability, and Ethereum settlement are recurring requirements, including market infrastructure, custody, and tokenized asset workflows.
  • Evaluation and Adoption Work: We continued supporting institutions through evaluation paths including pilots, technical workshops, and design-partnership discussions.

3. Private Atomic Interoperability & Protocol Architecture

Private interoperability was the focus of protocol work this quarter. Institutions evaluating or operating Prividium environments increasingly asked for the same next capability: the ability to connect private environments to one another without exposing sensitive state.

  • Private Atomic Interoperability: We advanced the architecture for private atomic interoperability, designed to support settlement flows such as delivery-versus-payment, tokenized deposits moving between banks, and institutional settlement between parties that cannot reveal their books to one another.
  • Selective Disclosure: Selective disclosure work completed in Q2, creating a foundation for institutions to reveal transactions or data only to the parties that need to see them. This is a critical building block for regulated multi-party workflows where privacy and auditability must coexist.
  • Multi-Prover Support: Multi-prover proof-of-concept work completed, enabling more than one independent proof system to check transactions. This improves resilience and trust minimization for high-value institutional environments.
  • v31 Upgrade Focus: Protocol work concentrated on the v31 upgrade, and we prioritized the technical basis for private network connectivity.
  • Protocol Focus and Legacy Cleanup: We continued reducing legacy surface area through the ZKsync Lite and legacy Gateway sunset, concentrating engineering focus around the Prividium roadmap and private interoperability.

4. Network Economics & Governance

Governance and funding for protocol and network development strengthened over the quarter. ZKsync governance participation deepened, and the protocol received a clear funding mandate for the Prividium roadmap.

  • ML Funding TPP Passed and Executed: In June, token holders passed the 2026 ZKsync Protocol & Network Development Allocation. The proposal allocates 67M ZK per month for 12 months, or approximately 804M ZK in total, to fund protocol and network development.
  • Funding the 2026 Prividium Roadmap: The allocation supports private interoperability, ZK Stack and prover development, and the broader network build.
  • ZKsync Lite Sunset: ZKsync Lite, the first-generation protocol, was sunset in Q2. The transition reduces legacy maintenance burden and concentrates the ecosystem around ZK Stack, Era, and Prividium.
  • Governance Participation: Season 1 of the staking pilot closed with approximately 350M ZK staked, about 200M ZK in new active delegation, and approximately 1.2B ZK in total active governance delegation.
  • Token Transparency: ZK reporting was included in Blockworks’ Token Transparency framework, receiving a 100% “Complete” rating with no disclosure gaps. Reported Q2 metrics included approximately 48% float and more than 360K holders.

5. Token Access, Public Momentum & Institutional Attention

Public attention in Q2 increasingly mapped to the same themes driving institutional demand: regulated finance, token access, and governance participation.

  • Revolut $ZK Access: $ZK became available to more than 15M Revolut users across the UK and EEA.
  • Bitstamp $ZK Access: $ZK became available to more than 4M Bitstamp users across more than 100 countries.
  • Governance and Delegation Scale: The staking pilot and delegation growth showed that governance participation is operating at meaningful scale, with active delegation reaching approximately 1.2B ZK by quarter end.
  • Tier-1 Media and Events: ZKsync maintained institutional visibility through media features and interviews in outlets including CNBC, The Verge, ETN, and NYSE TV, as well as keynote presence at events including Point Zero Forum, ETH Conf, Consensus, and the Linux Foundation Privacy Workshop.
  • Policy Engagement: ZKsync joined more than 200 organizations urging the U.S. Senate to bring the CLARITY Act to the floor, supporting regulatory clarity for digital finance infrastructure.
  • Institutional Research: ZKsync co-sponsored SODA’s 2026 “Tokenization at Investment Banks” report, based on the views of 16 of the world’s largest sell-side institutions.

6. Performance, Proving & Technical Focus

Technical work narrowed around production Prividium deployments, private interoperability, and the protocol foundations needed for institutional settlement networks. Airbender proving also gained adoption beyond ZKsync OS.

  • Prividium Production Readiness: Engineering work focused on production operations for live deployments, including monitoring, support readiness, and auditability.
  • Tokenized Deposit Platform Readiness: The tokenized-deposit platform reached first-bank-testnet readiness for bank-governed deposit networks.
  • Selective Disclosure and Multi-Prover Foundations: These technical building blocks were completed in Q2 and now form the basis for Q3 work on the connecting layer between private institutional environments.
  • **Airbender in EthProofs On-Prem:** Airbender was enrolled in the EthProofs on-prem proving initiative, and the EthProofs runner was updated to 100-bit security.
  • **ethrex Proving Backend Integration:** The ethrex client integrated Airbender as a proving backend. This is Airbender’s first use outside ZKsync OS and advances its goal of proving Ethereum directly.
  • Erigon / zilkworm Integration (Experimental): The Erigon team prepared an experimental Airbender proving backend for zilkworm. Public materials show continued progress toward efficient Ethereum block proving on consumer-grade GPUs, including Airbender and zilkworm-related work. Further details should follow through official release channels.
  • Besu Compatibility: Besu support expands Prividium’s ability to serve institutions that have already standardized on enterprise Ethereum infrastructure.
  • Stage 1 Decentralization Support: Protocol work continued on Stage 1 decentralization support while the company reduced legacy surface area and concentrated resources on the Prividium roadmap.

This quarter narrowed our work around institutional privacy and settlement. Prividium is now in production, governance has funded the next phase of development, and the technical foundations for private interoperability are in place. The next phase is connecting these institutions to one another through private, auditable, Ethereum-settled infrastructure.

1 Like

One would expect that you’d show some respect to the community you tricked, who is requesting clarification and asking questions about the disaster your leader caused, BUT YOU’RE COMPLETELY IGNORING THAT. THAT’S extremely disrespectful and kind of SHAMELESS! Don’t you dare to ban my account like you did before to try to silence us! I took screenshots and documented everything.

1 Like

Cross-chain interoperability has long been ZKsync’s core selling point. Now that this vision is poised to materialize, the project is pivoting toward private interoperability. The questions remain: Can private interoperability generate revenue? Will such revenue be tied to ZKsync? And how can these earnings fuel further advancement of ZK token

Fair questions @junkui.eth, and they’re the same ones the alignment thread asks in fuller form, so I’ve answered them completely there.

The short version: private interop is being designed so protocol-level fees can exist at the network layer. Those network-level fees, distinct from Matter Labs’ services revenue, are what governance can route through the Fee Flow system already deployed onchain.

How they’re structured, allocated, and whether any mechanism is activated is governance’s decision. Activation makes sense when there are real, recurring fees to route, not symbolic activation when there are no fees.

Also, since you flagged the token page language earlier in another thread, it’s been updated so its architecture descriptions match the current state of the network.