v30.3-roots.1 · Commit 29: [PATCH 29/68] docs(release): prepare v30.3-roots.1 candidate notes
doc/release-notes.md
Before: doc/release-notes.md · After: doc/release-notes.md
File metadata
index f8ccd6615c1a88618dc10036e8c3c308a3a8914c..6c18b6b7ff1c686215bc4097f3777505b288cc7d 100644
Download original patch · Release notes
Diff rows 1–53 of 53. Line numbers refer to the original before/after files.
+ Added− RemovedUnmarked lines are context.
Scroll the code area horizontally to read long lines. The two line-number columns refer to before and after.
doc/release-notes.md
CHANGED
|
@@ -1,3 +1,53 @@
|
|
|
1
|
+
Bitcoin Roots v30.3-roots.1 candidate notes
|
|
2
|
+
============================================
|
|
3
|
+
|
|
4
|
+
This is candidate documentation for the intended `v30.3-roots.1` release, not
|
|
5
|
+
a release announcement. The published `v29.4-roots.2` release remains the
|
|
6
|
+
baseline; verify any executable with `bitcoin-cli --version` and
|
|
7
|
+
`bitcoin-cli help sweepprivkeys` before operating it.
|
|
8
|
+
|
|
9
|
+
Wallet privacy tools
|
|
10
|
+
--------------------
|
|
11
|
+
|
|
12
|
+
- `sweepprivkeys` performs an explicit, operator-controlled sweep of confirmed
|
|
13
|
+
UTXOs for supported Base58 WIF keys into a spendable destination in the
|
|
14
|
+
selected wallet. The supported configuration is a descriptor wallet with
|
|
15
|
+
local private keys. P2PKH is supported for compressed and uncompressed WIF;
|
|
16
|
+
compressed WIF also supports native and wrapped P2WPKH. It does not scan
|
|
17
|
+
Taproot or other script forms, import supplied keys, or act as a backup or
|
|
18
|
+
wallet-recovery mechanism.
|
|
19
|
+
- A non-broadcast signed preview is the default. Review the destination, input
|
|
20
|
+
total, fee, transaction ID, and Replace-By-Fee state before requesting a
|
|
21
|
+
broadcast. Chain, fee, and relay conditions can change after a preview.
|
|
22
|
+
- The Qt sweep dialog masks the key, disables copy/cut/context-menu actions,
|
|
23
|
+
uses transient secure key handling, and can cancel an outstanding scan or
|
|
24
|
+
preview. Broadcast submission has a final authorization boundary and cannot
|
|
25
|
+
be cancelled once it begins. These safeguards reduce secret exposure; they do
|
|
26
|
+
not guarantee that a displayed key or all GUI/host memory copies can be
|
|
27
|
+
erased.
|
|
28
|
+
- Send Coins coin control shows wallet-reported amount, effective value,
|
|
29
|
+
confirmations, reuse, grouping, lock/spendability, input-size, fee, change,
|
|
30
|
+
and RBF facts. Locked outputs remain visible but cannot be selected; unsafe
|
|
31
|
+
and immature outputs excluded by the normal availability filters are not
|
|
32
|
+
added only to display a status. This is not a privacy score, an anonymity
|
|
33
|
+
guarantee, CoinJoin, payjoin, automatic consolidation, key export, or a
|
|
34
|
+
chain-analysis dashboard.
|
|
35
|
+
|
|
36
|
+
Compatibility and verification
|
|
37
|
+
------------------------------
|
|
38
|
+
|
|
39
|
+
Bitcoin Roots remains compatible with Bitcoin Core v30.3 consensus and P2P
|
|
40
|
+
wire behavior. This Roots feature series introduces no wallet-format migration. Descriptor
|
|
41
|
+
wallets with local private keys are the supported sweep configuration;
|
|
42
|
+
watch-only, private-key-disabled, and external-signer wallets are not eligible
|
|
43
|
+
sweep destinations. Legacy wallets must be migrated to descriptor wallets; the
|
|
44
|
+
Core 30.3 port does not restore a Berkeley DB build option. Back up wallet material
|
|
45
|
+
before any upgrade or sweep, and use the built help, a non-broadcast preview,
|
|
46
|
+
and the focused wallet tests as the verification record for a particular build.
|
|
47
|
+
|
|
48
|
+
The Bitcoin Core v30.3 notes below are retained as upstream compatibility
|
|
49
|
+
context. Their availability statements do not announce a Bitcoin Roots release.
|
|
50
|
+
|
|
1
51
|
v30.3 Release Notes
|
|
2
52
|
===================
|
|
3
53
|
|