Read ZKsync state, build smart-account flows, and send transactions with reliable, high-performance ZKsync Era RPC infrastructure.
Connect to ZKsync Era Mainnet or Sepolia over HTTPS and WebSocket. Use Ethereum JSON-RPC alongside ZKsync-specific APIs for batches, fees, and transaction details.
Build ZKsync Era applications with historical state, native ZKsync APIs, and predictable RPC capacity.
Run ZKsync Era indexers and application backends with unlimited requests within your selected RPS tier. Keep monthly RPC costs predictable as request volume grows.
Query historical contract state and backfill event logs for ZKsync Era indexers, accounting, and DeFi analytics.
Inspect ZKsync Era execution with debug APIs on a paid archive-mode node. Diagnose reverted calls and follow transaction execution.
Use native account abstraction and paymasters for sponsored transactions and custom wallet flows. Connect zksync-ethers when your app needs Era-specific features.
Read the paymaster tutorial
Read contract state, simulate calls, and submit signed transactions. Connect Solidity applications through Ethereum tooling or the ZKsync SDK.
Explore ZKsync tooling
Combine Ethereum event logs with zks_getTransactionDetails and batch APIs. Track application activity through L2 execution and L1 publication.
Explore ZKsync methods
Use debug APIs on a paid archive-mode node to investigate reverted calls and transaction execution.
Explore ZKsync debug APIs
Connect to chain ID 300 and exercise your integration with testnet ETH. Keep testnet credentials separate from your mainnet endpoint.
Explore ZKsync network detailsChoose ZKsync Era mainnet or Sepolia and an available node configuration to estimate monthly infrastructure costs.
Choose an available ZKsync Era network and node configuration to estimate monthly infrastructure costs.
Save over 50% on our elite pay as you go plan
Chat on Telegram (opens in a new tab)Customer stories from teams using Chainstack across supported networks.
Chainstack’s robust infrastructure has significantly enhanced our ability to secure Web3 environments effectively.Chainstack has been crucial in enhancing Brave Wallet’s multi-chain functionality and UX.The Unlimited Node flat-fee model gives us cost predictability, and the performance is rock-solidWe’ve gone from weekly incidents to zero incidents.Working with Chainstack helped us cut our infrastructure costs by over 70%, all while tackling intricate challenges in Web3 security.Combine Ethereum JSON-RPC with ZKsync-specific fee and transaction APIs. Build paymaster flows, query L1 batches, and track L2 execution without maintaining a node.
Get a ZKsync Era endpointGet ZKsync Era Sepolia testnet ETH from the Chainstack faucet. Deploy contracts, test wallet flows, and exercise your RPC integration before using real assets on mainnet.
Get ZKsync testnet ETH (opens in a new tab)
Read token-transfer events from the latest ZKsync Era block with eth_getLogs.
AI-ready infrastructure
Refer and earn
Ethereum
Hyperliquid
Solana
Arbitrum
BNB Smart Chain
Base
Polygon
TRON
Sui
Robinhood
SOC 2 Type II
ISO 27001
99.99%+ uptime
Learn morehttps://zksync-mainnet.core.chainstack.com/YOUR_ENDPOINT_IDwss://zksync-mainnet.core.chainstack.com/YOUR_ENDPOINT_IDCreate a ZKsync Era node. Copy your authenticated HTTPS URL from Access and credentials and replace YOUR_ENDPOINT_ID in the example.
curl --request POST \
--url https://zksync-mainnet.core.chainstack.com/YOUR_ENDPOINT_ID \
--header 'Content-Type: application/json' \
--data '{
"jsonrpc": "2.0",
"id": 1,
"method": "eth_getLogs",
"params": [
{
"fromBlock": "latest",
"toBlock": "latest",
"topics": [
"0xddf252ad1be2c89b69c2b068fc378daa952ba7f163c4a11628f55a4df523b3ef"
]
}
]
}'The result is an array of matching contract logs. ZKsync-specific methods such as zks_getTransactionDetails provide additional L2 and L1-batch information.
Start with free ZKsync Era RPC. Scale your application with paid plans, higher throughput, and dedicated infrastructure.
Includes:
All Developer features, plus:
Add-ons and Dedicated Node infrastructure are billed separately.
Exceptional support on every paid planExplore ZKsync Era RPC, application development, and infrastructure guides.
Explore ZKsync infrastructure on Chainstack.
Read article
Fund a test wallet before deploying contracts.
Read article
Explore programmable accounts and wallet workflows.
Read article
Use access rules to protect application credentials.
Read article
ZKsync Era RPC connects applications to ZKsync Era through JSON-RPC over HTTPS or WebSocket. Read balances and contract state, retrieve event logs, and submit signed transactions. ZKsync also exposes native zks_* methods for fees, batches, and transaction details. See ZKsync Era developer documentation.
Create a free Chainstack account, create a project, and deploy a ZKsync Era Global Node on mainnet or Sepolia. Copy your HTTPS or WebSocket URL from Access and credentials. The Developer plan includes 3 million request units per month, up to 25 requests per second, and one node. No credit card is required.
Your mainnet HTTPS URL follows https://zksync-mainnet.core.chainstack.com/YOUR_ENDPOINT_ID. Sepolia uses https://zksync-sepolia-testnet.core.chainstack.com/YOUR_ENDPOINT_ID. Copy the complete authenticated URL from your node and replace the example endpoint ID. See the ZKsync Era tooling guide.
ZKsync Era Mainnet uses chain ID 324 (0x144). ZKsync Era Sepolia uses 300 (0x12c). The gas currency is ETH. Use the chain ID matching your endpoint when configuring a wallet or signing transactions. See the official network details.
Yes. Chainstack supports ZKsync Era Mainnet and Sepolia. Deploy a separate node for each network and use the matching chain ID and endpoint. Sepolia ETH is for testing and has no mainnet monetary value. Check supported networks.
Yes. Configure your wallet or library with your ZKsync Era RPC URL and chain ID. Use HTTPS for JSON-RPC requests and your WSS URL for supported subscriptions such as new blocks and contract logs. Use zksync-ethers for Era-specific workflows such as paymaster transactions. Follow the ZKsync Era tooling guide.
Chainstack supports ZKsync Era archive access on mainnet and Sepolia. Archive state supports historical contract reads and analytics. Archive requests are billed at 2 request units; the exact classification depends on the method and block age. Archive access is available from Growth. See request-unit rules and supported network modes.
Use a paid archive-mode ZKsync Era node to access the debug_* APIs. Do not assume every Ethereum tracer or the separate trace_* namespace is available. See ZKsync Era debug requirements.
Standard EVM bytecode can run through ZKsync Era’s EVM Bytecode Interpreter. Use normal Ethereum tooling for that path. Contracts targeting EraVM natively use ZKsync-specific compilers and plugins, while native account-abstraction and paymaster flows can use zksync-ethers. See the ZKsync tooling guide.
Call eth_getLogs with a bounded block range and the event topics you need. ERC-20 transfers use the standard Transfer(address,address,uint256) event signature. Filter by contract address for a specific token, and paginate larger backfills. The request uses standard Ethereum-compatible event-log parameters.
Start with the free Developer plan. Paid plans start at $40 per month with annual billing. Unlimited Node adds flat-fee request capacity from Growth. Dedicated Nodes require Pro or above, with infrastructure billed separately. Compare current plan features.
Use the Chainstack faucet and select ZKsync Sepolia. Testnet ETH lets you deploy contracts and test transactions without spending mainnet ETH. Connect the same wallet to ZKsync Era Sepolia, chain ID 300.
Connect to ZKsync Era Mainnet at https://zksync-mainnet.core.chainstack.com/YOUR_ENDPOINT_ID. Copy the authenticated URL from Access and credentials. Mainnet uses chain ID 324 and ETH for gas. Sepolia uses https://zksync-sepolia-testnet.core.chainstack.com/YOUR_ENDPOINT_ID and chain ID 300. See the ZKsync Era tooling guide.
Use eth_getBalance for ETH balances, eth_call for contract reads, eth_getLogs for event history, and eth_sendRawTransaction for signed transactions. Connect over WebSocket for supported new-block and log subscriptions. Use native zks_* methods for fees, transaction details, and L1 batches. ZKsync method availability describes chain-specific APIs.
