Mycelium Bitcoin Wallet

[adamas]

thanks guys,

so as for my queries, is this going to effect the way I transact now as well as transact from my cold storage, I really do not want to mess around with different change addresses, I just do not want to know about it and I want to use the same address as I do now. I also want to keep 1 Cold Storage backup and not keep changing my backup every single time I make a simple transaction from it.

In that case, after the 2.0 upgrade, you should just keep using your existing (legacy accounts) and cold storage spending.

Sorry, but I don't understand it, could you make it a bit clear. Thanks

[1715550349]

1715550349

[1715550349]

1715550349

[1715550349]

1715550349

[Jan]

thanks guys,

so as for my queries, is this going to effect the way I transact now as well as transact from my cold storage, I really do not want to mess around with different change addresses, I just do not want to know about it and I want to use the same address as I do now. I also want to keep 1 Cold Storage backup and not keep changing my backup every single time I make a simple transaction from it.

In that case, after the 2.0 upgrade, you should just keep using your existing (legacy accounts) and cold storage spending.

Sorry, but I don't understand it, could you make it a bit clear. Thanks

With the current version of Mycelium you can go to the Keys tab and see the addresses you are working on. Some of those addresses have a key associated with them, they are the ones you can spend from. The ones without a key are so called read-only addresses, you can monitor them but not spend from them.

With Mycelium 2.0 the Keys tab is renamed to Accounts. All your existing keys/addresses are now called accounts and work like before. Those are the ones I call legacy accounts.

In addition you will have one or more Hierarchal Deterministic  (HD) accounts following the BIP32/BIP44 standard. An HD account is one that automatically generates new addresses as you use the wallet for sending and receiving. This means that you get much more anonymous (today anyone who knows your Mycelium bitcoin address can see all transactions associated with it).
Furthermore, because we now have BIP32 support this means that one backup of one secret is enough to generate all the private keys/addresses you will ever need for all the HD accounts you will ever need. Everything can be deterministically generated from one secret. The backup mechanism we use follows the BIP39 standard, and basically involves that you write down 12 random words on paper.

As a user you will not have to worry about all of those addresses, they are managed internally.


Today Mycelium lets you monitor 20 separate bitcoin addresses. For some of those addresses you also have a key (the default), which lets you spend from them

[gtraah]

thanks guys,

so as for my queries, is this going to effect the way I transact now as well as transact from my cold storage, I really do not want to mess around with different change addresses, I just do not want to know about it and I want to use the same address as I do now. I also want to keep 1 Cold Storage backup and not keep changing my backup every single time I make a simple transaction from it.

In that case, after the 2.0 upgrade, you should just keep using your existing (legacy accounts) and cold storage spending.

Sorry, but I don't understand it, could you make it a bit clear. Thanks

With the current version of Mycelium you can go to the Keys tab and see the addresses you are working on. Some of those addresses have a key associated with them, they are the ones you can spend from. The ones without a key are so called read-only addresses, you can monitor them but not spend from them.

With Mycelium 2.0 the Keys tab is renamed to Accounts. All your existing keys/addresses are now called accounts and work like before. Those are the ones I call legacy accounts.

In addition you will have one or more Hierarchal Deterministic  (HD) accounts following the BIP32/BIP44 standard. An HD account is one that automatically generates new addresses as you use the wallet for sending and receiving. This means that you get much more anonymous (today anyone who knows your Mycelium bitcoin address can see all transactions associated with it).
Furthermore, because we now have BIP32 support this means that one backup of one secret is enough to generate all the private keys/addresses you will ever need for all the HD accounts you will ever need. Everything can be deterministically generated from one secret. The backup mechanism we use follows the BIP39 standard, and basically involves that you write down 12 random words on paper.

As a user you will not have to worry about all of those addresses, they are managed internally.


Today Mycelium lets you monitor 20 separate bitcoin addresses. For some of those addresses you also have a key (the default), which lets you spend from them

Great So what your saying is the old way will not disappear, I will be able to choose ?
Lets just say I want to make a new account can I make it like a legacy ? And how will I be able to make another legacy type account with Mycelium 2.0, I assume there are options for this? Or are you saying that ANY new account created from M-2.0 will be HD and will transact in the NEW style?
If this is the case does this mean I will never be able to make another legacy account with M-2.0 other than my old account from previous  version of mycelium meaning I will have to make it outside of M-2.0 and then import it? Thanks for clarification

I mean who knows when I feel comfortable I may jump to HD, but its still great to have a choice.

[Jan]

...

