Takeaways from the activation discussion:
1. Unanimous support for BIP8. RIP BIP 9.
2. Overwhelming consensus that 1yr is correct timeout value (it's actually defined in blocks, so 26x2016 or maybe 87600).
3. Majority consensus for lockin false, though @lukedashjr strongly opposed.
4. No decision I could see on start time, but 2 months was done for segwit, and that didn't seem too objectionable.

C̶a̶n̶ ̶B̶i̶t̶c̶o̶i̶n̶ ̶w̶i̶t̶h̶s̶t̶a̶n̶d̶ ̶a̶ ̶f̶u̶l̶l̶ ̶b̶l̶o̶w̶n̶ ̶s̶t̶a̶t̶e̶ ̶o̶f̶f̶e̶n̶s̶i̶v̶e̶?̶

Can the state withstand a full blown offensive?

This PR should now be fully testable, see the doc added to it for details on how:


For those less interested in the main functionality, you might find the little scanning tool `snicker-finder.py` interesting because it also finds #Joinmarket coinjoins if you add the `-j` option, I think it does a decent job of avoiding false positives. Unfortunately, being Python, it takes several seconds per block in the range you choose (obviously more high performance tools exist!).

Does anyone know a mastodon twitter repost bot written in Rust / DotNet / Python?

Bitcoin Optech newsletter #133 is here:

- announces a meeting to discuss taproot activation mechanisms
- includes a link to a Bitcoin Core usage survey
- lists top questions and answers from the Bitcoin StackExchange


I created this account in 2018, but am doing the first tweet now. 🤔

Sometimes it's ok to wait till develops to a decent extend before using it in production.

Bitcoin Mastodon

Bitcoin Maston Instance