0xB10C @0xb10c@x0f.org

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!

https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2021-September/019413.html

I've summarized my work on Userspace, Statically Defined Tracing support for Bitcoin Core in my Coinbase grant half-time report.

https://b10c.me/blog/008-bitcoin-core-usdt-support/

If future tracepoints for e.g. peer dis / connections, addrman, UTXO set changes, etc get merged, this might be an alternative to
@lopp
's Statoshi.info which requires a rebase on each Bitcoin Core release. I'd also argue that the bitcoind-observer setup is easier.

And block connection timings during IBD and data about validated blocks/second, transactions/second, inputs/second, and sigops/second.

https://bitcoind.observer/d/V5pGXBW7k/block-validation-during-idb?orgId=1&from=1627333200000&to=1627390800000

While limited by the three trancepoints added in #22006, it is already showing real time P2P message count and traffic per message type.

https://bitcoind.observer/d/Z3_pFfZnz/p2p-network-traffic?refresh=30s&var-msg_types=All

I build an experimental Bitcoin Core Prometheus metrics exporter based on the eBPF and USDT tracepoints I add in PR #22006 (https://github.com/bitcoin/bitcoin/pull/22006).

https://github.com/0xB10C/bitcoind-observer

Grafana demo available on https://bitcoind.observer

@michaelfolkson you might find this interesting

Couldn't really talk about it on Tuesday as everything was still in limbo 😬

transaction:

b10c007c60e14f9d087e0291d4d0c7869697c6681d979c6639dbd960792b4d41
https://mempool.space/tx/b10c007c60e14f9d087e0291d4d0c7869697c6681d979c6639dbd960792b4d41

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!

https://b10c.me/blog/007-spending-p2tr-pre-activation/?x0f

I was surprised to learn that there are only 20 key-path and 5 script-path spends of P2TR outputs on SigNet yet. Had assumed more people played around with taproot on SigNet.

Maybe it's to early for e.g. wallets to be testing this or they test on regtest.

@michaelfolkson thank you for asking (and answering or archiving answers to) all these questions on bitcoin.stackexchange.com

super helpful

Quiz: Which Bitcoin Core data-structure does this visualization show?

This is inspired by https://blog.bitmex.com/bitcoin-miner-transaction-fee-gathering-capability/ , which is a good read for everyone interested in this topic.

I'd like to thank the people who have provided feedback on this project. You shall remain anonymous, as I don't want to imply endorsement.

For example, it becomes apparent that #682170 did NOT filter transactions.

All transactions missing from the block had only been in my mempool for a few seconds. None are sanctioned.

Differences between templates and blocks are to be expected!

https://miningpool.observer/template-and-block/000000000000000000003f8cb66fe1ecfb38754abc9c4d4a62b71de45fef8777

In response to block #682170, mined by MARA Pool, I'm announcing a project I've been working on. I hope this brings transparency into mining pool transaction selection.

http://miningpool.observer

This compares block templates generated by my node to the blocks mined by pools.