With the current version of Mycelium you can go to the Keys tab and see the addresses you are working on. Some of those addresses have a key associated with them, they are the ones you can spend from. The ones without a key are so called read-only addresses, you can monitor them but not spend from them.

With Mycelium 2.0 the Keys tab is renamed to Accounts. All your existing keys/addresses are now called accounts and work like before. Those are the ones I call legacy accounts.

In addition you will have one or more Hierarchal Deterministic  (HD) accounts following the BIP32/BIP44 standard. An HD account is one that automatically generates new addresses as you use the wallet for sending and receiving. This means that you get much more anonymous (today anyone who knows your Mycelium bitcoin address can see all transactions associated with it).
Furthermore, because we now have BIP32 support this means that one backup of one secret is enough to generate all the private keys/addresses you will ever need for all the HD accounts you will ever need. Everything can be deterministically generated from one secret. The backup mechanism we use follows the BIP39 standard, and basically involves that you write down 12 random words on paper.

As a user you will not have to worry about all of those addresses, they are managed internally.


Today Mycelium lets you monitor 20 separate bitcoin addresses. For some of those addresses you also have a key (the default), which lets you spend from them

Great So what your saying is the old way will not disappear, I will be able to choose ?
Lets just say I want to make a new account can I make it like a legacy ? And how will I be able to make another legacy type account with Mycelium 2.0, I assume there are options for this? Or are you saying that ANY new account created from M-2.0 will be HD and will transact in the NEW style?
If this is the case does this mean I will never be able to make another legacy account with M-2.0 other than my old account from previous  version of mycelium meaning I will have to make it outside of M-2.0 and then import it? Thanks for clarification

I mean who knows when I feel comfortable I may jump to HD, but its still great to have a choice.

Correct, you have a choice.
But, the wallet will no longer let you create new random legacy accounts (create a new random key), you can however import a private key that you have made elsewhere by selecting Advanced when creating a new account. In that scenario we expect the user to know what he does and that he has the private key stored safely outside the wallet. It will not be part of the HD account backup.

We really wish our users to be safe and not loose funds because they sent funds to a key that they cannot recover.

You should really try it out. Everything is available for the testnet, where you can play around with worthless testnet coins: https://play.google.com/store/apps/details?id=com.mycelium.testnetwallet
Once you have it installed you can get free testnet coins by "buying" them  (for free) from Virtual Trader when you click Buy / Sell Bitcoins

[gtraah]

great I now understand it all, If I want to use the old way, simply goto bitcoinaddress.org create a standard address make a backup , then import it into mycelium AWESOME.

AHHH so this is how i get test coins I was wondering how to get these coins as I do have the testnet installed on my s5

------------------------------------------------------------------

By the way the NFC chip offline signing is an awesome idea, you may like to check this out

https://bitcointalk.org/index.php?topic=610453.0

[KLmoney]

I realise that one of the “philosophies” behind the Mycelium 2.0 wallet is to take users away from managing addresses. The UI as it stands basically requires users to use receiving addresses in sequence as they are offered up.

However, with the availability of BIP32/39/44 key/address generators, it is easy to generate forward addresses online/offline using our 12 word mnemonic code with or without password. For a particular Account, a user might want to generate receiving addresses, say, 1 to 10 and give them out to one party who is going to make regular payments to him. I have tried simulating something like this with the testnet version and everything seems fine.

1) Are there any issues with using 2.0 in this way?
2) Could future versions of Mycelium offer the option to generate forward addresses within the application?
3) How far out in a chain, over unused addresses, does 2.0 scan to look for funds?

[Jan]

I realise that one of the “philosophies” behind the Mycelium 2.0 wallet is to take users away from managing addresses. The UI as it stands basically requires users to use receiving addresses in sequence as they are offered up.

However, with the availability of BIP32/39/44 key/address generators, it is easy to generate forward addresses online/offline using our 12 word mnemonic code with or without password. For a particular Account, a user might want to generate receiving addresses, say, 1 to 10 and give them out to one party who is going to make regular payments to him. I have tried simulating something like this with the testnet version and everything seems fine.

1) Are there any issues with using 2.0 in this way?
2) Could future versions of Mycelium offer the option to generate forward addresses within the application?
3) How far out in a chain, over unused addresses, does 2.0 scan to look for funds?

1. No issues. This is perfectly fine.
2. Yes
3. We scan 20 address ahead on the external chain to comply with account lookahead discovery as dictated by BIP44

[KLmoney]

Thanks for your reply Jan.

[anarchoatheist]

thanks guys,

