#Bitcoin #Taproot meeting tomorrow, 19:00 UTC, in freenode ##Taproot-activation
https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2021-March/018636.html
Today's #Bitcoin #Taproot meeting was IMO largely unproductive, but we did manage to come to consensus on everything but LockinOnTimeout.
Activation height range: 693504-745920
MASF threshold: 1815/2016 blocks (90%)
https://en.bitcoin.it/wiki/Taproot_activation_proposal_202102
Keep in mind only ~100 people showed for the meetings, hardly representative of the entire community.
So, these details remain JUST a proposal for now.
It seems inevitable that there won't be consensus on LOT.
Everyone will have to choose for himself. :/
In half an hour, the second #Bitcoin #Taproot activation meeting on #IRC begins in ##taproot-activation on freenode!
Join via web browser: https://webchat.freenode.net/?channel=##taproot-activation
Topic is activation params, particularly lockinontimeout and startheight
Ahead of the #Bitcoin #Taproot activation meeting this coming Tuesday, I am preparing a draft of a proposal we can adapt/polish and send to the wider community for approval.
Still WIP; contributions welcome.
https://docs.google.com/document/d/1Ewnxxxc51_JWJLZQfqc5W55Pvkgcf9TEh6Ks3wiHbRk/edit?usp=sharing
New graph tracking network upgrade to #Bitcoin Core 0.19.2 / 0.20.2 / 0.21.0 / 0.21.0.Knots post-release:
https://luke.dashjr.org/programs/bitcoin/files/charts/historical-pretaproot.html
In half an hour, the first #Bitcoin #Taproot activation meeting on #IRC begins in ##taproot-activation on freenode!
Join via web browser: https://webchat.freenode.net/?channel=##taproot-activation
Topics:
- Discussion of activation params & making a formal proposal
- BIP review (2 PRs)
- Code review (1 PR)
#Bitcoin Knots 0.21.0.knots20210130 released! 🎉
#Bitcoin reminder: #Taproot activation can't really begin until N months after software is released with the activation parameters. That N months needs to be enough time to be sure enough of the community has upgraded to it.
The quicker the community upgrades to 0.21 (or the upcoming 0.20.2 backport), the clearer it will be that a shorter timeframe can be used for activation!
#Bitcoin #Taproot activation meeting on #IRC
Tuesday 2nd February 19:00 UTC
Agenda:
- BIP review (2 PRs)
- Code review (1 PR)
- Discussion of activation params & making a formal proposal (if we have time)
https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2021-January/018370.html
#Bitcoin Core PPA updated for 0.21
Now also including support for @Ubuntu 21.04 (Hirsute Hippo)
Preliminary analysis on the GCC 9 & 10 memcmp bug suggests it CAN affect #Bitcoin Core & Knots, but does NOT affect the Bitcoin consensus code (phew).
If yours was compiled with GCC 9/10, use caution for now (or rebuild with GCC 8).
Affected: p2p & PSBT
Note that gitian builds use GCC 7 and LLVM, so should be unaffected.
PPAs for Ubuntu 20.04 (Focal) and 20.10 (Groovy) are affected (and will not be fixed immediately).
IMO if you're spending $849 for a dedicated #Bitcoin full node machine, you should expect a POWER9 CPU in it.
Just saying.
(You should also make sure you're only buying node hardware made by reputable developers... But that's another topic.)
#Bitcoin Knots 0.20.1.knots20200815 released! 🎉
PSA: #Bitcoin is written in C++, which is almost normal English.
If you're anxious to have #Taproot deployed, reviewing the code can help.
Taproot: https://github.com/bitcoin/bitcoin/pull/17977
BIP 8 (Versionbits v2): https://github.com/bitcoin/bitcoin/pull/19573
Thanks to @[email protected] for merging my BIP 8 improvements and adding me as a co-champion.
Hopefully just in time for finishing it up for deploying #Taproot to #Bitcoin!
https://github.com/bitcoin/bips/blob/master/bip-0008.mediawiki
Faithful lay Roman #Catholic* convert, husband, father of 7 children, and #Bitcoin Core developer
INTP
* I completely disavow and condemn the pedos who currently control Vatican City. They are NOT Catholics. (Catholics have been required to reject them as heretics, since long before the pedo news broke.)
#PGP key fingerprint (do not trust this alone!): E463A93F5F3117EEDE6C7316BD02942421F4889F