Mycelium now has full Segwit support

[gentlemand]

Mycelium has now gone full Segwit including bech32. When it updated it said something about certain seeds not being able to migrate to a Segwit set up. Dunno what that means. Mine crossed over just fine and it's a pretty old seed. You can switch between legacy, p2sh and bech32 to receive and send.

Now I don't have to justify my sentimental attachment to it any more.

[BitMaxz]

I think what they mean about the seeds is that old user with old seed will not be converted or transfer to new seeds that include both segwit and your old bitcoin addresses. So if you are planning to export the seed and import it to another wallet(like electrum) you can only recover the old addresses without segwit addresses.

Even though it still in beta version and we will expect more improve about the segwit to the wallet.

Honestly, this is one of my favorite mobile wallets before but since they don't support segwit I stopped using them but right now I'll be going to use it again until they clarify the seeds about segwit addresses.

[gentlemand]

I think what they mean about the seeds is that old user with old seed will not be converted or transfer to new seeds that include both segwit and your old bitcoin addresses. So if you are planning to export the seed and import it to another wallet(like electrum) you can only recover the old addresses without segwit addresses.

That makes sense.

I've only exported seeds to get my hands on forks, and Segwit seems to be problematic for that and forks are dead anyway so it makes no difference to me. Either I didn't read it properly or they could do with explaining it better. Someone might get a shock if they expect their Segwit coins to show up again.

[bL4nkcode]

You can switch between legacy, p2sh and bech32 to receive and send.
re.

Seems this is not working or just me? There's no option to switch back to legacy since one of my wallets was once in legacy only to p2sh and bech32.

[Rath_]

I have just installed Mycelium and I can't generate nested and native SegWit addresses. I can only see the default HD account. It would be a shame if I had to send some coins to a legacy address in order to convert the whole account to SegWit. I can't see SegWit related buttons anywhere. Does this update work with compatible hardware wallets? Can you access your Trezor's or Ledger's SegWit accounts? I guess I am going to stick with Samourai despite their strange decisions.

[bL4nkcode]

Earlier I just sent a small amount to one of my bech32 address from my segwit (P2SH) and the remaining amount in my p2sh address automatically transferred to segwit native (bech32). I wonder how it happened

Does this update work with compatible hardware wallets? Can you access your Trezor's or Ledger's SegWit accounts? I guess I am going to stick with Samourai despite their strange decisions.

Yeah, I just did. But never tried to sent any amount from ledger segwit account, I assumed it will do since it just connected.

[gentlemand]

That's the message you get with the update.

It's starting to sound like it's more trouble than it's worth to attempt to migrate your old account to this. I'll have to experiment a little with it before deciding.

[Rath_]

It looks like I had to sign up for the beta version in order to receive the update. Trezor T can't be used if the passphrase protection is turned on. Passphrase is being requested before the Trezor T asks user whether he wants to type it in on the host or on the device. However, I got it work to with my Trezor One. SegWit accounts are being displayed correctly and I was able to switch easily to bech32 addresses even though they aren't officially supported by Trezor in their web interface.

[HCP]

Earlier I just sent a small amount to one of my bech32 address from my segwit (P2SH) and the remaining amount in my p2sh address automatically transferred to segwit native (bech32). I wonder how it happened

How many UTXOs did you have in your original P2SH address? If you only had the one unspent output, then the whole thing would have needed to be spent even when sending "a small amount" and then I suspect what has happened is that Mycelium has returned your change to a bech32 change address... rather than creating a new P2SH change address (or returning the change to the original address).

[bL4nkcode]

Earlier I just sent a small amount to one of my bech32 address from my segwit (P2SH) and the remaining amount in my p2sh address automatically transferred to segwit native (bech32). I wonder how it happened

How many UTXOs did you have in your original P2SH address? If you only had the one unspent output, then the whole thing would have needed to be spent even when sending "a small amount" and then I suspect what has happened is that Mycelium has returned your change to a bech32 change address... rather than creating a new P2SH change address (or returning the change to the original address).

What I mean here is, when I send the small amount from p2sh (from imported private key) to some of my bech32 address, in the tx, mycelium returns my change to the bech32 address of the p2sh address and you're right. I know mycelium can automatically generate the p2sh to bech32 or vice versa but this thing doesn't mentioned in their update 

