What is the Scroll RPC URL?

The Scroll Mainnet RPC URL with BoltRPC is https://endpoints.boltrpc.io/rpc/YOUR_API_KEY/scroll. Replace YOUR_API_KEY with your API key from dashboard.boltrpc.io. The chain ID is 534352.

Do existing Ethereum smart contracts work on Scroll without changes?

Yes. Scroll is designed for bytecode-level EVM equivalence. Ethereum smart contracts deploy on Scroll without any modifications. The same Solidity code, same tooling and same RPC methods all work as-is.

What makes Scroll different from other zkEVMs?

Scroll prioritises bytecode-level EVM equivalence, meaning Ethereum smart contracts deploy without modifications. Other zkEVMs make trade-offs that require minor changes. Scroll is the simplest migration path for existing Ethereum projects.

How do I add Scroll to MetaMask?

Open MetaMask, go to Settings, then Networks, then Add Network and enter: Network Name: BoltRPC Scroll, RPC URL: https://endpoints.boltrpc.io/rpc/YOUR_API_KEY/scroll, Chain ID: 534352, Currency Symbol: ETH, Block Explorer: https://scrollscan.com.

What is the difference between Scroll and Linea?

Both are zkEVM L2s settling to Ethereum. Scroll focuses on bytecode-level EVM equivalence for lowest-friction Ethereum migration. Linea is built by ConsenSys and integrates natively with MetaMask. Both use zero-knowledge proofs.

Does BoltRPC support WebSocket for Scroll?

Yes. BoltRPC provides WebSocket endpoints for Scroll at wss://endpoints.boltrpc.io/ws/YOUR_API_KEY/scroll. Use WebSocket for real-time event subscriptions: new blocks, pending transactions, contract event logs.

What is Scroll's approach to ZK proof generation?

Scroll generates ZK proofs that verify EVM execution at the bytecode level, enabling exact EVM compatibility. Proofs are submitted to Ethereum in batches and once verified, transactions achieve finality in approximately 1 to 2 hours.

Does BoltRPC provide Scroll archive access?

Yes. BoltRPC serves Scroll with full archive access: historical balances, contract state at any block and the debug tracing methods (debug_traceTransaction, debug_traceBlockByNumber, debug_traceCall), all on the standard endpoint.

Scroll RPC Endpoint

Scroll's ZK-EVM stays true to Ethereum semantics. Your existing tooling works day one on a dedicated endpoint with WebSocket included.

chain id · 534352JSON-RPC 2.0WebSocketFull archiveDebug

Start free trial Contact sales

LIVE LATENCY

17ms

LIVE

gateway round-trip · sampled every second

IN PRODUCTION AT Chainlink

Your endpoint, ready in one line.

Drop this URL into your RPC client, HTTP library or wallet config. No SDK install required.

HTTPS

https://endpoints.boltrpc.io/rpc/YOUR_API_KEY/scroll

WEBSOCKET

wss://endpoints.boltrpc.io/ws/YOUR_API_KEY/scroll

Replace YOUR_API_KEY with your API key. Get a free key →

Pick your stack.

Copy-paste examples for the libraries you already use. Swap the API key, hit run.

import { ethers } from "ethers";

const provider = new ethers.JsonRpcProvider(
  "https://endpoints.boltrpc.io/rpc/YOUR_API_KEY/scroll"
);

const blockNumber = await provider.getBlockNumber();
console.log("Latest block:", blockNumber);

import { createPublicClient, http } from "viem";
import { scroll } from "viem/chains";

const client = createPublicClient({
  chain: scroll,
  transport: http("https://endpoints.boltrpc.io/rpc/YOUR_API_KEY/scroll"),
});

const blockNumber = await client.getBlockNumber();
console.log("Latest block:", blockNumber);

