Bitcoin Core 0.19.1 Released

[achow101]

0.19.1 Release Notes

Bitcoin Core version 0.19.1 is now available from:

https://bitcoincore.org/bin/bitcoin-core-0.19.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 for older versions), 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 datadir 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.10+, and Windows 7 and newer. It is not recommended
to use Bitcoin Core on unsupported systems.

Bitcoin Core should also work on most other Unix-like systems but is not
as frequently tested on them.

From Bitcoin Core 0.17.0 onwards, macOS versions earlier than 10.10 are no
longer supported, as Bitcoin Core is now built using Qt 5.9.x which requires
macOS 10.10+. Additionally, Bitcoin Core does not yet change appearance when
macOS "dark mode" is activated.

In addition to previously supported CPU platforms, this release's pre-compiled
distribution provides binaries for the RISC-V platform.

0.19.1 change log

Wallet

• #17643 Fix origfee return for bumpfee with feerate arg (instagibbs)
• #16963 Fix unique_ptr usage in boost::signals2 (promag)
• #17258 Fix issue with conflicted mempool tx in listsinceblock (adamjonas, mchrostowski)
• #17924 Bug: IsUsedDestination shouldn't use key id as script id for ScriptHash (instagibbs)
• #17621 IsUsedDestination should count any known single-key address (instagibbs)
• #17843 Reset reused transactions cache (fjahr)

RPC and other APIs

• #17687 cli: Fix fatal leveldb error when specifying -blockfilterindex=basic twice (brakmic)
• #17728 require second argument only for scantxoutset start action (achow101)
• #17445 zmq: Fix due to invalid argument and multiple notifiers (promag)
• #17524 psbt: handle unspendable psbts (achow101)
• #17156 psbt: check that various indexes and amounts are within bounds (achow101)

GUI

• #17427 Fix missing qRegisterMetaType for size_t (hebasto)
• #17695 disable File->CreateWallet during startup (fanquake)
• #17634 Fix comparison function signature (hebasto)
• #18062 Fix unintialized WalletView::progressDialog (promag)

Tests and QA

• #17416 Appveyor improvement - text file for vcpkg package list (sipsorcery)
• #17488 fix "bitcoind already running" warnings on macOS (fanquake)
• #17980 add missing #include to fix compiler errors (kallewoof)

Platform support

• #17736 Update msvc build for Visual Studio 2019 v16.4 (sipsorcery)
• #17364 Updates to appveyor config for VS2019 and Qt5.9.8 + msvc project fixes (sipsorcery)
• #17887 bug-fix macos: give free bytes to F_PREALLOCATE (kallewoof)

Miscellaneous

• #17897 init: Stop indexes on shutdown after ChainStateFlushed callback (jimpo)
• #17450 util: Add missing headers to util/fees.cpp (hebasto)
• #17654 Unbreak build with Boost 1.72.0 (jbeich)
• #17857 scripts: Fix symbol-check & security-check argument passing (fanquake)
• #17762 Log to net category for exceptions in ProcessMessages (laanwj)
• #18100 Update univalue subtree (MarcoFalke)

Credits

Thanks to everyone who directly contributed to this release:

• Aaron Clauson
• Adam Jonas
• Andrew Chow
• Fabian Jahr
• fanquake
• Gregory Sanders
• Harris
• Hennadii Stepanov
• Jan Beich
• Jim Posen
• João Barbosa
• Karl-Johan Alm
• Luke Dashjr
• MarcoFalke
• Michael Chrostowski
• Russell Yanofsky
• Wladimir J. van der Laan

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

Code:

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

