# Brainstorming: What data to collect and monitor during the BIP-110 & BIP-300 forks in August 2026?
**URL:** https://bnoc.xyz/t/brainstorming-what-data-to-collect-and-monitor-during-the-bip-110-bip-300-forks-in-august-2026/139
**Category:** Data
**Created:** [June 9, 2026, 9:51am UTC](https://bnoc.xyz/t/brainstorming-what-data-to-collect-and-monitor-during-the-bip-110-bip-300-forks-in-august-2026/139 "2026-06-09T09:51:55Z")
**Posts on this page:** 7
**Page:** 2
### Author:  [@GuiSchet](https://bnoc.xyz/u/GuiSchet)
#### Post date: [August 22, 2026, 1:14pm UTC](https://bnoc.xyz/t/brainstorming-what-data-to-collect-and-monitor-during-the-bip-110-bip-300-forks-in-august-2026/139/21 "2026-08-22T13:14:52Z")
Quick update on my side for BIP300/301 monitoring: I built pilot bip300-monitor ( [GitHub - GuiSchet/bip300-monitor: A Rust monitor for BIP300/301 enforcer events, state, and metrics. · GitHub](https://github.com/GuiSchet/bip300-monitor) ), a pipeline that collects the enforcer’s validated chain state, normalizes snapshots and live block events, and publishes them through NATS. It also includes an event logger, container images, automated checks, and a reproducible eCash Drynet deployment.
I currently have the stack running on a dedicated VM. Over the next weeks, I plan to complete the enforcer synchronization and end-to-end verification, test live event delivery, and adapt the deployment to the latest eCash test-network stage.
---
### Author:  [@b10c](https://bnoc.xyz/u/b10c)
#### Post date: [August 24, 2026, 11:45am UTC](https://bnoc.xyz/t/brainstorming-what-data-to-collect-and-monitor-during-the-bip-110-bip-300-forks-in-august-2026/139/22 "2026-08-24T11:45:17Z")
Cool! Did you manage to use it this weekend during the alpha hard-fork?
---
### Author:  [@b10c](https://bnoc.xyz/u/b10c)
#### Post date: [August 24, 2026, 9:47pm UTC](https://bnoc.xyz/t/brainstorming-what-data-to-collect-and-monitor-during-the-bip-110-bip-300-forks-in-august-2026/139/23 "2026-08-24T21:47:59Z")
posted the following to [IRC](https://bitcoin-irc.chaincode.com/bitcoin-core-dev/2026-08-24):
> I’ve been seeing a higher stale block rate over the past two weeks since 961632. 6 stale blocks where I would have expected about 2. Wondering if this is variance or if propagation is hindered a bit by BIP-110 nodes
---
### Author:  [@ajtowns](https://bnoc.xyz/u/ajtowns)
#### Post date: [August 25, 2026, 12:36pm UTC](https://bnoc.xyz/t/brainstorming-what-data-to-collect-and-monitor-during-the-bip-110-bip-300-forks-in-august-2026/139/24 "2026-08-25T12:36:24Z")
I don’t see how bip110 nodes would have any impact? They should disconnect fairly fast, shouldn’t attempt to announce new blocks to interfere with queue slots, and shouldn’t be triggering much resource usage?
If there’s a real higher stale rate, main cause should be that it takes longer for new work to get to mining devices; if there had been significant uptake of datum or stratumv2 job negotiation, I could see that having an effect, but I don’t think that’s plausible.
Oh, I think I have seen a bunch of tx spikes recently; so if any have been particularly severe, lack of [PR#34628](https://github.com/bitcoin/bitcoin/pull/34628) could trigger it if pools’ nodes are overloaded enough to see delays in receiving blocks or generating updated templates. I have no idea if the spikes were severe enough to cause this, or if any were correlated with the observed stale blocks.
---
### Author:  [@b10c](https://bnoc.xyz/u/b10c)
#### Post date: [August 25, 2026, 9:43pm UTC](https://bnoc.xyz/t/brainstorming-what-data-to-collect-and-monitor-during-the-bip-110-bip-300-forks-in-august-2026/139/25 "2026-08-25T21:43:53Z")
Oh, you’re right. I should have checked the BIP-110 node I run. For some reason I assumed the connections it has to Bitcoin Core nodes are longer-lived. It currently has only BIP-110 and spy-node connections, so it’s unlikely to hinder propagation in this case.
---
### Author:  [@GuiSchet](https://bnoc.xyz/u/GuiSchet)
#### Post date: [August 26, 2026, 7:09pm UTC](https://bnoc.xyz/t/brainstorming-what-data-to-collect-and-monitor-during-the-bip-110-bip-300-forks-in-august-2026/139/26 "2026-08-26T19:09:57Z")
Yeah, I’m a bit behind on it. I only updated the monitor to Alphanet this week, so I wasn’t able to properly use it during the alpha hard-fork weekend.
---
### Author:  [@GuiSchet](https://bnoc.xyz/u/GuiSchet)
#### Post date: [September 16, 2026, 10:11pm UTC](https://bnoc.xyz/t/brainstorming-what-data-to-collect-and-monitor-during-the-bip-110-bip-300-forks-in-august-2026/139/27 "2026-09-16T22:11:06Z")
I’ve uploaded a first snapshot from my eCash Alphanet BIP300301 enforcer monitor:
> **[bip300301-monitor – Google Drive](https://drive.google.com/drive/folders/1DOkpoXGuoNpnGr9M1sfrzqA-mFp4DfMP?usp=sharing)**
It contains BIP300/301 events and block-level data from height 963,648 through 997,202.
I plan to keep tracking protocol changes from now through the October 30 mainnet launch.
I’m also working on a web app to explore and visualize the data. Feedback and ideas for useful visualizations or additional data are very welcome!
[Previous page](https://bnoc.xyz/t/brainstorming-what-data-to-collect-and-monitor-during-the-bip-110-bip-300-forks-in-august-2026/139.md?page=1)