diff options
| author | MarcoFalke <falke.marco@gmail.com> | 2021-12-11 09:41:20 +0100 |
|---|---|---|
| committer | MarcoFalke <falke.marco@gmail.com> | 2021-12-11 09:41:25 +0100 |
| commit | ac92ab6da58e34993d0641b98eef5b5f55b6cbf9 (patch) | |
| tree | 81cb5432b9e9697f607e907c78cb922b7e8e5ad6 /doc/build-openbsd.md | |
| parent | 90deb9f980d02b9ca4000a78baa2beb15a5f1bbd (diff) | |
| parent | d5cab1a96d26e66d342fb5ec35c809bb82869d00 (diff) | |
Merge bitcoin/bitcoin#23113: Add warnings to createmultisig and addmultisig if using uncompressed keys
d5cab1a96d26e66d342fb5ec35c809bb82869d00 Add createmultisig and addmultisigaddress warnings release note (Samuel Dobson)
e46fc935aa6eb392ef9411dad310697aba601f6a Add warnings field to addmultisigaddress to warn about uncompressed keys (Samuel Dobson)
d1a9742623e2a8f3307c84c2df6993f62617a6f6 Add warnings field to createmultisig to warn about uncompressed keys (Samuel Dobson)
Pull request description:
Fixes #21368
Currently, if there are any uncompressed keys when calling `AddAndGetMultisigDestination`, it will just default to a legacy address regardless of the chosen `address_type`. Rather than keeping this silent behaviour which may be confusing to users, we explicitly add a `warnings` field which will warn the user why their address format is different.
ACKs for top commit:
achow101:
ACK d5cab1a96d26e66d342fb5ec35c809bb82869d00
Tree-SHA512: c2ac7f7689251bd4fcd8c26506f053921fbaf34c7a26a74e82ebc7f82cc0bd25407fd7954bf98365dcafa51fa45dcdbee6214320580ca69509690c3555e71cc0
Diffstat (limited to 'doc/build-openbsd.md')
0 files changed, 0 insertions, 0 deletions