Quote from: hugeblack on March 01, 2018, 08:38:49 AM

I am sorry because my question is off-topic, but I dont want to create a new topic

why Bitcoin Core 0.16.0 developers start using/enabling native segwit addresses by default while sign message/verify message doesnt support segwit addresses? I know this is because some RPCs do not yet support segwit addresses but why they make it default? "its better to make a new private key and full support segwit by default, correct?"
Sources : https://bitcoin.org/en/release/v0.16.0

This might help a little: https://bitcointalk.org/index.php?topic=2885058.msg29664816#msg29664816

Quote from: achow101 on February 05, 2018, 04:38:12 PM

Quote from: bitmover on February 05, 2018, 04:33:49 PM

My doubt, regarding signing in segwit address is if this is a "bug" and will soon be corrected, or is it an abandoned feature?

It is neither a bug nor an abandoned feature. It is just that we are still working on creating a more generalized signing scheme that lets people sign with things like P2SH addresses (e.g. sign with a multisig address). There is simply no standard yet for signing with such scripts or with Segwit.

Note that you don't actually sign with an address. You sign with a public-private keypair and your wallet interprets it as an address. Your wallet could just as easily interpret it as a segwit address. We are working on creating something that actually specifies the address type, and more generally, allows signing with scripts.

But don't be afraid to start a new topic if you still have further questions.