[Rath_]

I know mycelium can automatically generate the p2sh to bech32 or vice versa but this thing doesn't mentioned in their update  

Isn't it the "mixed spending" thing that was mentioned in the changelog? There would be nothing wrong with forcing you to use native SegWit address if all services were compatible with it. I wonder if forcing users to use bech32 addresses would result in services finally implementing support for them.

[bL4nkcode]

Isn't it the "mixed spending" thing that was mentioned in the changelog?

Ah, okay, maybe that was the reason, I didn't notice that one. So far, nothing to worry about the funds.

There would be nothing wrong with forcing you to use native SegWit address if all services were compatible with it. I wonder if forcing users to use bech32 addresses would result in services finally implementing support for them.

For mycelium users, yes that would be great and to some wallet also. The only missing thing is most explorer should support bech32 aside btc.com.

[Rath_]

The only missing thing is most explorer should support bech32 aside btc.com.

There are actually quite a lot of block explorers which support bech32 addresses. Blockbook, OXT, smartbit, blockchair, BlockCypher and more. They are not as popular as blockchain.com, but as you can see, there are many alternatives.

[bL4nkcode]

The only missing thing is most explorer should support bech32 aside btc.com.

There are actually quite a lot of block explorers which support bech32 addresses. Blockbook, OXT, smartbit, blockchair, BlockCypher and more. They are not as popular as blockchain.com, but as you can see, there are many alternatives.

I must be lazy without knowing these explorers are existing already. Thanks for indicating this btw.

[giszmo]

There would be nothing wrong with forcing you to use native SegWit address if all services were compatible with it. I wonder if forcing users to use bech32 addresses would result in services finally implementing support for them.

For mycelium users, yes that would be great and to some wallet also. The only missing thing is most explorer should support bech32 aside btc.com.

Mycelium will not force users to use bech32. bech32 is still not popular and has clear issues as for example the signing of messages is not yet well defined. If using bech32 puts you into a smaller anonymity set, it degrades your privacy. We opted to improve privacy instead by providing the mixed account feature, where you can seamlessly switch between address types.

[Rath_]

Mycelium will not force users to use bech32. bech32 is still not popular and has clear issues as for example the signing of messages is not yet well defined. If using bech32 puts you into a smaller anonymity set, it degrades your privacy. We opted to improve privacy instead by providing the mixed account feature, where you can seamlessly switch between address types.

Well, that's an interesting approach. Electrum has just released a software update in which bech32 addresses are the default ones. Users are obviously allowed to select a legacy type of addresses during the wallet setup but they can't switch between these two types (nested is only supported while importing the seed) without having to change currently opened wallet file. What will you do once SegWit becomes much more widely used?

[STT]

I'm way behind the story here but I thought Mycelium already supported segwit, the latest address my wallet has given to share is : 197bBbqV6yowtzax4ChWhyGBhxkMW87Mwc

So I guess I'm no longer fully compliant the big change is bech32 and I need to read up on advantages with that.   Time to update

Google telling me to read - https://bitcointalk.org/index.php?topic=2624630.msg26762627#msg26762627

[BitMaxz]

I'm way behind the story here but I thought Mycelium already supported segwit, the latest address my wallet has given to share is : 197bBbqV6yowtzax4ChWhyGBhxkMW87Mwc
~snip~

What version of mycelium you have? Seems my mycelium wallet working fine because I have 2 option to use both bench32 native and P2SH segwit compatible with different address start from "3" and "bc1"

I think you are using an old version of mycelium that is why your address still legacy wallet.

The big problem of Mycelium right now the syncing process takes longer if you didn't open it for how many weeks or months.

[AanotherUser]

Can you guide me with latest update where my single legacy address stopped observe and show me tx sent to similiar address but in SegWit format ("3"). Previously it was fine with displaying (like recieving too) both legacy and segwit balances under "one" account. And now it says that io have private key only for legacy format so i dont see and dont own these coins on "3"-address.

Thanks in advance.
D.C.

[HCP]

I can click the "receive" button and then choose the "address type". You should get 3 options in the dropdown...

Legacy (P2PKH)
SegWit compatible (P2SH)
SegWit native (Bech32)

Is your account from a Mycelium generated HD seed? Or was it imported individual private keys?