Bitcoin Core 0.21.1 Released

[achow101]

0.21.1 Release Notes

Bitcoin Core version 0.21.1 is now available from:

https://bitcoincore.org/bin/bitcoin-core-0.21.1/

This minor release includes various bug fixes and performance
improvements, as well as updated translations.

Please report bugs using the issue tracker at GitHub:

https://github.com/bitcoin/bitcoin/issues

To receive security and update notifications, please subscribe to:

https://bitcoincore.org/en/list/announcements/join/

How to Upgrade

If you are running an older version, shut it down. Wait until it has completely
shut down (which might take a few minutes in some cases), then run the
installer (on Windows) or just copy over /Applications/Bitcoin-Qt (on Mac)
or bitcoind/bitcoin-qt (on Linux).

Upgrading directly from a version of Bitcoin Core that has reached its EOL is
possible, but it might take some time if the data directory needs to be migrated. Old
wallet versions of Bitcoin Core are generally supported.

Compatibility

Bitcoin Core is supported and extensively tested on operating systems
using the Linux kernel, macOS 10.12+, and Windows 7 and newer.  Bitcoin
Core should also work on most other Unix-like systems but is not as
frequently tested on them.  It is not recommended to use Bitcoin Core on
unsupported systems.

From Bitcoin Core 0.20.0 onwards, macOS versions earlier than 10.12 are no
longer supported. Additionally, Bitcoin Core does not yet change appearance
when macOS "dark mode" is activated.

Notable changes

Taproot Soft Fork

Included in this release are the mainnet and testnet activation
parameters for the taproot soft fork (BIP341) which also adds support
for schnorr signatures (BIP340) and tapscript (BIP342).

If activated, these improvements will allow users of single-signature
scripts, multisignature scripts, and complex contracts to all use
identical-appearing commitments that enhance their privacy and the
fungibility of all bitcoins. Spenders will enjoy lower fees and the
ability to resolve many multisig scripts and complex contracts with the
same efficiency, low fees, and large anonymity set as single-sig users.
Taproot and schnorr also include efficiency improvements for full nodes
such as the ability to batch signature verification.  Together, the
improvements lay the groundwork for future potential
upgrades that may improve efficiency, privacy, and fungibility further.

Activation for taproot is being managed using a variation of BIP9
versionbits called Speedy Trial (described in BIP341). Taproot's
versionbit is bit 2, and nodes will begin tracking which blocks signal
support for taproot at the beginning of the first retarget period after
taproot’s start date of 24 April 2021.  If 90% of blocks within a
2,016-block retarget period (about two weeks) signal support for taproot
prior to the first retarget period beginning after the time of 11 August
2021, the soft fork will be locked in, and taproot will then be active
as of block 709632 (expected in early or mid November).

Should taproot not be locked in via Speedy Trial activation, it is
expected that a follow-up activation mechanism will be deployed, with
changes to address the reasons the Speedy Trial method failed.

This release includes the ability to pay taproot addresses, although
payments to such addresses are not secure until taproot activates.
It also includes the ability to relay and mine taproot transactions
after activation.  Beyond those two basic capabilities, this release
does not include any code that allows anyone to directly use taproot.
The addition of taproot-related features to Bitcoin Core's wallet is
expected in later releases once taproot activation is assured.

All users, businesses, and miners are encouraged to upgrade to this
release (or a subsequent compatible release) unless they object to
activation of taproot.  If taproot is locked in, then upgrading before
block 709632 is highly recommended to help enforce taproot's new rules
and to avoid the unlikely case of seeing falsely confirmed transactions.

Miners who want to activate Taproot should preferably use this release
to control their signaling.  The getblocktemplate RPC results will
automatically be updated to signal once the appropriate start has been
reached and continue signaling until the timeout occurs or taproot
activates.  Alternatively, miners may manually start signaling on bit 2
at any time; if taproot activates, they will need to ensure they update
their nodes before block 709632 or non-upgraded nodes could cause them to mine on
an invalid chain.  See the versionbits
FAQ for
details.

For more information about taproot, please see the following resources:

• Technical specifications
  
  • BIP340 Schnorr signatures for secp256k1
  • BIP341 Taproot: SegWit version 1 spending rules
  • BIP342 Validation of Taproot scripts
• Popular articles
  
  • Taproot Is Coming: What It Is, and How It Will Benefit Bitcoin
  • What do Schnorr Signatures Mean for Bitcoin?
  • The Schnorr Signature & Taproot Softfork Proposal
• Development history overview
  
  • Taproot
  • Schnorr signatures
  • Tapscript
  • Soft fork activation
