Dedicated Waves RPC Node & Waves RPC Endpoint | RedSwitches
// dedicated waves rpc node

Private Waves RPC Endpoints on a Dedicated Node

A private Waves RPC endpoint on single-tenant NVMe bare metal. Full, archive, or validator nodes serving the Waves Node REST API and gRPC server, with zero rate limits and no compute units.

Get a QuoteStart Live Chat
  • Private Endpoint, Zero Rate Limits
  • No Compute Units, Unlimited Requests
  • Full, Archive & Validator Builds
  • REST API & gRPC Server Ready
  • NVMe Tuned For State Reads
  • 20+ Global Tier III Locations
deploy.shlive

$ rs deploy waves --type full --region fra

allocating single-tenant bare metal

restoring waves node snapshot

syncing microblocks to tip

serving rest api + grpc server

attaching DDoS shield + IP allowlist

private endpoint live · rest + grpc

region Frankfurt · LPoS + Waves-NG · ~3s microblocks

  • UnlimitedRequests
  • ZeroRate Limits
  • 100%Isolation
// why redswitches

Why Teams Run Waves Nodes With RedSwitches

A single-tenant node with people behind it: unlimited throughput, a named account manager, direct engineering access, and billing built for Web3 teams.

Unlimited RPS & Responses

One node, unlimited requests and responses. No compute units, no rate caps, no overage bills. A flat monthly price, run as hard as the hardware allows.

Dedicated Account Manager

A named account manager who knows your setup, not a ticket queue. One contact for provisioning, scaling, and anything urgent.

Direct Engineering Access

Talk to the engineers who run the metal. Waves Node config, the REST API and gRPC server extension, LPoS leasing setup, and Data Service indexing, handled by people who run Waves nodes daily.

20+ Global Data Centers

Place your node beside your users across 20+ Tier III locations. Multi-region for redundancy, split read and write endpoints.

Pay In Crypto

Settle in crypto or fiat, WAVES included. Flexible billing for Web3 teams, with the same predictable flat monthly price either way.

Tailored Load Balancing

Custom load balancing, failover, and split read/write topology, designed and tuned for your traffic by our engineers.

// request your endpoint

Configure Your Waves Node

Pick a node type, tell us your workload, and an engineer sizes and quotes it. One flat monthly price, no compute units, no overages.

1 Dedicated Node = Unlimited RequestsNo Compute Units$0 Overages, Guaranteed

Waves Full Node

For dApps, wallets, DEXs & bots

CPU
4–8 high-clock cores
RAM
16–32 GB
Storage
500 GB–1 TB NVMe (grows with state)
Network
1 Gbps+ on a 10/25 Gbps port
Stack
Waves Node (Scala) · REST API + gRPC server
Best for
  • Account, asset, and transaction reads
  • High-refresh wallet, DEX, and dApp traffic
  • Broadcasting signed transactions to the network
Included with every node
  • Unlimited RPS, no rate limits
  • HTTPS & WebSocket (WSS)
  • 99.99% uptime SLA
  • Multi-region endpoints
  • Private networking + IP allowlisting
  • 24/7 Web3 engineering support
From$199/moflat, no compute units

Final price is sized to the node specs your chain needs (full vs archive, storage, region), and typically lands 30-40% below comparable RPC providers.

Node specs above are based on the official Waves documentation.

View official Waves node docs →

Inquiring about: Waves · Full Node

Replies in ~5 minA RedSwitches Web3 engineer specs your private endpoint

No compute units, no rate limits. From $199/mo, flat.

Prefer to talk it through first? Start Live Chat

// why dedicated

Stop Fighting For Bandwidth On Shared Waves RPC

Shared Waves RPC pools throttle you, bill you per compute unit, and seat you next to noisy neighbors. A dedicated Waves node is your own private backbone: flat-priced, uncapped, and yours alone.

