v1.0.0

The header now counts LinkingLion connections on their own, with a link explaining who they are. Peer Map now recognises LinkingLion by the ranges in the bnoc banlist, including two single addresses it missed: on my node one of them alone had opened 5,822 connections under 82 fake wallet names. Peers whose user agent contains /mempool count as indexers again. Locations and network names now come from October's DB-IP data.

v0.9.6

"Fake" is now called "Disguised", and it now also catches peers that call themselves Bitcoin Core but offer nothing – real Core always offers at least blocks. ckp2p is no longer listed as a pool node, a "(mempool…)" label no longer makes a node a pool or an indexer, and NBitcoin and Bitcore get a short description. On Umbrel, inbound IPv6 peers now show as "IPv6 (address hidden)" instead of "Private": umbrelOS hands them over through Docker, which hides their real address.

Peer Map 0.9.5

Peer Map now names LinkingLion. Peers from the address ranges that 0xB10C tracks as LinkingLion – an entity that connects to many nodes and may link transactions to their IP addresses – are still listed as Fake, and their description now says who they probably are. Connections without a user agent from these ranges are recognised too.

Peer Map 0.9.4

Peer Map 0.9.4 is a maintenance release. It is built with Go 1.27, with the build image pinned, and when Bitcoin Lab's block information is too large to read it now says so in its log instead of quietly dropping the block card. Bitcoin Lab 1.25.8 keeps that reply small, so update both.

v0.9.3

See how spread out your peers are. Each group now counts its providers and countries, so you can tell at a glance whether your manual peers sit with one host or many. Struck through now means the same for every kind: this peer cannot deliver a block first.

0.9.2

See who your peers really are. Filtering by a kind now says why, and shows each peer's user agent and what that software is. A new Fake kind catches peers pretending to be something else - like an old Core version offering what it never had - and says what they claim and what they probably are. More crawlers and node software are recognised, and the header counts how many peers are fake or crawling.

0.9.1

The route card keeps the transaction count when your pool's job is ready the same moment as the template.

0.9.0

See why a job took longer. Next to the time your pool needed to build its job, the route now shows how many transactions the block template carried. The bigger the template, the longer the job takes. This needs Bitcoin Lab 1.24.0. With an older version the route looks as before.
A node that names a pool in its user agent, such as "(PyBLOCK-POOL)", now shows as a pool node. A lost connection to Core reads as a short sentence instead of a raw error with your node's address, and closing a browser tab no longer leaves the map showing an error for a few seconds.

v0.8.0 — the peers that deliver, in colour

Green rows in the peer tables are the connections Bitcoin Lab has seen
deliver a block first at least once. On one real node that is about one in
twelve connected peers — every manual peer and a handful of inbound ones. The
peer that brought the newest block is orange for as long as its star is
up, two minutes, and then turns green.

The route of a block reads better when your peer had the block before any
pool sent a job. The first job is the zero the times are counted from, not a
stop the block passes, so it no longer cuts the ping into two unlabelled
pieces.

Green and orange rows need Bitcoin Lab 1.23.0.

v0.7.0 — four stretches, and the typical block

The route of a block now has four stretches, each with its own lever: the
block reaching your peer, the hop into your node, Core building the next
template, and your pool turning it into a job. Where the time goes is where
you can make it shorter.

Beside this block's route there is the typical block: every stop at its
median over the last hundred blocks. One block scatters; the median shows
whether a change made anything shorter. Switch between the two above the
route — the choice is remembered.

The template stop needs Bitcoin Lab 1.22.0. With an older Bitcoin Lab the card
is as it was.