Dedicated CONX (formerly XPLA) RPC node. A private CONX (formerly XPLA) RPC endpoint that only you use: no rate limits, every method on, one fixed monthly price.
CONX Chain (formerly XPLA) is a Cosmos SDK proof-of-stake blockchain with EVM compatibility, hosting gaming and content dApps; the rebrand from XPLA passed governance in November 2025.
CONX (formerly XPLA) RPC endpoint and network details.
| Network | CONX (formerly XPLA) mainnet |
| Currency | XPLA |
| Interfaces | CometBFT RPC · REST · EVM JSON-RPC |
| Dedicated endpoint | Your own CONX (formerly XPLA) RPC endpoint, from $169/mo → |
Public endpoints are listed in CONX (formerly XPLA)'s official documentation (docs.xpla.io). They are shared and rate limited. Facts from CONX (formerly XPLA)'s official documentation.
Order a dedicated CONX (formerly XPLA) RPC node.
Pick the node and the city. Where a city shows a price, pay in crypto and we start building; anywhere else, you get a firm quote within the hour.
What every dedicated CONX (formerly XPLA) node includes.
- Fully managed at no additional cost: we set it up, sync it, monitor it 24/7, apply every upgrade and fix it if anything breaks
- Monitoring at no additional cost: live node and server metrics for your node in your dashboard
- No rate limits: the hardware is the only ceiling
- Every RPC method on, heavy queries included
- Unlimited connections, no per-plan cap
- Your own domain and an IP allowlist you control
- 99.99% SLA in writing, with service credits
- 24/7 support answered by engineers
CONX (formerly XPLA) node requirements, and what we build.
Chain facts from CONX (formerly XPLA)'s official documentation (docs.xpla.io). Where it is silent, the row says so.
| Node software | xplad |
| Interfaces | CometBFT RPC, REST, EVM JSON-RPC |
| Full node | Yes, from $169/mo |
| Archive node | Confirmed at quote time |
| Validator | Public validator role; quoted per setup |
| Gas token | XPLA |
| Official hardware guidance | For a mainnet (dimension_37-1) full node the docs specify CPU 4 (+4 threads), 32 GB RAM, 2 TB SSD (2000 MB/s R/W) and 300 Mbps bandwidth; testnet (cube_47-5) needs 2 (+2 threads), 16 GB, 500 GB SSD, 150 Mbps. source ↗ |
| Argusnodes build | Meets the official guidance above with headroom on top, never at the minimum. Ask and we tell you the exact CPU, RAM and NVMe; root access on request. |
What changed on CONX (formerly XPLA) recently
- The XPLA-to-CONX rebrand was announced 2 Nov 2025 and the governance proposal to rename the token, symbol and chain brand to CONX officially passed on 10 Nov 2025; the docs site is now branded 'CONX Docs' and refers to 'CONX Chain', while chain-id dimension_37-1 and binary xplad are unchanged. source ↗
- xplad v1.9.0 (16 Mar 2026) replaced the Ethermint EVM with cosmos/evm (v0.6.0-xpla), bumped wasmd to v0.60.5 and CometBFT to v0.38.21; the docs' EVM core-module page still describes Ethermint. source ↗
- Frequent 2026 releases follow: v1.10.0 (12 May 2026, security advisory CWA-2026-003), v1.11.3 (23 Jul 2026, EVM patch) and v1.11.4 (30 Jul 2026), the current release as of Aug 2026. source ↗
Sources: docs.xpla.io/full-node/full-node/resources/public-and-private-endpoints · docs.xpla.io/full-node/full-node/run-a-full-node/system-configuration · docs.xpla.io/learn/learn/about-xpla-chain
Dedicated CONX (formerly XPLA) RPC node: the questions buyers ask.
What is a CONX (formerly XPLA) RPC node?
A server running CONX (formerly XPLA)'s node software (xplad) 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.
What is a dedicated CONX (formerly XPLA) RPC node?
A CONX (formerly XPLA) 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.
Is my CONX (formerly XPLA) node managed and monitored, and what does that cost?
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.
What is a private CONX (formerly XPLA) RPC endpoint?
An RPC endpoint that only your applications use. It sits on a dedicated CONX (formerly XPLA) 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.
How long until my CONX (formerly XPLA) node is live?
As soon as it has synced with the CONX (formerly XPLA) network, and we tell you the moment it is ready. Sync time depends on the node type, 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.
What is included in the from $169/mo for my CONX (formerly XPLA) node?
Everything the node can do, with the premium add-ons other providers bill separately included free: unlimited RPS, every RPC method including heavy queries, unlimited 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.
What hardware will my CONX (formerly XPLA) node run on?
A machine that meets CONX (formerly XPLA)'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.
Does Argusnodes run CONX (formerly XPLA) archive nodes?
Archive support on CONX (formerly XPLA) is confirmed against its documentation as part of your quote. Every method the client exposes is on by default at no extra charge.
Can I run a CONX (formerly XPLA) validator with Argusnodes?
Yes. CONX (formerly XPLA) 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.
Can I move my CONX (formerly XPLA) endpoint from another provider?
Yes. A dedicated CONX (formerly XPLA) node speaks the same CometBFT RPC and REST and EVM JSON-RPC 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.
Are there rate limits or connection caps on a dedicated CONX (formerly XPLA) node?
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.
How do I pay for my CONX (formerly XPLA) node, and can I cancel?
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.
What is the CONX (formerly XPLA) RPC URL?
The public CONX (formerly XPLA) RPC URLs are listed in CONX (formerly XPLA)'s official documentation (docs.xpla.io). 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 CONX (formerly XPLA) RPC URL of your own, on your domain if you want, that nobody else uses.
Is CONX (formerly XPLA) RPC free?
Public CONX (formerly XPLA) endpoints are free and listed in CONX (formerly XPLA)'s official documentation (docs.xpla.io). They are shared and rate limited, which is fine for a wallet or a test. A dedicated CONX (formerly XPLA) node is the paid option for an app, bot or indexer, at one fixed monthly price.
What is the best CONX (formerly XPLA) RPC provider?
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.