CapabilityShared RPC PoolRedSwitches Dedicated
Request limitsHard rate caps and compute-unit quotas throttle your Waves calls the moment traffic spikesZero rate limits, your Waves node serves unlimited requests up to what the hardware can push
ResourcesA noisy-neighbor pool where another tenant's mint or airdrop steals the throughput you paid for100% single-tenant CPU, RAM, and NVMe, reserved for your Waves workload alone
BillingPer-compute-unit metering with surprise overage bills at the end of the monthOne flat monthly price for the whole node, $0 overages and no usage math
NetworkShared, throttled bandwidth you can neither see nor controlA dedicated 10 / 25 Gbps port, metered or unmetered, that is yours alone
PrivacyA public, pooled endpoint with a wide, shared attack surfaceA private Waves endpoint behind included DDoS protection and IP allowlisting
History & specsLimited history and fixed plans you cannot resize as you growFull Waves archive with custom RAM and disk, sized to your query depth
ControlNo server access, the provider picks the client, version, and configFull root, KVM, and IPMI, run the Waves client and tuning you choose
// network details

Waves Node Specifications

The networks, node software, data interfaces, and execution model your dedicated Waves node ships with. The node exposes the Waves Node REST API and an optional gRPC server, not Ethereum JSON-RPC.

Chain Parameters

Networks
Mainnet, Testnet, Stagenet
Native token
WAVES
Consensus
Leased Proof of Stake (LPoS)
Block protocol
Waves-NG (key blocks + microblocks)
Block time
~60s key blocks, ~3s microblocks
Throughput
~100 TPS
Smart contracts
Ride (functional, non-Turing-complete)
Fees
Fixed minimum fees by type, no gas auctions
Node software
Waves Node (Scala reference client)
Explorer
wavesexplorer.com

Supported Clients

Node software
  • Waves Node (Scala)
Data interfaces
  • Waves Node REST API
  • gRPC Server (extension)
  • Data Service API (indexed)
Official SDKs
  • TypeScript
  • Go
  • Java
  • Rust
  • Python

Keep your endpoint private behind IP allowlisting and firewall rules. The REST API runs on the standard node port; we enable the gRPC server extension and a Data Service index on request for streaming and analytics workloads.

// use cases

What Teams Build On Waves Nodes

Where a private, uncapped endpoint beats a shared RPC pool.

DEX Trading Loops

WX Network and other Waves DEXs read order and asset state and submit transactions under strict timing. A dedicated node keeps read paths stable, so trading bots and order books react without delay stacking.

Tokenization Flows

Waves issues and transfers tokens without contracts, plus smart assets via Ride scripts. A dedicated node keeps issuance, transfer, and balance calls responsive during high-volume minting and distribution.

Sponsored-Fee dApps

Sponsored fees let operators pay user transaction costs for gasless UX. A dedicated Waves node keeps broadcast and confirmation paths fast, so sponsored flows stay smooth at peak user concurrency.

Data Service Analytics

Indexed history and market data run on the Data Service API over PostgreSQL. A dedicated node isolates heavy indexing from app traffic, so analytics queries run for hours while live RPC stays responsive.

Wallet Balance Views

Keeper Wallet and custom wallets repeatedly fetch balances, assets, and recent status, and users notice the smallest lag. A dedicated Waves setup keeps high-refresh balance views consistent at peak.

Smart-Account Apps

Ride scripts on accounts and assets enforce custom logic with predictable execution costs. A dedicated node keeps script reads and invocations responsive so dApp loops stay steady when activity surges.

// how it works

From Waves To Private Endpoint In 3 Steps

Pick a node, we provision dedicated bare metal, you get a private, snapshot-ready RPC URL.

  1. 01

    Pick Your Waves Node

    Choose full, archive, or validator. New builds serve the Waves Node REST API and gRPC server; tell us the region closest to your users.

  2. 02

    We Provision Bare Metal

    Your single-tenant Waves Node deploys on NVMe sized for state reads, snapshot-bootstrapped, so you skip the long microblock sync from genesis.

  3. 03

    Get Your Private Endpoint

    Receive a dedicated REST API and gRPC endpoint with unlimited requests and zero rate limits, private behind IP allowlisting and DDoS protection.

// latency & locations

Put Your Node Where Milliseconds Are Won

RPC latency is mostly a function of distance. A dedicated node lets you choose the exact region, so you sit next to the traffic that matters instead of fighting for routing on a shared, far-away endpoint.

Place It Where Your Users Are

Deploy across 20+ Tier III locations in the US, EU, Asia, and Australia. Put your Waves node in the region your traffic actually comes from, not wherever a shared pool happens to route you.

