Web3 node map

Decentralized networks are public by design — every node gossips its peers so the network can find itself. We collect those peer lists from each project’s own feeds (and, where a project has no list, our own discovery crawler), normalize them to IP addresses, and store them as a lookup table plus a daily census so we can show change over time.

A web3 tag is a positive / neutral fact about an IP: it tells you the address runs participatory infrastructure. It is deliberately kept out of the reputation score — running a blockchain node is not abuse. Full provenance is on the data sources page.

Web3 is a loose term for internet services built on decentralized, peer-to-peer infrastructure rather than a single company’s servers. Instead of one provider hosting an application and its data, the work is spread across many independent machines — called nodes — that each hold a copy of the network’s state and talk directly to one another.

The contrast is with the traditional client-server model, where your browser (the client) connects to a known server controlled by one operator. In a web3 network there is no central server to point at: any node can serve the data, and the network keeps working as nodes join and leave. Common examples include blockchains such as Bitcoin and Ethereum, and storage networks such as IPFS, Filecoin and Arweave.

Because these networks run on real machines with real public IP addresses, IP-level visibility matters: it’s how you see where a decentralized network physically lives, how concentrated it is across providers and countries, and whether a given address is taking part. That is exactly what this web3 node map shows.

A blockchain is a distributed ledger — a shared, append-only record of transactions that is replicated across many computers at once. Records are grouped into blocks, each cryptographically linked to the one before it, so the history is tamper-evident: changing an old block would break every block that follows.

No single party holds the master copy. Instead, a network of nodes each maintains the full ledger and follows the same rules (a consensus protocol) to agree on which new blocks are valid. This is what makes a public, permissionless blockchain like Bitcoin or Ethereum decentralized: anyone can run a node, read the chain, and help verify it, without asking permission from a central authority.

Because the ledger is public and replicated, the machines maintaining it must be reachable by their peers — which is why blockchains are visible at the IP level at all.

A blockchain node is simply a machine running a network’s software and participating in it — storing some or all of the ledger and exchanging data with other nodes. Most public networks run on tens of thousands of nodes worldwide, though the exact count varies by network and changes constantly as machines come online and go offline.

Nodes come in several roles, depending on the network:

• Full nodes — download and independently verify the entire chain, enforcing every rule.
• Validator / consensus nodes — help produce and confirm new blocks (mining or staking).
• RPC / gateway nodes — expose an interface so wallets and apps can read the chain and submit transactions.
• Storage nodes — hold and serve data on networks like IPFS, Filecoin or Arweave.
• Relay / bootstrap nodes — help new peers find and connect to the rest of the network.

To do any of this, a node needs a reachable network address. Most have a public IP and openly advertise themselves so other peers can connect — a process called gossip. That public reachability is what lets a WorldIP.io IP page identify an address as a node in the first place.

A peer-to-peer (P2P) network has no central server: every participant is both a client and a server to the others. To function, peers must be able to find each other, so these networks build in their own discovery mechanisms — typically gossip (nodes share the addresses of peers they know) and distributed hash tables (DHTs) (a shared directory of who is reachable where).

A direct consequence is that node IP addresses are publicly observable by design. A node has to announce a reachable address for the network to work at all; if it stayed hidden, no peer could connect to it. So seeing a network’s nodes is not a security leak or a flaw — it is the network operating exactly as intended, and the same information any other participant can see.

WorldIP.io reads this already-public peer information, normalizes it to IP addresses, and indexes it — the same way it indexes public DNS and routing data elsewhere on the site.

Whether an IP runs a blockchain or P2P node is a useful piece of network intelligence — it tells you something concrete about what an address does. We fold it into the same per-IP picture as geolocation, ASN, reverse DNS and routing, so it’s available wherever you look up an address.

It is treated as a neutral, informational signal — not a threat or reputation factor. Running a node is legitimate participatory infrastructure, so a web3 tag is deliberately kept out of an IP’s reputation score; it never raises or lowers an address’s trust score.

The data is useful for researchers studying decentralization, for node operators checking how their network is distributed, and for anyone interested in the geographic and ASN distribution of web3 infrastructure — how many nodes there are and where they are located. You can see it two ways: as the map and per-network stats on this page, and as a web3 badge on any individual IP page that runs a node. Full provenance is on the data sources page.