Deployed Contracts
Official OBSDN smart contract addresses per network
OBSDN's settlement layer is on-chain. The Obsdn contract is the entry point for deposits, withdrawals, and signer registration, and it's the EIP-712 verifying contract for signed orders.
Use the runtime endpoint as the source of truth
Call GET /chain/config to discover the live addresses for whichever network the API
is bound to. The tables below are a snapshot; /chain/config stays in sync with deployments automatically.
Monad Testnet
https://api.obsdn.trade is currently bound to this network.
Testnet only
Do not deposit production funds. Mainnet is pending publication — see below.
Network
| Field | Value |
|---|---|
| Chain ID | 10143 |
| Native currency | MON (18 decimals) |
| RPC | https://testnet-rpc.monad.xyz |
| Explorer | testnet.monadscan.com |
Contracts
| Contract | Address |
|---|---|
Obsdn | 0x709fcaE0806870170b463B755A20cbF3A5ad0091 |
Collateral assets
Listed via GET /assets. The addr field is the on-chain ERC-20 address; dec is the token's native decimals — use this when computing the ERC-20 approve amount in Getting Started — Step 4.
| Asset | Address | Decimals | Min withdraw | Withdraw fee |
|---|---|---|---|---|
| USDC | 0x0F1c3B7a1598297F22A21AC2561Dea31b8037B2e | 6 | 2 | 1 |
Mainnet
Pending publication. GET /chain/config will return the mainnet configuration once the production deployment goes live.
Discover at runtime
curl https://api.obsdn.trade/chain/configSample response:
{
"data": {
"nm": "monad-testnet",
"chain_id": 10143,
"domain": {
"nm": "Obsidian",
"ver": "1",
"chain_id": "10143",
"verif_contract": "0x709fcaE0806870170b463B755A20cbF3A5ad0091"
},
"addrs": {
"obsdn_contract": "0x709fcaE0806870170b463B755A20cbF3A5ad0091"
},
"native_ccy": { "dec": 18, "nm": "Testnet MON", "sym": "MON" },
"rpc_urls": { "http": ["https://testnet-rpc.monad.xyz"] },
"blk_explorer": { "nm": "Monad Explorer", "url": "https://testnet.monadscan.com" },
"testnet": true
},
"request_id": "..."
}