Private Stable RPC Endpoints on a Dedicated Node

A Stable RPC node is a server running Stable's EVM client that exposes JSON-RPC APIs your app uses to read chain data and broadcast transactions. Teams rely on a Stable node to serve payment apps, wallets, indexers, and dashboards with stable, predictable access.

Stable mainnet uses chain ID 988, and the public testnet uses 2201. Gas is paid in USDT0 (Stable's canonical USDT asset), so fees are denominated in the same dollar unit as your transfers. STABLE is a separate token used only for staking and governance, not for paying gas.

Yes. Stable runs a fully EVM-compatible execution layer, so you can deploy existing Ethereum smart contracts and use standard tools like MetaMask, Hardhat, and Ethers without rewrites. It points to standard Ethereum JSON-RPC over HTTPS and WebSockets on your dedicated node.

Choose a full node when you mainly need the latest state, receipts, and recent logs. Choose an archive node when you need deep historical state for analytics, explorers, audits, or long-range backfills. Stable's storage layer keeps live state and historical data separate, so a dedicated tier matches your query depth without sharing limits.

Stable's public RPC is rate-limited to roughly 1,000 requests per 10 seconds per IP, which throttles production traffic. A dedicated Stable node runs on single-tenant CPU, RAM, and NVMe, so your throughput and response times depend on your hardware headroom, not a shared quota or other tenants.

Yes. Stable mainnet launched on December 8, 2025 with USDT0 as the gas token. It is a new, fast-moving Layer 1, so we size nodes conservatively, provision from current snapshots, and track client and network upgrades closely so your endpoint stays current as the chain evolves.

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.