ZKsync’s Prividium Engine Goes Open Source, and a Central Bank Is Already Testing It

“What open weights did for AI, giving serious institutions the option to hold the technology in their own hands, open source is now doing for financial infrastructure.” That’s how Alex…

Abstract glowing blue network of nodes and lines, symbolizing the Prividium permissioning engine's encrypted data flow

“What open weights did for AI, giving serious institutions the option to hold the technology in their own hands, open source is now doing for financial infrastructure.”

That’s how Alex Gluchowski, CEO of ZKsync developer Matter Labs, framed a release his team had held back for more than a year. On September 8, Matter Labs open-sourced the Prividium permissioning engine, the access-control core of its zero-knowledge banking platform, and handed the last locked piece of the system to anyone who wants to inspect, run, or modify it.

Prividium lets a bank run its own private blockchain while still proving, cryptographically, that its transactions are valid. Smart contracts and account data stay inside the institution’s walls. Zero-knowledge proofs do the vouching in public. Matter Labs had already open-sourced most of the stack behind this, including the ZKsync OS core, the Atlas sequencer, and the Airbender prover. The Prividium permissioning engine, the component that decides who can see what and who can act on the network, was the one piece the company kept proprietary. Not anymore.

Why the Prividium Permissioning Engine Was the Missing Piece

Banks don’t like single-vendor dependencies, especially for infrastructure that touches settlement and compliance. Gluchowski put it plainly: regulated institutions told Matter Labs, over and over, that a commercial-only core was a dealbreaker for anything mission-critical. If the company that wrote the code could change the license, raise the price, or disappear, no serious bank would build a production system on top of it.

Opening the permissioning engine removes that risk. An institution can now read every line that governs access control, fork it, run it entirely on its own servers, and never touch Matter Labs’ commercial product if it doesn’t want to. That’s a real technical shift, not just a licensing footnote. Permissioning is the part of a private blockchain that decides trust boundaries, and trust boundaries are exactly what a bank’s security team needs to audit before signing off on anything.

Bundesbank Puts the Open Code to Work

Germany’s central bank, the Deutsche Bundesbank, isn’t waiting on the sidelines. It’s already running trials on the newly public permissioning engine, working directly with Matter Labs on how the platform should evolve. A national central bank testing open infrastructure for programmable settlement is a different kind of validation than a startup integration announcement, and it lands weeks after DBS and Citi settled weekend payments on Swift’s private ledger, another sign that banks are moving past pilot programs into live infrastructure.

None of this means every bank will adopt ZKsync’s approach tomorrow. But the gap between “blockchain technology banks might eventually trust” and “blockchain technology a central bank is actively testing in the open” just got smaller. It follows a string of similar institutional bets this year, including Cashlink’s push to bring one billion euros in securities onto Avalanche, and suggests banks want infrastructure they can inspect, not just use.

Full details on the release are in The Block’s report on the Prividium open-source engine.

Related Reading