Three questions keep landing in my inbox: what happens on August 8th, whether I need to do anything, and whether this is going to activate. The first two have answers. Nobody has the third, and be wary of anyone who tells you otherwise. I built this to sort out what can actually be known:

BIP-110 Observer

BIP-110 signalling, measured against own Bitcoin nodes. Every number labelled by how much it can be trusted.

DO I NEED TO DO ANYTHING WITH MY BITCOIN? No. It is the first thing on the page, before any chart. If you keep your bitcoin in self-custody, you do not need to move anything, upgrade anything or pick a side. The real risk in these weeks is not the fork. It is the scams that come with it. HAS BITCOIN SPLIT IN TWO? Nobody needs to answer that one for you. It can be checked. Behind the panel there are two of my own nodes. One follows today's rules, the other follows the BIP-110 rules. While both see the same blocks there is one chain. The day they stop matching, there are two. Nobody has to announce it. And since the rules are already written, you can see today how that same page will look if the chain splits, and if it comes back together. Only the point marked NOW carries real data. The other two are an example, so the day it changes does not catch you off guard. THE FIGURE ALMOST NOBODY IS LOOKING AT Right now 2.33% of blocks signal and 55% is needed. But the percentage on its own says little. What says something is where it comes from: across the last five closed periods, 77 of the 78 blocks that signalled came from a single pool holding 3.2% of mining. That describes one operator, not a movement. AND A WARNING THAT LIVES ON THE PAGE ITSELF The node count does not measure support for BIP-110. Nobody can measure that, this panel included. The reasons are on screen, in full, not tucked away in a footnote. Every figure carries a label for how much it can be trusted, and none of them gets promoted. Also, the dates are three, not one. That is the most common mistake in the whole debate and it is explained there in plain language. Read from my own nodes. No explorers, no third party APIs, no analytics. MIT licensed and the methodology is public. github.com/decentralizedb/bip110-observer The metrics may have bugs and I will keep fixing them. The crawler is the most fragile part, so if you spot one, open an issue.