Testnet (open)
Testnet is the default environment for all examples in this documentation. Access is open — no partner agreement required.Testnet contract addresses
These are the verified deployments on ADI testnet. They are the authoritative target for every EIP-712verifyingContract field.
| Contract | Address |
|---|---|
ConditionalTokens | 0xB12c3c5573d9379dC7f6EE47C148E4C1695A0416 |
MockCollateral (mUSDC) | 0x9bC8244c0F531F27fe3636FFdAf2C586d11241e1 |
CTFExchange (binary) | 0xc3c197e42AfE809a7f34D3a7eE6aDE0cF7613D2b |
VaultFactory | 0xFFFBE32fF7B8a2AFD4FA2Af0C480FE59206A8ba3 |
DepositLimitRegistry | 0xA18a1ed7139a94654535EC5A5a8Aa803E694cDbb |
NegRiskAdapter | 0xe8573F401a1fa30c3Df0e7F427C7f25a68E1Ec98 |
PredictStreetNegRiskCtfExchange | 0xB1A9274D2a9bd8a8CDd4D836e4f5273d3870211a |
PredictStreetOracle | 0x24731ADFe7FB28E037c04D71f89f52974Ae76ee1 |
Getting testnet USDC
MockCollateral (0x9bC8244c0F531F27fe3636FFdAf2C586d11241e1) exposes
a public mint(address to, uint256 amount) on testnet — anyone can mint
themselves mUSDC. After minting, you still need to deposit into your
vault: see Vaults.
Testnet caveats
Testnet has compliance guards relaxed for integration testing — KYC,
geo, and the return-to-source cleared-deposit check are not enforced.
Practical consequences:
- Multi-wallet sub-accounts transact without per-wallet KYC.
- Every depositing EOA is auto-cleared as a withdrawal destination —
no
destination_not_clearedrejection. - Sanctions / geo blocks do not fire.
- Matcher state is not persisted across redeploys. After a testnet restart, your open orders may disappear (warm-restart of the matcher is planned for staging+).
- Oracle on testnet resolves against mock data. Do not use testnet resolution for real backtesting.
- Faucet, admin
pause/resume/cancel, and platform kill-switch can be triggered at any time during partner testing windows — expect occasional disruptions.
Staging (on request)
Production-like environment with real AML provider, real data-source adapters, real on-chain deployments on a production-ready chain. Used for the pre-launch dry-run before a new market opens to real users. Access requires:- A signed partner agreement (NDA + API access terms).
- A whitelisted source IP for the internal network (staging surfaces are gated behind VPN).
- A dedicated partner account provisioned by ops.
Mainnet (partner onboarding)
Production environment. Base URL, chain ID, and contract addresses are delivered to partners at onboarding as part of the live-rollout runbook. Do not hardcode mainnet values from this documentation — always read them from the onboarding package so configuration remains auditable.Partner onboarding
Request mainnet access and onboarding runbook.
Status page
Real-time status of all environments.
Environment capability matrix
| Feature | Testnet | Staging | Mainnet |
|---|---|---|---|
HTTP REST (core-api) | ✅ | ✅ | ✅ |
WebSocket (ws-gateway) | ✅ | ✅ | ✅ |
/api/docs OpenAPI UI | ✅ | on request | ❌ (internal only) |
| Faucet | ✅ | ❌ | ❌ |
MOCK_AUTH_ACCEPT_ALL | ❌ | ❌ | ❌ |
| Real AML screening (Global Ledger) | mock | ✅ | ✅ |
| Real sports data sources (SDDP, etc.) | mock | ✅ | ✅ |
| On-chain settlement | ✅ (testnet chain) | ✅ | ✅ |
| HSM-backed oracle signer | ❌ | ✅ | ✅ |
Admin multi-sig on cancel / void | ❌ | ✅ | ✅ |
| Platform kill-switch | ✅ | ✅ | ✅ |