--- title: "OUSD on Solana" url: https://openusd.dev/networks/solana/ description: "Identify OUSD on Solana: exact token address, network setup, fee model, developer tools and operational limits." --- # OUSD on Solana On Solana, identify OUSD by the [mint](https://openusd.dev/guides/concepts/#mint-account) address below. A mint defines a token; individual holdings live in separate token accounts. Do not use the OUSD mint as a customer receiving account. [Open Standard: Build with Open USD ↗](https://joinopenstandard.com/integrate) [Solana: Tokens ↗](https://solana.com/docs/tokens) Reviewed 2026-10-12. Token identity is source-backed; no OUSD transfer or provider integration independently tested. ## Official OUSD mint ``` ousd2mJsPEckLHcSCDxyKD7NDGARZcfLbDZkKiatYHB ``` [View OUSD on Solana explorer ↗](https://solscan.io/token/ousd2mJsPEckLHcSCDxyKD7NDGARZcfLbDZkKiatYHB) · [Official address listing ↗](https://joinopenstandard.com/integrate) This [mint address](https://openusd.dev/guides/concepts/#mint-account) identifies OUSD on Solana. It is not a customer receiving address. Do not send funds directly to it. ## Choosing the Solana cluster Solana’s documented public Mainnet RPC is https://api.mainnet.solana.com. For application development, use Devnet at https://api.devnet.solana.com. Testnet is intended for validator and network stress testing. Each cluster has separate state. [Solana: Clusters and public RPC endpoints ↗](https://solana.com/docs/references/clusters) Shared public RPC endpoints are rate-limited and are not intended for production applications. Select dedicated or private infrastructure before relying on RPC availability for customer payments. [Solana: Clusters and public RPC endpoints ↗](https://solana.com/docs/references/clusters) ## Reading an OUSD balance safely The read-only example checks the Mainnet genesis hash, the exact OUSD mint, its owning program and six decimals before summing visible amounts from every token account returned for an owner. It verifies each account’s program, mint, owner and amount precision. No key, signature or transaction is needed. [Solana: getGenesisHash ↗](https://solana.com/docs/rpc/http/getgenesishash) [Solana: getAccountInfo ↗](https://solana.com/docs/rpc/http/getaccountinfo) [Solana: getTokenAccountsByOwner ↗](https://solana.com/docs/rpc/http/gettokenaccountsbyowner) [Download: read-only Solana balance example ↗](https://openusd.dev/examples/read-ousd-solana.mjs) On October 12, 2026, getAccountInfo returned an initialized Token-2022 mint at finalized slot 456215899. Its extensions were mintCloseAuthority, permanentDelegate, defaultAccountState, confidentialTransferMint, transferHook, metadataPointer, pausableConfig and tokenMetadata. The mint was not paused; its transfer-hook program ID was null. These are dated observations, not permanent token guarantees. [openusd.dev: Solana read-only RPC evidence, October 12 ↗](https://openusd.dev/data/observations/ousd-solana-2026-10-12.json) [Solana: Token extensions ↗](https://solana.com/docs/tokens/extensions) Download the example below and run it with Node.js 18 or later and a public wallet address you intend to query. That address is sent to the RPC endpoint. The smoke test used the public system-program address, not a customer wallet; it returned no token accounts at finalized slot 456215919 and visibleBalance 0.000000. [Download: read-only Solana balance example ↗](https://openusd.dev/examples/read-ousd-solana.mjs) [openusd.dev: Solana read-only RPC evidence, October 12 ↗](https://openusd.dev/data/observations/ousd-solana-2026-10-12.json) Expected output includes cluster, slot, mint, tokenProgram, owner, decimals, tokenAccounts, rawVisibleBalance and visibleBalance. Amounts stay integer or exact decimal strings. The query does not decrypt confidential balances, establish spendability or prove a payment settled; account reads can be at a later finalized slot than the mint read. [Download: read-only Solana balance example ↗](https://openusd.dev/examples/read-ousd-solana.mjs) [Solana: getTokenAccountsByOwner ↗](https://solana.com/docs/rpc/http/gettokenaccountsbyowner) [Solana: Token extensions ↗](https://solana.com/docs/tokens/extensions) ### Run the read-only balance example Save the linked download as read-ousd-solana.mjs. This reproducible smoke test queries a public program address and should not be used as a customer receiving address. _Terminal window_ ```bash node read-ousd-solana.mjs 11111111111111111111111111111111 ``` Sources: [Download: read-only Solana balance example](https://openusd.dev/examples/read-ousd-solana.mjs) · [openusd.dev: Solana read-only RPC evidence, October 12](https://openusd.dev/data/observations/ousd-solana-2026-10-12.json) ## Budgeting SOL and token-account storage Solana transaction fees are paid in SOL and comprise a base fee plus an optional prioritization fee. Budget the fee payer’s SOL separately from the OUSD amount being transferred. [Solana: Transaction fees ↗](https://solana.com/docs/core/fees) An associated token account provides a predictable account address for an owner and mint. Creating one requires a refundable minimum storage balance, funded by the instruction’s payer even when another wallet owns the account. Include that cost when a recipient needs a new token account. [Solana: Tokens ↗](https://solana.com/docs/tokens) ## Reading balances and choosing commitment A token account records its mint, owner, and token amount. A wallet can own multiple accounts for one mint. Check those fields when reading OUSD holdings instead of treating the mint address as the customer’s balance account. [Solana: Tokens ↗](https://solana.com/docs/tokens) Solana RPC supports reads, simulation, and subscriptions. Choose the commitment level deliberately: processed data can roll back; confirmed reflects a supermajority vote; finalized is the network’s strongest confirmation state. [Solana: State commitment ↗](https://solana.com/docs/rpc#configuring-state-commitment) ## OUSD deployment and access limits OUSD uses Token-2022. The read-only mint observation on October 12, 2026 found six decimals and the program TokenzQdBNbLqP5VEhdkAS6EPFLC1PHnBqCXEpPxuEb. Inspect current extensions before selecting account-derivation or transfer tooling; a balance read does not test transfers. [Solana Foundation: OUSD and Token-2022 ↗](https://solana.com/news/open-usd-is-live-on-solana) [openusd.dev: Solana read-only RPC evidence, October 12 ↗](https://openusd.dev/data/observations/ousd-solana-2026-10-12.json) The native OUSD listing does not establish a Devnet deployment or every provider’s Solana OUSD route. This reference has not tested OUSD transfers or provider integrations on Solana. [Open Standard: Build with Open USD ↗](https://joinopenstandard.com/integrate) [Solana: Clusters and public RPC endpoints ↗](https://solana.com/docs/references/clusters) ## Provider routes involving Solana These records name Solana 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/)