Grin API Status

—
—
JSON-RPC /v2/foreign — checking… REST /rest/ — checking…
Block Height
…
Total Difficulty
…
Latest Block Hash
…
Circulating Supply
…
Emission Rate
1 GRIN / second
60 GRIN / block  ·  86,400 GRIN / day
Node Version
…
Header Version (increments on hard fork)
…
Response Time — last get_tip round-trip
…
Connected Peers
—
Chain Data Size
This one's tough for me to crack ^^ — help welcome!
Connect Your Wallet — Clearnet
grin-wallet  ·  Edit grin-wallet.toml
check_node_api_http_addr = "https://…"
Set check_node_api_http_addr to this node's URL, then restart your wallet. No local node required — the wallet will sync directly via this HTTPS endpoint.
Grim GUI Wallet  ·  External Connections
https://…
  1. Open Grim → go to External Connections
  2. Click ADD NODE
  3. Paste the URL shown above and click ADD
  4. The node should appear with status Available
External connections let Grim use a remote node — no local Grin node process needed.
Connect Your Wallet — Tor Onion Network 🧅
grin-wallet  ·  Edit grin-wallet.toml  ·  run via torsocks
check_node_api_http_addr = "http://….onion"
  1. Set check_node_api_http_addr to the onion URL above in grin-wallet.toml
  2. Install Tor on the wallet machine: apt install tor torsocks
  3. Run all wallet commands through torsocks: torsocks ./grin-wallet info
CLI only — Grim GUI does not support Tor/SOCKS5 routing  ·  The .onion identity survives node rebuilds (Ed25519 keys preserved)
REST Endpoints
REST API status — simple GET endpoints updated every 60 s
Checking…
Enable via script 04 → select network, then option 7
Available endpoints — click to open, or copy URL to fetch from anywhere
…
GET request  ·  CORS enabled (Access-Control-Allow-Origin: *)  ·  Cache-Control: public, max-age=60
Which API style should I use?
JSON-RPC /v2/foreignREST /rest/*.json
Request methodPOSTGET
Auth requiredNo (foreign API)No
Response format{"result":{"Ok":{…}}}{"height":…}
Live dataAlways freshUp to 60 s old
Best forWallets, explorers, tx push, full chain queriesCoinGecko, widgets, spreadsheets, no-code tools
Browser fetchNeeds POST + JSON bodyOne-line fetch(url)
Developer — JSON-RPC
Live API test — runs get_tip directly from this browser
Click "Run Test" to fetch live data from this node…
Executes in your browser — no terminal needed  ·  same-origin fetch to /v2/foreign
CORS test — verify any website can query this API
…
Expected response header: Access-Control-Allow-Origin: *  ·  Run from any terminal on any machine
Browser fetch test — get chain tip & circulating supply from any website's console
  1. Open any website — e.g. https://www.google.com
  2. Press F12  (or right-click anywhere → Inspect)
  3. Click the Console tab at the top of DevTools
  4. Paste the command below and press Enter
  5. The JSON response from this node will appear directly below
…
Circulating supply is not a direct field — it is derived as height × 60  ·  Copy this snippet into your own site to display live Grin data
Remote API checker — test another Grin node's public endpoint
Enter a remote Grin node origin above and click Check…
Sends get_tip to {origin}/v2/foreign directly from your browser  ·  If CORS is missing on the remote node, the browser will block it and show an error