• Other
  
  • Questions and answers related to taproot
  • Taproot review

Updated RPCs

• Due to BIP 350
    being implemented, behavior for all RPCs that accept addresses is changed when
    a native witness version 1 (or higher) is passed. These now require a Bech32m
    encoding instead of a Bech32 one, and Bech32m encoding will be used for such
    addresses in RPC output as well. No version 1 addresses should be created
    for mainnet until consensus rules are adopted that give them meaning
    (e.g. through BIP 341).
    Once that happens, Bech32m is expected to be used for them, so this shouldn't
    affect any production systems, but may be observed on other networks where such
    addresses already have meaning (like signet).

0.21.1 change log

Consensus

• #21377 Speedy trial support for versionbits (ajtowns)
• #21686 Speedy trial activation parameters for Taproot (achow101)

P2P protocol and network code

• #20852 allow CSubNet of non-IP networks (vasild)
• #21043 Avoid UBSan warning in ProcessMessage(…) (practicalswift)

Wallet

• #21166 Introduce DeferredSignatureChecker and have SignatureExtractorClass subclass it (achow101)
• #21083 Avoid requesting fee rates multiple times during coin selection (achow101)

RPC and other APIs

• #21201 Disallow sendtoaddress and sendmany when private keys disabled (achow101)

Build system

• #21486 link against -lsocket if required for *ifaddrs (fanquake)
• #20983 Fix MSVC build after gui#176 (hebasto)

Tests and QA

• #21380 Add fuzzing harness for versionbits (ajtowns)
• #20812 fuzz: Bump FuzzedDataProvider.h (MarcoFalke)
• #20740 fuzz: Update FuzzedDataProvider.h from upstream (LLVM) (practicalswift)
• #21446 Update vcpkg checkout commit (sipsorcery)
• #21397 fuzz: Bump FuzzedDataProvider.h (MarcoFalke)
• #21081 Fix the unreachable code at feature_taproot (brunoerg)
• #20562 Test that a fully signed tx given to signrawtx is unchanged (achow101)
• #21571 Make sure non-IP peers get discouraged and disconnected (vasild, MarcoFalke)
• #21489 fuzz: cleanups for versionbits fuzzer (ajtowns)

Miscellaneous

• #20861 BIP 350: Implement Bech32m and use it for v1+ segwit addresses (sipa)

Documentation

• #21384 add signet to bitcoin.conf documentation (jonatack)
• #21342 Remove outdated comment (hebasto)

Credits

Thanks to everyone who directly contributed to this release:

• Aaron Clauson
• Andrew Chow
• Anthony Towns
• Bruno Garcia
• Fabian Jahr
• fanquake
• Hennadii Stepanov
• Jon Atack
• Luke Dashjr
• MarcoFalke
• Pieter Wuille
• practicalswift
• randymcmillan
• Sjors Provoost
• Vasil Dimov
• W. J. van der Laan

As well as to everyone that helped with translations on
Transifex.

Code:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

