rpcserver: add parity with bitcoind for validateaddress #1613
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.
What is this about?
Updated the
rpcserver
handler forvalidateaddress
JSON-RPC command to have parity with the bitcoind 0.20.0 interface.The new fields included are -
isscript
,iswitness
,witness_version
, andwitness_program
. ThescriptPubKey
field has been left out since it requires wallet access.This update has no impact on the
rpcclient.ValidateAddress
method, which uses thebtcjson.ValidateAddressWalletResult
type for modelling the response from bitcoind.How to test?
Unfortunately, we lack a proper framework to write rpcserver tests, so here's you can test this PR:
Prepare
$ go build . $ ./btcd --testnet --rpcuser=aaaa --rpcpass=bbbb
In another tab,
P2PKH valid
P2SH-P2WPKH valid
P2WPKH valid
Invalid address
Invalid network