Mycelium Bitcoin Wallet

[Jebus]

Having a bit of an issue or maybe I just don't understand something. I'm using Mycelium beta 0.8.5 and it shows my regular balance 2.08+ but my spendable = 0 The incoming btc shows in my transaction history on 2 deposits. One with 264 Confirmations and one with 104 confirmations. Do I need to wait for a specific number of conf before these become spendable or am I doing something wrong?

I assume that when you say spendable = 0 then it is the number shown when clicking Send followed by clicking Enter Amount.

I think that you have imported a bitcoin address (without a key) which is a read-only wallet.
In this case the wallet displays the balance of the address on the main view (the sum of the balances of all your addresses).
When it comes to spending it only shows the spendable amount in your wallet, (the sum of the balances of all your private keys).

Let me know whether that was helpful.

Ahhh you are correct. I remember when I tried to import that address it only read the public key and I either didn't see or it didn't give me the option to import that private key. I wanted to take a key from my myc wallet on an old phone and move it to my new phone. When looking at key management I didn't see any indication that this particular key was read only. Throwing something like that in there might keep dummies like me from wasting your time. Thanks for the response. Overall I really like the myc wallet. Simple to use, light weight, stylish. Great work and thanks again.

***edit*** Oh, that must be what that giant key icon next to the address means. I'm such a twat. Sorry again. I've got it all sorted out now. I just entered the private key and it updated the key to full blown spendable while simultaneously downgrading me to Derp - 1.

[1715376343]

1715376343

[1715376343]

1715376343

[Jan]

Having a bit of an issue or maybe I just don't understand something. I'm using Mycelium beta 0.8.5 and it shows my regular balance 2.08+ but my spendable = 0 The incoming btc shows in my transaction history on 2 deposits. One with 264 Confirmations and one with 104 confirmations. Do I need to wait for a specific number of conf before these become spendable or am I doing something wrong?

I assume that when you say spendable = 0 then it is the number shown when clicking Send followed by clicking Enter Amount.

I think that you have imported a bitcoin address (without a key) which is a read-only wallet.
In this case the wallet displays the balance of the address on the main view (the sum of the balances of all your addresses).
When it comes to spending it only shows the spendable amount in your wallet, (the sum of the balances of all your private keys).

Let me know whether that was helpful.

Ahhh you are correct. I remember when I tried to import that address it only read the public key and I either didn't see or it didn't give me the option to import that private key. I wanted to take a key from my myc wallet on an old phone and move it to my new phone. When looking at key management I didn't see any indication that this particular key was read only. Throwing something like that in there might keep dummies like me from wasting your time. Thanks for the response. Overall I really like the myc wallet. Simple to use, light weight, stylish. Great work and thanks again.

***edit*** Oh, that must be what that giant key icon next to the address means. I'm such a twat. Sorry again. I've got it all sorted out now. I just entered the private key and it updated the key to full blown spendable while simultaneously downgrading me to Derp - 1.

This is very valuable input. I am certain that you will not be the only one who gets confused about this.
Andreas is currently working on re-making the UI to a more modern layout (I really suck at UI). One of the changes will be to use "cards" for keys. Each key/address will have a card that shows it's properties, and maybe we should really point out what is read-only and what is not, rather than having a key icon on the side.

[Newar]

Bug report (0.8.5):

I have four addresses in my wallet, of which one is watch-only.

In the main view the second address (not the watch-only address) shows a very, very small QR code unlike the others. Also if I tap that second address it does not show the dimming QR code like the others. Instead it shows the Android "Share with..." dialog.

[apetersson]

Bug report (0.8.5):

I have four addresses in my wallet, of which one is watch-only.

In the main view the second address (not the watch-only address) shows a very, very small QR code unlike the others. Also if I tap that second address it does not show the dimming QR code like the others. Instead it shows the Android "Share with..." dialog.

i know that the qr code size is not consistent across phones. we should find a more generic solution here.
but in order to verify the fix i need to reproduce it first - which model are you on?

[Jan]

Bug report (0.8.5):

