Published Sep 8, 2026
Today we are publishing Prividium Core, the permissioning engine of Prividium and the remaining piece needed to run a permissioned chain entirely from public code.
Repo: github.com/matter-labs/prividium-core
License: Apache 2.0
Docs: docs.prividium.zksync.io
Prividium Core is one application and six packages, published together:
permissions-api — the permissioning engine itself: the system of record for roles, access controls, and permission decisions on a Prividium chain. Every read and write on the chain is mediated by controls this service resolves.access-control — the policy and role primitives the engine is built on.prividium-sdk — the client SDK for building applications and tooling against the permissioning API.api-kit — shared server, database, and error-handling helpers used by the engine.api-types — the TypeScript client generated from the API's OpenAPI spec.api-metrics — instrumentation for operating the engine in production.test-deps — shared test dependencies, so the public repo tests stand alone.The repo ships with workspace and build config, a public CI workflow, and README, CONTRIBUTING, SECURITY, and LICENSE files. It is a working codebase, not a snapshot: it is the same code we develop and run, published byte-for-byte.
Prividium Core is designed to run against the already open-source ZKsync OS stack. The Atlas sequencer, the Airbender prover, and the interoperability contracts with the open-source block explorer components (worker, data fetcher, API, and app) running alongside. Cloning Prividium Core and running it against ZKsync OS is designed to yield a functioning permissioned chain: roles, access controls and permissions enforced by the engine, execution and proving by ZKsync OS, correctness verifiable through ZK proofs anchored to Ethereum.
No commercial component is required for that path.
Prividium Core is developed inside our monorepo and mirrored to the public repository via git subtree, synced in both directions: our changes to the open code flow out, and outside contributions land in the public repo first, then flow back in. Things worth knowing before you open a PR:
Public CI runs on the public repo. Private CI, internal tooling, and everything else in the monorepo are never mirrored.
The administration console, user access panel, and connectors (off-chain integrations into core banking systems, custody, ISO 20022 messaging, and enterprise logging) remain commercial products, delivered under agreement along with enterprise support, certified builds, and signed releases for institutions moving to production. The open core is complete without them: they make operating at scale easier; they are not required to operate.
Prividium exists so that an institution can run its own chain. Private, in its own environment, under its own control while anchoring the correctness of its transactions to an EVM-compatible settlement layer through ZK proofs. Open-sourcing the permissioning engine makes that control structural: the code that decides who can do what on the chain is now code the operator can read, run, and modify, with no dependency on us. You can read more about the reasoning in our announcement here.
Matter Labs is open-sourcing the Prividium permissioning engine, so institutions can run a permissioned chain from public code, in their own environment.
New security measures for ZKsync chains running EraVM, and what the upcoming EraVM transition means for users and chain operators.
ZKsync co-sponsored SODA's 2026 "Tokenization at Investment Banks" report, surveying 16 of the world's largest sell-side institutions on wholesale tokenization.