Sovereign rollups
Run your own sovereign rollup
Use the shared network, or run a dedicated rollup under your nation's control — with identical security and settlement. Your data, your borders, your keys.
What stays sovereign
What stays sovereign.
A sovereign rollup is yours. The network secures and connects it — it never governs it, and it can never lock you out or shut you down.
Your data.
Your data stays within your borders. Zero-knowledge proofs let others verify a result without seeing the underlying record.
Your keys.
You hold the keys to your rollup. The network never holds them and never signs on your behalf — there is no kill-switch.
Your operation.
You run it, on open software you can leave with. No lock-in: your state settles to a neutral L1, not to us.
No kill-switch, no lock-in
The network cannot pause, censor, or seize a sovereign rollup, and it cannot read its data. Each posture claim links to its proof on the security page.Settlement and interoperability
How it settles and interoperates.
A dedicated rollup is sovereign in operation but not isolated. It still settles to Ethereum and still verifies across borders — the same proofs, the same guarantees as the shared network.
Settles to Ethereum.
Your rollup posts state roots and validity proofs to Ethereum. Finality comes from L1 verification — identical to the shared network.
Settlement model →
Verifies across borders.
A credential, payment, or record proven on your rollup can be verified by another sovereign — with privacy preserved at each hop.
Interoperability →
When to choose which
When to choose which.
Both paths share the same security and settlement. Pick on operational fit, not on trade-offs in guarantees.
choose · shared network
Start on the shared network when
- — you want to participate without running infrastructure.
- — the shared validator set and data model already fit your residency needs.
- — you are piloting, and want the fastest path to a live, verifiable deployment.
choose · sovereign rollup
Run a sovereign rollup when
- — policy requires data and operation to sit within your borders.
- — you need dedicated capacity and control over upgrades and parameters.
- — you want a chain you fully operate, that still settles and verifies neutrally.
Optional — managed operation
If your ministry would rather not operate the rollup in-house, managed sovereign-rollup operation is available as a separate, optional service. It is one option, not a requirement — a self-operated rollup keeps the same sovereignty and the same guarantees. Managed operation (optional)Your data, your borders, your keys.
Compare the paths above, or talk to the Foundation about running a sovereign rollup.