Backend restarted. myTREZOR balances should work ok again.

Probably some Cloudflare glitch.

Yes, it can be read.

Keys stored in the bootloader are public as asymmetric cryptography is used there. There is no security reason why bootloader should stay closed, but we were quite hesitant to open it because that's the last piece of mosaic that our competition is missing from making a perfect TREZOR clone.

It's not worth using them. It creates a bigger transaction and you'll end up paying more in the end (because the transaction fee will be higher).

Wishes are quite obvious. But we have a limited workforce :-/ So there are two options basically:
* either we sell enough TREZORs so we can fund more developers
* or someone from the community picks up

Wallet32 is a fork of Schildbach's wallet and understands BIP44. So it makes more sense to fork Wallet32 instead, removing private key management and using trezor-android for communication. That said, it's still quite a big task.

Time.

Interfacing is easy - it's already done: https://github.com/trezor/trezor-android
Now we'd need someone to integrate it into an existing wallet or create a brand new myTREZOR app.

For iOS there is an app (in the store) called breadwallet that contains all building blocks for such watch-only app (SPV + BIP32). We'll just need to find someone who will use these blocks to create "myTREZOR Lite for iOS" ...

Introducing myTREZOR Lite for Android (SPV watch-only client based on BTCReceive by Ken Sedgwick)

Fix should be deployed now.

Most of the wallets are joining the BIP44 train. (TREZOR, Wallet32, Mycelium, MultibitHD, etc.) Yay! Breadwallet would probably also use BIP44 if it existed back then.

Unfortunately not. breadwallet uses BIP39, but uses different structure than BIP44. But javascript implementation just appeared here:

https://github.com/dcpos/bip39 (optional passphrase support is coming very soon, already sent a pullrequest)

(usual disclaimer: never ever enter your recovery seed to the computer unless you have no other option)

Could you please reach our support anyway, so this is fixed in IE11?

For that to make full sense we would need to have Certificate Authorities embedded in TREZOR firmware and expand the firmware to be able to work with crypto primitives used in PKI (such as SHA-1, RSA, etc.). As you can imagine this will take some time, but we understand that this would be the next huge leap in usability. (Because users would check just domain on TREZOR instead of the address).

Works for me. Please reach our support.

Works for me. Try refreshing the browser and if it does not help, please contact our support.

We are doing small improvements almost everyday.

This change is because mytrezor.com is now handling bitcoin:.... URI links, so we needed to have the Send tab enabled at all times. What is disabled now is the Send button on that tab.

Fixed already. Thanks for the report.

Wooden TREZOR by TKRSRY:



(via reddit)