ZKsync opens Prividium core code under Apache 2.0 license

Matter Labs, the company behind the ZKsync protocol, has open-sourced the core permissioning engine of Prividium, its enterprise blockchain platform. The code went public on September 8, 2026, under the Apache 2.0 license.

Germany’s Deutsche Bundesbank is the first organization testing a self-hosted instance. The Bundesbank is collaborating with Matter Labs on both design and testing for its self-hosted deployment.

The release does not hand over everything. Matter Labs is keeping its enterprise tooling, including user interfaces and deployment tools, proprietary. The engine is open. The polished dashboard around it still comes with a bill.

What’s actually in the repo

The release covers one main app and six packages. All of it lives in a public GitHub repository called matter-labs/prividium-core.

The permissioning engine is the part that decides who can do what on a private chain. For a regulated institution, that layer matters a lot. Permissions and auditability are the features compliance teams actually lose sleep over.

This piece completes a broader stack that was already public. ZKsync OS, the Atlas sequencer, the Airbender prover, and the interoperability contracts were all open-sourced before this announcement.

With the permissioning engine added, institutions can now independently build permissioned chains using publicly shared code. Previously, the gatekeeping layer was the missing puzzle piece.

The Apache 2.0 license lets institutions inspect and modify the engine without signing a commercial agreement for that specific component. A bank can read every line, change what it needs, and run it in-house without needing Matter Labs’ permission to do so.

Why a central bank cares about vendor lock-in

Prividium is built for validium-style chains. In this model, transaction data stays off-chain, which keeps sensitive financial activity private. The chain still anchors to Ethereum through zero-knowledge proofs.

Matter Labs framed the open-source move as a response to institutional feedback. Large organizations told the company they were wary of depending on a single vendor for critical technology.

Opening the permissioning engine addresses that worry at the layer where it bites hardest. If the gatekeeping logic is public, an institution can verify it does what it claims and keep it running regardless of what happens to the vendor.

What this means

The business model here is a familiar one: give away the engine, sell the car. Matter Labs keeps control over the commercial services that make deployment easier, while removing the biggest objection institutions raise in procurement meetings.

The Bundesbank test is the clearest signal of where this is aimed. A German central bank running a self-hosted Prividium instance is a meaningful credibility marker for ZKsync’s enterprise ambitions, though it remains a test rather than a production rollout.

Prividium chains anchor to Ethereum through zero-knowledge proofs, so institutional adoption of this model would route more enterprise activity back to Ethereum as the settlement layer.

There are also open questions about how far an open engine goes on its own. Institutions that self-host still need the skills to run and maintain the stack. The proprietary deployment tools exist precisely because that work is not trivial.