How to use Segwitaddress.ORG ?

[TheQuin]

Can you please throw some light over that bold part? I'm unsure of the issues with the current version of core and whether I should wait for the newer release of core (i.e.; 0.16)

Core is constantly being developed and if you go to github and download the latest commit in source code form and then compile it yourself then you have a newer version than the precompiled version (the official release if you like).
The Segwit functionality for the wallet was added in one of the commits for 0.15.0.1 but they delayed rolling into the 0.15.1 release and held it back for 0.16.0
One of the Core developers recently posted on this forum that he expects it to be released in February.

The reason why I'm interested in that is, when we have at least one thing fixed, we can use it to sign messages to prove that we possess it.

You can sign and verify a message with a bech32 address using Electrum. The Core implementation will use 3 addresses by default but also supports bech32 so should also be able to do this. I'm not sure what advantage there is in being able to sign a message from the underlying legacy address to '3' Segwit address if that is what you trying to achieve.

I'm aware of the fact that it breaches the code of anonymity for which bitcoin was created, but isn't it true that when we try to send all the funds in our wallet, it shows all the addresses in the list of the transaction when they are sent to one or more addresses?

If a transaction contains input from more than one address then it can be concluded that the addresses are in the same wallet, but I'm not sure how that is relevant to this.

[Stedsm]

I'm aware of the fact that it breaches the code of anonymity for which bitcoin was created, but isn't it true that when we try to send all the funds in our wallet, it shows all the addresses in the list of the transaction when they are sent to one or more addresses?

If a transaction contains input from more than one address then it can be concluded that the addresses are in the same wallet, but I'm not sure how that is relevant to this.

I said that for my current bech32 addresses, that if I receive coins on different (bech32) addresses and all of them are in the same wallet:
Let's say 'A' address receives 0.03 BTC
'B' address receives 0.02 BTC
'C' address receives 0.05 BTC,
And if I am interested in sending the whole 0.1 BTC to someone in a single transaction, won't these addresses A, B & C will be included in that transaction and shown in the list?

On a quick note, I would like to know that if it's possible to get SegWit addresses starting with '3' with our Legacy addresses' privkey, can't we use these privkeys to get bech32 addresses that are (maybe) connected to our Legacy addresses? Correct me if I'm wrong somewhere with the question here.

[TheQuin]

I said that for my current bech32 addresses, that if I receive coins on different (bech32) addresses and all of them are in the same wallet:
Let's say 'A' address receives 0.03 BTC
'B' address receives 0.02 BTC
'C' address receives 0.05 BTC,
And if I am interested in sending the whole 0.1 BTC to someone in a single transaction, won't these addresses A, B & C will be included in that transaction and shown in the list?

Yes, that's what I was saying. It's a privacy issue and there are ways of combatting it such as in Electrum you can create as many wallets as you want and then use each one for different purposes. Then use a service like ChipMixer to further distance yourself from the source of the coins before combining them.

On a quick note, I would like to know that if it's possible to get SegWit addresses starting with '3' with our Legacy addresses' privkey, can't we use these privkeys to get bech32 addresses that are (maybe) connected to our Legacy addresses? Correct me if I'm wrong somewhere with the question here.

I'm not 100% sure here but I think the answer is no. Before I go trying to look that up I'm still completely baffled as to what you are trying to achieve and maybe if you could explain that I might get it.

[Stedsm]

On a quick note, I would like to know that if it's possible to get SegWit addresses starting with '3' with our Legacy addresses' privkey, can't we use these privkeys to get bech32 addresses that are (maybe) connected to our Legacy addresses? Correct me if I'm wrong somewhere with the question here.

I'm not 100% sure here but I think the answer is no. Before I go trying to look that up I'm still completely baffled as to what you are trying to achieve and maybe if you could explain that I might get it.

I want to know that if Legacy address' privkey has SegWit address connected with it and it can get me a SegWit address starting with '3', didn't the SegWit devs make it possible to get a bech32 address too with that privkey? Or is there anything I'm currently unaware of?

[TheQuin]

I want to know that if Legacy address' privkey has SegWit address connected with it and it can get me a SegWit address starting with '3', didn't the SegWit devs make it possible to get a bech32 address too with that privkey? Or is there anything I'm currently unaware of?

That's sort of why I'm guessing you can't. I also seem to remember when I first upgraded to Electrum 3.0.0 and created my first Segwit wallet seeing a warning somewhere that it would not be possible to import these private keys into other wallet types.

That still leaves me wondering why anyone would want to use the same private key to generate different addresses. I cannot see any application that would benefit from that and it sets alarm bells off that it could make things less secure.


Edit: I've been thinking about it and I think this explains it but people with better technical knowledge may be able to answer it more fully.

A private key creates a legacy address. The 3 Segwit address is created from the legacy address, not from the private key. They are not meant to be associated, the Segwit address is just nested in the legacy address.
Another private key creates a bech32 address and that's all as it is native and doesn't need to be nested in anything.

Let's try this again. As I've only been learning about Segwit a couple of months this took a while to work out.

A legacy addresses private key doesn't have a Segwit address associated with it. The Segwit implementation using the 3 addresses is nesting Segwit in the old legacy address. That address is not intended to be used for anything else. It was only done this way as a tempory solution to provide backward compatibility of the address format (base58).

The native implementation of Segwit using bech32 addresses does not require any other address to make it work.

The devs didn't make it possible to do what you asking because there is no reason to.