[ESHOP launched] Trezor: Bitcoin hardware wallet

[freebit13]

Does anyone know why outgoing transactions take longer to confirm in mytrezor than incoming ones?

When sending coins to the trezor from my desktop client, they show up as confirmed on mytrezor after one confirmation, but when sending coins from the trezor to my desktop client they take longer. Mytrezor shows it as unconfirmed even though my desktop client reports 3of6 confirmations.

Edit: 6 confirmations in my desktop client (bitcoin core), but still shows as unconfirmed in mytrezor...

Close your browser window and reopen in a minute. This usually fizes it.

Perfect, that fixed it. Thanks Grau!

[1714637645]

1714637645

[1714637645]

1714637645

[1714637645]

1714637645

[molecular]

I was hoping this new firmware would allow us to label accounts instead of the "account#1... Etc".

+1

I was surprised that it wasn't available when I got my Trezor.

that's a feature that can be added by wallet software. electrum does it, for example.

[molecular]

Any idea how the trezor could be used to sign longer messages? Like if you wanted to sign a contract that was a few pages long.

maybe sign a hash of the document?

[DevonMiner]

hello, my trezor after plug in load load load and not show my bitcoin, why?
account 1 load load load

I've had many similar issues over the past weeks, and some evenings haven't been able to load my account at all.

Sent support a message about these ongoing issues, today they replied:

"The problems with the loading account was connected with some temporary problem on our backend.
We are currently working on new backend which should replace the actual one and should work with any similar issues."

So ... the good thing is they acknowledge it, but don't mention a time frame ...

[windpath]

Just wanted to check in and introduce myself....

Very happy to announce CoinCadence is the TREZOR authorized Amazon reseller.

We are up and running on Amazon US. International Amazon's coming soon.

All colors can be found here: http://www.amazon.com/gp/node/index.html?merchant=A134DA22UU5SK7

We wanted to ensure a verifiable chain of custody and the highest security possible so TREZORs are shipped directly from SatoshiLabs to Amazon's secure fulfillment centers, and from there on to you.

To ensure your TREZOR is direct from the facotry via Amazon you can verify these 3 things on the Amazon listing:

• By: SatoshiLabs
• Sold by: CoinCadence
• Fulfilled by: Amazon

Same price, free shipping (free 2 day for prime members), and any Amazon accepted payment method (no bitcoin yet ).

If anyone has any questions about TREZOR on Amazon I'm always happy to help!

ian at coincadence dot com or here.

 

[kkurtmann]

Just wanted to check in and introduce myself....

Very happy to announce CoinCadence is the TREZOR authorized Amazon reseller.

We are up and running on Amazon US. International Amazon's coming soon.

All colors can be found here: http://www.amazon.com/gp/node/index.html?merchant=A134DA22UU5SK7

We wanted to ensure a verifiable chain of custody and the highest security possible so TREZORs are shipped directly from SatoshiLabs to Amazon's secure fulfillment centers, and from there on to you.

To ensure your TREZOR is direct from the facotry via Amazon you can verify these 3 things on the Amazon listing:

• By: SatoshiLabs
• Sold by: CoinCadence
• Fulfilled by: Amazon

Same price, free shipping (free 2 day for prime members), and any Amazon accepted payment method (no bitcoin yet ).

If anyone has any questions about TREZOR on Amazon I'm always happy to help!

ian at coincadence dot com or here.

 

Took ya long enough to make an official announcement on this thread.

[windpath]

Took ya long enough to make an official announcement on this thread.

It sure did, sorry about that! I'll be sure to post new markets and news in a timely manner

[Perlover]

Dear Trezor team,

Thanks for last update!
I am very glad to get the feature of showing a receive address & a qrcode in the screen of device.
Now your device 100% secure as for a sending and for a getting of bitcoins!

[molecular]

Dear Trezor team,

Thanks for last update!
I am very glad to get the feature of showing a receive address & a qrcode in the screen of device.
Now your device 100% secure as for a sending and for a getting of bitcoins!

urm. Maybe I'm misunderstanding something, but shouldn't the qrcodes match:



EDIT: well, they decode to the same address, so I guess there's some non-deterministic component in qr-code generation?

[dnaleor]

Dear Trezor team,

Thanks for last update!
I am very glad to get the feature of showing a receive address & a qrcode in the screen of device.
Now your device 100% secure as for a sending and for a getting of bitcoins!

urm. Maybe I'm misunderstanding something, but shouldn't the qrcodes match:



EDIT: well, they decode to the same address, so I guess there's some non-deterministic component in qr-code generation?

odd, on my trezor the QR codes DO match...

[gweedo]

Dear Trezor team,

