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 ), 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.
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
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 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.
Oh, you’r 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.
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.