Dear Mycelium devs, two questions suggestions:

1. Any chance you can lower the default tx fee to 0.00001 BTC per 1000 bytes? This has actually been the default fee setting in Bitcoin Core already since v0.9. And the very commonly used Android Bitcoin Wallet by Andreas Schildbach has been using this fee setting as well for quite some time, always works fine (just very rarely, a tx might take two or three blocks to confirm, but never leads to any problems whatsoever).
The thing is, here in Europe, bank transfers are free. So when comparing Bitcoin to old fashioned banking, the 0.0001 BTC tx fee (approximately 0.03 euros) may actually seem quite expensive in comparison. Especially for microtransactions (e.g. a €1 donation) a 3% fee is relatively expensive. It would make a better case for Bitcoin usage if you apply the new default fee in Breadwallet too.

2. Dealing with crippled WiFi: in order to push transactions, do you actually connect to Bitcoin nodes directly (i.e. you need port 8333 access for most nodes) or can Mycelium also use a web stub that works through port 80? The problem is, we quite often experience problems with public WiFi networks that have been limited, e.g. only ports for http(s) and email being accessible. Or even worse, open WiFi networks (in stores or public places) that have no password, but require a one-time login page to accept terms before allowing full internet access. When this happens, people's phones *appear* to have internet access, but any http request will redirect them to a login page. Now when trying to send a Bitcoin payment it won't work (saying "Broadcasting transaction..." forever), thus giving the false impression that Bitcoin is having problems, rather than their WiFi internet connection being crippled.
It would be great if you can 1. push txs through port 80 as well (through external API sites, there's plenty available) if you're not doing so already, and 2. perhaps check if Mycelium has a working connection, and if not, warn the user "Your internet connection seems to be restricted, perhaps you need to login to your WiFi network?" This may avoid a lot of unnecessary confusion.

Good work! I'm very pleased.

As far as I know, you can tap outside of the keyboard to hide it on iOS. Cannot check it, though, since I don't own an iPhone.

We don't even have that in our Android version yet. We're still deciding how to implement it, and will probably release it when we release support for HD wallets in Entropy.


That probably won't happen, since we now support 12 word style seeds that must be written down. Encrypted backups have caused issues, with people losing their backups, or losing their passwords.

Just a delay. The iOS devs haven't gotten to it yet

you guys are unstoppable!

orchid?


this?

can you explain what you're planning there?

Certainly works for me. Sync is down from ~17 seconds to about 3.

Also, thanks for the change in fees.

We had multiple crash reports from Nexus 6 devices, with out of memory.

Since we don't own any N6 yet, it would be great to hear how it is possible to reproduce a crash.

When that happens, rescan.
Click on the account so the blue bar appears on top, click the three dots on the right, and hit rescan.
That will bring your account up to date.
Assuming you use the HD wallet then the only backup you need is your original 12 word list.