Current Testnet
This page describes the public Oro deployment currently selected by the application. Contract addresses are intentionally not copied into the documentation: the versioned runtime deployment export remains the source of truth.
This environment uses test assets and unaudited beta software. Do not send real XAUT or other assets with monetary value to the testnet contracts.
Compatibility
| Layer | Current target |
|---|---|
| Ethereum | Sepolia, chain ID 11155111 |
| EVM collateral | Mock XAUT (mXAUT), 6 decimals |
| Aztec contracts, artifacts and tooling | Aztec 5.2.0 |
| Aztec wallet | Azguard compatible with Aztec 5.2.0 artifacts |
| Deployment generation | Created by the latest complete manual deployment |
Aztec 5.2.0 is the only supported Oro version. A release update replaces the whole contract generation and runtime export manually after the complete test suite; Oro does not maintain a second build or staged release state.
Bridge configuration
| Parameter | Current value |
|---|---|
| Ethereum confirmations | 12 |
| Aztec → Ethereum exit fee | 1% |
| User-facing testnet estimate | About 1h 30m |
The estimate is not a finality guarantee. Ethereum confirmations, Aztec indexing, epoch proving and root publication can extend the wait. The transfer history and persisted relayer state are more authoritative than the countdown.
Credit configuration
| Parameter | Current value |
|---|---|
| Minimum mint ratio | 125% |
| Liquidation threshold | 112.5% |
| Liquidation bonus | 3.5% |
| Close factor | 50% |
| Mint fee | 0% |
| Account debt ceiling | 100,000 ORO |
| Global debt ceiling | 1,000,000 ORO |
These values are enforced on-chain and can only change through authorized contract calls. The app reads them from the contracts for position previews.
The values above are the current public-testnet configuration, not permanent protocol guarantees. They may be adjusted before the testnet ends as Oro collects operational evidence and validates oracle, liquidation, bridge and market behavior.
A future mainnet rollout may deliberately begin with more conservative limits, for example, a 150% minimum mint ratio. These limits may then be lowered in controlled corrective waves as the protocol demonstrates robustness and adoption. A long-term minimum mint ratio near 112.5% is an example target, not a committed launch value or schedule. Every change must preserve a safety margin above the liquidation threshold and should be supported by testing, monitoring, governance review and independent risk analysis.
Oracle and services
- The testnet oracle normally evaluates its independent sources once every 24 hours.
- The on-chain price freshness window is 25 hours. The worker reports before expiry instead of relying on a liveness-only heartbeat.
- Backend, oracle, relayer and Aztec RPC health are displayed in the app.
- Oracle and relayer use separate Aztec accounts and separate wallet datastores.
- Bridge intents and progress are persisted in SQLite for restart and recovery.
Current limitations
- CDP owner, collateral and debt accounting are public. Only token balances and token transfers use private notes today.
- Liquidations are restricted to approved liquidator accounts.
- Governance roles are not yet protected by the final multisig/timelock and production separation model.
- The operator stack is not a highly available mainnet topology.
- Independent security audits are still required before mainnet.
See Risks for the broader production-readiness boundary and Bridge Recovery for interrupted transfers.