I have four addresses in my wallet, of which one is watch-only.

In the main view the second address (not the watch-only address) shows a very, very small QR code unlike the others. Also if I tap that second address it does not show the dimming QR code like the others. Instead it shows the Android "Share with..." dialog.

My guess is that you have a long label for that address. If the display is small enough and the label long enough, then the QR code will shrink to make the label fit, and eventually disappear entirely if the label is too long. Does this fit with your observations?

[Newar]

Bug report (0.8.5):

I have four addresses in my wallet, of which one is watch-only.

In the main view the second address (not the watch-only address) shows a very, very small QR code unlike the others. Also if I tap that second address it does not show the dimming QR code like the others. Instead it shows the Android "Share with..." dialog.

My guess is that you have a long label for that address. If the display is small enough and the label long enough, then the QR code will shrink to make the label fit, and eventually disappear entirely if the label is too long. Does this fit with your observations?

You are correct. The label for that address is quite a bit longer than the others. But why the different behaviour when tapping on the address?

which model are you on?

It's a Galaxy Grand: http://www.samsung.com/ph/consumer/mobile-devices/smartphones/android/GT-I9082EWAXTC

[Jan]

Bug report (0.8.5):

I have four addresses in my wallet, of which one is watch-only.

In the main view the second address (not the watch-only address) shows a very, very small QR code unlike the others. Also if I tap that second address it does not show the dimming QR code like the others. Instead it shows the Android "Share with..." dialog.

My guess is that you have a long label for that address. If the display is small enough and the label long enough, then the QR code will shrink to make the label fit, and eventually disappear entirely if the label is too long. Does this fit with your observations?

You are correct. The label for that address is quite a bit longer than the others. But why the different behaviour when tapping on the address?

When you tap the text address it always shows the "Share with..." dialog. When you tap the QR code it always displays it large.
Since the label is shown together with the address the bounding box for opening the share dialog gets large when the label is large. However, we could make the bounding box be only on the text address.

[Abdussamad]

The wallet creates additional keys::
1. When it has no keys at all (first startup or when you delete the last key it has)
2. When you ask it to by going into Key Management, click + and select Create

Mycelium tracks the origin of the keys it manages in it's key metadata. So it known whether a key was imported or created. Going forward we will visualize whether the wallet thinks that you have a backup of a key, and give users a friendly reminder if they have funds on a key which has not yet been backed up. By combining this with proven import (import verification) we will have something really powerful.

Thanks for the clarification.

What about change addresses? Are separate addresses used for change or does it send change back to the originating address?

[apetersson]

right now it choses one of the originating addresses for change.

this is to avoid having to backup new keys just because you are sending something. in the future this might change significantly, tough.

[Jan]

right now it choses one of the originating addresses for change.

this is to avoid having to backup new keys just because you are sending something. in the future this might change significantly, tough.

Adding to Andreas' answer: the address that contributes the highest total input value is used as the change address.

[Abdussamad]

Thanks for the answers.

[visdude]

I have Orbot on my device.  In order for Mycelium to connect through the Tor network, what should I enter in the "Socks Proxy" field in Settings --  "localhost:9050" or "127.0.0.1:9050"...?

Edit:  Also, is there an indicator or a way to verify that Mycelium is indeed connected to the Tor network?

[apetersson]

I have Orbot on my device.  In order for Mycelium to connect through the Tor network, what should I enter in the "Socks Proxy" field in Settings --  "localhost:9050" or "127.0.0.1:9050"...?

Edit:  Also, is there an indicator or a way to verify that Mycelium is indeed connected to the Tor network?

"localhost:9050" or "127.0.0.1:9050" both are possible, but i would prefer the localhost variant.

the easiest way to validate this is to run an app like "OS monitor" that shows all active sockets. you should be able to identify the mycelium process and to what IP it connects. if connected through orbot, it should show

of course, have a look at the source code, too. everything is published on github for a reason

and yes, we could also run a tor hidden service but we are not there yet

[visdude]

I have Orbot on my device.  In order for Mycelium to connect through the Tor network, what should I enter in the "Socks Proxy" field in Settings --  "localhost:9050" or "127.0.0.1:9050"...?

