From: fanquake <fanquake@gmail.com>
To: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: [bitcoindev] Bitcoin Core v30.2rc1 Released
Date: Fri, 9 Jan 2026 03:57:08 -0800 (PST) [thread overview]
Message-ID: <66cd0bdb-e41d-40d8-9373-9e40d7555906n@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2582 bytes --]
Bitcoin Core version v30.2rc1 is now available from:
<https://bitcoincore.org/bin/bitcoin-core-30.2/test.rc1>
This release includes new features, 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
===============
### Wallet
- #34156 wallet: fix unnamed legacy wallet migration failure
- #34215 wallettool: fix unnamed createfromdump failure walletsdir deletion
### IPC
- #33511 init: Fix Ctrl-C shutdown hangs during wait calls
### Build
- #33950 guix: reduce allowed exported symbols
- #34107 build: Update minimum required Boost version
### Test
- #34137 test: Avoid hard time.sleep(1) in feature_init.py
### Fuzz
- #34091 fuzz: doc: remove any mention to address_deserialize_v2
### Doc
- #34182 doc: Update OpenBSD Build Guide
### Misc
- #34174 doc: update copyright year to 2026
Credits
=======
Thanks to everyone who directly contributed to this release:
- Ava Chow
- brunoerg
- fanquake
- furszy
- Hennadii Stepanov
- MarcoFalke
- Ryan Ofsky
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/66cd0bdb-e41d-40d8-9373-9e40d7555906n%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 3588 bytes --]
next reply other threads:[~2026-01-09 11:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-09 11:57 fanquake [this message]
2026-01-09 18:33 ` /dev /fd0
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=66cd0bdb-e41d-40d8-9373-9e40d7555906n@googlegroups.com \
--to=fanquake@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