Private Liberland RPC Endpoints on a Dedicated Node

The Liberland Blockchain is a Substrate-based Layer 1 that powers the decentralized governance of the Free Republic of Liberland. It runs on-chain governance, a blockchain court, and a company registry, and uses two native tokens: LLD, the operational currency that pays for transactions, and LLM, the political token tied to citizenship and voting. It is a standalone chain, not a parachain.

Most teams start with a full Liberland node because it serves current-state reads and transaction submission with far lower storage needs. Choose an archive node 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 Liberland RPC provider runs many customers on pooled infrastructure, which can create unpredictable latency during spikes, plus shared rate limits and noisy-neighbor slowdowns. Dedicated Liberland 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.

Yes. Liberland serves the Substrate JSON-RPC, so Polkadot.js, substrate-interface, and go-substrate-rpc-client all connect with no changes. Most developers use Polkadot.js over WebSocket for subscriptions and live updates. Your dedicated node can expose WSS endpoints, and you can keep them private or restrict access by IP and allow only trusted clients.

Yes. Liberland uses Nominated Proof-of-Stake where anyone can nominate but only citizens run validators. We provision single-tenant bare metal with SMT-off tuning, IPMI and KVM recovery, and a private network so your validator RPC ports stay closed to the public. You hold the keys, we run the metal.

Liberland uses the standard Substrate ports: 9933 for JSON-RPC over HTTP and 9944 for WebSocket, with peer-to-peer on 30333. The official guidance is to never expose validator RPC ports publicly. We recommend exposing only what you need, restricting access to known IPs, and putting a reverse proxy in front. With a dedicated server you define firewall rules that match your risk level.

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

Yes. That is a core benefit of running a dedicated Liberland 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.