Smart contracts on layer-1 blockchains and layer-2 networks are not identical. While L2s inherit much of their security from L1, the execution environment, fee structure, finality guarantees, and available opcodes differ in ways that matter for developers building production systems. Understanding these differences is necessary for choosing the right deployment environment and avoiding subtle bugs that only manifest in L2 contexts.
Execution Environments: EVM vs. Modified EVM
Most Ethereum L2s run modified versions of the EVM (Ethereum Virtual Machine), introducing compatibility considerations. Optimism and its OP Stack derivatives (Base, Mode, Zora) run a near-identical EVM — most contracts deploy identically, with minor differences around precompiles and gas accounting. Arbitrum runs the AVM (Arbitrum Virtual Machine), which is EVM-compatible at the Solidity source level but compiles differently — edge cases arise around BLOCKHASH (returns the L2 block hash, not L1), block.number (returns L2 block number, not L1), and gas costs that don't match Ethereum mainnet. zkSync Era uses its own zkEVM with known incompatibilities: certain precompiles are not available, SELFDESTRUCT behaves differently, and some assembly patterns fail.
Finality: Soft vs. Hard
On Ethereum mainnet, a transaction is finalized (irreversible under the protocol's economic security) after ~15 minutes (2 epochs). On optimistic rollups (Optimism, Arbitrum), transactions have "soft finality" immediately (the sequencer has included it) but "hard finality" only after the challenge period — typically 7 days — expires. For most applications, soft finality is sufficient, but for financial settlement that requires the full security of L1 (cross-chain bridges, institutional settlement), the 7-day window matters. ZK rollups (zkSync, Starknet, Scroll) achieve hard finality as soon as the validity proof is posted to L1 — typically 30 minutes to a few hours. This makes ZK rollups preferable for applications requiring fast finality with L1 security.
Gas and Fee Mechanics
L2 gas is structurally different from L1 gas. On L1, each opcode has a fixed gas cost defined in the EVM specification. On L2, costs have two components: L2 execution gas (usually much cheaper — Arbitrum's gas prices are typically 0.01–0.1 gwei vs. Ethereum's 10–100 gwei) and L1 data posting cost (the cost to include calldata in an Ethereum transaction). Contracts that post large calldata to L1 can be more expensive on L2 than expected if this component isn't accounted for. EIP-4844 (proto-danksharding), live on Ethereum and all major L2s since March 2024, introduced "blobs" — a separate data market with much cheaper L1 data costs, reducing L2 fees by 10–100x.
State Differences and Cross-Chain Complications
State on L2 is not immediately visible on L1. A contract deployed on Arbitrum doesn't exist on Ethereum mainnet; you can't call it from an L1 contract without a cross-chain messaging system. Cross-chain message passing has latency: an L1-to-L2 message typically takes 5–30 minutes to be processed on the L2; an L2-to-L1 message using optimistic rollup channels takes 7 days. This latency must be designed around in cross-chain applications — systems that assume atomic cross-chain state will behave unexpectedly.
Choosing the Right L2 for Deployment
The decision matrix: if maximum EVM compatibility is required (minimal code changes, use of obscure opcodes), Optimism or Base. If ZK security with fast finality is priority, zkSync Era or Scroll. If liquidity matters most, Arbitrum — which has the largest DeFi ecosystem of any L2 by TVL. If cost is paramount for high-throughput applications, Polygon zkEVM or Base benefit from particularly low fees post-EIP-4844. If the application is Solana-compatible, deploying on Solana L1 bypasses the EVM ecosystem entirely with a different set of tradeoffs: faster confirmation, different programming model (Rust/Anchor), and a separate liquidity ecosystem.