Cut The Round Trips

RPC latency is mostly physical distance. Running in the same region as your users and the Waves network's peers shaves the round-trips a far-away, shared endpoint can never give back, which is what high-frequency reads and transaction submission live or die on.

Multi-Region By Design

Run a primary node plus regional read replicas for fast reads everywhere and built-in redundancy. Split public read endpoints from private admin, debug, and trace endpoints.

Need a node within a target latency budget of a specific region or venue? Tell us the endpoint and we'll recommend the closest facility.

// supported chains

One Backbone For Every Major Chain

Run validators, RPC, and archive nodes across the chains your stack depends on, all on the same dedicated bare metal, with the same isolation, speed, and control.

// customer reviews

Trusted To Run Production Nodes

Real reviews from Trustpilot, HostAdvice, Cryptwerk, and Google.

  • 4.8/525Gbps Bare Metal
    Port speeds on cloud were capped and shady. With RS I actually get the 25Gbps they say. No throttle bs.
    Felix MartinsenDenmark
  • 5.0/5VPN Operations
    Network has been rock solid. They’ve got Tier 1 carriers like Arelion, GTT, and TATA… We just ping them on Telegram and they sort things out quickly.
    TomasNetherlands
  • 4.8/5Validators
    Set up multiple Solana + Avalanche validators through them. Hardware was clean, latency was low (especially in Europe), and uptime’s been 100% so far.
    Peppe TerranovaSouth Korea
  • 5.0/5Full Root Access
    As a sysadmin, I care more about control than flashy dashboards. RedSwitches gives me root access, IPMI, and actual hardware specs I can configure. Good for serious users.
    Eun-Woo GimSouth Korea
  • 5.0/5Enterprise Uptime
    We were searching for a truly reliable and stable hosting provider with maximum uptime and a powerful network infrastructure to ensure the lowest possible latency. RedSwitches not only met but exceeded our expectations.
    AppsLabGermany
  • 5.0/5Cloud Exit
    RedSwitches gave us full control over our infrastructure without the vendor lock-in we kept running into with cloud hosts. Customizable builds, fast provisioning, and actual humans handling support tickets. It’s refreshing.
    Princeton OttUnited States
  • 5.0/599.99% Uptime
    My website works smoothly, thanks to their 99.99% uptime guarantee. The support team is another plus for me, as I always have been able to get help whenever I needed it in just 5 minutes on average.
  • 5.0/5ETH & BTC Nodes
    Deployed a few Ethereum and Bitcoin nodes here. Uptime’s been flawless, and sync speed was great thanks to their storage config.
    Ervin KaruGermany
  • 5.0/510Gbps RPC
    They provide what they promise, I got no throttling while running my RPC Nodes. I got server in a Amsterdam for the best price.
    Atri MukherjeeIndia
  • 5.0/5Streaming
    I am using their 10gbps streaming server for last 6 months and I have no complaints. Extremely quick live chat support and I love that they accept crypto.
    Tarun GhoshIndia
  • 5.0/5Bare Metal
    A really great hosting provider - what stands out the most is the stability of the network connection and the wide selection of bare metal servers. We’re very satisfied, and RedSwitches covers all of our needs.
    Борис ВербицкийPoland
  • 5.0/5AI Workloads
    Pros: Extremely reliable hardware, low-latency network, transparent billing… Great choice if you need raw power without cloud complexity. Works well for our dev environment and some AI workloads.
    Henry HarrisonUnited States
  • 5.0/5Switched Provider
    I have worked with OVH and Contabo in the past, but RedSwitches hit a better balance of price vs. support. Not the cheapest, but I get better performance and faster help.
    Samual SuttonUnited Kingdom
  • 5.0/5Game Servers
    Been using RedSwitches for 6 months now for my small game server biz. Uptime has been great, and I haven’t run into any hidden charges.
    Jerold PerkinsUnited States
  • 5.0/5AI Storage
    Using the storage servers to archive logs and snapshots from our AI pipeline… I also love that I could pick the datacenter closest to our team.
    Eino KoppelEstonia
  • 4.8/5Support
    Support is super responsive. I had an issue with an OS reinstall and they jumped in within 10 minutes… Transparent pricing = win.
    Boniface LeandreUnited States
  • 5.0/5Instant Delivery
    They have an instant delivery section… they delivered it within 120 mins with all my requirements fulfilled (OS/RAID/Software configured etc).
    Daniel StuartSri Lanka
  • 5.0/5Fast Provisioning
    A dedicated server has been installed within 30 minutes. Thirty minutes. It takes DAYS for some famous providers out there, but these guys do their work right.
    Ярослав СавенковNetherlands
  • 5.0/55+ Years
    I have been using their services for over 5+ years… Uptime: 10/10, Network: 10/10, Hardware Quality: 10/10, Customer Support: 20/10 (No, That’s Not A Typo).
  • 5.0/51 to 14 Servers
    They offer top quality hardware, excellent uptime and very responsive support… They helped us scale our business exponentially and we went from 1 server to 14 dedicated servers in less than a year.
    Sandip PanditIndia
  • 5.0/5Reliability
    Great hardware, non congested network and excellent service. Already using them for over a year and would definitely recommend Redswitches if you are looking for a reliable hosting provider.
    CandiceUnited States
  • 4.8/5Global Locations
    With servers available in numerous strategic locations, RedSwitches offers exceptional versatility and performance for our company’s diverse hosting needs. Plus, their no setup fee policy really helps keep costs down.
    Tiberiu RomanUnited States
  • 5.0/5Exam Platform
    "Your server is ready" - I read this message within 30 mins of starting the chat with their Sales Team… Excellent DELL Hardware and 100% Uptime.
    Mridul MehtaIndia
  • 5.0/5Bare Metal Cloud
    The dedicated server I got from RedSwitches has been incredibly reliable and fast. Their bare metal cloud solutions offer excellent performance, and the cloud VPS options are perfect for scaling. Highly recommended!
  • 5.0/5Zero Downtime
    I have been using their dedicated server from 9 months now. Starting from pre-sales till today I have not experienced downtime or lack of support.
    Amit BhatiaIndia
  • 5.0/524/7 Support
    First of all, all services work as expected - secondly - support is outstanding, no matter when you start the conversation with colleagues at support they have knowledge to help you out.
    LukaSlovenia
  • 5.0/5Since 2021
    We have been using Red Switches for several years since 2021. I have never experienced such fast customer service.
    Eitan WaisgerberIsrael
  • 5.0/5Easy Onboarding
    Absolutely delighted with RedSwitches! The setup was quick and free, and the fact that they accept all major payment gateways made the process seamless.
    Birk SpillumNorway
  • 5.0/5Bare Metal
    Very good experience using their bare metal servers. Their customer service is one of the finest I have experienced - always prompt at resolving troubles. Highly recommend.
