Cryptographic Sovereignty

Traditional blockchains force users into an Optimistic Gap — minutes to hours where they hold belief without cryptographic knowledge of their state. Ring0 eliminates this gap entirely. Every user possesses computational knowledge backed by a verifiable proof that can be checked locally, presented to third parties, and enforced on-chain without any validator's cooperation.

optimistic gap

The Optimistic Gap

In traditional blockchains (optimistic rollups, sidechains, even many ZK rollups), users experience a temporal gap between submitting a transaction and obtaining cryptographic certainty of its inclusion. During this gap, users hold only belief — a probabilistic expectation without mathematical proof. This gap manifests as dead liquidity (capital locked during challenge periods), sequencer halt risk (single points of failure), censorship vulnerability (sequencers can reorder or exclude transactions), and MEV extraction (value captured during the uncertainty window).

belief to knowledge

From Belief to Knowledge

Ring0 transforms user experience from belief to cryptographic knowledge. The protocol provides computational knowledge where the user holds a proof that can be verified using only local information. This proof serves three functions: (1) the user can independently verify their own state without trusting any validator, (2) the proof can be presented to third parties as evidence of asset ownership, and (3) the user can enforce state transitions on-chain via Forced Inclusion, regardless of block producer cooperation.

forced inclusion

Forced Inclusion Protocol

Ring0 provides three priority intents that cannot be censored or delayed beyond one epoch boundary. These intents are processed by the protocol's smart contract on the L1 Rectangle, bypassing the block producer entirely.

• ForceWithdraw FW(c, amount, dest): Unconditional withdrawal of funds to a specified destination address
• ForceCancel FC(c, order_id): Cancellation of an open order, returning locked collateral to the user
• ForceRecall FR(c, position_id): Recall of a position, unwinding exposure and returning net value

escape hatch

Escape Hatch Mechanism

If the entire block producer set goes offline or refuses to process forced inclusion intents, the Escape Hatch activates after a configurable timeout (7-14 days). This mechanism allows users to withdraw directly from the L1 Rectangle using only their last verified state proof and inclusion witness. The escape hatch is a structural guarantee — it requires no honest majority assumption and no external coordinator. Users always retain the ability to exit.

session keys

Session Keys

Ring0 supports ephemeral session key pairs authorized by the user's master key. Session keys have bounded scope (specific operations only), bounded limits (maximum value per operation), and bounded lifetime (automatic expiration). Critically, session keys cannot authorize forced inclusion — only the master key can trigger ForceWithdraw, ForceCancel, or ForceRecall. Session keys are revocable via a priority intent signed by the master key.

privacy sovereignty

Privacy Sovereignty via HSS-CoFHE

Ring0 extends sovereignty beyond asset ownership to data privacy. Through HSS-CoFHE (Homomorphic Secret Sharing with Collaborative Fully Homomorphic Encryption), no single validator ever observes plaintext transaction data. Computation proceeds over secret-shared values. The user's privacy is a structural property of the protocol — not an opt-in feature that depends on validator goodwill.

sovereignty summary

Five Sovereignty Guarantees

Ring0 provides five distinct sovereignty guarantees, each independently enforceable:

• S1: Real-time proofs — cryptographic ownership certificate within 36ms
• S2: Forced inclusion — censorship-resistant priority intents processed within one epoch
• S3: Escape hatch — unconditional exit if block producers go offline (7-14 day timeout)
• S4: Session keys — delegated authority with bounded scope, no forced-inclusion delegation
• S5: Privacy — no single validator observes plaintext data via HSS-CoFHE