solana-network

To switch the Solana network to mainnet-beta safely, you must explicitly set the SOLANA_ACCEPT_RISK environment variable to true. This guarded switching mechanism prevents accidental mainnet transactions by requiring deliberate risk confirmation before applying the network context change.

Your Solana network context defaults to devnet because the switching logic reads the SOLANA_NETWORK environment variable and falls back to devnet if it is unassigned. This default ensures safe operational readiness by preventing unintended mainnet interactions during development and testing.

Yes, you can use a custom RPC URL for Solana network switching by setting the SOLANA_RPC_URL environment variable. This allows you to route account queries and transaction analysis through a specific cluster endpoint instead of relying on default public infrastructure.

The best way to prevent transacting on the wrong Solana cluster is to use an explicit network switching mechanism that defaults to devnet and requires SOLANA_ACCEPT_RISK confirmation for mainnet-beta. This makes network selection deliberate and guards against accidental production interactions.

A key limitation when changing Solana network contexts is that mainnet-beta switching is intentionally blocked unless SOLANA_ACCEPT_RISK is explicitly true. Users must also manually verify addresses, start with small transaction sizes, and simulate operations to mitigate irreversible mainnet errors.