Bitcoin Lab 1.26.0

Bitcoin Lab now notices pool apps installed on your Umbrel. With Stratum Race on, if it finds GoBrrr, Bassin, Public Pool, DATUM or Pogolo and they are not in Stratum Race yet, it offers to add them, once in each browser. The quick-fill buttons stay for later, now including DATUM and Pogolo. Finding them is only a name lookup: nothing connects to a pool until you add it.

Bitcoin Lab 1.25.8

Bitcoin Lab 1.25.8 closes a gap and makes rotation more careful with your choices. The dashboard now only accepts changes from its own page, so another website you have open can no longer reset your data or disconnect peers through your Umbrel login. Manual peers you set in Core yourself, for example in Umbrel's Bitcoin Node settings, are now protected, a reset keeps manual peers that are offline, and after Core restarts your manual peers are back within seconds. Typing in a peer never pushes out a protected one, and the same node written two ways now counts once. Without Stratum Race switched on, Bitcoin Lab no longer asks Core for a block template on every block.

1.25.7

Catching up no longer skews the ranking. Blocks your node fetches after being offline arrive several a second from many peers; they used to be scored like new blocks and credited whoever served the backlog. They are now left out, and only blocks that reach the tip are counted.

Opening a peer from Peer Map lands on it. Inbound peers outside the top ten of the live ranking had no row to mark, so the link opened Bitcoin Lab as if nothing had been asked. The list now opens for that peer, and the page moves to it right away.

v1.25.6

Quiet outbound peers are replaced again. Rotation now judges an outbound peer on the last 500 blocks, the same window the dashboard shows. A former manual peer that once delivered first used to be spared for good, even after a week without delivering anything, and kept one of Core's outbound slots from finding new candidates.

v1.25.5

Swaps connect the new peer right away. When rotation replaced a manual peer, the displaced one stayed connected and kept one of Core's eight manual slots, so the new peer could not connect until the old one dropped by itself. The displaced peer is now disconnected; it keeps its record and can win a slot back like any other peer.

v1.25.4

Core's anchors stay put. Rotation no longer disconnects or promotes block-relay-only peers, the two connections Bitcoin Core keeps as anchors against eclipse attacks. They are still measured and ranked, and you can still add one by hand. A new section in the docs answers whether choosing peers makes an eclipse attack easier. Peers that offer no services are now struck through, as in Peer Map.

1.25.3

Peer kinds. Recognises more crawlers, other chains and Kyoto light clients, the same way Peer Map does.

1.25.2

Manual peers. A padlock marks the peers the rotation keeps.

1.25.1

Traffic. Only the node's daily totals now; the table per peer is gone, and so is its data.

1.25.0

Traffic. See what your node sent and received per day, and which peers used the most. Plus a second widget for today's traffic.