diff options
| author | Russell Yanofsky <russ@yanofsky.org> | 2020-02-04 17:24:48 -0500 |
|---|---|---|
| committer | Russell Yanofsky <russ@yanofsky.org> | 2020-02-12 11:48:30 -0500 |
| commit | 005f8a92ccb5bc10c8daa106d75e1c21390461d3 (patch) | |
| tree | e31c354d46ed2095e63202a96bbedb29a5b34d6d /.appveyor.yml | |
| parent | 2bdc476d4d23256d8396bb9051a511f540d87392 (diff) | |
| download | bitcoin-005f8a92ccb5bc10c8daa106d75e1c21390461d3.tar.xz | |
wallet: Improve LegacyScriptPubKeyMan::CanProvide script recognition
Make LegacyScriptPubKeyMan::CanProvide method able to recognize p2sh scripts
when the redeem script is present in the mapScripts map without the p2sh script
also having to be added to the mapScripts map. This restores behavior prior to
https://github.com/bitcoin/bitcoin/pull/17261, which I think broke backwards
compatibility with old wallet files by no longer treating addresses created by
`addmultisigaddress` calls before #17261 as solvable.
The reason why tests didn't fail with the CanProvide implementation in #17261
is because of a workaround added in 4a7e43e8460127a40a7895519587399feff3b682
"Store p2sh scripts in AddAndGetDestinationForScript", which masked the problem
for new `addmultisigaddress` RPC calls without fixing it for multisig addresses
already created in old wallet files.
This change adds a lot of comments and allows reverting commit
4a7e43e8460127a40a7895519587399feff3b682 "Store p2sh scripts in
AddAndGetDestinationForScript", so the AddAndGetDestinationForScript() function,
CanProvide() method, and mapScripts map should all be more comprehensible
Diffstat (limited to '.appveyor.yml')
0 files changed, 0 insertions, 0 deletions