Private Tempo RPC Endpoints on a Dedicated Node

A dedicated Tempo RPC node runs on single-tenant bare-metal hardware reserved for you: CPU, RAM, NVMe storage, and network port are yours alone. Shared RPC endpoints split capacity across many users, so when payment traffic spikes they throttle requests or add latency. A dedicated setup avoids that and gives you full root control over the Tempo client, its version, and its configuration.

Tempo is an EVM-compatible Layer 1 built specifically for payments and stablecoin settlement, created by Stripe and Paradigm. It removes the native gas token requirement and lets users pay transaction fees in supported USD stablecoins, which is a better fit for merchant apps, treasury flows, and financial UX than ETH-style gas.

Tempo does not use a native gas token. Fees are denominated in USD and paid in supported stablecoins (TIP-20), so wallets and apps treat fee balances differently from ETH-style networks. This keeps costs easy to reason about for payments, but means your tooling should account for stablecoin-denominated gas.

Tempo is built on the Reth SDK, a high-performance Rust EVM execution client, with Simplex BFT consensus via Commonware for deterministic sub-second finality. The node software is open source at github.com/tempoxyz/tempo and installs via tempoup, Cargo, or Docker. Archive nodes run with the --archive flag for complete historical data.

A full node keeps current state and recent history and serves most RPC queries: balances, contract reads, receipts, and recent logs. An archive node retains full historical state at every block height, which is needed for eth_call at older blocks, historical balance lookups, and deep reconciliation. Archive needs significantly more NVMe and RAM, so choose full for standard payment workloads and archive when you need history.

Yes. Tempo uses Chain ID 4217 and supports standard Ethereum JSON-RPC methods, so existing EVM libraries and wallets work against it. Because it is Reth-based, common namespaces such as eth, net, web3, debug, txpool, and trace are available, alongside Tempo-specific namespaces. The exact exposed set is operator-configurable on your dedicated node.

Shared RPC endpoints throttle, vary in latency, and change policies without warning. A dedicated Tempo node runs on single-tenant CPU, RAM, and NVMe, so your throughput and response times depend on your hardware headroom, not other tenants or shared quotas. For payment workloads where confirmation timing matters, that predictability is the point.

No. Unlike shared RPC providers that bill per "compute unit" and throttle you past a quota, a dedicated node is a flat monthly price with unlimited requests and zero overages. One node equals all the throughput your hardware can serve. That makes budgeting predictable and removes the surprise bills that come with usage-based RPC pricing.

Shared RPC pools serve thousands of customers from pooled infrastructure, so you inherit rate limits, noisy-neighbor latency, and compute-unit billing. A RedSwitches node runs on single-tenant bare metal that is yours alone: reserved CPU, RAM, and NVMe, a dedicated 10/25 Gbps port, and a private endpoint you control. Performance tracks your hardware, not another tenant's traffic.

No. We provision from current snapshots so your node is live in hours rather than syncing from genesis for days. You can run it yourself with full root access, or choose our fully managed option where our engineers handle the sync, updates, and monitoring. Either way you receive a working private endpoint, not an empty server.

Yes. With 20+ Tier III locations across the US, EU, Asia, and Australia you can place your node in the same region as your users or a chain's sequencer to cut round-trip latency. Tell us your target region and we will recommend the closest facility. You can also run multi-region nodes for redundancy and split read and write endpoints.