Bitcoin Core 30.2 Released

[achow101]

v30.2 Release Notes

Bitcoin Core version v30.2 is now available from:

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

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
• #34221 test: migration, avoid backup name mismatch in default_wallet_failure

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
• #34227 guix: Fix osslsigncode tests

Test

• #34137 test: Avoid hard time.sleep(1) in feature_init.py
• #34226 wallet: test: Relative wallet failed migration cleanup

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
• davidgumberg
• fanquake
• furszy
• Hennadii Stepanov
• MarcoFalke
• Ryan Ofsky

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

[cr1776]

As it usual, the build from source when smoothly.  I can't remember the last time it didn't, thankfully.  I am curious how many people follow the instructions below and just download vs building it themselves.  :-)

[DeeppRockk]

yeah the v30.2 release looks solid! building from source is pretty straightforward these days and adds that extra layer of trust. i always recommend it if you can spare the time.

great to see the devs keeping things running smoothly.

btw, compiling yourself also lets you tweak settings for your setup.

[C10H15N]

Use the precompiled binaries after checking the hash

Only using core as a full node, not a wallet anymore. 

[Yamane_Keto]

I noticed that a new privatebroadcast boolean option via short-lived Tor or I2P connections has been added.
https://github.com/bitcoin/bitcoin/pull/29415

great privacy enhancement

[achow101]

I noticed that a new privatebroadcast boolean option via short-lived Tor or I2P connections has been added.
https://github.com/bitcoin/bitcoin/pull/29415

great privacy enhancement

Not in this release.

[AakZaki]

I just finished downloading the full Bitcoin Core 30.2. The process took about 50 hours to sync approximately 810GB of data on my PC. A fast SSD and internet connection really help and make the process much smoother.
After the synchronization was complete, I realized that running a full node is not only about having large storage, but also about intention and understanding. With nodes that are fully synchronized, I can verify my own transactions without relying on other parties, privacy is more maintained and indirectly contributes to maintaining the security and decentralization of the Bitcoin network.

Code:

Bitcoin getblockchaininfo
{
  "chain": "main",
  "blocks": 932987,
  "headers": 932987,
  "bestblockhash": "0000000000000000000133da8996d712e7f4e5dd65698e206105fc36bd516462",
  "bits": "1701ebf2",
  "target": "00000000000000000001ebf20000000000000000000000000000000000000000",
  "difficulty": 146472570619930.8,
  "time": 1768854957,
  "mediantime": 1768852597,
  "verificationprogress": 1,
  "initialblockdownload": false,
  "chainwork": "00000000000000000000000000000000000000010860d1e4320832be2978691c",
  "size_on_disk": 813667655496,
  "pruned": false,
  "warnings": [
  ]
}

[Vlad BTCTKVR]

Thank you, been waiting for this one! Updated right away.

[cr1776]

Use the precompiled binaries after checking the hash

Only using core as a full node, not a wallet anymore. 

I have been building from source since 0.3.21 - I always felt more comfortable doing so, and so just am in the habit of doing it.  It doesn't take long.

[HITTI2]

When does old wallet be not usable?

Discussion found here.

https://bitcointalk.org/index.php?topic=5558933.msg65799539#msg65799539

[Dbillion]

I downloaded version 30.2 from Bitcoincore.org to recover a legacy wallet, and once the wallet was restored with the new version, it had 41 Bitcoins.
To spend them, I synchronized the FULL node.
I sent a test transfer of 20.5 to one of my wallets before finishing, but it remained in the mempool with 0 confirmations because the synchronization wasn't complete yet.
I left it finishing, and when I woke up that morning, I saw that the 41 Bitcoins were gone and 15 different transactions had been made to different addresses in the same minute that I sent my first uncompleted transaction.
And mine is canceled (in conflict).
When I checked Blockchain Transactions were done a day before. Different track record in Bitcoin Core and Blockchain.
I hope you can look into what happened.

NOTE: I was not hacked or scammed because I checked all download and laptop before. It was clear and clean.

[cr1776]

I downloaded version 30.2 from Bitcoincore.org to recover a legacy wallet, and once the wallet was restored with the new version, it had 41 Bitcoins.
To spend them, I synchronized the FULL node.
I sent a test transfer of 20.5 to one of my wallets before finishing, but it remained in the mempool with 0 confirmations because the synchronization wasn't complete yet.
I left it finishing, and when I woke up that morning, I saw that the 41 Bitcoins were gone and 15 different transactions had been made to different addresses in the same minute that I sent my first uncompleted transaction.
And mine is canceled (in conflict).
When I checked Blockchain Transactions were done a day before. Different track record in Bitcoin Core and Blockchain.
I hope you can look into what happened.

NOTE: I was not hacked or scammed because I checked all download and laptop before. It was clear and clean.

This probably isn't the spot to ask it, but if you provide more information elsewhere (e.g. transaction IDs etc) someone may be able to explain what happened.

[nicolesilvra21]

Thank you, been waiting for this one! Updated right away.

[kiragaz]

did it fix legacy wallets migration problem?

[achow101]

did it fix legacy wallets migration problem?

Yes, this contains a fix for the wallet deletion issue that could occur during migration.

[0x000369]

achow101 good on you for setting the record straight
@Yamane_Keto always read the release notes bud before getting hyped
that privatebroadcast option sounds cool but it aint here yet
been through enough soft forks to know how this goes

everyone still arguing about building from source vs binaries
lmao its 2026 just get a fast ssd and check the hashes
the node runners are the real MVPs
but dont act like its new info @AakZaki we been doing this since the dark ages

[btcwoot]

I just finished downloading the full Bitcoin Core 30.2. The process took about 50 hours to sync approximately 810GB of data on my PC. A fast SSD and internet connection really help and make the process much smoother.
After the synchronization was complete, I realized that running a full node is not only about having large storage, but also about intention and understanding. With nodes that are fully synchronized, I can verify my own transactions without relying on other parties, privacy is more maintained and indirectly contributes to maintaining the security and decentralization of the Bitcoin network.

Code:

Bitcoin getblockchaininfo
{
  "chain": "main",
  "blocks": 932987,
  "headers": 932987,
  "bestblockhash": "0000000000000000000133da8996d712e7f4e5dd65698e206105fc36bd516462",
  "bits": "1701ebf2",
  "target": "00000000000000000001ebf20000000000000000000000000000000000000000",
  "difficulty": 146472570619930.8,
  "time": 1768854957,
  "mediantime": 1768852597,
  "verificationprogress": 1,
  "initialblockdownload": false,
  "chainwork": "00000000000000000000000000000000000000010860d1e4320832be2978691c",
  "size_on_disk": 813667655496,
  "pruned": false,
  "warnings": [
  ]
}

The pruning feature is a life changer for people who dont have the hard drive space for a block chain

[cr1776]

...
everyone still arguing about building from source vs binaries
...

Is anyone arguing about it?  I've just always built from source, to each his or her own.  It is certainly easier to just download a binary but it doesn't take long to build it.  :-)