curl https://endpoints.boltrpc.io/rpc/YOUR_API_KEY/scroll \
  -X POST \
  -H "Content-Type: application/json" \
  --data '{"jsonrpc":"2.0","method":"eth_blockNumber","params":[],"id":1}'

Connect your dApp, bot, or protocol to Scroll Mainnet with BoltRPC. For ZK-native developers who built on Ethereum and want the lowest-friction migration path, Scroll’s bytecode equivalence means your existing toolchain works unchanged and BoltRPC’s predictable request-unit pricing means your infrastructure costs stay predictable.

Chain at a Glance


Chain ID	534352
Protocol	ZK Rollup on ETH
Block time	~3 s
Native token	ETH
Finality	ZK proof verification on Ethereum (~1-2 hours)
EVM compatible	Yes

What Scroll is Built For

Scroll is a bytecode-compatible ZK rollup designed for maximum EVM equivalence. Its architecture prioritizes exact compatibility with the Ethereum Virtual Machine at the bytecode level, meaning smart contracts deployed on Ethereum can be deployed on Scroll without any code modifications. Existing Ethereum tooling, including Hardhat, Foundry, Remix and all standard Solidity libraries, works without changes. Scroll’s developer ecosystem is built around teams that want ZK proof security without the friction of a new execution environment. Its DeFi ecosystem is growing as Ethereum projects find Scroll to be the simplest migration path among all available ZK rollups.

Developer Notes for Scroll

Scroll is designed to be as close to Ethereum as technically possible at the bytecode level. In practice, this means a Solidity developer can deploy to Scroll using Hardhat or Foundry with no changes to their deployment scripts, the same private keys and the same ABI and contract addresses on the destination chain (assuming deterministic deployment). The only required change is the RPC endpoint and chain ID (534352).

One area where Scroll differs from standard EVM behavior is gas behavior under ZK proof constraints. While Scroll aims for EVM equivalence, some gas operations at the bytecode level may behave slightly differently due to proof circuit constraints. The Scroll documentation maintains a list of any known EVM-equivalent gaps. For most DeFi and NFT contracts, no differences will be encountered. For contracts that use low-level assembly or rely on precise gas metering, testing on Scroll before deploying to mainnet is recommended.

Scroll’s ZK proof verification timeline means that transaction finality has two distinct stages: sequencer confirmation (fast, within seconds) and Ethereum-verified ZK finality (1 to 2 hours). For applications that query eth_getTransactionReceipt immediately after sending a transaction, the transaction will appear confirmed at the sequencer stage. Bridge withdrawals and cross-chain processes that depend on cryptographic finality must wait for the ZK proof submission to Ethereum.

Common Use Cases on Scroll

Ethereum protocols deploying unchanged Bytecode equivalence means the same contracts and the same read patterns move over: eth_call polling, event streams and receipt confirmation, now at ZK rollup fees.

DeFi on a ZK rollup DEXes, lending markets and yield protocols on Scroll run the classic loop of continuous state reads plus WebSocket subscriptions for swaps and liquidations. The full eth_* surface is available.

Indexers and analytics Full archive access on the standard endpoint lets an indexer backfill Scroll from genesis and keep streaming new blocks without a second provider.

Debugging and transaction forensics debug_traceTransaction replays any Scroll transaction step by step. Protocol teams use it for incident review and integrators use it to see exactly why a call reverted.

Built for teams that ship on Scroll.

EVM-equivalent tooling, no surprises

Scroll is a zkEVM-equivalent L2 designed for maximum bytecode compatibility with Ethereum. Contracts deploy on Scroll without modification, making it the lowest-friction zkEVM migration path. The same RPC calls, same ABIs, same deployment flow, only the endpoint changes. This means your existing RPC integration requires no adjustment when moving to Scroll.

Growing DeFi ecosystem needs stable RPC

Scroll's DeFi ecosystem is expanding as more Ethereum projects discover its compatibility advantages. Production protocols require consistent RPC rather than the congested public endpoints, which hit rate limits and return errors under load.

