--- title: "OUSD on Ethereum" url: https://openusd.dev/networks/ethereum/ description: "Identify OUSD on Ethereum: exact token address, network setup, fee model, developer tools and operational limits." --- # OUSD on Ethereum Open Standard lists native OUSD on Ethereum. Pair the Ethereum contract below with Ethereum Mainnet, chain ID 1; a matching token symbol on another [network](https://openusd.dev/guides/concepts/#network) is not the same deployment. [Open Standard: Build with Open USD ↗](https://joinopenstandard.com/integrate) [Ethereum: JSON-RPC API ↗](https://ethereum.org/developers/docs/apis/json-rpc/) Reviewed 2026-10-12. Token identity is source-backed; no OUSD transfer or provider integration independently tested. ## Official OUSD contract ``` 0x9f6F3991D525015a6F8CaF062C83b62fD3AC4436 ``` [View OUSD on Ethereum explorer ↗](https://etherscan.io/address/0x9f6F3991D525015a6F8CaF062C83b62fD3AC4436) · [Official address listing ↗](https://joinopenstandard.com/integrate) This [token address](https://openusd.dev/guides/concepts/#token-address) identifies OUSD on Ethereum. It is not a customer receiving address. Do not send funds directly to it. ## Connecting to Ethereum Mainnet Connect through your Ethereum node or selected RPC provider, then check the network with eth\_chainId. The JSON-RPC reference returns chain IDs as hexadecimal strings; Ethereum Mainnet is 1, represented as 0x1. [Ethereum: JSON-RPC API ↗](https://ethereum.org/developers/docs/apis/json-rpc/) Sepolia is Ethereum’s recommended testnet for application development. Accounts can exist across networks, but their balances and transaction histories are separate. A Mainnet token address does not establish a corresponding Sepolia deployment. [Ethereum: Networks ↗](https://ethereum.org/developers/docs/networks/) ## Reading OUSD with a network check The downloadable Node.js example first requires chain ID 1, 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) 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) 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 RPC_URL="YOUR_ETHEREUM_MAINNET_RPC_URL" node read-ousd-evm.mjs ethereum 0x0000000000000000000000000000000000000000 ``` Sources: [Download: read-only EVM balance example](https://openusd.dev/examples/read-ousd-evm.mjs) ## Funding ETH execution fees Ethereum charges transaction fees in ETH. The cost depends on gas used and the base and priority fees. Keep fee funding separate from the OUSD amount; a failed transaction can still consume gas. [Ethereum: Gas and fees ↗](https://ethereum.org/developers/docs/gas/) Estimate the actual contract operation. Ethereum’s 21,000-gas example describes a basic ETH transfer, not a universal gas limit for token transfers or other contract calls. Use an estimate for the transaction you intend to submit. [Ethereum: Gas and fees ↗](https://ethereum.org/developers/docs/gas/) [Ethereum: JSON-RPC API ↗](https://ethereum.org/developers/docs/apis/json-rpc/) ## Inspecting contract state and receipts Use eth\_call for read-only contract queries and eth\_getTransactionReceipt to retrieve an included transaction’s receipt. These are general Ethereum interfaces; consult the token’s actual contract interface before constructing OUSD calls. [Ethereum: JSON-RPC API ↗](https://ethereum.org/developers/docs/apis/json-rpc/) Ethereum RPC distinguishes pending, latest, safe, and finalized block state. Set a confirmation policy for payment crediting instead of treating a pending observation as final settlement. [Ethereum: JSON-RPC API ↗](https://ethereum.org/developers/docs/apis/json-rpc/) ## OUSD deployment and access limits The canonical Ethereum listing does not grant minting or redemption access and does not establish that a particular provider accepts this OUSD contract. Confirm the required operation and account eligibility with that provider. [Open Standard: Build with Open USD ↗](https://joinopenstandard.com/integrate) Use the listed contract to identify OUSD, not as a personal receiving address. This reference has not tested Ethereum OUSD transfers, provider integrations, or a Sepolia OUSD deployment. [Open Standard: Build with Open USD ↗](https://joinopenstandard.com/integrate) [Ethereum: Networks ↗](https://ethereum.org/developers/docs/networks/) ## Provider routes involving Ethereum These records name Ethereum 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/)