Private IoTeX RPC Endpoints on a Dedicated Node

An IoTeX RPC node runs iotex-core and exposes APIs your app uses to read blockchain data and broadcast transactions. It serves the Ethereum JSON-RPC interface for EVM tooling plus IoTeX's native gRPC/REST API, so dApps, wallets, indexers, and DePIN backends get stable, predictable access.

IoTeX is an EVM-compatible Layer 1 purpose-built for DePIN and IoT. Alongside standard smart contracts it offers W3bstream for verifiable off-chain computing and ioID for decentralized machine identity, with Roll-DPoS consensus tuned for hardware-friendly, high-throughput device workloads.

IoTeX uses Roll-DPoS (Randomized Delegated Proof of Stake), combining DPoS with PBFT and VRFs. Each epoch it randomly selects 24 active delegates from the top 36 community-elected delegates, reaching roughly 5-second blocks and 2000+ TPS while staying decentralized.

Yes. IoTeX runs an EVM, so you can use ethers.js, Hardhat, and standard eth_ JSON-RPC methods over HTTP and WebSocket via its Babel API. The node also exposes IoTeX's native gRPC/REST API for IoTeX-specific reads. Both run on the same dedicated node.

Mainnet chain ID is 4689 and testnet is 4690. The Ethereum JSON-RPC gateway listens on 15014 (HTTP) and 16014 (WebSocket); the native IoTeX API uses 14014. Keep the API private by default and expose only what your app needs behind allowlists.

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. A dedicated setup lets you pick the right tier without sharing limits.

Shared RPC endpoints throttle, vary in latency, and change policies without warning. A dedicated IoTeX 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.

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.