From: Sebastian Kung <seb.kung@gmail.com>
To: bitcoindev@googlegroups.com
Subject: [bitcoindev] Bitcoin Core v29.3 Released
Date: Wed, 11 Feb 2026 19:42:33 +0100 [thread overview]
Message-ID: <CAO3Wf41sAHeZ-KR1mp=xNuydstcMk9R93ou5Jobmq9ngn7TKXA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3470 bytes --]
Bitcoin Core version 29.3 is now available from:
<https://bitcoincore.org/bin/bitcoin-core-29.3/>
This 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
macOS)
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 tested on operating systems using the
Linux Kernel 3.17+, macOS 13+, and Windows 10+. 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.
Notable changes
===============
### P2P
- #33050 net, validation: don't punish peers for consensus-invalid txs
- #33723 chainparams: remove dnsseed.bitcoin.dashjr-list-of-p2p-nodes.us
### Validation
- #32473 Introduce per-txin sighash midstate cache for legacy/p2sh/segwitv0
scripts
- #33105 validation: detect witness stripping without re-running Script
checks
### Wallet
- #33268 wallet: Identify transactions spending 0-value outputs, and add
tests for anchor outputs in a wallet
- #34156 wallet: fix unnamed legacy wallet migration failure
- #34226 wallet: test: Relative wallet failed migration cleanup
- #34123 wallet: migration, avoid creating spendable wallet from a
watch-only legacy wallet
- #34215 wallettool: fix unnamed createfromdump failure walletsdir deletion
- #34370 wallet: Additional cleanups for migration, and fixes for
createfromdump with BDB
### Mining
- #33475 bugfix: miner: fix `addPackageTxs` unsigned integer overflow
### Build
- #34227 guix: Fix `osslsigncode` tests
### Documentation
- #33623 doc: document capnproto and libmultiprocess deps in 29.x
### Test
- #33612 test: change log rate limit version gate
### Misc
- #32513 ci: remove 3rd party js from windows dll gha job
- #33508 ci: fix buildx gha cache authentication on forks
- #33581 ci: Properly include $FILE_ENV in DEPENDS_HASH
- #34344 ci: update GitHub Actions versions
Credits
=======
Thanks to everyone who directly contributed to this release:
- Anthony Towns
- Antoine Poinsot
- Ava Chow
- David Gumberg
- Eugene Siegel
- fanquake
- furszy
- Hennadii Stepanov
- ismaelsadeeq
- luke-jr
- m3dwards
- Padraic Slattery
- Pieter Wuille
- SatsAndSports
- sedited
- willcl-ark
As well as to everyone that helped with translations on
[Transifex](https://explore.transifex.com/bitcoin/bitcoin/).
--
You received this message because you are subscribed to the Google Groups "Bitcoin Development Mailing List" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bitcoindev+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/bitcoindev/CAO3Wf41sAHeZ-KR1mp%3DxNuydstcMk9R93ou5Jobmq9ngn7TKXA%40mail.gmail.com.
[-- Attachment #2: Type: text/html, Size: 4414 bytes --]
reply other threads:[~2026-02-11 18:43 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAO3Wf41sAHeZ-KR1mp=xNuydstcMk9R93ou5Jobmq9ngn7TKXA@mail.gmail.com' \
--to=seb.kung@gmail.com \
--cc=bitcoindev@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox