Source evidence snapshot July 4, 2026. Ink mainnet uses chain ID 57073 / 0xdef1, RPC URL https://rpc-gel.inkonchain.com, explorer.inkonchain.com, and ETH as the gas token. Verify Ink source links and current RPC availability before relying on a public endpoint.
Quick settings
Ink chain ID answer
Use chain ID 57073 / 0xdef1 for Ink mainnet, with RPC URL https://rpc-gel.inkonchain.com, explorer.inkonchain.com, and ETH as the gas token. Copy the fields below, then check source docs and endpoint availability before use.
Availability check:Ink lists multiple RPC providers and endpoints. If the public endpoint fails intermittently, compare the linked provider docs and test the current endpoint before changing app configuration.
the Ink chain ID, RPC URL, explorer, and gas token in one place;
source documentation links beside the copied setup fields;
manual wallet config fields without connecting a wallet or choosing an RPC provider.
Before you paste these fields:
compare the chain ID against the source link on this page;
open the explorer once and confirm it matches the network you expect;
use the public RPC for setup checks, then choose monitored infrastructure for production traffic.
Exact setup guide
Ink chain ID and RPC guide
Open this guide when you specifically need chain ID, RPC URL, explorer, gas token, or wallet configfor Ink. It keeps the copied fields, official/source docs, and setup cautions together in one focused reference.
Automated source snapshots and recorded probe evidence are tracked separately. The source snapshot timestamp is not a manual review date. This is not a live uptime, latency, or production reliability monitor. If a recorded public RPC probe fails, verify the source links and current endpoint availability before changing production configuration.
Automated source snapshot
Verification status
Verified metadata
Source snapshot run
source-monitoring-2026-07-04
Source snapshot tool
source-monitoring-refresh
Source set
Ink docs
Latest recorded chain ID probe
eth_chainId matched expected 0xdef1; observed 0xdef1 on
Wallet directory sites often expose a connect button. Main.net keeps the same MetaMask and EIP-3085 setup fields as text so developers can compare them with official/source docs before calling wallet_addEthereumChain.
These checks are review signals only. They are not uptime, latency, privacy, or production reliability claims. A source fetch failure or eth_chainId failure can mean a source page or public RPC endpoint was unavailable, changed, or rate-limited during a check. Re-open source links and test current RPC availability before relying on a public endpoint.
Snapshot generated
Source checks
3 sources checked
Source changes
0 changes since the previous source hash snapshot
Source fetch failures
0
eth_chainId probe
matched expected 0xdef1
Per-source check timing
Included in the monitoring snapshot, not represented as a manual review or page freshness date
source-monitoring-2026-07-04 via source-monitoring-refresh
Ink common questions
What is the Ink mainnet RPC URL?
Ink's listed primary public RPC URL is https://rpc-gel.inkonchain.com.
What is Ink's chain ID?
Ink's listed chain ID is 57073.
What block explorer does Ink use?
Ink's listed block explorer is https://explorer.inkonchain.com.
What gas token does Ink use?
Ink's listed gas token is ETH.
Copy-ready config
Neutral app configuration built from the verified fields above. Copy buttons only place text on your clipboard; they do not connect a wallet, request permissions, or rank RPC providers.
Static examples generated from Main.net fields. These snippets are for manual configuration review and read-only RPC checks; they do not connect wallets, create signers, submit writes, or rank providers.
ts
viem chain definition
Read-only snippet generated from Main.net fields. Review official sources before production use.
External dashboards a developer may inspect before choosing where to deploy. Main.net links to these references but does not collect the metric values, normalize methodologies, rank chains, or recommend deployments.
Ink lists multiple RPC providers and endpoints. Verify primary endpoint availability and provider fit before routing production traffic through a public endpoint.
Main.net is an independent reference site. It does not operate this chain, custody assets, execute transactions, or provide investment advice.
Report a correction
If this page has stale RPC, explorer, chain ID, or source information, open a public correction issue with a source link so it can be checked.