Private Hydration RPC Endpoints on a Dedicated Node

Hydration is the rebrand of HydraDX, a Substrate-based cross-chain liquidity protocol and DeFi hub on Polkadot. Its core is the Omnipool, a single automated market maker that combines many assets into one pool for capital-efficient routing. The project and node software were renamed from HydraDX to Hydration, though the GitHub repository and explorer still carry the hydradx name.

Most teams start with a full Hydration 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.

Yes. Hydration runs a Substrate runtime with an embedded Frontier EVM (chain ID 222222), so a node exposes both the Substrate JSON-RPC (chain_, state_, system_, author_) for Polkadot.js tooling and an Ethereum JSON-RPC (eth_ namespaces) for Web3.js and Ethers.js. Tell us which interfaces your app calls, and we configure the node accordingly.

A shared Hydration RPC provider runs many customers on pooled infrastructure. That can create unpredictable latency during spikes, plus shared rate limits and noisy-neighbor slowdowns. Dedicated Hydration 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. Because Hydration is a parachain, a node also syncs an embedded Polkadot relay chain, so we restore from snapshots to skip the long cold sync.

Yes. Most developers use Polkadot.js over WebSocket for subscriptions and real-time updates, and EVM teams can use Web3 tooling over the same node. Your dedicated Hydration RPC node can expose WebSocket endpoints, and you can keep them private or public based on your access model. For tighter control, you can restrict access by IP and allow only trusted clients.

For production Hydration RPC, you need fast NVMe storage, sufficient RAM for caching, and a stable network. Many teams start with 8+ cores and 64 GB RAM for full RPC, then scale to 16+ cores and 128 GB RAM as concurrency rises. Archive RPC requires larger NVMe capacity and more cache headroom, as historical queries and indexing are storage and memory intensive.

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