Predictable RU pricing for ZK-native infrastructure costs

ZK proof verification adds compute overhead that some providers pass on through opaque billing. BoltRPC prices every method with a fixed, published request-unit weight, so you pay for a plan sized to your call mix, not for unpredictable proof complexity. Your Scroll development and production costs stay predictable.

Full EVM compatibility

Any Ethereum code deploys on Scroll as-is. Switch the RPC endpoint and you're done.

WebSocket for Scroll event streaming

Subscribe to Scroll contract events and new blocks via WebSocket. The same subscription patterns used on Ethereum work on Scroll without changes.

One provider across all major zkEVMs

BoltRPC supports Scroll alongside Linea and zkSync Era. If you are evaluating zkEVM chains or running multi-chain deployments, one API key covers all three.

Full archive access included

BoltRPC serves Scroll with full historical state since genesis. Balance-at-block lookups, historical eth_call reads and audit exports run on the standard endpoint, without a separate archive provider.

Debug methods included

debug_traceTransaction, debug_traceBlockByNumber and debug_traceCall are available on Scroll, so you can replay any transaction or contract call step by step without running your own node.

Full JSON-RPC coverage.

Every standard Scroll method you would expect. Archive-only methods are available on request for qualifying plans.

STANDARD8

eth_calleth_blockNumbereth_estimateGaseth_getTransactionReceipteth_sendRawTransactioneth_getBalanceeth_calldebug_traceTransaction

Scroll, explained.

Common questions about connecting to Scroll over BoltRPC.

Ask a question →Read the docs

: The Scroll Mainnet RPC URL with BoltRPC is https://endpoints.boltrpc.io/rpc/YOUR_API_KEY/scroll. Replace YOUR_API_KEY with your API key from dashboard.boltrpc.io. The chain ID is 534352.
: Yes. Scroll is designed for bytecode-level EVM equivalence, which means Ethereum smart contracts deploy on Scroll without any modifications. The same Solidity code, the same tooling (Hardhat, Foundry, Remix) and the same RPC methods all work as-is.
: Scroll prioritises bytecode-level EVM equivalence, meaning Ethereum smart contracts deploy without modifications. Other zkEVMs make trade-offs that require minor contract changes. Scroll prioritises full compatibility over other optimizations, making it the simplest migration path for existing Ethereum projects.
: Open MetaMask, go to Settings, then Networks, then Add Network and enter: Network Name: BoltRPC Scroll, RPC URL: https://endpoints.boltrpc.io/rpc/YOUR_API_KEY/scroll, Chain ID: 534352, Currency Symbol: ETH, Block Explorer: https://scrollscan.com.
: Both are zkEVM L2s settling to Ethereum. Scroll focuses on bytecode-level EVM equivalence for the lowest-friction migration from Ethereum. Linea is built by ConsenSys and integrates natively with MetaMask. Both use zero-knowledge proofs. BoltRPC supports both Scroll and Linea.
: Yes. BoltRPC provides WebSocket endpoints for Scroll at wss://endpoints.boltrpc.io/ws/YOUR_API_KEY/scroll. Use WebSocket for real-time Scroll event subscriptions: new blocks, pending transactions, contract event logs.
: Scroll generates ZK proofs that verify the correctness of EVM execution at the bytecode level. This is more computationally intensive than other ZK approaches, but it enables exact EVM compatibility. Proofs are submitted to Ethereum in batches. Once verified, the transactions in that batch achieve finality. This process typically takes 1 to 2 hours for full cryptographic finality.
: Yes. BoltRPC serves Scroll with full archive access: historical balances, contract state at any block and the debug tracing methods (debug_traceTransaction, debug_traceBlockByNumber, debug_traceCall), all on the standard endpoint.

Ship on Scroll this week.

An API key in under 60 seconds, Scroll plus 35+ other chains, and a team that answers when you write.

Start free trial View pricing