BlockDAG Network Directory

Submit an endpoint

It is probed automatically and appears once it passes 2 consecutive checks. Private/internal addresses are rejected.

An explorer is fork-checked from its own block data at several heights incl. the fork point — so an explorer on a private node with no public RPC still gets a real works/other verdict. We read, in order: a /api/block/{height} endpoint, a Blockscout API, then your server-rendered block pages, then a linked/auto-detected RPC; otherwise it lists as live but fork-unverified.

Explorer operators — for the most robust, restyle-proof verification, expose one tiny endpoint that reads your node:
GET /api/block/<height> → {"height": N, "hash": "0x…"} (the canonical block hash at that height). Optional but recommended; if present we prefer it over scraping. Nothing else required — no wallet, no public RPC.

If you give the address(es) your pool mines to, we will say so publicly when one of them mines a block on the works chain — the only evidence of a pool's chain that cannot be faked. Multiple is fine (one wallet per backing pool behind a load balancer). Declared addresses are shown publicly, so claiming someone else's is visible to them.

What gets filled in automatically. Every probe resolves your host and we publish the IP addresses we see — you do not enter them. For a pool that is your real origin IP, because stratum is raw TCP and cannot sit behind an HTTP proxy like Cloudflare; if you run a pool from home, expect your home IP to be listed. RPC endpoints behind a proxy show only the CDN's edge addresses, labelled as such.
Wallet addresses are never auto-filled — only ever what you declare here or change later.