release-notes-28.1.md
1 Bitcoin Core version 28.1 is now available from: 2 3 <https://bitcoincore.org/bin/bitcoin-core-28.1> 4 5 This release includes new features, various bug fixes and performance 6 improvements, as well as updated translations. 7 8 Please report bugs using the issue tracker at GitHub: 9 10 <https://github.com/bitcoin/bitcoin/issues> 11 12 To receive security and update notifications, please subscribe to: 13 14 <https://bitcoincore.org/en/list/announcements/join/> 15 16 How to Upgrade 17 ============== 18 19 If you are running an older version, shut it down. Wait until it has completely 20 shut down (which might take a few minutes in some cases), then run the 21 installer (on Windows) or just copy over `/Applications/Bitcoin-Qt` (on macOS) 22 or `bitcoind`/`bitcoin-qt` (on Linux). 23 24 Upgrading directly from a version of Bitcoin Core that has reached its EOL is 25 possible, but it might take some time if the data directory needs to be migrated. Old 26 wallet versions of Bitcoin Core are generally supported. 27 28 Running Bitcoin Core binaries on macOS requires self signing. 29 ``` 30 cd /path/to/bitcoin-28.x/bin 31 xattr -d com.apple.quarantine bitcoin-cli bitcoin-qt bitcoin-tx bitcoin-util bitcoin-wallet bitcoind test_bitcoin 32 codesign -s - bitcoin-cli bitcoin-qt bitcoin-tx bitcoin-util bitcoin-wallet bitcoind test_bitcoin 33 ``` 34 35 Compatibility 36 ============== 37 38 Bitcoin Core is supported and extensively tested on operating systems 39 using the Linux Kernel 3.17+, macOS 11.0+, and Windows 7 and newer. Bitcoin 40 Core should also work on most other UNIX-like systems but is not as 41 frequently tested on them. It is not recommended to use Bitcoin Core on 42 unsupported systems. 43 44 Notable changes 45 =============== 46 47 ### P2P 48 49 - When the `-port` configuration option is used, the default onion listening port will now 50 be derived to be that port + 1 instead of being set to a fixed value (8334 on mainnet). 51 This re-allows setups with multiple local nodes using different `-port` and not using `-bind`, 52 which would lead to a startup failure in v28.0 due to a port collision. 53 54 Note that a `HiddenServicePort` manually configured in `torrc` may need adjustment if used in 55 connection with the `-port` option. 56 For example, if you are using `-port=5555` with a non-standard value and not using `-bind=...=onion`, 57 previously Bitcoin Core would listen for incoming Tor connections on `127.0.0.1:8334`. 58 Now it would listen on `127.0.0.1:5556` (`-port` plus one). If you configured the hidden service manually 59 in torrc now you have to change it from `HiddenServicePort 8333 127.0.0.1:8334` to `HiddenServicePort 8333 60 127.0.0.1:5556`, or configure bitcoind with `-bind=127.0.0.1:8334=onion` to get the previous behavior. 61 (#31223) 62 - #30568 addrman: change internal id counting to int64_t 63 64 ### Key 65 66 - #31166 key: clear out secret data in DecodeExtKey 67 68 ### Build 69 70 - #31013 depends: For mingw cross compile use `-gcc-posix` to prevent library conflict 71 - #31502 depends: Fix CXXFLAGS on NetBSD 72 73 ### Test 74 75 - #31016 test: add missing sync to feature_fee_estimation.py 76 - #31448 fuzz: add cstdlib to FuzzedDataProvider 77 - #31419 test: fix MIN macro redefinition 78 - #31563 rpc: Extend scope of validation mutex in generateblock 79 80 ### Doc 81 82 - #31007 doc: add testnet4 section header for config file 83 84 ### CI 85 86 - #30961 ci: add LLVM_SYMBOLIZER_PATH to Valgrind fuzz job 87 88 ### Misc 89 90 - #31267 refactor: Drop deprecated space in `operator""_mst` 91 - #31431 util: use explicit cast in MultiIntBitSet::Fill() 92 93 Credits 94 ======= 95 96 Thanks to everyone who directly contributed to this release: 97 98 - fanquake 99 - Hennadii Stepanov 100 - laanwj 101 - MarcoFalke 102 - Martin Zumsande 103 - Marnix 104 - Sebastian Falbesoner 105 106 As well as to everyone that helped with translations on 107 [Transifex](https://www.transifex.com/bitcoin/bitcoin/).