您正在運行一個Hyperliquid 節點嗎？透過Hyperliquid 對等連線，為區塊和完整的記憶池啟用直連路徑。
了解更多已通過 SOC 2 Type II 認證 · ISO 27001
Tempo 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.
Six ways to access Tempo 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 Tempo mainnet and Tempo Testnet. Every EVM method supported, including eth_call, eth_getLogs, eth_getBalance, eth_sendRawTransaction, and eth_subscribe, with predictable rate limits.
Tempo is a payments-first EVM layer 1, so the tooling you already know works unchanged. ethers.js, web3.js, viem, and web3.py all hit a Quicknode Tempo endpoint the same way they hit Ethereum. Same methods, same SDK, just a different RPC URL.
Point your existing Ethereum codebase at a Quicknode Tempo 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.
Open MetaMask, go to Settings, Networks, Add Network, and enter your Quicknode Tempo 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 Tempo workload. Clone, customize, and ship.
Full reference for every Tempo 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 Tempo.
From your first Tempo endpoint to mission-critical production workloads, Quicknode scales with you. Get started in minutes.
Spin up your Tempo endpoint and ship. The free tier covers prototyping and small production loads, no credit card required.
Dedicated Tempo infrastructure, contractual SLAs, priority support, and procurement-ready terms for wallets, exchanges, trading firms, and high-volume protocols.
常見問題
Still have unanswered questions? Reach out to support and the Quicknode team can help you find answers.
Query, subscribe, and stream Tempo data with low latency. From a single eth_call to billions of rows of historical logs, you get the right interface for the job.
The Ethereum toolchain you already know works unchanged on Tempo. Deploy contracts, manage endpoints, and ship from one Quicknode account.
Full historical state with no pruning, plus the deep analysis namespaces. Run debug_traceTransaction and trace_block against Tempo archive nodes for indexing, simulation, and analytics.
Backfill and real-time Tempo blocks, logs, and traces delivered to your datastore with guaranteed reliability. Filter upstream, receive only the data you actually need.
具備傳送保證、重試機制及內建重組處理功能的事件驅動式警示。訂閱特定地址、合約事件或鏈上條件，並即時做出反應。
Tempo-native methods alongside standard Ethereum JSON-RPC. Query payments-focused endpoints, then fall back to eth, debug, and trace on the same account.
Subscribe to new Tempo blocks and logs over a persistent WSS connection with eth_subscribe. Push updates the moment they land, with no polling.
// Your Ethereum code, pointed at Tempoimport { createPublicClient, http } from "viem";const client = createPublicClient({// Tempo mainnet, chain ID 4217chain: { id: 4217, name: "Tempo" },transport: http(QUICKNODE_TEMPO_URL)});const block = await client.getBlockNumber();// Same methods, same SDK. Tempo is a payments-first EVM layer 1.
Runnable sample apps and starter kits across Quicknode-supported chains, including Tempo. Clone one and ship.
"Our users share one link, pay3.so/@username, and their sender just pays. No addresses, no chain confusion, no 'did it go through?' messages. They just see 'payment received.' Quicknode Streams is what makes that real across four chains simultaneously, and it's the same infrastructure we're now extending to merchants without rebuilding a thing."Varun, Founder & CEO @ pay3