USDC Yield With Cover Built InQuicknode Earn now runs USDC yield with cover for protocol risk built in, underwritten by OpenCover. Six covered vaults on Base.
Lesen Sie die AnkündigungSOC 2 Typ II-zertifiziert · ISO 27001
Connect to Tempo mainnet and Testnet with low-latency RPC, full archive data, debug and trace APIs, and real-time Streams. The complete Tempo data stack, managed from a single Quicknode dashboard.
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.
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.
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.
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.
Ereignisgesteuerte Benachrichtigungen mit garantierter Zustellung. Abonnieren Sie bestimmte Adressen, Ereignistypen oder On-Chain-Bedingungen.
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.
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 und eth_subscribe verhalten sich alle genau so wie auf Ethereum.
// 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.
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.
Runnable sample apps and starter kits across Quicknode-supported chains, including Tempo. Clone one and ship.
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.
„Unsere Nutzer teilen einen Link – pay3.so/@username – und der Absender zahlt einfach. Keine Adressen, keine Verwirrung durch verschiedene Blockchains, keine Nachrichten wie ‚Ist die Zahlung angekommen?‘. Sie sehen lediglich ‚Zahlung eingegangen‘. Quicknode Streams – das macht dies über vier Blockchains hinweg gleichzeitig möglich, und es ist dieselbe Infrastruktur, die wir nun auf Händler ausweiten, ohne irgendetwas neu aufbauen zu müssen.“Varun, Gründer und CEO von pay3
Häufig gestellte Fragen
Haben Sie noch offene Fragen? Wenden Sie sich an den Support – das „ Quicknode “ unterequipe hilft Ihnen gerne weiter.