what tooling or extra data in p2p messages you wish bitcoin had
I’m not sure if you’re asking about adding more P2P messages to the Bitcoin protocol intended for all nodes, or something specifically for p2poolv2? From reading your post, I’m unsure if p2poolv2 uses the same P2P message format as Bitcoin, but extends the implementation with more features.
So what can we add to p2p messages or headers to improve observability?
There are the the proposals for a staleheader messages by @gmaxwell or the staletip message proposal and implementation by @ajtowns that come to mind here. These would allow observing stale headers/blocks on the network.
Also, is there a compact block miss rate observation tool somewhere? I see this: Calculate and expose the stale block rate per network · Issue #94 · 0xB10C/fork-observer · GitHub
This fork-observer issue is more a UI thing for the page showing the number of stale blocks per e.g. 1000. This is not related to compact blocks. There are some long-term stats on Bitcoin Stale Block Dataset for the stale rates over time.
I do have Stats on compact block reconstructions - #44 by 0xB10C - Protocol Design - Delving Bitcoin for numbers on stale blocks reconstructions not needing an extra round trip. This is done by grepping my Bitcoin Core node debug logs and generating a plot from the result. There isn’t much tooling too it, but I’ll post the scripts there the next time I make an update (I just noticed it has been a while, so probably good to make one soonish).
Does that answer some of your questions?