zkSync Era RPC Endpoint

Flat-rate zkSync Era RPC provider and zkSync Era RPC node access: free tier, no KYC, HTTP & WebSocket. zkSync Era mainnet chain ID 324.

zkSync Era is a general-purpose zk-rollup developed by Matter Labs. It pioneered native account abstraction at the protocol level, allowing every account to be a smart contract with custom signing, gas payment, and multi-sig logic.

About zkSync Era

zkSync Era launched mainnet alpha in March 2023. It uses a custom zkEVM (not fully bytecode-equivalent — closer to language-equivalent), requiring contracts to be recompiled with the zkSync compiler. The tradeoff is significantly cheaper proof generation and unique features like native AA.

Native account abstraction means every wallet on zkSync Era can use arbitrary signature schemes (passkeys, multi-sig, social recovery), pay gas in any token, and batch operations natively — no EIP-4337 bundler required. This is the biggest architectural divergence from other zkEVMs.

Common Use Cases on zkSync Era

• Wallets with custom signature schemes (passkeys, social recovery)
• Gasless dApps (sponsor pays user gas)
• DeFi with token-flexible gas payment
• ZK chains via ZK Stack (sovereign rollups on zkSync infrastructure)
• High-frequency trading with low fees

zkSync Era Ecosystem

SyncSwap, Maverick (DEXes), Aave V3, native AA-first wallets (Clave). The ZK Stack lets other teams launch sovereign rollups (hyperchains) on zkSync infrastructure — analogous to OP Stack but with zk proofs.

zkSync Era Mainnet RPC URL (HTTP)

zkSync Era WebSocket RPC URL

Quick Start: Connect to zkSync Era

cURL

curl -X POST https://rpc.swiftnodes.io/rpc/zksync?key=YOUR_API_KEY \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","method":"eth_blockNumber","params":[],"id":1}'

ethers.js

import { JsonRpcProvider } from "ethers";

const provider = new JsonRpcProvider(
  "https://rpc.swiftnodes.io/rpc/zksync?key=YOUR_API_KEY"
);

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

viem

import { createPublicClient, http } from "viem";

const client = createPublicClient({
  transport: http("https://rpc.swiftnodes.io/rpc/zksync?key=YOUR_API_KEY"),
});

const blockNumber = await client.getBlockNumber();

web3.py

from web3 import Web3

w3 = Web3(Web3.HTTPProvider("https://rpc.swiftnodes.io/rpc/zksync?key=YOUR_API_KEY"))
print("zkSync Era block:", w3.eth.block_number)

Add zkSync Era to MetaMask

Bridging to zkSync Era

Native bridge (https://bridge.zksync.io) for Ethereum ↔ zkSync Era. Across, Stargate, Squid for fast alternatives.

Features of SwiftNodes for zkSync Era

• Load-balanced across multiple upstream nodes wherever a chain has more than one, with automatic failover
• Health-checked every 2 minutes with automatic failover
• Free tier available — no credit card or KYC required
• Flat-rate monthly pricing with no per-request fees
• HTTP and WebSocket support
• One API key works across all 75+ supported chains, including zkSync Era

Rate Limits

Frequently Asked Questions: zkSync Era

zkSync Era RPC methods

Measured weekly through this endpoint: what each method returns on zkSync Era, its limits, and an example request.

• eth_getLogssupported
• eth_getBlockReceiptssupported
• eth_feeHistorysupported
• eth_getProofnot available
• eth_createAccessListnot available
• debug_traceCallsupported
• trace_blocknot available
• trace_transactionnot available

zkSync Era guides from the blog

• zkSync Era RPC: What Differs from EthereumzkSync 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.

Related L2 & rollup chains

Explore RPC endpoints for other L2 & rollup networks on SwiftNodes: