Issue Details

Number

30632

Title

An "output descriptor" should not have many different checksums

Description

### Is there an existing issue for this? - [X] I have searched the existing issues ### Current behaviour There are different BIP-380 checksums for the same addresses/ScriptPubKey/keys: "mpfvuvu6" and "ecrayewn", e.g.: ``` $ bitcoin-cli deriveaddresses "wpkh([b8688df1]xprv9s21ZrQH143K2x4gnzRB1eZDq92Uuvy9CXbvgQGdvykXZ9mkkot6LBjzDpgaAfvzkuxJe9JKJXQ38VoPutxvACA5MsyoBs5UyQ4HZKGshGs/84'/0'/0'/0/0)#mpfvuvu6" [ "bc1qgkju4yvvtuz0s8vqn837q396jezu2h8ex7gk98" ] ``` ``` $ bitcoin-cli deriveaddresses "wpkh([b8688df1]xprv9s21ZrQH143K2x4gnzRB1eZDq92Uuvy9CXbvgQGdvykXZ9mkkot6LBjzDpgaAfvzkuxJe9JKJXQ38VoPutxvACA5MsyoBs5UyQ4HZKGshGs/84h/0h/0h/0/0)#ecrayewn" [ "bc1qgkju4yvvtuz0s8vqn837q396jezu2h8ex7gk98" ] ``` ### Expected behaviour The checksum should be the same irrespectively how a ScriptPubKey is represented ("output descriptor" formats, hex string, binary etc.). Different checksums are against their purpose, confuse users, alerting as if ScriptPubKey/data were entered incorrectly by a user. ### Steps to reproduce See the "current behaviour" section above. ### Relevant log output _No response_ ### How did you obtain Bitcoin Core Pre-built binaries ### What version of Bitcoin Core are you using? 27.1 and older ones ### Operating system and version Any ### Machine specifications _No response_

URL

https://github.com/bitcoin/bitcoin/issue/30632

Closed by

Notes

Attention of

Kill Factor (1-10)

Save

Back to List