🔹Public RPC Specs

Orbion Testnet provides high-availability JSON-RPC endpoints that are fully compatible with the Ethereum RPC standard. These endpoints are intended for developers, dApps, indexers, and wallets seeking quick access to blockchain state, transactions, and contract interaction — without running a full node.


✅ Supported Protocols

Type
Status

HTTPS (HTTP/1.1)

✅ Enabled

WebSocket (WS)

❌ Not yet available

HTTP POST only

✅ Standard RPC method support

CORS Enabled

✅ Allows browser-based requests

Note: WebSocket support may be added in a future upgrade.


🌐 RPC Endpoint URLs

https://rpctestnet-1.orbionchain.com
https://rpctestnet-2.orbionchain.com

You may use either endpoint interchangeably. They are load-balanced and monitored for uptime.


📡 Network Info

Parameter
Value

Network Name

Orbion Testnet

Chain ID

109901

Currency Symbol

ORB


🧠 Supported Methods

Orbion supports the Ethereum JSON-RPC 1.0 spec, including:

  • Read Methods eth_blockNumber, eth_getBalance, eth_call, eth_getLogs, eth_getTransactionByHash, eth_getCode, net_version, web3_clientVersion

  • Write Methods eth_sendRawTransaction, eth_estimateGas, eth_sendTransaction (for unlocked nodes only)

  • Other eth_chainId, eth_gasPrice, eth_feeHistory, eth_getTransactionCount

Compatible with MetaMask, Hardhat, Foundry, Remix, and Web3.js / Ethers.js libraries.


🔧 Use Cases

  • dApp frontend integration

  • Automated deployment scripts

  • Indexing and event listeners

  • Contract interaction / signing

  • Monitoring tools and dashboards


📉 Performance & Redundancy

  • Geo-distributed routing

  • Load-balanced across multiple nodes

  • Rate limited per IP for fair access (see next section)

  • Auto-recovery on service failure (≥99.5% testnet SLA)


Orbion’s public RPC is designed to support rapid prototyping and light-to-moderate application traffic. For high-throughput production usage, we recommend running your own dedicated node.

Last updated