Bug report: When attempting to send from this address: https://blockchain.info/address/1K3bMZ7SvkzoGZTYD5EpYPKbN8PPQKqidGwhich currently contains 2.48345024 BTC and hitting the "max" button to send everything it will only allow me to send 1.91515024 BTC Any attempt to enter any larger amount will be denied with "insufficient funds to pay fee". This address contains only a dozen outputs and a fee of 0.5683 BTC (over 400 Euro!) seems a bit high to me. Edit: is it maybe the unusual pay-to-pubkey format of some of the unspent outputs? These were generated by Schildbach when It moved coins internally between 2 addresses (this is a key that was formerly used in my Schildbach wallet and was imported into Mycelium). If this is the case then you need to fix it so that it can use these types of outputs as transaction inputs. You will need a different type of signature script for these inputs, only the signature and not the pubkey because the pubkey will come from the output script, see wiki: https://en.bitcoin.it/wiki/Script#Standard_Generation_Transaction_.28pay-to-pubkey.29Edit2: This will most likely happen more often when people start importing keys from Schildbach. These pay-to-pubkey transactions are generated by Schildbach when it does its emergency transactions, when funds are sent to an old address that was flagged as insecure (due to the Android bug) it will immediately sweep the funds into a new secure address and it will use pay-to-pubkey for it. All these pay-to-pubkey transactions you can see arriving in my above address result from this. sounds like a bug to me. the fees should not be that high. we will try to reproduce it, but i don't expect a fix extremely soon (realistically, i'd work on that week 20.1-24.1) as a workaround, i'd recommend importing the key to bitcoin-qt and consolidating the funds there. |
|
|
|
|
would it be possible to modify the checksum to a bloom filter so that you can do plausible deniability with multiple passwords?
|
|
|
|
|
Mycelium already supports this. "Cold storage spending" keeps private keys in RAM only.
|
|
|
|
|
on 2014-01-26 the latest. would bet on it.
|
|
|
|
|
i don't quite get it. how is an exchange supposed to happen if funds cannot flow in + out?
i feel we are missing some important information here. the previous releases did not sound like they want to ban exchanges..
|
|
|
|
Okay, I will admit Mycelium + 0038 cold storage spending is pretty darn cool.
Couple issues: Ideally I like to throw in unicode characters to encrypt the private key. Couple dozen of those will ruin an attackers day and make it secure enough to store in broad daylight. I'll have to see if there's an easier way to enter these
How does Mycelium handle change back to a paper wallet? Does it keep the remaining funds in the paper wallet address and is this any less secure to use the same wallet again?
I ask this because ideally, I'd have a second wallet that can set up new BIP 0038 each time dynamically, whenever BTC is spent.
1) yes. it is cool. 2) for that you will need to install a custom android keyboard, configure exotic languages or use the clipboard (less secure, all apps have access to it) 3) in Mycelium, change always flows back to the "biggest contributer" of a transaction. so if you spend from paper wallet, it flows back to paper. 4) this is currently not possible in any wallet, afaik |
|
|
|
|
the way i wrote it was slightly misleading.
i think they will be intrinsically motivated to roll out Bitcoin support in 1 Year.
If they are not motivated at all, they will be toast. they sure have some reserves to last for some time, longer than 1 year, even if they are declining.
|
|
|
|
|
David Marcus, pumping Bitcoin. Incredible.
I give Paypal 1 year max until they roll out something Bitcoin related. if not, they will be toast.
|
|
|
|
|
v1.1.4 has been released to the beta channel (100%) and is in rolling update mode for the rest.
since 1.0 we have added:
Bip38 support
translations to Deutsch, English, Español, Italiano, Nederlands, Português,Русский,简体字
default unit mBtc
support for BTC China
the latest update reintroduced graceful out of memory checking for exports/bip38 keys that was broken in 1.1.0. basically, devices with less than 20 megs of ram will be unable to do the encrypted export. those users are encouraged to enable expert mode and export single, unencrypted keys.
if you notice anything worth improving, don't hesitate to ask.
We also have a brand-new Dutch translation thanks to Martijn Wismeijer!
please take a look at it.
|
|
|
|
|
it looks like you are looking for the Mycelium Wallet with watch-only addresses and Bip38 cold storage spending support.
|
|
|
|
Cool. BTW, when you go to "Export", the QR code of the key is shown, but not the private key itself (text). I don't see why. I can use the QR code or copy key to the clipboard, but I cannot copy the key by hand directly from this screen.
valid point. clipboard is more insecure than display (which is protected from rogue screenshots). it makes some sense to add this. |
|
|
|
There is still the private key export function in the menu of the keys view. Thus exported keys are not encrypted. There is also the reverse function, key import, activated by the new key icon.
if you like to view the private key directly (without the 2-factor pdf) one of the best ways to secure the key is to take a photo with a old-fashioned (digital) camera and print it. if you like analog, you need to develop it yourself though  |
|
|
|
|
it is a good idea, especially if you have a solid ROM, like an updated stock rom, or better Cyanogenmod.
Tons of people are doing this with the Mycelium Wallet, since it runs really well on limited resources.
For the truly paranoid, you can even combine this with BIP38 cold storage spending from paper wallet and you have a pretty secure setup.
|
|
|
|
Wow, that did it. I was in landscape mode. there is no indication there is stuff below.
thanks for the reminder to fix landscape mode. this needs some love. |
|
|
|
all bitcoiners are wealthy, some just don't know it yet. *) number grouping for large numbers
Is this for wealthy bitcoiners??? No if you pair that with "default unit mBtc"  . |
|
|
|
sources for version 1.1.0 rc7 have been pushed to github. testers in the beta group can already get an update from play store, too. https://plus.google.com/107839384289577985803/posts/2pDGGfhX9T1*) Bip38 support *) translations to de, es, it, pt, ru, zh *) ability to change language in options *) camera fixes (landscape mode) *) number grouping for large numbers *) bugfix when sharing PDF with Samsung Email App *) default unit mBtc *) allow encrypted backup verification through clipboard in addition to qr code. please report any bugs you might encounter. |
|
|
|
You might want to move your post to the correct forum.
do we have a humor section? |
|
|
|
Could someone please tell me what possible risks there are when using the "Cold Storage" option?
Could malware read the key from memory before it's deleted?
this is a good question. i don't believe there is malware that specialized yet, and we had no report indicating that a mycelium user lost bitcoins, even a hot wallet, due to malware. cold storage will not persist the key into flash memory. so any attack that looks there (even if it can peek into private storage of apps, with a root-exploit) will not work. but if malware has full control over the system with a root exploit it can try to read the private keys by accessing the camera sensor data directly, or by instrumenting the whole app, and intercepting the data passed between intents. (it would basically re-package the entire mycelium wallet apk if it finds an exploit to bypass signature checks) this is technically extremely sophisticated, requires significant effort to implement and has a very low, almost zero chance of infecting people if they just use the play store. if you install any random .apk from your email or you run a really bad custom ROM, like MIUI you are more in danger than normal. IMO, the best protection is to keep a lower amount of bitcoins in your normal mycelium wallet. if they do not get stolen you can be pretty sure that there is no malware targeting your bitcoins. so right now security of cold wallet spending is pretty good, but there is still room to improve it. that is what keeps us busy. there is plenty to do, to improve security even further. |
|
|
|
|
Show Posts
