ERROR Electrum Addresses

[SuperInvestor]

hello anyone can tell me why  this is my btc addresses? http://prntscr.com/m199ht is it really like that?? i taught it should start with 3 or 1 .... pls help me how to change that

[OmegaStarScream]

It's a SegWit wallet (bec32 addresses). There is no nothing wrong with your wallet. If whoever you gave your address to can't send funds, you can always make a new wallet and choose "standard" instead of "SegWit" as the screenshot below shows:

[SuperInvestor]

can i change this? instead of creating new..

[Abdussamad]

no you have to create a new wallet. start via file menu > new/restore, enter a unique filename for the new wallet file and click next. proceed as per on-screen instructions. make sure you have a pen and paper handy to write down the seed.

[MrMoores]

Is there any way of validating the currently installed version of Electrum to determine autheticity?

[Abdussamad]

if you have the original download file you can check the gpg sig.

[bob123]

can i change this? instead of creating new..

Is there a reason you don't want to use segwit ?

Segwit introduced quite a few advantages (such as smaller size of transactions which result in lower fees).

It doesn't only help you to save on fees, it also reduces the complete network load, which results in a more healthy network.
Additionally it paves the way to HTLC's (basically lightning network).


It has also things fixed (e.g. transaction malleability) compared to the legacy format.


I can't think of a single reason to not use bech32 (segwit, ḅc1.. addresses).

[Abdussamad]

I can't think of a single reason to not use bech32 (segwit, ḅc1.. addresses).

Most exchanges don't support bech32 addresses so people have difficulty withdrawing to their wallets.

[HCP]

I can't think of a single reason to not use bech32 (segwit, ḅc1.. addresses).

Most exchanges don't support bech32 addresses so people have difficulty withdrawing to their wallets.

Pretty much this is the biggest reason preventing widespread implementation of bech32. Lack of support.

It is a catch-22 situation... users won't use it until services support it... services won't support it until users are "demanding" it.


For now, you can get the best of both worlds, universal address support and segwit benefits by using the nested segwit (P2SH-P2WPKH) "3" type addresses

[pooya87]

~
For now, you can get the best of both worlds, universal address support and segwit benefits by using the nested segwit (P2SH-P2WPKH) "3" type addresses

nested SegWit or P2SH-P2WPKH is a workaround and like any other workarounds it is not the best option in my opinion. specially because you would be wasting a lot of space by using a script hash method and including an extra hash inside your scriptsig field whereas it would have been empty if you used SegWit or P2WPKH.