Edit:  Also, is there an indicator or a way to verify that Mycelium is indeed connected to the Tor network?

"localhost:9050" or "127.0.0.1:9050" both are possible, but i would prefer the localhost variant.

the easiest way to validate this is to run an app like "OS monitor" that shows all active sockets. you should be able to identify the mycelium process and to what IP it connects. if connected through orbot, it should show

of course, have a look at the source code, too. everything is published on github for a reason

and yes, we could also run a tor hidden service but we are not there yet

Thank you for the clarification.

I prefer to leave the coding stuff to the folks who are way smarter than me.  Otherwise, I'd smell my own brain burning.  

[visdude]

Is the miner/tranx fee in Mycelium determined by the network or is it hard-coded at .0001 btc?  Is it possible to make this amount a user-defined option in future releases?

Another cool feature to have (I think) is the option to be able to input the fiat amount to be converted to btc when sending.

[Jan]

Is the miner/tranx fee in Mycelium determined by the network or is it hard-coded at .0001 btc?  Is it possible to make this amount a user-defined option in future releases?

Another cool feature to have (I think) is the option to be able to input the fiat amount to be converted to btc when sending.

Fee
The fee is calculated to be 0.0001 for each 1000 bytes of transaction size. This way the fee matches the minimum relay fee enforced by bitcoin nodes. If you go below that you risk that your transaction gets stuck in the network and never confirms. If we allow users to go below that, and blame it on us when their transactions get stuck.
However, adding a larger fee may me desirable if you want faster confirmations, especially once the number of transactions start hitting the 1 MB block limit. Here is my thinking about how dynamic fees could be achieved: https://bitcointalk.org/index.php?topic=166302.0

Sending Fiat
It is already there. When you enter the amount to send there is a blue BTC button at the top right. Clicking it converts to your selected local fiat currency (in settings) and uses the exchange rate from your selected exchange (in settings).

[visdude]

Is the miner/tranx fee in Mycelium determined by the network or is it hard-coded at .0001 btc?  Is it possible to make this amount a user-defined option in future releases?

Another cool feature to have (I think) is the option to be able to input the fiat amount to be converted to btc when sending.

Fee
The fee is calculated to be 0.0001 for each 1000 bytes of transaction size. This way the fee matches the minimum relay fee enforced by bitcoin nodes. If you go below that you risk that your transaction gets stuck in the network and never confirms. If we allow users to go below that, and blame it on us when their transactions get stuck.
However, adding a larger fee may me desirable if you want faster confirmations, especially once the number of transactions start hitting the 1 MB block limit. Here is my thinking about how dynamic fees could be achieved: https://bitcointalk.org/index.php?topic=166302.0

Sending Fiat
It is already there. When you enter the amount to send there is a blue BTC button at the top right. Clicking it converts to your selected local fiat currency (in settings) and uses the exchange rate from your selected exchange (in settings).

Yes, it would be for having the flexibility to increase the fee from the default minimum of 0.0001 for faster confirmation when needed.

I got it!  Thanks a lot.

[apetersson]

Yes, it would be for having the flexibility to increase the fee from the default minimum of 0.0001 for faster confirmation when needed.
I got it!  Thanks a lot.

in practice, i have noticed all mycelium wallet transactions were included in the next block with the suggested fee of 0.1 mBTC - do you have any txid where this was not the case?

[visdude]

Yes, it would be for having the flexibility to increase the fee from the default minimum of 0.0001 for faster confirmation when needed.
I got it!  Thanks a lot.

in practice, i have noticed all mycelium wallet transactions were included in the next block with the suggested fee of 0.1 mBTC - do you have any txid where this was not the case?

None really.  I was just trying to familiarize myself with it and did a transfer to test it out and indeed, a 0.0001 btc tranx fee was suggested and it was fine.  I was just wondering if an option to increase the default suggested fee would be possible for more flexibility.

[Rassah]

Will Mycelium be implementing HD wallets, or the new payment protocol, any time soon?