So an update on my situation. I had already tried electrum with no joy worst is after finally getting annoyed I wiped device then recovered it with the seed and useless wallet in the exact same state. Useless and lost funds
Please wait until the backend is fixed and picks up your transaction ... There's nothing to worry about, coins are yours, they are just not showing in the user interface.
|
|
|
what if the modified firmware also modified this message? How this is protected?
This message is shown by bootloader which cannot be changed.
|
|
|
BTW.. that device works great ... I figured from python-trezor that litecoin and namecoin are already available from the device .. only thing missing is the webinterface (bop service).
Right. Same for the firmware (trezor-mcu) that runs inside of TREZOR. Could you set up a tutorial on how to setup your own mytrezor page (including backend) so that we can set up this service for different coins, aka doge, protoshares, peercoins etc....
mytrezor sources are here: https://github.com/trezor/webwallet - installation instructions are in README backend (bits of proof server) is not open-source at the moment. you can ask tamas whether he has any plans to support altcoins. btw. BIP44 (when I remember correctly) is in draft mode only .. any idea of how complicated it will be to add other coins to BIP44?
That's just a matter of defining that e.g. Dogecoin is coin type "2".
|
|
|
Only chance is, if extension was released some weeks ago then I might have installed it and forgotten about it...
Sounds plausible. The plugin 1.0.5 was out for quite some time now. You might have visited mytrezor.com in the past and installed it ... clicking transactions also brings me to an infinitely loading page
This supports my theory. Will report back when we have more info or even fix. Meanwhile, could you please report which browsers and which their versions are you having problems with?
|
|
|
Does it auto-install on Chrome?
I seriously doubt it. :-) Probably someone else installed the plugin on this computer. My hunch is saying me that the behavior you see might be caused by more strict HTTPS policy in newer browser releases. We'll try to dig into that later today.
|
|
|
This morning I have come into work and I wanted to setup myTrezor on my work computer (windows machine using google chrome). But when I plug in the device and visit the site it has not prompted me to install the extension on this machine...
It does however recognise the device name
This is really weird. Without the plugin the site could not communicate with TREZOR at all and thus should not be able to read its name. Are you sure the extension is not installed? (type about:plugins in URL bar)
|
|
|
Sorry guys, there is no option to upgrade from Metallic to Classic preorder. Only limited number of metallic cases were made and they are all being shipped.
When are you planning to start general sales of the metals? We never implied there will be any.
|
|
|
Sorry guys, there is no option to upgrade from Metallic to Classic preorder. Only limited number of metallic cases were made and they are all being shipped.
|
|
|
We have now an additional 6 month. That's 200% additional scaling up time. And still nothing. If you want to play with percentages: the scale of production went 10000% up since then ...
|
|
|
Is there any chance to get Dogecoin implemented?
That's the question for Dogecoin developers. Do they already have a block explorer server with stable API and BIP32 support? If this requirement is fulfilled it is just a matter of few minutes to add new coin to TREZOR as it is more-or-less coin agnostic.
|
|
|
I like how many BIPs came out of your project.
Thanks! That is just the beginning.
|
|
|
That's right, they should give us a small update, and explain firmware and or security issues if they exist.
There will be an announcement next week. The only thing that is holding us back are the plastic cases. Firmware is ready for quite some time, but there will be a small change on myTREZOR wallet because of the newly accepted BIP44 ( https://github.com/bitcoin/bips/blob/master/bip-0044.mediawiki)
|
|
|
Since there were absolutely no donations in Litecoins since the beginning, I was already tempted to remove the support for quite some while. I will probably do so in the following days, because I am not really sure if this page is used by Litecoin people at all. Or maybe they are all bunch of Scrooge McDucks, haha!
|
|
|
Mike Hearn got his already for free...
He did not get his for free. I don't understand where did you get this information :-/
|
|
|
The POS can create tx and just require your Trezor to sign.
In order for POS to create TX it would need to know addresses and their balances which basically is scanning. This is being addressed with BIP70, payment protocol, and will be implemented in future TREZOR firmware releases.
|
|
|
What I understand from the video is that that thing say to the phone : "pay x to y address"
Please don't hijack the thread. If you want to talk about something else than TREZOR, please create a separate discussion.
|
|
|
Seems to be dead the past few days....
Works from here ...
|
|
|
Well, one of my fears (perhaps unfounded) is that a tampered device will ignore my randomly generated input seed, and instead use some kind of weak method for generating the master private key.
That is a valid concern. What TREZOR does is that it shows its internal entropy on display (if asked to) before requesting an external one. Once provided, these two entropies are mixed (using hash) and you can verify that external was used and not omitted.
|
|
|
Why is the confirm button on the right? General convention is that yes/confirm buttons are on the left
(reposting from reddit) We always put "positive" actions (next, confirm, ok) on the right and "negative" on the left (previous, abort, cancel) button. It makes sense when you realize that in order to confirm transaction you have to press "next" several times (for each output) and then "confirm". I guess you agree that putting Next on the left and Back on the right is not a good idea.
|
|
|
The package is very hard to open
That's how we wanted it to be.
|
|
|
|