Skip to content
Oris Docs
Sign in Get API Key

Deployment status

Every layer of the Oris Trust and Compliance Protocol ships to Base Sepolia first. Mainnet rollout is planned. Contract bytecode is identical between testnet and mainnet, so the move is a re-deploy with no source change.

Layer state

LayerComponentAddress (Base Sepolia)State
L1OrisAgentRegistrySix contracts LIVE
L2OrisL2PolicyRegistry0xb43a7d6efdd2df1F11af130133965f00C99dE356 LIVE
L3Veris Engine (gRPC)mTLS LIVE
L4Bundle assemblerAPI at api.useoris.xyz/v1/bundles LIVE
L5OrisL5RevocationRegistryDeployed on Base Sepolia LIVE
L6OrisComplianceVerifier0xD0aCf4a873C5bBEA4296958C27c1eA652D98fA5C (block 42019099) LIVE
L7OrisAuditLogRegistry0xAde6DC06178904194FaE72CC83C6d2ec65Ed34c8 LIVE
L8Python SDKoris-sdk 0.2.0 on PyPI LIVE
L8TypeScript SDKoris-sdk 0.4.0 on npm LIVE

SDK versions in production

Terminal window
# Python
pip install "oris-sdk==0.2.0"


# TypeScript
npm install oris-sdk@0.4.0

The oris.protocol namespace ships with the L8 verifier client (OrisProtocol, verifier.verify(), offline verify_response_signature()). Cross-language parity confirmed against the live verifier at api.useoris.xyz.

Supported chains today

ChainAdapter typeStablecoinsVerifier
BaseERC-4337 smart accountUSDC, USDbCSolidity on-chain
EthereumERC-4337 smart accountUSDC, USDT, DAICCIP-Read federation
ArbitrumERC-4337 smart accountUSDC, USDTCCIP-Read federation
OptimismERC-4337 smart accountUSDC, USDTCCIP-Read federation
PolygonERC-4337 smart accountUSDC, USDTCCIP-Read federation
AvalancheERC-4337 smart accountUSDC, USDTCCIP-Read federation
BNB Smart ChainERC-4337 smart accountUSDC, USDT, BUSDCCIP-Read federation
CeloERC-4337 smart accountUSDC, cUSDCCIP-Read federation
SolanaSPL tokenUSDC, USDTAnchor reference verifier
TronTRC20USDT, USDCHTTP gateway

Partner-led adapters

These exist as HTTP gateways or pilot integrations and roll forward as partners co-sign their integration.

RailStatePhase
Stripe MPP PENDING Partner pilot
Visa Tap PENDING Issuer pilot
AWS AgentCore PENDING Partner pilot
x402 PENDING Spec align
Coinbase Agent PENDING Partner pilot

Audit gates closed

Every layer has passed independent pre-deploy and post-deploy security audits with zero critical and zero important findings open. Audit reports are available to enterprise customers under NDA.

Mainnet rollout order

Mainnet rollout order:

  1. L1 (identity contracts) — bytecode-identical re-deploy.
  2. L2 (policy registry) — same.
  3. L5 (revocation registry) — same.
  4. L6 (verifier contract) — same.
  5. L7 (audit log registry) — same.
  6. L3 (Veris gRPC) — promote the gRPC endpoint to mainnet.
  7. L4 (bundle API) — point to mainnet adapters.
  8. L8 (SDK) — bump network default from base-sepolia to base.

Each step is independently atomic. Rollback is a redeploy of the prior step.

ZK boundary (v2)

L4 ships today with Ed25519 (proof_type = 0x01). The ZK boundary is the only protocol surface that can change. Two candidate proof systems are queued behind the same wire format:

  • SP1 — proof_type = 0x02. Succinct Labs zkVM.
  • Halo2 — proof_type = 0x03. Per-circuit recursive proof.

Both share the 196-byte public input layout from v1. The verifier dispatches on proof_type. Customers writing against the SDK do not change a line of code.

Where to go next