Dedicated Japan Open Chain RPC node. A private Japan Open Chain RPC endpoint that only you use: no rate limits, every method on, one fixed monthly price.
Japan Open Chain is an Ethereum-compatible Layer 1 that runs on Go Ethereum with Proof of Authority consensus, operated by a consortium of Japanese companies and built to comply with Japanese law. Mainnet uses chain ID 81 and JOC as the transaction fee token.
Japan Open Chain RPC endpoint and network details.
| Network | Japan Open Chain mainnet |
| Chain ID | 81 (0x51) |
| Currency | JOC |
| Public RPC URL | https://rpc-1.japanopenchain.org:8545 |
| Wallet | Add Japan Open Chain to MetaMask or another browser wallet. |
| Interfaces | JSON-RPC |
| Dedicated endpoint | Your own Japan Open Chain RPC endpoint, from $139/mo → |
Public URLs are shared and rate limited: fine for a wallet, not for an app, bot or indexer. Facts from Japan Open Chain's official documentation.
Order a dedicated Japan Open Chain 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 Japan Open Chain 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 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
Japan Open Chain node requirements, and what we build.
Chain facts from Japan Open Chain's official documentation (www.japanopenchain.org). Where it is silent, the row says so.
| Node software | geth |
| Interfaces | JSON-RPC |
| Full node | Yes, from $139/mo |
| Archive node | Confirmed at quote time |
| Validator | Permissioned consortium (PoA); validators are 21 approved Japanese companies, not open to the public. |
| Chain ID | 81 |
| Gas token | JOC |
| Argusnodes build | Meets Japan Open Chain's official requirements 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 Japan Open Chain recently
- The official node setup guide is tested up to Geth 1.13.5 and the mainnet runs at the London hard fork level, so run a full sync (--syncmode=full --snapshot=false) with a Geth build from that line rather than assuming the newest upstream release. source ↗
- The public RPC endpoints are for non-commercial use only; commercial applications are told to run their own node or use an endpoint provider. source ↗
- JOC COIN, the native fee token, listed on the Zaif exchange on 12 Feb 2026 (announced 3 Feb 2026 by Japan Blockchain Foundation). source ↗
- Japan Blockchain Foundation announced on 13 May 2026 that it will issue EJPY, a trust-type JPY-pegged stablecoin, primarily on Japan Open Chain; the chain is actively developed as of mid-2026 but no hardware guidance is published. source ↗
Sources: www.japanopenchain.org/en/docs · www.japanopenchain.org/en/docs/developer/dev-on-ethereum · www.japanopenchain.org/en/docs/developer/connect-joc/mainnet
Public Japan Open Chain RPC URLs, checked every week.
Free, shared Japan Open Chain endpoints from the chain registry that answered eth_chainId with 81 in our weekly check (3 of 3). Good for a wallet or a test; once an app, bot or indexer depends on it, move to a dedicated Japan Open Chain RPC endpoint.
| Endpoint | |
|---|---|
https://rpc-1.japanopenchain.org:8545 | |
https://rpc-2.japanopenchain.org:8545 | |
https://rpc-3.japanopenchain.org |
Dedicated Japan Open Chain RPC node: the questions buyers ask.
What is a Japan Open Chain RPC node?
A server running Japan Open Chain's node software (geth) 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 Japan Open Chain RPC node?
A Japan Open Chain 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 Japan Open Chain 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 Japan Open Chain RPC endpoint?
An RPC endpoint that only your applications use. It sits on a dedicated Japan Open Chain 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 Japan Open Chain node is live?
As soon as it has synced with the Japan Open Chain 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 $139/mo for my Japan Open Chain 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 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 Japan Open Chain node run on?
A machine that meets Japan Open Chain's official requirements 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 Japan Open Chain archive nodes and trace methods?
Archive support on Japan Open Chain 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 Japan Open Chain validator with Argusnodes?
Permissioned consortium (PoA); validators are 21 approved Japanese companies, not open to the public. We run every node type the chain actually offers and none it does not.
Can I move my Japan Open Chain endpoint from another provider?
Yes. A dedicated Japan Open Chain node speaks the same JSON-RPC interface 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 Japan Open Chain 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 Japan Open Chain 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 Japan Open Chain chain ID?
81 (hex 0x51), per Japan Open Chain's official documentation. A dedicated Japan Open Chain node answers eth_chainId with it, so wallets and libraries configured for Japan Open Chain work against your endpoint unchanged.
What is the Japan Open Chain RPC URL?
Public Japan Open Chain RPC URLs from the chain registry that answered our weekly check on chain ID 81: https://rpc-1.japanopenchain.org:8545, https://rpc-2.japanopenchain.org:8545, https://rpc-3.japanopenchain.org. Japan Open Chain's official documentation (www.japanopenchain.org) 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 Japan Open Chain RPC URL of your own, on your domain if you want, that nobody else uses.
Is Japan Open Chain RPC free?
Yes, public Japan Open Chain 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 Japan Open Chain node is the paid option for an app, bot or indexer, at one fixed monthly price.
What is the best Japan Open Chain 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.
How do I add Japan Open Chain to MetaMask with my own RPC URL?
Add a network manually with the chain ID 81, the currency symbol JOC and your private Japan Open Chain 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.