16 posts.
Ronin became an OP Stack layer 2 in May 2026. Measured: 2 s blocks, a fixed 20 gwei base fee, a 200-block getLogs cap, ~23 min to finalized, and no pre-migration history.
Read →opBNB is an OP Stack L2 settling to BNB Smart Chain, with 250 ms blocks. Measured finality, fees, the 50,000-block getLogs cap and a stale-finality trap.
Read →Katana (chain ID 747474) is an OP Stack L2 with ZK proofs and 1-second blocks. Measured finality, fees, getLogs limits, archive access and code.
Read →How to connect to Arbitrum One over JSON-RPC — chain ID 42161, why the block gas limit is a sentinel value, what safe and finalized actually mean here, zero priority fees, and where archive reads stop working.
Read →Boba Network mainnet RPC endpoint and chain ID 288 — the EVM optimistic rollup where smart contracts can call off-chain compute and APIs. Live fee numbers, block cadence, what carries over from Ethereum, and what to verify.
Read →Optimism (chain ID 10) is both a mature optimistic rollup — 2-second blocks, ETH gas, fault proofs live since 2024 — and the origin of the OP Stack, the codebase behind Base, Zora, opBNB, Unichain, and Soneium. The developer map: what the two-layer fee model means for gas estimation, why traces are uneven there, and how everything you learn on OP Mainnet carries across the family.
Read →Scroll is a bytecode-equivalent zkEVM rollup (chain ID 534352) — it targets opcode-level equality with Ethereum, so your existing contracts, audits, and tooling work with zero changes, while ZK validity proofs give ~1-hour hard finality instead of the 7-day optimistic window. Standard eth_* (viem/ethers/foundry). Here's the developer map, including how it differs from zkSync Era.
Read →L2s differ on two independent axes: how they prove state (validity/ZK proofs vs fraud proofs) and where they put data availability (on Ethereum vs off-chain). Those two choices give you rollups, validiums, and optimiums — with real differences in cost, security, and worst-case fund recovery. Here's the taxonomy, plainly, and why it matters for developers.
Read →Manta Pacific is an EVM OP Stack L2 (chain ID 169) that posts its data availability to Celestia instead of Ethereum — making it a validium, and making it cheap. It's standard EVM (viem/ethers/foundry work), with ETH gas and a ~7-day optimistic withdrawal window. Here's the developer map, including what modular DA changes about how you reason on security.
Read →Metis is an EVM-equivalent optimistic rollup (chain ID 1088) notable for moving from a single sequencer to a sequencer pool — reducing the single-operator risk most L2s still carry. It's standard EVM (viem/ethers/foundry work), with METIS (not ETH) as gas. Here's the developer map, including what sequencer decentralization does and doesn't change for you.
Read →Starknet is a non-EVM validity (ZK) rollup where contracts are Cairo, not Solidity. The RPC is JSON-RPC over HTTP — but it's the starknet_* namespace, not eth_*, so viem/ethers/foundry don't connect. Accounts are contracts (native AA, no EOAs), values are felts, and finality comes from STARK proofs with no challenge window. Here's the developer map, including the eth_* → starknet_* method translation.
Read →Blast is an Ethereum L2 (chain ID 81457) with native yield — bridged ETH and USDB rebase into accounts automatically, no action required. It's standard EVM (viem/ethers work), but the rebasing changes balances with no Transfer event and contracts default to Void yield mode. Here's the developer map, including how native yield reshapes indexing and contract design.
Read →Fraxtal is Frax Finance's OP Stack L2 (chain ID 252) with two twists most Superchain L2s don't have: gas is paid in FRAX, not ETH, and its Flox system pays contract developers FXTL points for the gas their users spend. It's standard EVM (viem/ethers/foundry work), with ~2s blocks and the usual ~7-day OP Stack withdrawal window. Here's the developer map.
Read →Unichain is Uniswap's own L2 — an OP Stack rollup on the Optimism Superchain, purpose-built for DeFi with ~1s blocks. It speaks standard eth_* JSON-RPC, so viem and ethers just work. Here's the chain ID, what carries over from Ethereum, and the Superchain and finality details that actually matter.
Read →zkSync Era speaks the eth_* JSON-RPC you already know — until it doesn't. Native account abstraction, a zks_ method namespace, a pubdata gas model, and non-standard deployment all trip up devs who treat it like plain Ethereum. Here's what actually differs.
Read →If your L2 fees dropped through the floor in 2024, blobs are why. Here's what EIP-4844 blobs actually are, why they're cheap and temporary, how data availability works, and what changes for you as a developer reading the chain.
Read →