28264751c982d30b9330e6c1475ddb9ed28be6a2601e8a5f33b6ba49a3d9f5f2  bitcoin-0.21.1-aarch64-linux-gnu.tar.gz
3a92e312ffd3ca92579d46ec52e3dcb1b09bbdd11fe7c6a735e8546c7d9975e0  bitcoin-0.21.1-arm-linux-gnueabihf.tar.gz
1ea5cedb64318e9868a66d3ab65de14516f9ada53143e460d50af428b5aec3c7  bitcoin-0.21.1-osx64.tar.gz
2df15131cd18fd1941adc26f014012b437ccaadab39f1f5dc10282a68e8f9923  bitcoin-0.21.1-osx.dmg
259d74f13271dc51eb4db4b733fb1589038ff7819e849d2351e899f67de218c5  bitcoin-0.21.1-riscv64-linux-gnu.tar.gz
caff23449220cf45753f312cefede53a9eac64000bb300797916526236b6a1e0  bitcoin-0.21.1.tar.gz
afdd0f1717a74af01b88631d17a2f29f89d21ca2e3be0fec0678e7a1e20712d5  bitcoin-0.21.1-win64-setup-unsigned.exe
94c80f90184cdc7e7e75988a55b38384de262336abd80b1b30121c6e965dc74e  bitcoin-0.21.1-win64.zip
366eb44a7a0aa5bd342deea215ec19a184a11f2ca22220304ebb20b9c8917e2b  bitcoin-0.21.1-x86_64-linux-gnu.tar.gz
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iQIcBAEBCAAGBQJgja0mAAoJEJDIAZ42wulkV+IQAI84JuMhIs5muAqTX6G/sxPV
sJ2RJ5aansLEcnFQrrmUNqXpGRB+yiCwlUg9cXLV6zKQkdmDnSuqhTGbivFDLoO3
WeEcQdvkUEodHOk9NK8AVB8NGRK2lkevij4OK0jUUdSVg31dJsygs09TKQGmfXKJ
QnGR7Oz4h/BExrzYfC6PY3AYVJXOkVR86hb2w4r33xNy9DMkvxqbX+B9v1fvqO/V
arcPriVKd0YiEi5nIV5/4ghkHGPAakXzd49DgxW8BVXXqPILBS/MatjgQ5BWJWpK
p4B6V0FYJ2ZpvaTWNBOllUTNRq7YACcKSAEyW3cD9aNPz4o8mb3O7LMr+qb2z0+4
KZuubmOT3sJD37nsZ7DfmERQ7hFYHdlqvthCEQQyglasEZrsLnuCJQNGOSAT+ixM
8jPf3XFDNWm3QFS5icAmykzOWSV4Z0WcQfDjIRbcoXR09N5PgYavhSiwPqpfQ94/
q2igiMmIPH8rlRySc9fKfpYomkWP4W1vfm/wIeSrNm2oNeedL4/4zcv4v6mmnQhO
+i1Npk1TY9+pMAh5xrjUxw3W1QgpVxttIlRmKw6StpVB2Lxl+bGAXp5N7hA8znWX
3AHSDYcdIVEpjvAWGpNPspsyrDv42zElgR8PqS462d/Go6HHhIqd+wHoRIEJTfXM
m6bC44Ak09Ayxu4IxxBw
=5612
-----END PGP SIGNATURE-----

Note that for this release, due to issues with acquiring a Windows code signing certificate, the Windows installer is not code signed. This means that there will be additional warnings when attempting to run the Windows installer.

[1714667971]

1714667971

[1714667971]

1714667971

[1714667971]

1714667971

[1714667971]

1714667971

[1714667971]

1714667971

[BitcoinGirl.Club]

I hope theymos got notified to update the news section.

[Carlton Banks]

bitcoincore.org Bittorrent link for 0.21.1: magnet:?xt=urn:btih:205b0189271c50a02fe966491e15737a01f94e08

[DireWolfM14]

Note that for this release, due to issues with acquiring a Windows code signing certificate, the Windows installer is not code signed. This means that there will be additional warnings when attempting to run the Windows installer.

Not that it's a big deal (signatures match the hashes, hashes match the files) but I'm just curious what the issue is.  Is this just a delay, or will the certificate remain unobtainable?

FYI, other than the extra Windows notification I had no issue updating.

[achow101]

but I'm just curious what the issue is.  Is this just a delay, or will the certificate remain unobtainable?

For past few years, we've been getting 1 year certificates around the end of March. So this year, I went to renew the certificate, but Sectigo (the CA we've been using) asked us to register the organization we use with a government. The legal entity we have been using for certificates is a Swiss Association, and those don't require government registration. But apparently the CA/B Forum (the group that sets the rules for certificates) added a new rule late last year that requires CAs to make sure that organizations are registered with governments.

So we've spent the past 2 months figuring out how to register the Association with the Swiss government, and then waiting for the registration to go through and become publicly searchable so that whatever CA we use will be able to find it. So this should just be a delay, but it might take another month or two.

We did also setup another organization, this time a LLC in the US. So this should give us a backup option in the future, as well as possibly for right now if the LLC can be fully setup before the Swiss Association is registered.

There was also another annoying thing that happened when I tried to renew the certificate: Sectigo revoked the one that was about to expire, with a backdated revocation. This means that any release that was code signed with that certificate now shows even scarier warnings when you try to install it. This affects 4 released versions and we will be re-releasing those versions once we get the new certificate.

[DireWolfM14]

There was also another annoying thing that happened when I tried to renew the certificate: Sectigo revoked the one that was about to expire, with a backdated revocation. This means that any release that was code signed with that certificate now shows even scarier warnings when you try to install it. This affects 4 released versions and we will be re-releasing those versions once we get the new certificate.

So, when you tried to renew the certificate, they revoked it retroactively due to their new national-registration policy?  Talk about salt on the wound.  It seems like they should have warned you that was going to be case when they enacted the new policy late last year. 

Thanks for the explanation (and everything else you and dev team do.)  Best of luck with the certificate.

[achow101]

So, when you tried to renew the certificate, they revoked it retroactively due to their new national-registration policy?

