Use Solana dApps and test networks

How to do it

1. In the dApp, choose the Solana cluster you intend to use and connect with WalletConnect.
2. Approve the requested cluster in Oath and verify the selected wallet/account. Devnet and Testnet are separate networks from mainnet.
3. When a request arrives, read its network, fee payer, fee and simulated SOL or token balance changes.
4. Inspect mint identities and invoked programs, particularly when a token name is unavailable or inspection is incomplete.
5. For a signing-only request, understand that the dApp receives a signed transaction. For sign-and-send, follow the pending result until confirmation or failure.
6. When testing, use only test-cluster assets and check the corresponding explorer. Test-cluster submissions do not become mainnet balances or mainnet history.

The selected Solana derivation must match the account requested by the dApp. Switching accounts can invalidate a pending review.

Supported flows include readable message signing, legacy and version-0 transaction signing, supported transaction batches and sign-and-send. Unknown cluster aliases, unsupported versions and durable-nonce transactions are not silently converted to mainnet.

A batch is not a guarantee of atomic execution. Transactions that depend on an earlier batch member can fail independent simulation; Oath does not blindly approve them.