Private Humanode RPC Endpoints on a Dedicated Node

Humanode is a Sybil-resistant, EVM-compatible Layer 1 built on Substrate and secured by privacy-preserving biometric verification, where one verified human runs one node. It exposes both Substrate and Ethereum JSON-RPC, so a dedicated node gives anti-Sybil dApps and EVM apps a private endpoint with unlimited requests instead of shared-pool rate limits.

Yes. Humanode runs a Frontier EVM on top of Substrate, so a single humanode-peer node exposes the Substrate JSON-RPC (chain, state, system, author) for Polkadot.js and the Ethereum-compatible JSON-RPC (eth, net, web3) for Web3.js and Ethers.js. You can use either interface over HTTP or WSS on the same dedicated endpoint.

Humanode uses crypto-biometric Sybil resistance rather than proof-of-work or financial proof-of-stake. There is no token stake to bond; node rights are granted through biometric authentication of a unique human, and rewards are shared across active nodes. A validator must keep authenticating and stay online, which is why steady uptime and fast recovery via IPMI and KVM matter.

Most teams start with a full Humanode node because it serves current-state reads and transaction submission with far lower storage needs. Choose archive RPC when your product must query full history, power explorers, run deep analytics, or support heavy historical lookups. If you are unsure, tell us your workload and we will map you to the right node type.

A shared Humanode RPC provider runs many customers on pooled infrastructure, which can create unpredictable latency during spikes plus shared rate limits and noisy-neighbor slowdowns. Dedicated Humanode RPC node servers give you single-tenant resources, your own access rules, and clearer fault boundaries. You control performance and security instead of inheriting someone else's traffic.

Provisioning is fast. The real variable is sync time, which depends on chain state, node type, storage speed, and network conditions. A full RPC usually reaches a usable state earlier than an archive setup because an archive has far more data to process. We deploy according to sync time, restoring from snapshots where available, so you are not sold a fake instant promise.

You can expose the standard HTTP and WSS RPC ports used by Substrate-based nodes. We recommend exposing only what you need. Many teams restrict access to known IPs, put a reverse proxy in front, and keep admin surfaces closed. With a dedicated server, you can define firewall rules that match your risk level and traffic profile.

Yes. That is a core benefit of running a dedicated Humanode RPC node on dedicated servers. You can scale up resources as load grows, add storage for archive needs, and move to higher core counts for heavy concurrency. This keeps your endpoint stable while your product grows, without rebuilding everything on a new platform.

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.