They never gave a reason, so I have no idea.

[clorasteinberg]

I was very much convinced with the upgrade but when I read about the warning signs, I started having second thoughts. Isn’t there any way by which we can avoid these?

[Carlton Banks]

I was very much convinced with the upgrade but when I read about the warning signs, I started having second thoughts. Isn’t there any way by which we can avoid these?

which warnings?

there is only 1 warning I know of: the "Unknown version bits activated" warning if you are using older versions of Bitcoin Core. This means that there is a new soft fork activated on the network, and that the older software doesn't recognize it.


only Bitcoin 0.21.1+ recognizes the taproot fork, which is the unknown fork being detected by old Bitcoin software.

[unwashed]

Hi, Please help. I'm running Ubuntu 16.04 and have Bitcoin core 18 installed. When I installed BC 21 it created a separate folder and no executable icon on my desktop. The only way to run BC 21 now is from the terminal, it opens and has my wallet and all info but that is stored in the previous versions folder. All other versions merged the upgrade, so is there a way to merge the two.  I tried to follow the OP instructions but I do not have bitcoin-qt or bitcoind in my BC 18 folder and not sure where they are. Oh and the Bitcoin icon on my desktop only executes the BC 18 version. Also, can I continue to use BC 18 without any real issues?

[Carlton Banks]

Hi, Please help. I'm running Ubuntu 16.04 and have Bitcoin core 18 installed. When I installed BC 21 it created a separate folder and no executable icon on my desktop. The only way to run BC 21 now is from the terminal, it opens and has my wallet and all info but that is stored in the previous versions folder. All other versions merged the upgrade, so is there a way to merge the two.  I tried to follow the OP instructions but I do not have bitcoin-qt or bitcoind in my BC 18 folder and not sure where they are. Oh and the Bitcoin icon on my desktop only executes the BC 18 version. Also, can I continue to use BC 18 without any real issues?

1. do

find / -name bitcoin-qt

in a terminal


2. then

find / -name bitcoin*.desktop


3. open the .desktop files in text editor. read them.


new bitcoin-qt (0.21.1) will have a newer date.

what you want is the Exec= line in your .desktop file to point to the new bitcoin-qt, not the old one


if you installed the old bitcoin-qt (0.18 or whatever) or the new bitcoin-qt (0.21.1) with Snap or any of these other "easy" methods, then you've got a bigger problem. That's what you get for believing in the "easy" way

[TakeitDo]

Trying to get it installed, but I keep getting an error.

Is there a video tutorial on how to upgrade?

[DireWolfM14]

Trying to get it installed, but I keep getting an error.

Is there a video tutorial on how to upgrade?

This isn't the best thread for getting technical help, not to mention it's off-topic.

Create a thread in the Bitcoin Technical Support board, and provide more details about your system, current configuration, intentions, and issues.

[Dydy94]

Hello,

I'm on Bitcoin Core 0.21.1

I have the blockchain but an error remains,
this debug command line dismays me:

  BerkeleyEnvironment :: Open: LogDir = C: \ Users \ user \ AppData \ Roaming \ Bitcoin \ bitcoinpy \ database ErrorFile = C: \ Users \ user \ AppData \ Roaming \ Bitcoin \bitcoinpy \ db.log

ErrorFiles from db.log ...

what to do please?

[achow101]

this debug command line dismays me:

  BerkeleyEnvironment :: Open: LogDir = C: \ Users \ user \ AppData \ Roaming \ Bitcoin \ bitcoinpy \ database ErrorFile = C: \ Users \ user \ AppData \ Roaming \ Bitcoin \bitcoinpy \ db.log

ErrorFiles from db.log ...

what to do please?

That's normal. It's just telling you where the error log file is. There is no error.

[dexzbitz]

can andybody know how to law ram usage of bitcoin core node
we 8 gb ram and 6gb will be consumed by the bitcoin core node

[OmegaStarScream]

can andybody know how to law ram usage of bitcoin core node
we 8 gb ram and 6gb will be consumed by the bitcoin core node

Yes. You can try and run the node using these parameters: https://bitcoin.stackexchange.com/a/50743

[cygan]

since ages i am a windows user and therefore my bitcoin core wallet always ran under windows
now i want to run my bitcoin-qt on linux debian (lxqt), but i have the problem that i can't start the bitcoin qt...
bitcoin-0.21.1-x86_64-linux-gnu.tar.gz was downloaded and unpacked but i must have forgotten something
maybe someone can help me?

edit: has been done - i have managed myself (thanks google)💪

[achow101]

Bitcoin Core 22.0 has been released