net_version - Plasma RPC Method

Returns the current network ID on Plasma as a decimal string. The network ID identifies which network the node is connected to.

Why Plasma? Build on an EVM Layer 1 for stablecoin payments with PlasmaBFT consensus and Reth execution with 1 second blocks, XPL gas, full EVM JSON-RPC, and debug plus txpool on Dwellir.

When to Use This MethodCopy Anchor Link

net_version is essential for payment app developers, wallet teams, and teams shipping Solidity contracts for dollar transfers:

• Endpoint Identification - Confirm your application is connected to the expected Plasma network
• Multi-Chain App Routing - Dynamically detect which network an RPC endpoint serves and route logic accordingly
• Connection Validation - Perform a quick sanity check during node or provider initialization

{
  "jsonrpc": "2.0",
  "method": "net_version",
  "params": [],
  "id": 1
}

Code ExamplesCopy Anchor Link

Common Use CasesCopy Anchor Link

1. Multi-Chain Connection ValidatorCopy Anchor Link

Verify your application connects to the expected network before processing any transactions:

const EXPECTED_NETWORKS = {
  '1': 'Ethereum Mainnet',
  '137': 'Polygon',
  '42161': 'Arbitrum One',
  '10': 'Optimism',
};

async function validateNetwork(provider, expectedNetworkId) {
  const networkId = await provider.send('net_version', []);

  if (networkId !== expectedNetworkId) {
    const actual = EXPECTED_NETWORKS[networkId] || `Unknown (${networkId})`;
    const expected = EXPECTED_NETWORKS[expectedNetworkId] || expectedNetworkId;
    throw new Error(`Wrong network: connected to ${actual}, expected ${expected}`);
  }

  console.log(`Connected to ${EXPECTED_NETWORKS[networkId]}`);
  return networkId;
}

2. Dynamic Chain RouterCopy Anchor Link

Route application logic based on the detected network:

async function createChainRouter(rpcUrl) {
  const provider = new JsonRpcProvider(rpcUrl);
  const networkId = await provider.send('net_version', []);

  const config = {
    '1': { explorer: 'https://etherscan.io', confirmations: 12 },
    '137': { explorer: 'https://polygonscan.com', confirmations: 128 },
    '42161': { explorer: 'https://arbiscan.io', confirmations: 1 },
  };

  if (!config[networkId]) {
    throw new Error(`Unsupported network ID: ${networkId}`);
  }

  return { provider, networkId, ...config[networkId] };
}

3. Network ID vs Chain ID ComparisonCopy Anchor Link

Compare net_version with eth_chainId when you need both endpoint identity and signing context:

from web3 import Web3

def verify_chain_identity(rpc_url):
    w3 = Web3(Web3.HTTPProvider(rpc_url))

    network_id = int(w3.net.version)
    chain_id = w3.eth.chain_id

    if network_id != chain_id:
        print(f'Network ID ({network_id}) differs from chain ID ({chain_id})')
    else:
        print(f'Network and chain ID match: {chain_id}')

    print('Use eth_chainId as the signing source of truth')

    return {'network_id': network_id, 'chain_id': chain_id}

Best PracticesCopy Anchor Link

• Use eth_chainId for transaction signing (EIP-155 replay protection) -- net_version is for network identification only
• Cache the network ID at startup -- it does not change during a session
• Some L2 and sidechain networks share the same network ID as their L1 -- always combine with eth_chainId for unambiguous identification
• For multi-chain dApps, maintain a mapping of network IDs to chain-specific contract addresses and RPC endpoints
• The net_* namespace may be disabled on some node configurations -- handle the -32601 error gracefully

Error HandlingCopy Anchor Link

Related MethodsCopy Anchor Link

• eth_chainId - Get the EIP-155 chain ID (preferred for transaction signing)
• net_listening - Check whether the client reports peer-listening state
• net_peerCount - Get number of connected peers
• eth_syncing - Check node sync progress