Topic: Mycelium Bitcoin Wallet - page 100. (Read 586368 times)

Maybe instead of putting the sign option as an address option, add it as a menu option (like cold storage) and then you can choose an address or to scan, etc. Also, not sure if you noticed the new samsung discovery of a backdoor/feature. I personalky use a galaxy, and was concerned enough to move it onto my computer for a bit. Can you advise on that?

yes. this makes a lot of sense. it is just a question of how to integrate it in the UI.

Thanks Jan, that makes sense - I think BitcoinAverage would be more than enough for my needs (I just like extra options to play with )

One more thing: I had the chance to use message signing for the first time the other day, and it got me thinking - it's currently only possible to do this for keys that are stored on the device - would it be possible to integrate this feature with the cold storage spending functionality, so that we can sign messages on an ad-hoc basis, without needing to fully import the private key?

Fees are a quick fix, so should be out soon after 0.9. Merchant protocol will take a while longer. BIP32 HD wallets are more important

Is Mycelium ready for the changes coming with 0.90? I expect we should have support for lower fees cery soon after official release and support for payment requests later on?

Did you record him on a camera?
It would be nice to see what he was telling to you.

regards!

Thank you Rassah for taking the time at the Texas Conference to sit down with us and answer several questions about using Mycelium.

We will be doing some small workshops in our town for small businesses about using bitcoin and the time spent with you was very helpful.

 

Thanks for the clarification. Much appreciated!

Compressed and uncompressed form of the same public key correspond to different Bitcoin addresses.  They have individual balances and behave like independent addresses.  They just happen to have the same private key which can be used to spend coins from each of them.


Private key representations usually include a flag to indicate whether the key is meant to be used with a compressed public key or uncompressed one.  I believe if you set that flag to 'uncompressed', Mycelium will attach it to the other address.


Yes.


I don't think there is such a thing as a "private key's balance".

If you want to use both compressed and uncompressed public keys, I think you can load your private key twice with different flags and Mycelium should do the right thing then.  Mathematically these private keys are identical, but logically they are different.


I don't know BIP38, unfortunately.  The SIPA format for private keys includes the compression flag.  It was either the loss of information (flag) during private key transfer to the dedicated device, or a failure of the app on that device to interpret that flag correctly, that created such situation.

I would personally love the ability to set your own fee, since this can be done safely if you know what you are doing (txn priority and so forth). I would definitely hide it behind an "expert" mode, though.

I've run into a situation where Mycelium was monitoring two public keys - one the compressed version of the other. It showed a positive balance for the the compressed public key and a zero balance for the normal public key.

I loaded the private key to see if it was required for Mycelium to recognize that the two public keys are for the same private key, but it simply attached it to the compressed public key. The uncompressed one remained observer only (no private key associated) and still with a zero balance.

Questions:
- Is it mathematically possible to calculate the compressed public key from the uncompressed one (and visa-versa) in the absence of the private key? (I assume if you have the private key they can theoretically be associated since you can calculate each from the private key.)

- Is it possible to make one of the two forms the canonical form internally so that loading either into Mycelium causes the correct private key's balance to be tracked?


Background: I ended up with a compressed version of the public key when I loaded a BIP38 protected key into the app on a dedicated device separate from my phone. I then transferred some coin to it.
I had been monitoring the full public key on my regular phone and it failed to show the new balance. I then loaded the compressed key to my phone and ended up with the situation described.

Right now the fee in default Bitcoin-QT nodes is hardcoded to 0.0001BTC, so setting it lower runs the risk of your transaction not being broadcast. We will lower the fee once 0.9 comes out, which will drop the fee further.

It would be really nice if the user could set the tx fee to 0 or lower than 0.0001.
For most Transactions 0.00001 or 0.000001 BTC fee would be enough. So it would be nice to set the fee at the users own wishes.

BTW: I really like the App.. especially the function to spend btc directly from a cold / paper wallet.. good job guys.

Thanks.

We have started adding rates from sources that are not actual exchanges such as Coinbase and BitPay.
Many users have requested this as it allows them to see what their coins are worth when buying at for instance Coinbase or spending at a BitPay enabled merchant. Since these sources do not have a volume associated we cannot really calculate a weighted average.

In the testnet version (released 2 days ago) we have added BitcoinAverage. They make a business out of monitoring and selecting relevant exchange sources, and we believe that they track the markets closer than the Mycelium developers.

The default choice is right now Bitstamp, and it is up to the user to select a source that he/she finds valuable and trustworthy.

I'd also like to see this feature brought back, and if possible, add the ability to customize which of the exchanges count towards this average. Also, are there any plans to add multi-send to the wallet?

Thanks for all your hard work, Mycelium makes it a pleasure to use Bitcoin - you guys are on the forefront of wallet software development - never stop innovating! 

that depends on your paranoia level. i'd say it is cold enough.
since i don't know anything about root exploits of that dumb smartphone, be sure to ONLY install mycelium.

Would it be considered "unsafe" to test a cold wallet address (properly generated, live USB, BIP 38, dumb printer etc.) with the Mycelium cold storage spending function. All this on a dumb smartphone (factory reset, not connected to GSM network, just connected to wpa2 secure wifi to D/L mycelium to make the test spend)

Or should I be more paranoid and this address should be considered not "cold" anymore by having touched breifly the network? And using Armory is the only solution ?

Imagine a die like a magic 8 ball, except the die is a cube, and on each side there is a seperate container for a magic 8 ball type liquid filled chamber with another die inside of it, making a 36 sided die.

What about cat generated passwords? I'd trust my little fellow* more than any human


*no, it isn't that in the pic

Of course, that's pretty obvious. Have some faith in me