EDIT, NM the latest version is v3.2.1.1. I used this rather long versioning in order to track what version it is origionally forked from. The latest update fixes the bug where the orange decorations disappear, and draws most of the mining pool icons.
Thanks. I did notice a new version was released
I do see a bug in the latest version I’ll need to fix:
Ths bar is supposed to fill up as blocks signal within the sliding window (if 55% is hit, then the soft fork activates early). It isn’t counting the one signalling block though ![]()
I understand the bar reporting is buggy but I notice a bar on screen saying
Scanning blocks for BIP-110 data: 4%
Scanning ALL blocks?
Yes, it has to examine the contents of each block to identify violations, and then tag two properties to each block (number of violating transactions, and percentage of block space in violation). This process scans all blocks since Taproot activated, since that’s the genesis of what BIP-110 primarily targets. Technically there could be large OP_RETURN’s before then, but since there were mempool policy filters in place since 2014, you’d be scrolling a long time to try and find one. The process is throttled way down so that it isn’t consuming a huge amount of resources (should finish in a couple of days)
You find anytime for this yet?
Not yet. I’ve been preparing to record a video for the big project I’ve been working on for the last couple of months (won’t reveal more yet, though if you follow my GitHub account you might have an idea). I will definitely get back to focusing on my ant-spam and BIP-100 projects next.
Yes…I think I know what your working on. Looking forward to it actually.
March 27, 2026. Barefoot Mining
I also see Signaling=1 (should be 2 …weird it didn’t pick up the first one earlier)
I don’t have the BIT 4 SIGNAL bar on my instance so don’t see BIP-110 deployment detail.
Feels like I’m missing something?
Just checked Paul’s opening post so understand why I don’t get the same detail.
Yet another one today.
I noticed that the BIP 4 signals is only lasting a little while though…seems it resets to zero after the block further into the ledger. Not a huge deal but it nice to see that 3 OCEAN miners are signalling BIP-110
Yes, I think it only sees them when they are in the immediate cache upon loading, or when the UI is left open. I think the issue is that it doesn’t save the BIP110 bit with the rest of the high-level block properties. Should be a simple fix.
I have been using this for a few weeks now, thank you for releasing it. Looking forward to the update to the block counter especially now that more BIP-110 blocks are being mined ![]()