3a80431717842672df682bdb619e66523b59541483297772a7969413be3502ff  bitcoin-0.19.1-aarch64-linux-gnu.tar.gz
657f28213823d240dd3324d14829702f9ad6f0710f8bdd1c379cb3c447197f48  bitcoin-0.19.1-arm-linux-gnueabihf.tar.gz
10d1e53208aa7603022f4acc084a046299ab4ccf25fe01e81b3fb6f856772589  bitcoin-0.19.1-i686-pc-linux-gnu.tar.gz
1ae1b87de26487075cd2fd22e0d4ead87d969bd55c44f2f1d873ecdc6147ebb3  bitcoin-0.19.1-osx64.tar.gz
206d8d92189d22e735393abebeb7a2e7237a119dd448b4a40df8c357da1287b2  bitcoin-0.19.1-osx.dmg
aa7a9563b48aa79252c8e7b6a41c07a5441bd9f14c5e4562cc72720ea6cb0ee5  bitcoin-0.19.1-riscv64-linux-gnu.tar.gz
f2591d555b8e8c2e1bd780e40d53a91e165d8b3c7e0391ae2d24a0c0f23a7cc0  bitcoin-0.19.1.tar.gz
69e4d7f710a29be6ead2ef5da2905736b7cea107213ae6ddde3bcca8affbb8fd  bitcoin-0.19.1-win64-setup.exe
56323ec91afecd8e321a2925c0ca5f1da8b2ae1c99f4e08a3652e1dc68908717  bitcoin-0.19.1-win64.zip
5fcac9416e486d4960e1a946145566350ca670f9aaba99de6542080851122e4c  bitcoin-0.19.1-x86_64-linux-gnu.tar.gz
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iQIcBAEBCAAGBQJeZiE8AAoJEJDIAZ42wulkkQsQAIlvZ9Em4wm2jpn4L7QUJgCE
4Mr6Q/tCPMs4U15q4wkjoBbdP06Bts1DzV0m/qoirTKoTKCCyRwdaeRn+Oj5Kkoh
MuyPt9EEsrnNk80xaPXSpYnhYjqSGrKux+IuHrlZtCy0QEoeIiOVaWWEtEe6I/eU
lvooE8ywxcUvsOwU3Kga0WnCA0WsfwduMAU+LvmtiXgjudsWvoERwHav+eiQva60
kgfwK5W+XI0lt7clFw6zPXBTZeWWhc97fp1uKv7KBPpACHWgKUaXP3WPMHZhsnSF
1L5fi5EcafjNzbbUusmgo807xThM5eMFZQpzHFZhiFNngW6mjxyEo1m2vrvVE8mN
1LZ7h1QahdSUVsgr+w/JkN1Wx9WcJyzGvFuH7dIbe1J6kb5IMyUKESEtTkWgJeo4
5MCk9pwvstAXcXPnWbNolrBo2IB9mrFC9o/9n2ZCyncCofre8BmbIsvxVqBu4hfE
9E4rCTHDGwWvCDYY68iWdlnyUl9FAvYB8UEOYs4o4f1fDMLdbOEqDojIa7ZnOJwV
oPth/MJxHcaCHNTAk7981LbOyn/oJMMzly4br5WFqWbdgzdXUSBTZDoeT26gdX8P
rnCo7JMvaxcvE8AASD9OpegKZP/E5TnHEzcgkVncABj9gVrsuOm7DlTFsE9YuRv+
jerPsU4Izg+hoVdUiuPT
=Iefa
-----END PGP SIGNATURE-----

[Carlton Banks]

Surprised to see this thread is not stickied?


Anyway, here is the trackerless, decentralized (i.e. DHT-only) link for those wishing to download version 0.19.1 using Bittorrent:

magnet:?xt=urn:btih:8b6ad1da5bbb24656234efc2370abc14781a6f83


IMO, decentralized network technologies are becoming more important, as we now have renewed impetus from government/corporate bullies seeking to censor the internet

[gmaxwell]

IMO, decentralized network technologies are becoming more important, as we now have renewed impetus from government/corporate bullies seeking to censor the internet

Back in 2011 (or 2012? I forget) we tried doing releases with trackerless torrents and found that they essentially didn't work.  The trackerless stuff works well enough to make DOS attacking trackers somewhat ineffective for extremely popular torrents, but for niche torrents they mostly didn't work at all (partially due to the background DDOS level against the bittorrent DHT stuff).  I don't think anything has changed regarding this.

[Carlton Banks]

Back in 2011 (or 2012? I forget) we tried doing releases with trackerless torrents and found that they essentially didn't work.  The trackerless stuff works well enough to make DOS attacking trackers somewhat ineffective for extremely popular torrents, but for niche torrents they mostly didn't work at all (partially due to the background DDOS level against the bittorrent DHT stuff).  I don't think anything has changed regarding this.

try it. I found it worked for me, and always has done. even LTS bugfix releases like 0.17.2 downloaded for me using only DHT peers, and my own bittorrent peer typically serves a few hundred MB to other peers. Seeding ratio for the LTS releases tends to be < 1.0 however (although maybe that's just a representation of how popular those releases are)

could it be that implementations of bittorrent's DHT design have improved since 2011-12? not sure, but I've been using a DHT trawler recently to discover torrents from the DHT, and the daemon typically finds 40,000-60,000 per day (rate limited to 20 Mbit/s using a wonderful linux utility called Traffic Control, which I understand you're familiar with thanks for that!)

[distributedconsensus]

Already installed from scratch and running smooth. Took 7 hours to synchronize to the tip of the chain. Not bad at all. I was surprised by some changes in the way bitcoin-cli works now, I guess I will need to recycle myself once again.

As a side note, I am still surprised how the general public perceives Bit Coin, most out there are so confused right now. Instead of entering the Bitcoin environment to stay, they think of profiting in fiat money that, by now, should be already known to be obsolete. I guess we need strategic companies accepting payments in BTC, like Electricity paid in the same currency taking in consideration not the value by trade but the value considering the maximum amount of coins that will circulate.

I am kind of surprised how long it is taking to the whole society to see the point... I guess it is like the internet at the beginning or even the cell phones, people will just get it when it is already a reality and something normal in their daily lives.

[0daybug]

This version is still using confined Snap packages (https://snapcraft.io/bitcoin-core) so it is not possible to choose any data directory outside the user's home. This prevents anyone with small OS disks (like SSDs) to use it.

[karter_18]

Hi

Can anyone help out with a wallet issue?

It’s a fresh install and I’m getting:

error:incorrect or no genesis block found. Wrong datadir for network?

The install hasn’t asked me for a directory yet.

In on Windows 10 64 bit OS

thanks

[achow101]

0.20.0 has been released