OUSD on Base
Open Standard lists native OUSD on Base. Use the Base-specific contract below with Base Mainnet, chain ID 8453. Base uses ETH for network fees. Open Standard: Build with Open USD ↗ Base: Connect to Base ↗
Reviewed 2026-10-12. Token identity is source-backed; no OUSD transfer or provider integration independently tested.
Official OUSD contract
0xB2000000000000000000002fEb517dFeC7415344View OUSD on Base explorer ↗ · Official address listing ↗
This token address identifies OUSD on Base. It is not a customer receiving address. Do not send funds directly to it.
Connecting to Base
Base Mainnet uses chain ID 8453 and the public RPC endpoint https://mainnet.base.org. Base Sepolia is a separate development network with chain ID 84532 and RPC endpoint https://sepolia.base.org. Both use ETH as their network currency. Base: Connect to Base ↗
Use the RPC endpoint for reads and other requests. Base separately lists https://mainnet-sequencer.base.org for mainnet transaction submission. Check which endpoint your client uses rather than sending balance queries to the submission endpoint. Base: Connect to Base ↗
Reading OUSD with a network check
The downloadable Node.js example first requires chain ID 8453, then queries the exact OUSD contract above. It pins eth_getCode, decimals() and balanceOf(address) to the same block number and prints the raw integer plus an exact decimal-string balance. eth_getBalance reads a native-currency balance, not OUSD. Open Standard: Build with Open USD ↗ Ethereum: JSON-RPC API ↗ Download: read-only EVM balance example ↗ Base: Connect to Base ↗ Base: RPC overview ↗
The example makes JSON-RPC reads only; it requests no wallet connection, signature or transaction. The queried owner address is sent to the selected RPC endpoint. The command below uses the zero address only as a syntax illustration; replace it with the public address you intend to inspect. Download: read-only EVM balance example ↗
The example queries decimals at runtime and checks the ABI response shape; it does not hard-code an unverified OUSD precision. It also rejects a contract with no bytecode at the selected block. Review the deployed interface before relying on the result. Open Standard: Build with Open USD ↗ Ethereum: JSON-RPC API ↗ Download: read-only EVM balance example ↗ Base: Connect to Base ↗ Base: RPC overview ↗
Validation limit: the script passed syntax and mocked-response checks, including wrong-network and malformed-response failures. Live RPC requests from this review environment were blocked, so no live EVM balance result is claimed. Output should include network, chainId, block, token, owner, codeBytes, decimals, rawBalance and balance. A latest-block read is not a settlement or spendability guarantee. Download: read-only EVM balance example ↗
Run the read-only balance example
Save the linked download as read-ousd-evm.mjs and use Node.js 18 or later. Use a trusted RPC endpoint; do not paste an RPC credential into source code or shared logs.
node read-ousd-evm.mjs base 0x0000000000000000000000000000000000000000Estimating both fee components
A Base transaction has an execution fee on Base and an L1 fee for publishing transaction data to Ethereum. Estimate both components when budgeting a transfer; an execution-only estimate does not cover the complete network cost. Base: Network fees ↗
Base documents GasPriceOracle methods for estimating the L1 component from a serialized transaction or its approximate size. Fees vary with network conditions, so use the current estimate rather than a fixed price per OUSD transfer. Base: Network fees ↗
Reading contracts and confirming payments
Base’s JSON-RPC reference covers eth_chainId, read-only contract queries with eth_call, event logs, and transaction receipts. eth_getBalance returns an account’s ETH balance; it is not a query for the account’s OUSD holdings. Base: RPC overview ↗
The pending block tag can expose pre-confirmed Flashblock state. Distinguish it from safe or finalized data when deciding when to credit a payment. Public Base endpoints are HTTP-only; applications needing WebSocket subscriptions must choose a WebSocket-capable provider. Base: RPC overview ↗
OUSD deployment and access limits
Open Standard’s native Base listing identifies OUSD, but does not establish a supported OUSD bridge route, a Base Sepolia deployment, or every provider’s deposit and withdrawal routes. Confirm the asset, network, and operation with the selected provider. Open Standard: Build with Open USD ↗
The listed contract identifies the token, not a customer receiving address. This reference has not tested OUSD transfers or provider integrations on Base. Open Standard: Build with Open USD ↗
Provider routes involving Base
These records name Base in an OUSD-specific documented operation. Read the direction, delivered asset and eligibility limits; this is not a claim that every provider operation supports the network.
- Bridge: OUSD custodial wallets — The custodial-wallet asset table explicitly lists OUSD on these four networks.
- Bridge: OUSD transfers and conversion — OUSD destinations are documented on all four networks. OUSD source sections are documented for Base, Ethereum, Solana and Bridge Wallet; a Tempo source route is not established by the reviewed table.