Your policy stays yours
Minimum yield, loss tolerance and duration are committed as a salted hash. Counterparties can verify you are bound to a policy without learning what it is, so they cannot price against your limits.

LIVE ON SEPOLIA + ARC
Private risk policy, enforced onchain
Sovereign lets a lender commit to a private risk policy, have it enforced automatically across two chains, and publish only the decision needed for enforcement. No thresholds onchain. SAFE monitoring stays silent.
CHAINS SETTLED ACROSS
02
POLICY VALUES PUBLISHED
00
CONTRACTS VERIFIED
05
01 / Commit a policy
Publish a salted commitment to your risk thresholds. The thresholds themselves never touch the chain.
02 / Negotiate terms
Counterparties exchange EIP-712 signed offers bound to the intent, the registry and the chain.
03 / Confidential validation
The workflow checks the signed terms against the committed policy and activates the agreement.
04 / Continuous enforcement
Authenticated position data is evaluated on a schedule. A breach unwinds escrow across chains.
THE PROBLEM
Automated enforcement normally means putting your risk parameters onchain where everyone can read them. Once a counterparty knows your exact loss tolerance, they know precisely how far they can push before anything happens to them. The safer you try to be, the more you give away.
THE APPROACH
Your policy is committed as a salted hash, so it is provably fixed but not readable. Evaluation happens off-chain against authenticated data, and only an actionable decision is ever written. A safe position produces no transaction at all, reducing observable output without guaranteeing complete threshold secrecy.
CAPABILITIES
Minimum yield, loss tolerance and duration are committed as a salted hash. Counterparties can verify you are bound to a policy without learning what it is, so they cannot price against your limits.
A healthy position produces no report, no transaction and no event. This reduces routine disclosure, while timing, public observations and repeated agreements can still reveal bounded information.
The workflow reads authenticated private position data and publishes a single decision. Inputs never leave the handler, and the receiver rejects anything that is not a well-formed, correctly bound report.
Agreements settle on Ethereum while capital sits in escrow on Arc. A breach recorded on Sepolia unwinds the escrow and returns capital, gated on finalized source evidence.
Observations arrive over an authenticated channel with separate, agreement-scoped read and write credentials, freshness limits, quotas and revocation. Stale or mismatched data yields no decision at all.
Replay protection, decision nonces, terminal-state guards and strict caller authorization are enforced in the contracts, covered by fuzz and invariant tests, not by convention.
PROVEN ONCHAIN
One agreement ran the entire path on public testnets: validated and activated, breached on fresh position data, escrow unwound on Arc, and reconciled to a terminal state on Ethereum. Every transaction is finalized and independently checkable on a block explorer.
ETHEREUM SEPOLIA
SETTLED
Agreement reached a terminal state after owner reconciliation.
ARC TESTNET
UNWOUND
Escrow released and capital returned in full.
DECISIONS PUBLISHED
2
One validation, one breach. Safe checks published nothing.
ARCHITECTURE
Intent and agreement registries, decision sink, and the authenticated report receiver.
Confidential evaluation of a private policy against authenticated position data.
USDC escrow, locked on activation and unwound on a finalized breach.
Contracts are source-verified on Etherscan. Cross-chain settlement waits for finalized source evidence before moving capital, and every decision is bound to a specific agreement, check kind and nonce.
START HERE
Public status reads both chains at their finalized block and returns the agreement state, chain IDs and block numbers. No wallet required, and no private evaluation data is ever exposed.