Private Chiliz RPC Endpoints on a Dedicated Node

A Chiliz RPC node is a server running the chiliz-chain client that exposes the Ethereum JSON-RPC APIs your app uses to read blockchain data and broadcast transactions. Most teams rely on a Chiliz node to serve fan-token dApps, wallets, indexers, and dashboards with stable, predictable access.

Yes. Chiliz Chain is EVM-compatible and derived as a fork from BSC, which is itself a go-Ethereum fork. It inherits most tooling, concepts, and binaries from BSC and Ethereum, so standard Ethereum libraries and the usual eth_ JSON-RPC methods work as expected.

Chiliz Chain uses Proof of Staked Authority (PoSA), combining elements of DPoS and PoA. It inherits BSC's Parlia engine, where a limited set of 11 validators take turns producing blocks. Double-sign detection and slashing logic support security, stability, and finality.

Choose a standard 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.

The native token is CHZ. It pays gas for smart contract execution, can be used for cross-chain operations, and secures the network through staking or delegating to one of the validators. Staking CHZ also enables participation in community governance.

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

Most failures trace back to storage I/O saturation, CPU contention, or too many concurrent WebSocket sessions. Dedicated hardware removes noisy-neighbor contention, and local NVMe reduces read and write stalls. That is why teams move to a dedicated Chiliz RPC node when usage becomes production-grade.

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.