Matter Labs released Prividium Core under the Apache 2.0 license on Sept. 8, 2026, opening the access-control engine that gates participation in its ZKsync-based institutional blockchain stack.

The release ships the permissioning layer that institutions previously had to license from the ZKsync developer. Until now, running a permissioned ZKsync environment required buying a commercial component on top of the already open-source ZKsync OS chain software.

In its announcement, Matter Labs said Deutsche Bundesbank had deployed Prividium on infrastructure it controls itself. Smart-contract state and token data remain inside the German central bank's environment. Matter Labs described a collaboration on "design and testing" but stopped short of identifying a production use case.

CEO Alex Gluchowski tied the move to a broader strategic pivot. "The entire company is committed to bringing enterprises and regulated financial institutions onchain with privacy at its core," he said when Matter Labs restructured around Prividium earlier in 2026.

What is now public, and what stays commercial?

The Prividium Core repository documents the software as a permissioned proxy and API sitting in front of a ZKsync sequencer. It authenticates callers, applies role-based access controls to JSON-RPC requests and forwards approved traffic to the underlying chain node.

Matter Labs released three pieces of code:

• The core permissioned-proxy and authentication service
• A developer SDK for integrating institutional identity and policy engines
• Access-control helpers that map corporate roles to onchain actions

Surrounding products stay closed. The operating tooling, managed infrastructure, system integrations and customer support remain paid offerings sold by Matter Labs.

Why does a Bundesbank deployment matter?

A central bank running source-controlled permissioning logic inside its own perimeter shifts the trust model for institutional chains. Engineers at Bundesbank can audit every transaction-policy change at the source level rather than rely on a vendor's binary releases.

The configuration carries regulatory weight beyond Germany. Bundesbank has explored blockchain prototypes for settlement and interbank use; running Prividium locally keeps transaction data off the infrastructure of a U.S.-headquartered vendor. European supervisors tracking vendor concentration risk are likely to read the deployment as a reference design.

What restrictions apply to forks?

Apache 2.0 lets any party modify and redistribute the core code under the license's standard terms. A separate clause in the repository adds a branding constraint: using the "Prividium" name on a modified or redistributed version requires written approval from Matter Labs.

That carve-out separates code governance from brand governance. Institutions can fork the access-control logic but must sell a derivative under a different label unless they negotiate directly with Matter Labs.

What comes next?

Matter Labs must now translate an open-source release into managed-service revenue. The Apache 2.0 grant removes one procurement barrier for regulated buyers, but customers still need operational tooling, audit trails and service-level commitments — the paid layer Matter Labs continues to sell.

The first durable test will be a Bundesbank production deployment. If the central bank carries Prividium from sandbox to a named workload and publishes its findings, the move would hand European supervisors a working precedent for sovereign-grade rollups before the end of 2027.