--- title: "OUSD on Base" url: https://openusd.dev/networks/base/ description: "Identify OUSD on Base: exact token address, network setup, fee model, developer tools and operational limits." --- # 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](https://openusd.dev/guides/concepts/#network) fees. [Open Standard: Build with Open USD ↗](https://joinopenstandard.com/integrate) [Base: Connect to Base ↗](https://docs.base.org/get-started/connect-to-base) Reviewed 2026-10-12. Token identity is source-backed; no OUSD transfer or provider integration independently tested. ## Official OUSD contract ``` 0xB2000000000000000000002fEb517dFeC7415344 ``` [View OUSD on Base explorer ↗](https://basescan.org/address/0xB2000000000000000000002fEb517dFeC7415344) · [Official address listing ↗](https://joinopenstandard.com/integrate) This [token address](https://openusd.dev/guides/concepts/#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 ↗](https://docs.base.org/get-started/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 ↗](https://docs.base.org/get-started/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 ↗](https://joinopenstandard.com/integrate) [Ethereum: JSON-RPC API ↗](https://ethereum.org/developers/docs/apis/json-rpc/) [Download: read-only EVM balance example ↗](https://openusd.dev/examples/read-ousd-evm.mjs) [Base: Connect to Base ↗](https://docs.base.org/get-started/connect-to-base) [Base: RPC overview ↗](https://docs.base.org/base-chain/api-reference/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 ↗](https://openusd.dev/examples/read-ousd-evm.mjs) 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 ↗](https://joinopenstandard.com/integrate) [Ethereum: JSON-RPC API ↗](https://ethereum.org/developers/docs/apis/json-rpc/) [Download: read-only EVM balance example ↗](https://openusd.dev/examples/read-ousd-evm.mjs) [Base: Connect to Base ↗](https://docs.base.org/get-started/connect-to-base) [Base: RPC overview ↗](https://docs.base.org/base-chain/api-reference/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 ↗](https://openusd.dev/examples/read-ousd-evm.mjs) ### 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. _Terminal window_ ```bash node read-ousd-evm.mjs base 0x0000000000000000000000000000000000000000 ``` Sources: [Download: read-only EVM balance example](https://openusd.dev/examples/read-ousd-evm.mjs) ## Estimating 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 ↗](https://docs.base.org/specifications/transactions/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 ↗](https://docs.base.org/specifications/transactions/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 ↗](https://docs.base.org/base-chain/api-reference/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 ↗](https://docs.base.org/base-chain/api-reference/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 ↗](https://joinopenstandard.com/integrate) 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 ↗](https://joinopenstandard.com/integrate) ## 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](https://openusd.dev/providers/bridge/#bridge-ousd-wallets) — The custodial-wallet asset table explicitly lists OUSD on these four networks. - [Bridge: OUSD transfers and conversion](https://openusd.dev/providers/bridge/#bridge-ousd-transfers) — 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. ## Related references - [All OUSD networks and exact addresses](https://openusd.dev/networks/) - [How network fees work](https://openusd.dev/guides/concepts/#network-fees) - [Finality and settlement](https://openusd.dev/guides/concepts/#finality-and-settlement) - [Payment events, retries and reconciliation](https://openusd.dev/guides/integration-architecture/) - [Network records as JSON](https://openusd.dev/data/)