Solana Beta is now live
Try it free
Scroll's ZK-EVM stays true to Ethereum semantics. Your existing tooling works day one on a dedicated endpoint with WebSocket included.
latency
Quick connect
Drop this URL into your RPC client, HTTP library or wallet config. No SDK install required.
https://eu.endpoints.matrixed.link/rpc/scroll?auth=YOUR_API_KEY wss://eu.endpoints.matrixed.link/ws/scroll?auth=YOUR_API_KEY
Replace YOUR_API_KEY with your API key.
Get a free key →
Connect
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://eu.endpoints.matrixed.link/rpc/scroll?auth=YOUR_API_KEY"
);About Scroll
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 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 |
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.
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.
Why BoltRPC
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.
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.
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.
Any Ethereum code deploys on Scroll as-is. Switch the RPC endpoint and you're done.
Subscribe to Scroll contract events and new blocks via WebSocket. The same subscription patterns used on Ethereum work on Scroll without changes.
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.
Methods
Every standard Scroll method you'd expect. Archive-only methods are available on request for qualifying plans.
standard
5 eth_call eth_blockNumber eth_estimateGas eth_getTransactionReceipt eth_sendRawTransaction FAQ
Common questions about connecting to Scroll over BoltRPC.
Get started
One endpoint format, 20+ networks, no SDK. Drop our URL into the client you already use and your integration is done.
No credit card required. · 14-day trial on any tier.