Everything collected from official sources.
141 publications
Headers sync gains a presync phase in Bitcoin Core 24.0.1: to head off a potential denial-of-service, nodes verify a peer's cumulative work before storing its headers, which can slow first-time sync (#25717). Also new are the sendall RPC and a mempoolfullrbf option that accepts replacements without BIP125 signaling, while wallets now default to opt-in RBF.
Bitcoin Core
CJDNS gets full support in Bitcoin Core 23.0, and the old preference for peers on port 8333 is dropped (#23542). Fee estimation now counts RBF replacements, the -rescan startup parameter is removed, and Linux binaries ship experimental tracepoints.
Bitcoin Core
Misbehaving peers show up as "discouraged" rather than banned in Bitcoin Core 0.20.2 logs: they can still connect but get evicted first, and the state clears on restart. -walletnotify fires again for wallet transactions dropped from the mempool over a conflict with a new block, and PSBTs carry both witness and non-witness utxo for segwit inputs.
Bitcoin Core
Rumoured addresses get rate limited in Bitcoin Core 0.21.2 (#22569), and a command line containing -noincludeconf=0 no longer crashes the parser (#22002). In the GUI, URI error messages stop echoing user input (gui#280).
Bitcoin Core
I2P support arrives in Bitcoin Core 22.0, and Tor v2 addresses are gone now that the Tor network itself has dropped them. NAT-PMP port mapping is added, RPCs demand Bech32m for native witness version 1 addresses under BIP 350, and release binaries come from a Guix-based build.
Bitcoin Core
Block templates from Bitcoin Core 0.21.1 signal readiness for taproot over roughly three months. If 90% of blocks in a 2,016-block retarget period signal, taproot locks in and this version enforces BIPs 341 and 342 from block 709,632. Windows users face an extra install prompt because of a code-signing certificate problem.
Bitcoin Core
Bitcoin Core 0.21.0 adds signet test networks (BIP325) and ships Taproot's consensus rules from BIP341 and BIP342, active on signet but not on mainnet. Nodes also gain Tor v3 hidden services, BIP339 wtxid relay and the option to serve BIP157 compact filters to peers.
Bitcoin Core
Automatic bans give way to a discouragement filter in Bitcoin Core 0.20.1: misbehaving peers may still connect, but they are preferred for eviction. Conflicted wallet transactions trigger -walletnotify again after breaking in v0.19, and PSBTs for segwit inputs now carry both the witness and non-witness UTXO.
Bitcoin Core
BIP61 reject messages and BIP70 payment support are both removed from Bitcoin Core 0.20.0, which also stops using OpenSSL. An experimental -asmap option spreads peer connections across Autonomous Systems, and rpcwhitelist settings can restrict an RPC user to chosen calls.
Bitcoin Core
Tor users can now reach the Bitcoin Core website through an onion address, following frequent requests. The hidden service adds another route around censorship and a trust path that depends on neither certificate authorities nor DNS.
Bitcoin Core
Passing -blockfilterindex=basic twice no longer causes a fatal leveldb error in Bitcoin Core 0.19.1, a maintenance update. It also corrects the origfee value returned by bumpfee and adds bounds checks on indexes and amounts in PSBTs.
Bitcoin Core
Anyone downloading 0.19.0 actually gets 0.19.0.1, because an issue surfaced just after the rc process. New in this Bitcoin Core version: an avoid_reuse wallet flag that can keep already used addresses out of an operation, a getbalances RPC meant to replace older balance calls, and BIP158 block filters through -blockfilterindex.
Bitcoin Core
A malicious SOCKS proxy could overwrite the program stack of a Bitcoin Core node, according to the full disclosure of CVE-2017-18350. The buffer overflow entered with SOCKS5 support in v0.7.0rc1 and was quietly fixed in 0.15.1; only nodes configured to use such a proxy, on systems with a signed char type, were exposed.
Bitcoin Core
More than $15,000 worth of bitcoin, funded by community donations, has gone to volunteers translating the website first registered by Satoshi Nakamoto and Martti Malmi. Simon Hinterreiter and Koichi Hendrawan are thanked for organizing the project and its teams.
Bitcoin.org
A step-by-step wizard and a side-by-side comparison table replace the old wallet pages, where comparing two wallets meant juggling tabs or clicking back and forth. Each wallet is rated good, acceptable, caution or neutral across six categories, among them control, validation and privacy, and the list can be sorted by nine features.
Bitcoin.org
Version 0.18.1 of Bitcoin Core corrects the prune height returned by pruneblockchain and makes signrawtransactionwithkey report an error when a redeemScript or witnessScript is missing. On the GUI side, a Mac bug with opening the configuration file is fixed.
Bitcoin Core
Miners calling getblocktemplate without the segwit rule now get an error in Bitcoin Core 0.18.0, since leaving it out lowers their rewards. RPC setup tightens too: rpcallowip no longer makes the node listen on every interface, and a hash character in rpcpassword stops startup.
Bitcoin Core
Bitcoin's original website now reads in more than 25 languages, from Arabic to Turkish. Volunteers received bitcoin bonuses during 2018, paid from community donations and a Paxful sponsorship, and developer documentation is among the areas to be translated in 2019.
Bitcoin.org
Bitcoin Core 0.17.1 brings labels back to listtransactions: the account parameter, deprecated and renamed dummy in 0.17.0, becomes label. Fixes cover a deserialization overflow edge case and a PSBT signing bug.
Bitcoin Core
Wallets can now be loaded, created and unloaded at runtime over RPC in Bitcoin Core 0.17.0, instead of only at startup. A new -avoidpartialspends flag spends coins paid to the same address together, at the possible cost of higher fees, and a label API replaces the deprecated account one. CVE-2018-17144 does not affect this version.
Bitcoin Core
