Brainstorming: What data to collect and monitor during the BIP-110 & BIP-300 forks in August 2026?

Data
1

For August 2026, there are currently two forks scheduled:

  • BIP-110 at height 961632 (early August; around 2026-08-07)
  • BIP-300 on 2026-08-21 (ecash.com). I think there’s no fixed activation height set yet?

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.

2 Likes
2

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.

1 Like
3

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?

1 Like
4

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.

1 Like