Support for testnet4
and Legacy RPC Compatibility with bitcoind
Backend
#985
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Overview
This PR introduces support for
testnet4
, as recently introduced by the Bitcoin community. Additionally, it enhances compatibility by enabling support for Legacy RPC, allowing the wallet to connect to thebitcoind
backend in addition to the existingbtcd
backend.Key Changes
Testnet4 Support:
testnet4
support from the PR opened againstbtcd
(feat: Add testnet4 chain support (recreated) btcd#2318).testnet4
inbtcwallet
.go.mod
import accordingly once the upstream PR is merged.Backend Selection Enhancement (Fixes Add bitcoind Support as a Backend Option in btcwallet #983 ):
bitcoind
as a backend, in addition to the existingbtcd
backend.--backend
flag to allow users to select their preferred backend.How to Use
--testnet4
flag.--backend
flag:Impact & Compatibility
✅ No breaking changes – existing behavior remains unchanged.
✅ Fully backward-compatible – extends functionality without modifying interfaces or APIs.
Once the
btcd
PR #2318 is merged, we should update thego.mod
dependency to finalizetestnet4
support.