Currently backports:
Pulls release notes: https://github.com/bitcoin-core/bitcoin-devwiki/wiki/27.0-Release-Notes-Draft.
Finalizes v27.0
.
Currently backports:
Pulls release notes: https://github.com/bitcoin-core/bitcoin-devwiki/wiki/27.0-Release-Notes-Draft.
Finalizes v27.0
.
Pretty much all library packages were renamed in the 64-bit time_t
migration to add `t64` (even on 64-bit platforms).
Instead of complicating the doc with conditional package names, suggest
installing the `-dev` packages which still have the same name, and
besides that, are the right way to go about it as they contain the
"user facing" C++ headers needed to build against Qt5.
For Fedora, devel packages are already suggested.
This affects Ubuntu 24.04 and Debian Testing.
Github-Pull: #29764
Rebased-From: a3c6a13cb23999fa70c428f1229acbf1b3883f11
Fix CI build for t64 migration.
Github-Pull: #29764
Rebased-From: 6c2990416e2dabd845f5ec50ec6ff138136c9b08
The following sections might be updated with supplementary metadata relevant to reviewers and maintainers.
For detailed information about the code coverage, see the test coverage report.
See the guideline for information on the review process.
Type | Reviewers |
---|---|
ACK | stickies-v, achow101 |
If your review is incorrectly listed, please react with 👎 to this comment and the bot will ignore it on the next update.
Github-Pull: #29740
Rebased-From: fa22a438fa8f1c9cd4b4c44ff45cefd178bf5999
The developer mailing list was migrated to Google Groups in February 2024
as announced in https://groups.google.com/g/bitcoindev/c/aewBuV6k-LI.
The archives maintained by the Linux Foundation stopped updating in December
2024. Thus, we point to the new archive maintained by gnusha.org.
The codebase refers to old discussions linked to the Linux Foundation archives.
Since all links are still active to this date, we keep them as they are.
See #29782.
Github-Pull: #29782
Rebased-From: 0ead466a0c72bef0a8622749b84e9c7c5c37144f
54+ blocks. (#29189)
55+
56+mempool.dat compatibility
57+-------------------------
58+
59+- The `mempool.dat` file created by -persistmempool or the savemempool RPC will
0- The `mempool.dat` file created by `-persistmempool` or the savemempool RPC will
80+ fall out of consensus with the network. (#28956)
81+
82+Mempool Policy Changes
83+----------------------
84+
85+- Opt in Topologically Restricted Until Confirmation (TRUC) Transactions policy
0- Opt-in Topologically Restricted Until Confirmation (TRUC) Transactions policy
82+Mempool Policy Changes
83+----------------------
84+
85+- Opt in Topologically Restricted Until Confirmation (TRUC) Transactions policy
86+ (aka v3 transaction policy) is available for use on test networks only with
87+ `-acceptnonstdtxn=1`. By setting the transaction version number to 3, TRUC transactions
0 (aka v3 transaction policy) is available for use on test networks when
1 `-acceptnonstdtxn=1` is set. By setting the transaction version number to 3, TRUC transactions
100+ library. (#28967)
101+
102+Updated RPCs
103+------------
104+
105+- The addnode RPC now follows the -v2transport option (now on by default, see above) for making connections.
0- The addnode RPC now follows the `-v2transport` option (now on by default, see above) for making connections.
129+
130+Pruning
131+-------
132+
133+- When pruning during initial block download, more blocks will be pruned at each
134+ flush in order to speed up the syncing of such nodes.
0 flush in order to speed up the syncing of such nodes. (#20827)
136+Init
137+----
138+
139+- Various fixes to prevent issues where subsequent instances of Bitcoin Core would
140+ result in deletion of files in use by an existing instance. (#28784, #28946)
141+- Improved handling of empty settings.json files (#28920)
0- Improved handling of empty `settings.json` files. (#28920)
Incorrect pull number
0- Improved handling of empty settings.json files (#29144)
57+-------------------------
58+
59+- The `mempool.dat` file created by -persistmempool or the savemempool RPC will
60+ be written in a new format, which can not be read by previous software
61+ releases. To allow for a downgrade, a temporary setting `-persistmempoolv1` has
62+ been added to fall back to the legacy format. This new format includes the XOR'ing
“This new format” right after talking about the legacy format is consusing imo.
Suggested rewrite 1)first explains the new format, 2) then describes how to fall back, 3) adds the PR number:
0- The `mempool.dat` file created by -persistmempool or the savemempool RPC will
1 be written in a new format. This new format includes the XOR'ing of transaction
2 contents to mitigate issues where external programs (such as anti-virus) attempt
3 to interpret and potentially modify the file.
4
5 This new format can not be read by previous software releases. To allow for a
6 downgrade, a temporary setting `-persistmempoolv1` has been added to fall back
7 to the legacy format. (#28207)
88+ request the application of limits on spending of their unconfirmed outputs. These
89+ restrictions simplify the assessment of incentive compatibility of accepting or
90+ replacing TRUC transactions, thus ensuring any replacements are more profitable for
91+ the node and making fee-bumping more reliable. TRUC transactions are currently
92+ nonstandard and can only be used on test networks where the standardness rules are
93+ relaxed or disabled (e.g. with `-acceptnonstdtxn=1`).
0 relaxed or disabled (e.g. with `-acceptnonstdtxn=1`). (#28948)
LGTM 4681f554bc6eb6f603512575de19bc52d08813e9 with a few release note nits
https://github.com/bitcoin-core/bitcoin-devwiki/wiki/27.0-Release-Notes-Draft.