// Japan Open Chain

The Stack Japan Open Chain Builders Ship On

Connect to Japan Open Chain Mainnet with low-latency RPC, full archive data, debug and trace APIs, and real-time Streams. The complete Japan Open Chain data stack, managed from a single Quicknode dashboard.

// Supported networksMainnet
// 99.99% uptime SLA17+ global regions
// Unified Japan Open Chain Stack

Mainnet, Archive, and
Streams in One Dashboard.

Japan Open Chain builders need more than basic RPC. Quicknode runs the full surface: low-latency JSON-RPC, full archive with debug and trace, and real-time Streams, all from one dashboard.

InterfaceStatus
MAINNETONLINE
ARCHIVEONLINE
EVMONLINE
STREAMSACTIVE
// Read & Stream

Data Access for Every Japan Open Chain Workload

Query, subscribe, and stream Japan Open Chain data with low latency. From a single eth_call to billions of rows of historical logs, you get the right interface for the job.

JSON-RPC over HTTPS and WSS on Japan Open Chain Mainnet and Testnet
Full archive nodes on Mainnet with debug_traceTransaction and debug_traceBlockByNumber
Streams for backfill and real-time Japan Open Chain blocks, logs, and traces
Webhooks for push notifications on addresses and events
WebSocket subscriptions with eth_subscribe for new blocks and logs
// Build & Ship

EVM Tooling You Already Know

The Ethereum toolchain you already know works unchanged on Japan Open Chain. Deploy contracts, manage endpoints, and ship from one Quicknode account.

Deploy and verify Solidity contracts with Hardhat, Foundry, and Remix
Token authentication, rate-limiting, JWT, and whitelisting on every endpoint
ethers.js, web3.js, viem, and @quicknode/sdk supported out of the box
Archive access with debug and trace for indexing and simulation

Enterprise-grade security and compliance built in

SOC 1
SOC 2 Type II
ISO 27001
// Every Japan Open Chain Data Pattern

The Full Data Suite.
Every Japan Open Chain Data Pattern.

Multiple ways to access Japan Open Chain data, from a single eth_call to real-time streams. Pick the interface, ship faster.

Japan Open Chain JSON-RPC

Standard JSON-RPC over HTTPS and WSS on Japan Open Chain Mainnet and Testnet. Every EVM method supported, including eth_call, eth_getLogs, eth_getBalance, eth_sendRawTransaction, and eth_subscribe, with predictable rate limits.

Full Archive History

Full historical Japan Open Chain state on Mainnet with no pruning. Query any block, balance, or contract state from genesis over HTTPS and WSS.

Streams

Backfill and real-time Japan Open Chain blocks, logs, and traces delivered to your datastore with guaranteed reliability. Filter upstream, receive only the data you actually need.

Webhooks

Event-driven alerts with guaranteed delivery. Subscribe to specific addresses, event types, or onchain conditions.

Debug API

Trace transactions and inspect execution with the debug namespace, including debug_traceTransaction and debug_traceBlockByNumber, for deep analysis and reliable indexing.

WebSocket Subscriptions

Subscribe to new Japan Open Chain blocks and logs over a persistent WSS connection with eth_subscribe. Push updates the moment they land, with no polling.

// Built for EVM Developers

Your Ethereum app runs on Japan Open Chain.

Japan Open Chain is an Ethereum-compatible layer 1 running the Geth client, so the tooling you already know works unchanged. ethers.js, web3.js, viem, and web3.py all hit a Quicknode Japan Open Chain endpoint the same way they hit Ethereum. Same methods, same SDK, just a different RPC URL.

No rewrites

Point your existing Ethereum codebase at a Quicknode Japan Open Chain endpoint and deploy. Contracts, libraries, and tooling carry over.


Same JSON-RPC methods

eth_call, eth_getLogs, eth_sendRawTransaction, and eth_subscribe all behave exactly as they do on Ethereum.

  • 01
  • 02
  • 03
  • 04
  • 05
  • 06
  • 07
  • 08
  • 09
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
// Your Ethereum code, pointed at Japan Open Chain
import { createPublicClient, http } from "viem";
const client = createPublicClient({
// Japan Open Chain, chain ID 81
chain: { id: 81, name: "Japan Open Chain" },
transport: http(QUICKNODE_JOC_URL)
});
const block = await client.getBlockNumber();
// Same methods, same SDK. Japan Open Chain is EVM compatible.
// Add Japan Open Chain to MetaMask

Connect MetaMask to Japan Open Chain in seconds.

Open MetaMask, go to Settings, Networks, Add Network, and enter your Quicknode Japan Open Chain RPC URL with the details on the right. Save, and MetaMask routes through your private Quicknode endpoint instead of a rate-limited public RPC.

FIELDVALUE
Network nameJapan Open Chain
RPC URLYour Quicknode Japan Open Chain URL
Chain ID81
Currency SymbolJOC
Block Explorerexplorer.japanopenchain.org
// Resources

Build on Japan Open Chain quicker.

Docs, guides, and runnable sample apps for every Japan Open Chain workload. Clone, customize, and ship.

// Docs

Japan Open Chain Documentation

Full reference for every Japan Open Chain JSON-RPC method, WebSocket subscription, and the debug and trace namespaces. Code examples for @quicknode/sdk, ethers.js, web3.js, and viem.

// guide

Build a Japan Open Chain Indexer with Streams

Indexes token transfers on an EVM chain using Quicknode Streams and delivers them to your own datastore and API. Works unchanged on Japan Open Chain.

// Sample Apps

Sample App Library

Runnable sample apps and starter kits across Quicknode-supported chains, including Japan Open Chain. Clone one and ship.

// Let's Build

Start where you are.

From your first Japan Open Chain endpoint to mission-critical production workloads, Quicknode scales with you. Get started in minutes.

// Developers

For builders who move fast.

Spin up your Japan Open Chain endpoint and ship. The free tier covers prototyping and small production loads, no credit card required.

Start building for free
// Enterprise

For teams scaling with confidence.

Dedicated Japan Open Chain infrastructure, contractual SLAs, priority support, and procurement-ready terms for wallets, exchanges, trading firms, and high-volume protocols.

Contact sales
"We run a lot of service dependencies. Quicknode's Admin API was one of the first we could plug directly into our burn rate dashboards. The MCP slots right into our cross-service incident triage stack alongside our other providers. Solid tooling that respects your time."
Liam Harris, Head of Operations @ Defi App
// FAQ

Frequently Asked Questions

Still have unanswered questions? Reach out to support and the Quicknode team can help you find answers.