We have been working on making reorgs on SigNet a reality and are looking for feedback on approach and parameters. If you want to test the reorg handling of your app, please let us know!
@michaelfolkson Yes, debugging is definitely one of the USDT applications. Also developers can be use the tracepoints to evaluate/review changes like I do with the erlay vs master nodes dashboard. Or for general monitoring, anomaly detection, benchmarking, and testing.
Additionally, I think 'tracing' via USDT and debugging are two very different things. You can use tracing via USDT as part of the search for a bug, but you can't replace debugging with tracing.
Sometimes debugging, as in stepping through code and looking at state with e.g. GDB, is something you do manually.
The tracing done with USDT allows you to use internal state programatically. You can automatically react to some state.
@michaelfolkson I'm not sure if I'd see reading "BPF Performance Tools" as a requirement. The tools are very specific for tracepoints in the Linux kernel. We don't use any of these tools or tracepoints.
We just implement our own tracepoints in our userspace application (Bitcoin Core) and write custom scripts to get insights into the parts we find important.
@michaelfolkson Yes! I've been thinking about some kind of USDT workshop for CoreDev too.
A Socratic might be better once we have more tracepoints merged and people building tools/using the tracepoints? Maybe sometime between CoreDev and 23.0. release?
I've summarized my work on Userspace, Statically Defined Tracing support for Bitcoin Core in my Coinbase grant half-time report.
[bitcoin] Merged PR from 0xB10C: tracing: first tracepoints and documentation on User-Space, Statically Defined Tracing (USDT) https://github.com/bitcoin/bitcoin/pull/22006
And block connection timings during IBD and data about validated blocks/second, transactions/second, inputs/second, and sigops/second.
While limited by the three trancepoints added in #22006, it is already showing real time P2P message count and traffic per message type.
We donated 4 of the 6 existing mainnet Pay-to-Taproot outputs (currently anyone-can-spend) to @bitcoinbrink.
Thank you @f2pool_official and @satofishi for including the non-standard transaction in a block!🐟
We donated 4 of the 6 existing mainnet Pay-to-Taproot outputs (currently anyone-can-spend) to brink.dev.
Thank you f2pool.com and @satofishi for including the non-standard transaction in a block!
Discussing the roll out of Taproot at next week's online Socratic Seminar. Would be great to have you there @0xb10c :) https://www.meetup.com/BitDevsLDN/events/279041693/
@michaelfolkson thank you for asking (and answering or archiving answers to) all these questions on bitcoin.stackexchange.com