Bitcoin Roots v32.1-roots.1 candidate
This is an unpublished candidate, not a release announcement. No public tag, downloadable package, deployment or publication is established by this text. Source acceptance and release approval remain separate gates.
The direct base is the exact official Bitcoin Core v32.1 commit f0de87f040621468b956f01f526a43a010310501. This new series folds the complete released Roots v31 line through v31.1-roots.6 and its follow-up repairs into the owning semantic changes. Bitcoin Knots 29.3.knots20260507 is historical feature provenance, not the direct base or a release dependency. Historical v31.1-roots.6 notes are retained unchanged and do not qualify this candidate.
Preserved policy and network behavior
Roots remains compatible with Bitcoin Core consensus and does not enforce RDTS/BIP110. Relay, mempool and mining-template restrictions are local and configurable: consensus-valid blocks containing locally rejected transactions remain acceptable.
- Retain scoped policy parsing, local standardness/coin-age/reuse/replacement controls, independent subdust arithmetic, initialized dynamic-dust lifecycle and effective-policy reporting. Core v32 graph/package invariants remain native. Full RBF remains the default, with explicit Never/OptIn policies and v3/TRUC qualification. Applied settings are reported by
getmempoolinfo.policy; the legacy top-levelfullrbffield requires native v32-deprecatedrpc=fullrbfcompatibility. - Default data-carrier policy remains 83 aggregate bytes with full recognized input/witness counting and a cost of 1 vbyte per detected data byte. More than one OP_RETURN output retains
multi-op-returnrejection. Nonstandard/bare carrier controls and consensus rules remain separate. Current help describes the aggregate counting and single-output boundary. - Preserve priority-template selection, dependency ordering, priority-selected ancestor accounting, resource limits and native residual chunks. GBT and mining IPC consume the same applied policy.
- Keep the compact reconstruction count default at Core's 100, not the old Roots value of 32,768. The 10 decimal MB cap charges transaction dynamic storage; slot/object overhead and shared ownership are separate. Either zero limit disables the cache. Cache retention does not change admission or consensus.
- Preserve permission and address-relay repairs, manual block-fetch tracking, current-connection peer facts and GUI refresh/reset behavior. Consumers must not expect the removed
misbehavior_scorefield. Bare whitelist grants do not implyaddr; address-based outbound grants apply to manual connections.
Wallet migration and disclosure
The port keeps descriptor wallets with SQLite and native external-signer boundaries. It does not restore a Berkeley DB build option. Follow the supported Core legacy-wallet migration path and retain independent secure backups.
Core v32 sends create PSBT v2 by default. The GUI reports actual reconstructed signaling for PSBT v0/v2 and starts per-send RBF from the wallet preference. Signaling does not promise replacement acceptance. Native settxfee/paytxfee removal is retained; sweep uses fee estimation and configured fallback.
sweepprivkeys and the Qt6 Sweep Private Key dialog retain transient WIF input, confirmed P2PKH and compressed-key native/wrapped P2WPKH scanning, selected-wallet local signing and signed-preview default. They do not scan Taproot or import keys. Submission requires the exact reviewed preview transaction and final authorization; after that boundary cancellation cannot undo broadcast.
exportaddresskey, listdescriptors, gethdkeys and derivehdkey are disabled entirely by default, including public-only modes. Enable them only by starting the node with --allow-dangerous-rpc (or =1). Configuration files, JSON and runtime settings cannot enable the permission. Omission or =0 disables it; invalid values and negated forms are rejected. RPC authentication and wallet unlock requirements remain in force. This also applies to the Qt RPC console.
With that explicit startup opt-in, exportaddresskey ADDRESS [key_type] retains the released roots.6 contract for recognized local descriptor-wallet scripts: P2PKH/P2WPKH, P2SH/P2WSH wrappers, multisig/Miniscript and Taproot internal/leaf/direct-output and MuSig2 participant keys. The sorted keys array is canonical. Original P2PKH/native-P2WPKH top-level aliases remain compatible; omitted/null key_type selects wallet, while taproot_output requires an available effective output secret and exact commitment metadata. Participant keys are not aggregate keys.
Normal selected-wallet authorization and unlock are required. Watch-only, private-key-disabled and external-signer wallets cannot export local secrets. Partial ownership does not promise an independent spend. Export does not recover unknown derivation paths, scripts or commitments or advance keypools/balances.
An exported scalar may control other addresses, including an HD master private key. A non-hardened child secret together with the ancestor xpub can compromise the private subtree. Protect authenticated local RPC and use protected stdin for transfers, keeping secrets out of command arguments, environment variables, logs and files. Host/client/Qt copies may persist; complete memory erasure is not promised. Export is not backup, does not broaden sweep's script coverage and does not establish additional Quietproof proof support. Read the complete wallet manual before operating on funds.
Current build and operator interfaces
Qt >=6.2 is supported; Qt5 and libevent dependencies are not restored. HTTP, IPC, PSBT and index/resource behavior follows the native v32 interfaces where it satisfies the retained contract. Embedded libraries remain default; explicit system LevelDB/secp256k1 builds must meet the current API probes. Windows optional MiniUPnPc discovery does not establish UPnP runtime support.
Read/write configuration, initialized effective policy and native monotonic uptime remain available. Statistics source is dormant: getmempoolstats is not registered and no samples are collected. No Network Watch, privacy score, CoinJoin/payjoin, automatic consolidation or anonymity guarantee is introduced.
Product help/version/About output identifies Bitcoin Roots and Plan-B Foundation, with separate historical Bitcoin Core attribution. Wire identity remains Satoshi; numeric protocol/version identifiers are unchanged. See the feature catalog and build profile guide.
Verification and release boundary
Owning-theme evidence, retained failures and remaining limitations are recorded in the port review. Current manuals and the example configuration are generated from current candidate help through isolated regtest wrappers; optional-build and debug-only help omissions must not be interpreted as removed features. No old manual is reused as current help.
Local maintenance, archive, synthetic-signing/draft and mocked transport tests do not establish hosted CI or actual five-platform builds. Full candidate, compatibility, integration and final accepted-SHA portable replay remain their own gates. Earlier source snapshots and binary results apply only to their recorded inputs; later source changes require renewed affected verification.
The portable patch is exported from the exact Core base and excludes .github/**. Local replay uses git am -3 --keep-cr with required commit signing and product blob/mode/symlink parity, while Core hosting files remain unchanged. Release machinery targets Linux x86_64/aarch64, macOS x86_64/arm64 and Windows x86_64 packages. Package builds disable test execution and do not close source-verification gaps.
Only a separately authorized tag push reaches required SHA512 manifest signing and new-draft creation. Every existing draft/public release blocks replacement. Manifest signing is separate from Git-tag and platform-code signing. The workflow describes unsigned annotated tags, ad-hoc macOS app signatures without Developer ID/notarization, and no Windows Authenticode signature; verify the actual future artifacts and signing disclosures independently. No such run, signature or draft is claimed here. Upstream Core-tag signature verification was explicitly waived for this port; source identity/ancestry checks remain required and the waived check is not recorded as passed.
Acknowledgements
Thanks to @danielabrozzoni for the P2P review behind retained permission and reporting corrections.
Thank you to devjoinedthechat for priority-selected ancestor accounting (#24) and configured RBF reporting (#25). Their contributions and regressions are preserved. Thanks also to Jaromil, Plan-B Foundation and the Bitcoin Core contributors. Historical releases, source credits and assets remain immutable.