so as for my queries, is this going to effect the way I transact now as well as transact from my cold storage, I really do not want to mess around with different change addresses, I just do not want to know about it and I want to use the same address as I do now. I also want to keep 1 Cold Storage backup and not keep changing my backup every single time I make a simple transaction from it.

Trust me, you are definitely gonna want to switch to the HD wallet once you get used to it. It is comparable to using an old rotary telephone, when a Samsung galaxy note 4 is available for you to use.

[Newar]

This question is sort of off topic as I don't think the problem is with Mycelium, but maybe you can offer some insight.

If I scan a bitcoin address from Mycelium using QtQR (a QR code reader / generator for Linux) I get as expected for example:
bitcoin:1KYk5DezaCQKui6RrqLPhBqS6PdSAgRpeB

If I have QtQR encoding the exact same string (as "text") and scan from Mycelium, I get an error "Unrecognized format". The codes also differ visually, but that could be due to different error correction.

Or is there something else that needs to be added (uri=)?

[trasla]

I remember we had some errors with tools putting byte order marks into strings when generating QR codes, could be something like that. (Though the case where we got to know about it, we made sure to read those anyway.) There is nothing wrong with the address, if I turn that into a QR code with Wolfram Alpha, I can perfectly scan it with mycelium. Could you maybe provide the QR code which causes the error (link, or send to developers@mycelium.com)?

[Newar]

[...] Could you maybe provide the QR code which causes the error (link, or send to developers@mycelium.com)?

Sure, should have thought of that :-/

Output from QtQR that does not work:

http://i59.tinypic.com/72ftzr.png

This is what it looks like in Mycelium:

http://i59.tinypic.com/111p0yv.png

When I scan these with the Barcode Scanner app, they both return the same string. The upper has low error correction and the Mycelium one has medium error correction, but other than that I can not spot a difference.

As far as I can tell QtQR uses this to encode: https://bazaar.launchpad.net/~david4dev/qr-code-creator/trunk/view/head:/qr.py

[trasla]

Yes, the QtQR code includes a zero-width non-breaking space as first character, I made a fix to remove this character from scan results if necessary.
It works now for me, and will work for you with the next release as well

[Newar]

Yes, the QtQR code includes a zero-width non-breaking space as first character, I made a fix to remove this character from scan results if necessary.
It works now for me, and will work for you with the next release as well

Great! Thank you!

[OnkelPaul]

Yes, the QtQR code includes a zero-width non-breaking space as first character, I made a fix to remove this character from scan results if necessary.
It works now for me, and will work for you with the next release as well

Sounds like the generated QR code is slightly non-spec-compliant. It should contain only the URL characters, not invisible spaces or other weird stuff.
Of course, handling off-spec data robustly is good, but you can only work around so many errors...

Onkel Paul

[msx]

Yes, the QtQR code includes a zero-width non-breaking space as first character, I made a fix to remove this character from scan results if necessary.
It works now for me, and will work for you with the next release as well

Some text editors (notably, Notepad under Windows, but I guess Linux might have that kind of thing too) insert BOM characters into text files to indicate that the content is in unicode, type of unicode encoding, byte order etc.

I imagine it can be entirely possible that it was not QtQR who inserted that BOM (zero-width space).

I wouldn't include a fix for that.  What if next thing someone types a URI in MS Word?

[Rassah]

Mycelium 2.0 RC1 has been pushed to the play store for everyone in the beta channel, and will be available for upgrade in an hour or two.
Please give us feedback over the next week so we can improve before the global launch.

New Features
 - Support for BIP32/BIP44 compliant HD accounts based on a single master seed
 - Setter security through one-time wordlist-backup (BIP39)
 - Better anonymity, no more address reuse
 - Ability to label transactions
 - Create transactions with poor or no internet connectivity for later broadcasting
 - No more restrictions to the number of watch only addresses

More info here https://plus.google.com/u/0/+JanM%C3%B8ller/posts/bF7yhyDHTfW

P.S. To be eligible for testing you need to join the g+ group at https://plus.google.com/communities/102264813364583686576  After joining, you need to explicitly enable beta versions for the software at https://play.google.com/apps/testing/com.mycelium.wallet

[RustyNomad]

Your post just made my day... 

[Ruckus42]

Problem:

I'm trying to send 0.00619512 BTC. I have 0.28831103 BTC. Mycelium tells me I have "insufficient funds." 

[Rassah]

Problem:

I'm trying to send 0.00619512 BTC. I have 0.28831103 BTC. Mycelium tells me I have "insufficient funds." 

Make sure the funds have more than 0 confirmations (swipe to the right and check that the topmost transaction has some confirmations), and that you are not spending from a watch only address.