Hyperliquid ノードを運用していますか？Hyperliquid のピアリング機能を使用して、ブロックおよびフルメンプールへのダイレクトパスを有効にします。
詳細はこちらConnect to ZKsync mainnet and every active testnet with low-latency RPC, full archive data, debug and trace APIs, and real-time Streams. The complete ZKsync data stack, managed from a single Quicknode dashboard.
SOC 2 タイプ II 認証取得・ISO 27001
ZKsync builders need more than basic RPC. Quicknode runs the full surface: low-latency JSON-RPC, full archive with debug and trace, and real-time Streams, all from one dashboard.
Query, subscribe, and stream ZKsync data with low latency. From a single eth_call to billions of rows of historical logs, you get the right interface for the job.
Six ways to access ZKsync data, from a single eth_call to billions of rows of queryable history. Pick the interface, ship faster.
Standard JSON-RPC over HTTPS and WSS on ZKsync Era mainnet and ZKsync Sepolia testnet, plus the zks_ namespace. Every EVM method supported, including eth_call, eth_getLogs, eth_getBalance, eth_sendRawTransaction, and eth_subscribe, with predictable rate limits.
Full historical ZKsync state with no pruning. Run debug_traceTransaction and debug_traceBlockByNumber against archive nodes for indexing and simulation.
Backfill and real-time ZKsync blocks, logs, and traces delivered to your datastore with guaranteed reliability. Filter upstream, receive only the data you actually need.
配信保証、再送信、および組み込みの再編成処理機能を備えたイベント駆動型アラート。特定のアドレス、コントラクトイベント、またはオンチェーンの条件をサブスクライブし、リアルタイムで対応できます。
ZKsync-specific zks_ methods for L2 proofs, batches, fee estimation, and account abstraction. Same endpoint as the Ethereum JSON-RPC.
eth_subscribe を使用すると、永続的な WSS 接続を介して、新しいブロック、ログ、および保留中のトランザクションを購読できます。ポーリングを行うことなく、更新情報が到着した瞬間にプッシュされます。
ZKsync Era is a zkEVM, so the EVM tooling you already know works unchanged. ethers.js, viem, and zksync-ethers hit a Quicknode ZKsync endpoint the same way they hit Ethereum. Same methods, same SDK, just a different RPC URL and chain ID 324.
Point your existing Ethereum codebase at a Quicknode ZKsync endpoint and deploy. Contracts, libraries, and tooling carry over.
eth_call、eth_getLogs、eth_sendRawTransaction、および eth_subscribe は、すべてEthereum での動作とまったく同じです。
// Your Ethereum code, pointed at ZKsyncimport { createPublicClient, http } from "viem";import { zksync } from "viem/chains";const クライアント = createPublicClient({chain: zksync,transport: http(QUICKNODE_ZKSYNC_URL)});const ブロック = await client.getBlockNumber();// Same methods, same SDK. Just chain ID 324.
Open MetaMask, go to Settings, Networks, Add Network, and enter your Quicknode ZKsync RPC URL with the details on the right. Save, and MetaMask routes through your private Quicknode endpoint instead of a rate-limited public RPC.
Docs, guides, and runnable sample apps for every ZKsync workload. Clone, customize, and ship.
Full reference for every ZKsync Era JSON-RPC method, WebSocket subscription, and the zks_ and debug namespaces. Code examples for @quicknode/sdk, ethers.js, web3.js, and viem.
Indexes token transfers on an EVM chain using Quicknode Streams and delivers them to your own datastore and API. Works unchanged on ZKsync.
Runnable sample apps and starter kits across Quicknode-supported chains, including ZKsync. Clone one and ship.
From your first ZKsync endpoint to mission-critical production workloads, Quicknode scales with you. Get started in minutes.
Spin up your ZKsync endpoint and ship. The free tier covers prototyping and small production loads, no credit card required.
Dedicated ZKsync infrastructure, contractual SLAs, priority support, and procurement-ready terms for wallets, exchanges, trading firms, and high-volume protocols.
"We run a lot of service dependencies. Quicknode's Admin API was one of the first we could plug directly into our burn rate dashboards. The MCP slots right into our cross-service incident triage stack alongside our other providers. Solid tooling that respects your time."リアム・ハリス、Defi App オペレーション責任者
よくある質問
まだ疑問が残っていますか？ サポートにお問い合わせいただくか、Quicknode （equipe ）をご利用いただければ、答えを見つけるお手伝いをいたします。
Land transactions on the same Quicknode account. The Ethereum toolchain you already know works unchanged on chain ID 324.