Instead of whitelisted, the permissions field indicates if the peer has special privileges. Instead of addnode, the connection_type field returns manual. getpeerinfo no longer returns the following fields: addnode, banscore, and whitelisted, which were previously deprecated in 0.21.High-bandwidth peers send new block announcements via a cmpctblock message rather than the usual inv/headers announcements. The getpeerinfo RPC returns two new boolean fields, bip152_hb_to and bip152_hb_from, that respectively indicate whether we selected a peer to be in compact blocks high-bandwidth mode or whether a peer selected us as a compact blocks high-bandwidth peer.Once that happens, Bech32m is expected to be used for them, so this shouldn’t affect any production systems, but may be observed on other networks where such addresses already have meaning (like signet). No version 1 addresses should be created for mainnet until consensus rules are adopted that give them meaning (as will happen through BIP 341). These now require a Bech32m encoding instead of a Bech32 one, and Bech32m encoding will be used for such addresses in RPC output as well. Due to BIP 350 being implemented, behavior for all RPCs that accept addresses is changed when a native witness version 1 (or higher) is passed.Added NAT-PMP port mapping support via libnatpmp.Henceforth, Bitcoin Core ignores Tor v2 addresses it neither rumors them over the network to other peers, nor stores them in memory or to peers.dat. This release removes support for Tor version 2 hidden services in favor of Tor v3 only, as the Tor network dropped support for Tor v2 with the release of Tor version 0.4.6.Added support for running Bitcoin Core as an I2P (Invisible Internet Project) service and connect to such services.It is not recommended to use Bitcoin Core on unsupported systems.įrom Bitcoin Core 22.0 onwards, macOS versions earlier than 10.14 are no longer supported. Bitcoin Core should also work on most other Unix-like systems but is not as frequently tested on them. Compatibilityīitcoin Core is supported and extensively tested on operating systems using the Linux kernel, macOS 10.14+, and Windows 7 and newer. Old wallet versions of Bitcoin Core are generally supported. 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. 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 Mac) or bitcoind/ bitcoin-qt (on Linux). If you are running an older version, shut it down. Video: Live map of reachable nodes in the Bitcoin network being crawled by the Bitnodes crawler. Version 0.21.0 was released in January 2021. Over 70% are using Bitcoin Core 0.21.0 and above. To receive security and update notifications, subscribe to: /en/list/announcements/join/Īt the time of writing this blog post around 18% of reachable nodes in the Bitcoin network crawled by Bitnodes are using Bitcoin Core 0.22.0.Bugs can be reported using the issue tracker at GitHub: /bitcoin/bitcoin/issues.This release includes new features, various bug fixes and performance improvements, as well as updated translations.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |