Dedicated KUB RPC node. A private KUB RPC endpoint that only you use: no rate limits, every method on, one fixed monthly price.

A server running KUB's node software (geth (KUB fork, kub-chain/bkc)) that answers RPC requests: reading balances and state, and sending transactions. It can be public and free, shared by a provider's customers, or dedicated to one client.

A KUB node on a bare-metal server that runs for one client only, with its own private RPC endpoint. Nobody else's traffic shares the machine, so there is no rate limit and no noisy neighbour, and every method the client exposes is on. Argusnodes builds, syncs, monitors and upgrades it for you at one fixed monthly price.

Yes, and so is monitoring, both at no additional cost. We set up and sync the node, watch it 24/7 with live node and server metrics in your dashboard, apply every network upgrade and client update, and fix it when something breaks. If you need help around the node, such as connecting it to your app, moving off another provider or setting up an indexer, our engineers help with that too, at the same monthly price.

An RPC endpoint that only your applications use. It sits on a dedicated KUB node that is yours alone, on your own domain if you want one, and answers only the IP addresses you allowlist. No other customer's traffic shares the machine, so nobody else's burst becomes your latency, and there is no rate limit to hit.

As soon as it has synced with the KUB network, and we tell you the moment it is ready. Sync time depends on the node type (an archive node replays the full history, so it takes longest), so your quote carries an estimate for your exact setup rather than a number that is sometimes wrong. The quote itself lands within the hour, around the clock.

Everything the node can do, with the premium add-ons other providers bill separately included free: unlimited RPS, every RPC method including debug and trace, unlimited WebSocket connections, your own domain with an IP allowlist, 18 cities to choose from, a 99.99% SLA with credits, 24/7 engineer support and live p50/p99 in your dashboard. There is no add-on price list because nothing is an add-on.

A machine that meets KUB's official hardware guidance (quoted in the spec sheet on this page) with headroom on top, on a dedicated bare-metal server. We never build at the minimum, because a node sized to the minimum becomes the bottleneck the day the chain grows. Ask before you order and we tell you the exact CPU, RAM and NVMe; the delivery email names the server, and root access is yours if you want it.

Yes. KUB's documentation describes full-history operation; we run KUB archive nodes, from $509/mo, with trace and historical queries unmetered. Debug and trace methods are on for full nodes too, within their state window.

Yes. KUB has a public validator role, and we operate validators under the same monitoring and support as RPC nodes, quoted per setup. Pick "Validator" in the configurator and describe the stake setup.

Yes. A dedicated KUB node speaks the same JSON-RPC and WebSocket interfaces as the shared endpoint you use today, so migration is pointing your application at your own endpoint. Billing is monthly with no lock-in on our side, and support engineers are on the channels 24/7 during cutover.

No artificial ones: unlimited RPS and no connection cap. The machine is yours alone, so the hardware is the only ceiling: if it can serve the request, you can send it. There is no per-plan connection cap because there is no plan tier.

In crypto, with no KYC and no setup fee. Pay monthly, or save 5% quarterly and 10% annually, and your price is locked for as long as your node runs. Cancel at the end of any term; the node is provisioned for you alone, so there is no meter to escape and no exit fee.

96 (hex 0x60), per KUB's official documentation. A dedicated KUB node answers eth_chainId with it, so wallets and libraries configured for KUB work against your endpoint unchanged.

Public KUB RPC URLs from the chain registry that answered our weekly check on chain ID 96: https://rpc.bitkubchain.io. KUB's official documentation (docs.kubchain.com) is the reference for its own endpoints. They are shared, rate limited and run by third parties, so they are fine for a wallet and not for an application. A dedicated node gives you a private KUB RPC URL of your own, on your domain if you want, that nobody else uses.

Yes, public KUB RPC endpoints are free: the ones that passed our weekly check are listed on this page. They are shared and rate limited, which is fine for a wallet or a test. A dedicated KUB node is the paid option for an app, bot or indexer, at one fixed monthly price.

It depends on the workload. Check four things: whether the node is single-tenant or shared, whether there are rate limits or credits, whether archive, trace and debug are included, and who answers when it breaks. For a wallet, a free public endpoint is enough. For an app, bot or indexer, a dedicated node with no rate limits avoids the throttling of shared plans. Our comparison pages (argusnodes.com/vs) set us against other providers, with sources.

Add a network manually with the chain ID 96, the currency symbol KUB and your private KUB RPC URL in place of the public one. The steps are the same as for a public URL; the difference is that the endpoint is yours alone, so the wallet never hits someone else's rate limit.