Thanks for last update!
I am very glad to get the feature of showing a receive address & a qrcode in the screen of device.
Now your device 100% secure as for a sending and for a getting of bitcoins!

urm. Maybe I'm misunderstanding something, but shouldn't the qrcodes match:



EDIT: well, they decode to the same address, so I guess there's some non-deterministic component in qr-code generation?

Both qr codes bring up the same address.

[molecular]

Both qr codes bring up the same address.

yes.

It's a bit confusing for the user, isn't it. I'd also be interested in why this is the case for me and not for dnaleor.

[gweedo]

Both qr codes bring up the same address.

yes.

It's a bit confusing for the user, isn't it. I'd also be interested in why this is the case for me and not for dnaleor.

I bet one has extra information in the bitcoin: URI. Agreed it is confusing but it looks to be an overlooked error.

[stick]

It's a bit confusing for the user, isn't it. I'd also be interested in why this is the case for me and not for dnaleor.

Yes, we realised that various QR code generators produce different results (even for the same settings). Actually I have not found 2 implementations that DO produce same results. It's a mess and we'll look into that later, but it's low priority at the moment.

That said I really doubt that codes for dnaleor do match.

[2112]

urm. Maybe I'm misunderstanding something, but shouldn't the qrcodes match:

QR codes are deterministic, but contain error-correction information in addition to the encoded payload. There are a lot of libraries that intentionally do a sloppy work in letting you specify the ratio of payload bits to forward-error-correction bits to be user-friendly (or loser-friendly). Get a good library and you'll get 100% reproducibility.

Moreover get a good QR reader that not only displays the payload bits but the signal/noise ratio for the decoded result.

Edit: OK, I need to explain the "loser-friendly" to avoid making it sound like a vain vapid insult.

One can intentionally produce "bad" QR code images in the sense that they aren't perfect representation of the correct encoded bitstream. Because of the redundancy in encoding they will still read correctly with a normal decoder (with S/N ratio of say 20dB). The "bad"-ness is a side channel that can still be read with a modified decoder that not only reads the "main" payload but also the "side" payload (with a lower S/N margin of say 3dB).

Tricks like that have been used in e.g. theft tracing or as a secret "cookie" in marketing campaigns intended to be read by some closed-source free app. So if your good QR reader some QR code with very large noise margin or surprisingly large ratio of FEC bits you may have a reason to believe that the QR code contains a side channel.

Edit2: Obviously with cryptographic application modified QR codes with side-channels can be used to leak the private key information, but I haven't heard of that happening yet.

[Coiner.de]

I wouldn't say deterministic as the library may choose a mask. Masks are are used to get a uniform distribution of black and white and to avoid large areas with only one color. I don't think there is a norm for choosing a mask or for the amount of effort to get the best result.

[klokan]

Dear Trezor team,

Thanks for last update!
I am very glad to get the feature of showing a receive address & a qrcode in the screen of device.
Now your device 100% secure as for a sending and for a getting of bitcoins!

urm. Maybe I'm misunderstanding something, but shouldn't the qrcodes match:



EDIT: well, they decode to the same address, so I guess there's some non-deterministic component in qr-code generation?

Both qr codes bring up the same address.

OFC, they don't match, because the one on the device leaks the seed through the side channel BTW: thanks for sharing.

/// just kidding

[2112]

I wouldn't say deterministic as the library may choose a mask. Masks are are used to get a uniform distribution of black and white and to avoid large areas with only one color. I don't think there is a norm for choosing a mask or for the amount of effort to get the best result.

I think the "mask" you are talking about is a 2-dimensional implementation of http://en.wikipedia.org/wiki/Decorrelation or http://en.wikipedia.org/wiki/Whitening_transformation . It only needs to be pseudo-random http://en.wikipedia.org/wiki/Scrambler , not an actual non-deterministic noise source.

[dnaleor]

It's a bit confusing for the user, isn't it. I'd also be interested in why this is the case for me and not for dnaleor.

Yes, we realised that various QR code generators produce different results (even for the same settings). Actually I have not found 2 implementations that DO produce same results. It's a mess and we'll look into that later, but it's low priority at the moment.

That said I really doubt that codes for dnaleor do match.

checked again.
Indeed, different QR-code, but decoded as same address. Odd

[kkurtmann]

It's a bit confusing for the user, isn't it. I'd also be interested in why this is the case for me and not for dnaleor.

Yes, we realised that various QR code generators produce different results (even for the same settings). Actually I have not found 2 implementations that DO produce same results. It's a mess and we'll look into that later, but it's low priority at the moment.

That said I really doubt that codes for dnaleor do match.

checked again.
Indeed, different QR-code, but decoded as same address. Odd

Is this different look of the qr that big of a deal? I thought they only need around 30 percent of it to be readable.