Private Basilisk RPC Endpoints on a Dedicated Node

Basilisk is a liquidity-bootstrapping DeFi protocol on Kusama, serving as the canary network for HydraDX/Hydration. Young projects bootstrap liquidity on Basilisk through Snek Swap XYK pools and Liquidity Bootstrapping Pools, then graduate to HydraDX as they mature. It runs as a Kusama parachain (parachain ID 2090) with a leased core, and its native token is BSX.

Most teams start with a pruned Basilisk 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 Basilisk RPC provider runs many customers on pooled infrastructure. That can create unpredictable latency during spikes, plus shared rate limits and noisy-neighbor slowdowns. Dedicated Basilisk 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. Basilisk serves the standard Substrate JSON-RPC, so Polkadot.js, py-substrate-interface, and go-substrate-rpc-client all connect with no changes. Your dedicated node can expose WebSocket (WSS) endpoints for subscriptions and real-time updates, and you can keep them private or restrict access by IP to trusted clients.

Provisioning is fast. The real variable is sync time, which depends on chain state, node type, storage speed, and network conditions. A pruned RPC 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.

You can expose the standard RPC and WebSocket 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 Basilisk 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.