Dedicated Taiko RPC node. A private Taiko RPC endpoint that only you use: no rate limits, every method on, one fixed monthly price.
Taiko is a based rollup on Ethereum: blocks are proposed by anyone and sequenced by Ethereum L1 validators.
Taiko RPC endpoint and network details.
| Network | Taiko mainnet |
| Chain ID | 167000 (0x28c58) |
| Currency | ETH |
| Public RPC URL | https://rpc.mainnet.taiko.xyz |
| Wallet | Add Taiko to MetaMask or another browser wallet. |
| Testnet pages | Taiko Hoodi |
| Interfaces | JSON-RPC · WebSocket |
| Block explorer | taikoscan.io |
| Testnet | Taiko Hoodi · chain ID 167013 · hoodi.taikoscan.io |
| Dedicated endpoint | Your own Taiko RPC endpoint, from $199/mo → |
Public URLs are shared and rate limited: fine for a wallet, not for an app, bot or indexer. Facts from Taiko's official documentation.
Order a dedicated Taiko 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 Taiko 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, debug and trace included
- Unlimited WebSocket connections
- Your own domain and an IP allowlist you control
- 99.99% SLA in writing, with service credits
- 24/7 support answered by engineers
Taiko node requirements, and what we build.
Chain facts from Taiko's official documentation (docs.taiko.xyz). Where it is silent, the row says so.
| Node software | alethia-reth, taiko-geth, taiko-client |
| Interfaces | JSON-RPC, WebSocket |
| Full node | Yes, from $199/mo |
| Archive node | Yes, quoted per setup |
| Validator | Taiko has no validator set of its own: blocks are sequenced by Ethereum L1 validators, proposing is open to anyone, and preconfirmers are whitelisted on chain. |
| Chain ID | 167000 |
| Gas token | ETH |
| Official hardware guidance | The docs give a minimum of 4 CPU cores, 16 GB RAM and a 2 TB SSD, noting storage grows over time; the node also needs an Ethereum L1 execution and beacon endpoint, and the docs warn that third-party RPC providers will eventually rate-limit it. 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 Taiko recently
Sources: docs.taiko.xyz/guides/run-a-node.md · docs.taiko.xyz/protocol/preconfirmations.md · docs.taiko.xyz/protocol/unzen-fork.md
Public Taiko RPC URLs, checked every week.
Free, shared Taiko endpoints from the chain registry that answered eth_chainId with 167000 in our weekly check (2 of 2). Good for a wallet or a test; once an app, bot or indexer depends on it, move to a dedicated Taiko RPC endpoint.
| Endpoint | |
|---|---|
https://rpc.mainnet.taiko.xyz | |
https://taiko-rpc.publicnode.com |
Dedicated Taiko RPC node: the questions buyers ask.
What is a Taiko RPC node?
A server running Taiko's node software (alethia-reth, taiko-geth, taiko-client) 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 Taiko RPC node?
A Taiko 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 Taiko 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 Taiko RPC endpoint?
An RPC endpoint that only your applications use. It sits on a dedicated Taiko 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 Taiko node is live?
As soon as it has synced with the Taiko 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) and the client you pick (alethia-reth, taiko-geth, taiko-client), 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 $199/mo for my Taiko node?
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.
What hardware will my Taiko node run on?
A machine that meets Taiko'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.
Which Taiko client should I choose?
alethia-reth: The default execution client since the Unzen fork, on mainnet and Hoodi (binary alethia-reth). taiko-geth: The geth-based alternative execution client (binary geth); runs as an archive node with --gcmode archive. taiko-client: The rollup driver that follows Ethereum L1 and drives the execution client; the same binary also runs the proposer and prover roles.
Does Argusnodes run Taiko archive nodes and trace methods?
Yes. Taiko's documentation describes full-history operation; we run Taiko archive nodes, quoted per setup, with trace and historical queries unmetered. Debug and trace methods are on for full nodes too, within their state window.
Can I run a Taiko validator with Argusnodes?
Taiko has no validator set of its own: blocks are sequenced by Ethereum L1 validators, proposing is open to anyone, and preconfirmers are whitelisted on chain. We run every node type the chain actually offers and none it does not.
Can I move my Taiko endpoint from another provider?
Yes. A dedicated Taiko 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.
Are there rate limits or connection caps on a dedicated Taiko 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 Taiko 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 Taiko chain ID?
167000 (hex 0x28c58), per Taiko's official documentation. A dedicated Taiko node answers eth_chainId with it, so wallets and libraries configured for Taiko work against your endpoint unchanged.
What is the Taiko RPC URL?
Public Taiko RPC URLs from the chain registry that answered our weekly check on chain ID 167000: https://rpc.mainnet.taiko.xyz, https://taiko-rpc.publicnode.com. Taiko's official documentation (docs.taiko.xyz) 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 Taiko RPC URL of your own, on your domain if you want, that nobody else uses.
Is Taiko RPC free?
Yes, public Taiko 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 Taiko node is the paid option for an app, bot or indexer, at one fixed monthly price.
What is the best Taiko 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.
Is Taiko the same as Taiko Alethia?
Yes. Taiko Alethia is the network's full name, chain ID 167000, with ETH as its gas token. A dedicated Taiko RPC node and a dedicated Taiko Alethia RPC node are the same thing.
How do I add Taiko to MetaMask with my own RPC URL?
Add a network manually with the chain ID 167000, the currency symbol ETH and your private Taiko 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.
Does Taiko have a block explorer?
Yes: taikoscan.io, as listed in Taiko's official documentation.
What is the Taiko testnet?
Taiko Hoodi, chain ID 167013, per Taiko's official documentation. We build dedicated Taiko Hoodi nodes too, on the same terms as mainnet.