Sunday, 1 September 2019

Bitcoin Core 18.1 still does not support SegWit addresses for message signing, rendering the sign message feature useless for new wallets. Is there a reason for this?

Headline sounds passively aggressive, but I just don't get it how the Bitcoin Core Wallet still does not support this while being the main force regarding Bitcoin's development.

More than two years after the introduction Bitcoin Core still does not support the signing of messages using standard P2SH ("3"-addresses) and bench32 encoded addresses ("bc1"-addresses), which are de facto becoming the standard for transactions on the blockchain.

Unfortunately it is not possible to create old style P2PKH "Legacy" addresses with Bitcoin Core anymore; new addresses are always SegWit-compatible. This is *not* a bad thing, as it thrives SegWit adoption, however the in the title mentioned signing feature does not work with these addresses.

The sign message feature is was such a wonderful function to easily prove the ownership of funds and their address. Electrum and Trezor support the signing with the new standard btw, so is there a reason why Bitcoin Core does not?

THE FEATURE I'M TALKING ABOUT. ARGHHHHHHHHHHHHHHHHHHHHHH!



Submitted September 02, 2019 at 05:11AM by AdditionalStruggle6 http://bit.ly/2ZETGVx

No comments :

Post a Comment