templates produced by this version of Bitcoin Core will signal readiness
to enforce taproot during the roughly three month period specified by
BIP341.</p>
<p>If, during that time, 90% of blocks within a 2,016 retarget period
signal readiness, taproot will be locked in and this version of Bitcoin
Core will begin enforcing the additional consensus rules specified in
BIPs 341 and 342 at block 709,632, which is expected in early or mid
November.</p>
<p>If miners don’t lock in taproot by the end of the three month signaling
period, a separate attempt to activate it using another mechanism is
expected to be tried. The activation mechanism has been designed so
that, by roughly mid August, it will either provide us with an assurance
that we’ll soon have taproot or immediately give us valuable information
that users and developers can use to make the next activation attempt
more likely to succeed.</p>
<p><strong>Note:</strong> due to a <a href=”https://github.com/bitcoin-core/gui/issues/252#issuecomment-802591628″>problem</a> with the certificate authority
that provides the code signing certificates for the Windows versions of
Bitcoin Core, users on Windows will need to click through an extra
prompt to install. It is also expected that there will be a 0.21.1.1
release with an updated certificate when the problem is fixed. If you
are planning to upgrade anyway, there’s no reason to delay using 0.21.1
because of this problem.</p>
<p>If have any questions, please stop by the #bitcoin IRC chatroom
(<a href=”irc://irc.freenode.net/bitcoin”>IRC</a>, <a href=”https://webchat.freenode.net/#bitcoin”>web</a>) and we’ll do our best to help you.</p>
please see the <a href=”https://bitcoincore.org/en/releases/0.21.0/”>release notes</a>.</p>
<p>If have any questions, please stop by the #bitcoin IRC chatroom
(<a href=”irc://irc.freenode.net/bitcoin”>IRC</a>, <a href=”https://webchat.freenode.net/#bitcoin”>web</a>) and we’ll do our best to help you.</p>
please see the <a href=”https://bitcoincore.org/en/releases/0.20.1/”>release notes</a>.</p>
<p>If have any questions, please stop by the #bitcoin IRC chatroom
(<a href=”irc://irc.freenode.net/bitcoin”>IRC</a>, <a href=”https://webchat.freenode.net/#bitcoin”>web</a>) and we’ll do our best to help you.</p>
please see the <a href=”https://bitcoincore.org/en/releases/0.20.0/”>release notes</a>.</p>
<p>If have any questions, please stop by the #bitcoin IRC chatroom
(<a href=”irc://irc.freenode.net/bitcoin”>IRC</a>, <a href=”https://webchat.freenode.net/#bitcoin”>web</a>) and we’ll do our best to help you.</p>
through an onion address:</p>
<p><a href=”http://6hasakffvppilxgehrswmffqurlcjjjhd76jgvaqmsg6ul25s7t3rzyd.onion/”>http://6hasakffvppilxgehrswmffqurlcjjjhd76jgvaqmsg6ul25s7t3rzyd.onion/</a></p>
<p>As well as adding another means of censorship resistance, a hidden
service gives an alternative trust path that doesn’t rely on certificate
authorities nor DNS infrastructure.</p>
Published at
