您正在運行一個Hyperliquid 節點嗎？透過Hyperliquid 對等連線，為區塊和完整的記憶池啟用直連路徑。
了解更多已通過 SOC 2 Type II 認證 · ISO 27001
Ink 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 Ink 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 Ink 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 Ink mainnet and Ink Sepolia. Every EVM method supported, including eth_call, eth_getLogs, eth_getBalance, eth_sendRawTransaction, and eth_subscribe, with predictable rate limits.
Full historical Ink state with no pruning. Run debug_traceTransaction and debug_traceBlockByNumber against archive nodes for indexing and DeFi analytics.
Backfill and real-time Ink blocks, logs, and traces delivered to your datastore with guaranteed reliability. Filter upstream, receive only the data you actually need.
具備傳送保證、重試機制及內建重組處理功能的事件驅動式警示。訂閱特定地址、合約事件或鏈上條件，並即時做出反應。
Read rollup sync status and L2 output roots with optimism_syncStatus and optimism_outputAtBlock. This is the data bridges and withdrawal-proving flows use to verify Ink state against Ethereum L1.
Subscribe to new Ink blocks and logs over a persistent WSS connection with eth_subscribe. Push updates the moment they land, with no polling.
Ink is an OP Stack layer 2, so the tooling you already know works unchanged. ethers.js, web3.js, viem, and web3.py all hit a Quicknode Ink endpoint the same way they hit Ethereum. Same methods, same SDK, just a different RPC URL.
Point your existing Ethereum codebase at a Quicknode Ink endpoint and deploy. Contracts, libraries, and tooling carry over.
eth_call, eth_getLogs, eth_sendRawTransaction, and eth_subscribe all behave exactly as they do on Ethereum.
// Your Ethereum code, pointed at Inkimport { createPublicClient, http } from "viem";const client = createPublicClient({// Ink mainnet, chain ID 57073chain: { id: 57073, name: "Ink" },transport: http(QUICKNODE_INK_URL)});const block = await client.getBlockNumber();// Same methods, same SDK. Ink is an OP Stack L2.
Open MetaMask, go to Settings, Networks, Add Network, and enter your Quicknode Ink 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 Ink workload. Clone, customize, and ship.
Full reference for every Ink JSON-RPC method, WebSocket subscription, and the debug and trace 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 Ink.
Runnable sample apps and starter kits across Quicknode-supported chains, including Ink. Clone one and ship.
From your first Ink endpoint to mission-critical production workloads, Quicknode scales with you. Get started in minutes.
Spin up your Ink endpoint and ship. The free tier covers prototyping and small production loads, no credit card required.
Dedicated Ink infrastructure, contractual SLAs, priority support, and procurement-ready terms for wallets, exchanges, trading firms, and high-volume protocols.
「對於一個每毫秒都至關重要的交易平台而言Quicknode專用gRPC 展現出無與倫比的優勢。憑藉無縫的技術支援與始終如一的穩定效能，我們從第一天起便能充滿信心地進行規模擴展。」Joseph Murphy, CEO @ Rhythm
常見問題
Still have unanswered questions? Reach out to support and the Quicknode team can help you find answers.
The Ethereum toolchain you already know works unchanged on Ink. Deploy contracts, manage endpoints, and ship from one Quicknode account.