wallet: #17261 regression: addmultisigaddress addresses not treated as solvable #18075
Description
Filing this issue to record steps to reproduce a small regression from #17261, which is fixed in #18067. Reproducing the bug has to be done manually because we don't have a framework for writing wallet backwards compatibility tests (#12134 is stuck in review)
Steps to reproduce
MERGE=2d6e76af240969aa284cd4c3d376493988e218c2 # 17261 merge commit
PK1=0296b538e853519c726a2c91e61ec11600ae1390813a627c66fb8be7947be63c52 # key from wallet_address_types.py
PK2=037211a824f55b505228e4c3d5194c1fcfaa15a456abdf37f9b9d97a4040afc073 # key from wallet_address_types.py
git checkout $MERGE^
make
src/bitcoind -regtest &
ADDRESS=$(src/bitcoin-cli -regtest addmultisigaddress 1 "[\"$PK1\", \"$PK2\"]" true legacy | jq -r .address)
src/bitcoin-cli -regtest stop
git checkout $MERGE
make -C src bitcoind
src/bitcoind -regtest &
src/bitcoin-cli -regtest getaddressinfo $ADDRESS | jq .solvable # BUG: expect true, actual false
src/bitcoin-cli -regtest stopExpected behavior
getaddressinfo reports multisig address is solvable
Actual behavior
getaddressinfo returns "solvable": false