Solana Beta is now live
Try it free
zkSync Era's account abstraction and paymaster flows need reliable RPC. Dedicated endpoints with zks_ method support 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/zksync?auth=YOUR_API_KEY wss://eu.endpoints.matrixed.link/ws/zksync?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/zksync?auth=YOUR_API_KEY"
);About zkSync
Connect your dApp, bot, or protocol to zkSync Era Mainnet with BoltRPC. As the ZK chain ecosystem matures and TVL grows, having reliable RPC infrastructure with predictable request-unit pricing lets you scale without renegotiating costs.
| Chain ID | 324 |
| Protocol | ZK Rollup (zkEVM) on ETH |
| Block time | ~1 s |
| Native token | ETH |
| Finality | ZK proof verification on Ethereum (~1-3 hours) |
| EVM compatible | Yes (EVM-compatible) |
zkSync Era is Matter Labs’ ZK rollup, designed for developer-friendly ZK infrastructure with native account abstraction built into the protocol. Every account on zkSync Era can be a smart contract wallet, enabling session keys, gas sponsorship and social recovery without separate EIP-4337 infrastructure. The ecosystem includes native DEXs, lending protocols, and a growing developer grants program. zkSync Era targets developers who want Ethereum security with ZK finality and a programmable account model not available on standard EVM chains.
zkSync Era is EVM-compatible but not EVM-equivalent. Most Ethereum smart contracts deploy without changes, but there are known differences developers should check before assuming full compatibility. Specifically, some EVM opcodes behave differently on zkSync Era: SELFDESTRUCT is not supported, EXTCODECOPY has restrictions, and some low-level assembly patterns may behave unexpectedly. The zkSync documentation maintains a full list of differences. Standard Solidity contracts using common patterns (ERC-20, ERC-721, Uniswap-style AMMs) typically work without changes.
Native account abstraction on zkSync Era means every account is a smart contract by default. This has implications for how RPC calls work: eth_getCode on a zkSync Era address returns contract bytecode even for externally owned accounts, and some libraries that check for contract vs. EOA using msg.sender == tx.origin may behave differently. Teams building wallet apps or tools that inspect account types should account for zkSync’s AA-first account model.
The zkSync Era JSON-RPC extends the standard eth_* methods with zkSync-specific methods like zks_getBlockDetails, zks_getBridgeContracts, and zks_getTransactionDetails. BoltRPC supports the full zkSync Era JSON-RPC specification including these extensions. If your application needs to query proof batch status, bridge contract addresses, or zkSync-specific transaction details, these methods are available alongside the standard EVM interface.
Why BoltRPC
zkSync Era's DeFi TVL is growing as more protocols deploy. Reliable infrastructure becomes more critical as the value of assets depending on your RPC increases. BoltRPC provides dedicated capacity with predictable request-unit pricing that does not scale against you as your usage grows.
zkSync Era has native account abstraction built into the protocol. AA-powered dApps generate more RPC calls per user interaction than standard EOA wallets: fee estimation for paymasters, validation calls, and signature verification all add up. BoltRPC handles the higher call volume without degradation.
zkSync Era's proving pipeline means nodes process significant data alongside standard JSON-RPC requests. BoltRPC's infrastructure is sized for this load, not just for standard EVM traffic.
zkSync Era is EVM-compatible. Most Ethereum code deploys with minor adjustments, and the same JSON-RPC methods apply. Teams migrating from Ethereum or other EVM chains can connect in minutes.
Subscribe to account changes and new blocks via WebSocket. Essential for account abstraction wallets tracking session key states and paymaster events.
BoltRPC supports the complete zkSync Era JSON-RPC specification including all eth_* methods and zkSync-specific extensions like zks_getBlockDetails and zks_getTransactionDetails.
Methods
Every standard zkSync method you'd expect. Archive-only methods are available on request for qualifying plans.
standard
5 eth_call eth_estimateGas eth_getTransactionReceipt eth_sendRawTransaction eth_blockNumber FAQ
Common questions about connecting to zkSync 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.