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

A server running GIWA's node software (op-reth, op-node) 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 GIWA 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 GIWA 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 GIWA 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 (op-reth, op-node), 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 GIWA'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.

op-reth: The only supported execution client since the Karst hardfork; the official docker-compose builds it at v2.3.3 and offers snap-synced full (RETH_GCMODE=full), archive (RETH_GCMODE=archive) or consensus-driven sync, one at a time (https://github.com/giwa-io/node). op-node: The rollup client, v1.19.1 in the official compose, driving op-reth over the Engine API (OP_NODE_L2_ENGINE_KIND=reth) with a Sepolia L1 RPC of kind debug_geth and an L1 beacon endpoint (https://github.com/giwa-io/node).

Yes. GIWA's documentation describes full-history operation; we run GIWA 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.

GIWA is an OP Stack rollup: blocks come from the network sequencer and are settled on Ethereum, so there is no validator or staking role. Full nodes verify the chain and serve RPC. We run every node type the chain actually offers and none it does not.

Yes. A dedicated GIWA 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.

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

Public GIWA RPC URLs from the chain registry that answered our weekly check on chain ID 91342: https://sepolia-rpc.giwa.io. GIWA's official documentation (docs.giwa.io) 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 GIWA RPC URL of your own, on your domain if you want, that nobody else uses.

Yes, public GIWA 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 GIWA 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 91342, the currency symbol ETH and your private GIWA 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.