Kava RPC: A Developer's Guide (Chain ID 2222)
Kava runs an EVM beside a Cosmos SDK chain. Measured: 5.7 s blocks, instant finality, a 10,000-block getLogs cap, ~100 blocks of state, archive routing.
Read →12 posts.
Kava runs an EVM beside a Cosmos SDK chain. Measured: 5.7 s blocks, instant finality, a 10,000-block getLogs cap, ~100 blocks of state, archive routing.
Read →Aurora is an EVM running as a contract on NEAR. Measured: 0.6 s blocks, instant finality, a 2^53 gas limit, zero cumulativeGasUsed, NEAR receipt hashes.
Read →How to use Cronos EVM over JSON-RPC — chain ID 25, ~0.42 second blocks with instant finality, a 10,000-block eth_getLogs cap, historical state pruned after ~100 blocks, and no debug or trace namespace.
Read →How to query HyperEVM over JSON-RPC — chain 999, ~1s blocks, a near-fixed 0.1 gwei base fee, a 1000-block and 1 MiB eth_getLogs cap, no WebSocket, and the one that will cost you money: state methods accept a block number and then ignore it, so historical reads silently return the latest state.
Read →sn_* methods land on every paid SwiftNodes plan: token balances with metadata, multi-address portfolios, transactions with decoded logs, allowance audits, full block bundles — each one call, each counted as one request.
Read →Plasma is a stablecoin-focused EVM L1 (chain ID 9745) with a protocol paymaster that makes basic USDT transfers zero-fee — users don't even need the native token. It's standard EVM (viem/ethers work), with sub-second PlasmaBFT finality and Bitcoin anchoring. Here's the developer map, including how the gasless-stablecoin model changes payment flows.
Read →Astar is a Polkadot parachain that runs both EVM and WebAssembly contracts. Chain ID 592 is its EVM endpoint — standard eth_*, so viem/ethers/foundry just work — but underneath it's Substrate with Polkadot's deterministic GRANDPA finality. Here's the developer map: what the EVM RPC gives you, and what the parachain model changes.
Read →Flare is an EVM L1 (chain ID 14) where decentralized data feeds aren't a third-party add-on — they're enshrined in the protocol. FTSO gives you price feeds and FDC verifies cross-chain and Web2 data, both read via ordinary eth_call. viem/ethers just work; here's the developer map, including how the native data layers change what you build.
Read →WEMIX3.0 is a Korean gaming L1 from Wemade — EVM-compatible (chain ID 1111), ~1s blocks, WEMIX gas. viem and ethers just work, but two things shape how you build: a stake-based PoA council means instant finality and no reorgs, and the traffic is game-heavy. Here's the developer map.
Read →Story (chain ID 1514) is an EVM L1 purpose-built for intellectual property — registration, licensing, and royalties as protocol modules. It's CometBFT under the hood, so finality is instant, and it's standard eth_* on top, so viem just works. Here's the developer map, including how to read the IP graph.
Read →Rootstock (RSK) is an EVM sidechain merge-mined by Bitcoin — chain ID 30, RBTC gas pegged 1:1 to BTC, ~30s blocks. viem and ethers connect in one line, but two things trip up Ethereum devs: gas is denominated in Bitcoin, and addresses use an EIP-1191 checksum that standard tooling gets 'wrong'. Here's the map.
Read →Kaia is the EVM Layer 1 formed by merging Klaytn and Finschia — chain ID 8217, ~1s blocks, immediate finality, and a huge Asian user base via LINE and Kakao. It speaks standard eth_* RPC, so viem and ethers just work. Here's what carries over and the Klaytn-heritage features worth knowing.
Read →