RISE RPC for onchain trading

RISE specializes in trading rather than general-purpose activity, with onchain orderbooks running in the same EVM as the rest of its DeFi. Its Continuous Block Pipeline executes transactions as they arrive instead of pausing for block building, and Shreds split each 1-second block into sequencer-signed sub-blocks that return preconfirmations in milliseconds. Data is posted to EigenDA with Ethereum as fallback, and disputes are settled through ZK Fraud Proofs, which replace multi-round fault games with a single validity proof. The chain stays EVM-compatible, so Solidity contracts and standard tooling deploy without changes.

GetBlock provides managed RPC access to RISE mainnet with JSON-RPC and WebSocket. Endpoints expose the full eth_, net_, and web3_ namespaces plus debug_ tracing methods. GetBlock handles node operations, upgrades, and monitoring, so teams can focus on trading logic and app development instead of infrastructure.

Any EVM-compatible wallet, including MetaMask, mobile wallets, and hardware wallets, can connect to RISE. On the SDK side, viem ships a built-in RISE chain definition, and ethers.js, web3.py, and other EVM libraries work with a standard JSON-RPC provider. Foundry and Hardhat deploy to RISE like any other EVM network. RISE also publishes an official shreds package that extends viem with Shreds-specific actions.

RISE RPC nodes return account balances, nonces, contract bytecode, and storage values, along with blocks, transactions, receipts, and event logs. They also simulate calls with eth_call, estimate gas, generate access lists, and return Merkle proofs via eth_getProof. With debug_ methods, developers can trace transactions and blocks to inspect execution step by step, which helps when debugging order matching or liquidation logic.

Create a RISE mainnet endpoint in the GetBlock dashboard and copy the HTTPS URL or the WebSocket URL for subscriptions. Point your SDK or wallet to that URL and set chain ID 4153. You can verify the connection by calling eth_chainId, which should return 0x1039.

RISE supports the standard Ethereum JSON-RPC methods. The most used are eth_blockNumber and eth_getBlockByNumber for chain state, eth_getBalance and eth_call for reads, eth_estimateGas and eth_sendRawTransaction for submitting transactions, and eth_getLogs and eth_getTransactionReceipt for events and results. Note one EVM difference: because RISE pre-executes transactions, BLOCKHASH reads of the pending block fail, while historical block hashes work normally.

RISE endpoints support WebSocket connections with eth_subscribe for newHeads, logs, and newPendingTransactions events. This lets apps track new blocks, contract events such as order fills, and incoming transactions.

The RISE mainnet chain ID is 4153, or 0x1039 in hexadecimal. RISE Testnet uses chain ID 11155931 (0xAA39DB). Wallets and libraries use the chain ID to sign replay-protected transactions under EIP-155, so a mismatch between chain ID and endpoint will cause transactions to be rejected.