An archive of bnoc.xyz · view original topic →
For August 2026, there are currently two forks scheduled:
It would be good to discuss what monitoring and data collection would be worthwhile for this. I invite everyone interested in this to participate in the discussion here.
I’ll probably run a fork-observer instance with a Bitcoin Core node and a BIP-110/300 node side by side. I’ll likely also live-stream this in some capacity.
Monitoring for transaction replay across the forks, assuming there are blocks for them, should be interesting as well. Not sure if I’ll get to this.
For the BIP-110 fork, someone might attempt to publish data-embedding transactions into the chain around the fork height or shortly after. Especially on the BIP-110 side. It would be good to have coverage of this, even if it’s not given that this will happen.
Additionally: observe on which side of these forks pools are mining. This can be done with stratum data. On top of that: What side is currently more profitable to mine on given the current fees and price?
At block ~964,000, the Bitcoin blockchain is read. Every address holding BTC at that moment is credited an equal amount of eCash — automatically, with no action required from you.
# · 
Mark "Murch" Erhardt · #5 ·
It might be helpful to some to create a data set that shows whether UTXOs are unique to Bitcoin, i.e., immune to replay on RDTS. Same for eCash, if they don’t have replay protection.
I’ve been thinking about adding a visualization of what-is-being-mined-on to fork-observer using stratum data: Show next block based on stratum jobs by 0xB10C · Pull Request #137 · 0xB10C/fork-observer · GitHub
An idea for an activation live stream would be to show a Core and Knots+BIP110 node on fork-observer and have them both connected to a ckpool instance each, which are then connected to a stratum-observer instance. This would show which blocks the nodes consider active and which block they are mining on. Could also mix in some of the bigger pools like AntPool, F2Pool, ViaBTC, … Maybe Foundry if we can get pool details too.
The same works for the eCash activation.
Seeing this makes me think we are going to see a bunch of inscriptions being broadcast for a potential BIP-110 compliant block right before around/activation: Add BIP-110 compatible envelope parser by lifofifoX · Pull Request #4545 · ordinals/ord · GitHub . Well, there also seems to be policy: count bare data envelopes (OP_2DROP/pushnum runs) as datacarrier by kwsantiago · Pull Request #319 · bitcoinknots/bitcoin · GitHub now…
added a height based countdown feature for halving/soft-forks/special heights to fork-observer: add: per-network height countdown by 0xB10C · Pull Request #142 · 0xB10C/fork-observer · GitHub
Relevant for tracking Ocean, a variety of stratum endpoints:
They updated the activation date to block 963,648, instead of 964,000. Aprox 22/08/2026
Found the node’s repo too:
b10c · 
Deadmanoz · 
Guille ·