Private Waves RPC Endpoints on a Dedicated Node

With dedicated Waves RPC node servers, you run your own Waves Node on single-tenant hardware. Shared providers place many apps on the same pool, so traffic spikes can trigger throttling and inconsistent latency. Dedicated Waves nodes give you predictable compute, RAM, and NVMe IOPS, plus full control over access rules, upgrades, and workload separation.

Waves uses Leased Proof of Stake (LPoS): holders lease WAVES to block-producing nodes without transferring ownership, and lessors earn a share of rewards. The Waves-NG protocol separates key blocks, elected roughly every 60 seconds, from microblocks streamed about every 3 seconds for fast inclusion. We provision validator-class metal so you can run a generating node and accept leases, with full root and IPMI access and your keys held by you.

All three, sized to your workload. The Waves Node REST API is the main interface for accounts, assets, transactions, and broadcasting. The optional gRPC server extension adds typed, streaming-friendly access for backends and indexers. The Data Service API runs an indexed PostgreSQL backend for fast historical and market-data queries. Tell us your read patterns and we map the right interface for your Waves RPC workload. Note that Waves is non-EVM, so it does not expose Ethereum JSON-RPC namespaces.

Smart contracts use Ride, a functional, non-Turing-complete language with predictable execution and fixed minimum fees by transaction type, so there are no gas auctions. Scripts attach to accounts (dApps and smart accounts) or to assets (smart assets). Predictable fees mean predictable load patterns, which makes capacity planning on a dedicated node straightforward versus fighting shared rate limits during spikes.

Waves node hardware needs are modest compared with heavier L1s. A common baseline is 4 to 8 cores, 16 to 32 GB RAM, and 500 GB to 1 TB NVMe for a full node, then scale for archive history and Data Service indexing. We size your dedicated Waves nodes from your actual endpoints, expected request rate, and whether you need indexing-heavy analytics on the same node.

Yes, and it is a clean way to protect user-facing performance. Many teams run one Waves node for app traffic and a second for the Data Service index, history backfills, and analytics. This keeps noisy internal jobs from affecting public APIs. RedSwitches can provision dedicated Waves nodes per role, so your production endpoints stay responsive while data pipelines run continuously.

Yes. Many teams keep Waves endpoints private and expose access only to app servers, CI, or partner IPs. You can enforce firewall rules, restrict inbound access, and allowlist known sources. This reduces abuse risk and keeps the endpoint clean for production. If you need public access, you can still limit it with rate controls and strict observability.

We include a 99.99% uptime SLA for infrastructure availability. You also get root, KVM, and IPMI access to reduce incident time when the OS or node process needs recovery. If you choose managed service, you also get operational help that reduces downtime risk through monitoring and upgrade support. For mission-critical launches, we recommend redundancy planning across two dedicated Waves RPC node servers.

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.