// faqs

Frequently Asked Questions

Chain IDs, clients, archive data, getLogs limits, and why dedicated beats compute-unit billing.

What do I get with a dedicated Waves RPC node provider versus shared Waves RPC providers?

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.

How does Waves consensus work, and can I run a block-generating node with you?

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.

Which Waves interfaces do you serve, REST API, gRPC, or the Data Service API?

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.

How do smart contracts and fees work on Waves, and does that affect node load?

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.

What specs do I need for a Waves full node, and how do you size storage?

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.

Can I separate workloads, one node for RPC traffic and another for indexing and history?

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.

Can we lock down the Waves RPC node with firewall rules, private networking, and IP allowlisting?

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.

What uptime do you commit to for a dedicated Waves RPC endpoint, and what does the SLA cover?

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.

Do you charge per request or per compute unit?

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.

How is this different from a shared RPC endpoint?

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.

Do I have to sync the node myself, or wait days for it?

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.

Can I deploy close to a specific region or sequencer?

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.

// developer resources

Waves Developer Resources

Official Waves resources for builders running a node: docs, explorers, source, network status, and faucets. Every link points at the first-party source, not a wrapper.

// launch your node

Launch Your Private Waves Node

From $199/mo flat, sized to your chain's node specs and typically 30-40% below other providers. Snapshot-ready provisioning, zero setup fees, 24/7 Web3 engineers, no compute units, no rate limits.

Get a QuoteStart Live Chat