Bitcoin Forum
December 16, 2024, 02:23:13 AM *
News: Latest Bitcoin Core release: 28.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: How to verify a Trezor Message if you don't own Trezor HW wallet?  (Read 203 times)
TheBeardedBaby (OP)
Legendary
*
Offline Offline

Activity: 2254
Merit: 3150


₿uy / $ell ..oeleo ;(


View Profile
June 26, 2020, 01:06:42 PM
Merited by ABCbits (1)
 #1

Maybe a dump question but if I sign a message with my Trezor, and the address is just a SegWit P2WPKH-in-P2SH addresses (starting with 3) then the only way to verify it is to use the trezor's own verification tool.

That means that if you have no Trezor HW wallet, you cannot verify my message.

^ Is that correct?

mocacinno
Legendary
*
Offline Offline

Activity: 3612
Merit: 5279


https://merel.mobi => buy facemasks with BTC/LTC


View Profile WWW
June 26, 2020, 01:10:56 PM
Merited by ABCbits (1)
 #2

You're more or less correct...

Here's some extra info by a Satoshilab employee:
https://www.reddit.com/r/TREZOR/comments/8vyenv/please_help_cannot_verify_trezor_signed_messages/

Trezor is open source, so even without the above post, it *should* *theoretically* be possible to create an application outside trezor's wallet to verify messages signed with a trezor HW device (since, if you'd read the sourcecode, you'd probably find how trezor handles the signature verification). This being said, i don't know any of these tools...

IF you're ever stuck with a signed message you can't verify, don't hesitate to PM me. I have a couple trezor's laying around and i don't mind verifying a message now and then.

█▀▀▀











█▄▄▄
▀▀▀▀▀▀▀▀▀▀▀
e
▄▄▄▄▄▄▄▄▄▄▄
█████████████
████████████▄███
██▐███████▄█████▀
█████████▄████▀
███▐████▄███▀
████▐██████▀
█████▀█████
███████████▄
████████████▄
██▄█████▀█████▄
▄█████████▀█████▀
███████████▀██▀
████▀█████████
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
c.h.
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
▀▀▀█











▄▄▄█
▄██████▄▄▄
█████████████▄▄
███████████████
███████████████
███████████████
███████████████
███░░█████████
███▌▐█████████
█████████████
███████████▀
██████████▀
████████▀
▀██▀▀
bitmover
Legendary
*
Online Online

Activity: 2520
Merit: 6374


Wheel of Whales 🐳


View Profile WWW
June 26, 2020, 04:45:10 PM
 #3

Maybe a dump question but if I sign a message with my Trezor, and the address is just a SegWit P2WPKH-in-P2SH addresses (starting with 3) then the only way to verify it is to use the trezor's own verification tool.

Have you tried to verify in Electrum? There is no standard way to sign/verify messages from segwit addresses, but Electrum created it own standard. Maybe Trezor uses the same one ( I don't know)

███████████▄
████████▄▄██
█████████▀█
███████████▄███████▄
█████▄█▄██████████████
████▄█▀▄░█████▄████████
████▄███░████████████▀
████░█████░█████▀▄▄▄▄▄
█████░█
██░█████████▀▀
░▄█▀
███░░▀▀▀██████
▀███████▄█▀▀▀██████▀
░░████▄▀░▀▀▀▀████▀
 

█████████████████████████
████████████▀░░░▀▀▀▀█████
█████████▀▀▀█▄░░░░░░░████
████▀▀░░░░░░░█▄░▄░░░▐████
████▌░░░░▄░░░▐████░░▐███
█████░░░▄██▄░░██▀░░░█████
█████▌░░▀██▀░░▐▌░░░▐█████
██████░░░░▀░░░░█░░░▐█████
██████▌░░░░░░░░▐█▄▄██████
███████▄░░▄▄▄████████████
█████████████████████████

█████████████████████████
████████▀▀░░░░░▀▀████████
██████░░▄██▄░▄██▄░░██████
█████░░████▀░▀████░░█████
████░░░░▀▀░░░░░▀▀░░░░████
████░░▄██░░░░░░░██▄░░████
████░░████░░░░░████░░████
█████░░▀▀░▄███▄░▀▀░░████
██████░░░░▀███▀░░░░██████
████████▄▄░░░░░▄▄████████
█████████████████████████
.
...SOL.....USDT...
...FAST PAYOUTS...
...BTC...
...TON...
Rath_
aka BitCryptex
Legendary
*
Offline Offline

Activity: 1876
Merit: 3139



View Profile
June 26, 2020, 05:13:50 PM
 #4

Have you tried to verify in Electrum? There is no standard way to sign/verify messages from segwit addresses, but Electrum created it own standard. Maybe Trezor uses the same one ( I don't know)

It won't work. As far as I remember, Trezor implemented it before Electrum. Since it is not a standard, they have no reason to put effort into adapting Electrum's implementation because it might become obsolete. BIP-322 is supposed to address this problem.
jackg
Copper Member
Legendary
*
Offline Offline

Activity: 2856
Merit: 3071


https://bit.ly/387FXHi lightning theory


View Profile
June 26, 2020, 10:09:57 PM
 #5

I haven't used nested segwit for a long term address and it seems to have so many compativilities that is probably a bad idea to try to (I'd probably pick legacy over it even with the fees)...

Is it possible to verify one when you use electrum if you generated it from electrum or can you just not generate a trezor signature eon a nested segwit address? I didn't think it'd be possible to create a signature without electrum then wanting to verify it before displaying it...
Rath_
aka BitCryptex
Legendary
*
Offline Offline

Activity: 1876
Merit: 3139



View Profile
June 27, 2020, 01:04:19 AM
 #6

I haven't used nested segwit for a long term address and it seems to have so many compativilities that is probably a bad idea to try to (I'd probably pick legacy over it even with the fees)...

What are your other reasons not to use nested SegWit addresses? I have switched completely to native SegWit addresses and I didn't encounter any major inconveniences. If I need to sign a message using one of my addresses then I include an information in the message that it can be verified using Electrum.

Is it possible to verify one when you use electrum if you generated it from electrum or can you just not generate a trezor signature eon a nested segwit address?

If you set up an Electrum wallet using your Trezor device, you can use it to sign messages just as if you were using a standard Electrum wallet. They can only be verified in Electrum, though. Messages signed using legacy addresses can be verified by Electrum, Trezor Wallet and any other software. Let me know if that's not what you wanted to know.

I didn't think it'd be possible to create a signature without electrum then wanting to verify it before displaying it...

Could you rephrase this sentence? I don't get what you mean.
jackg
Copper Member
Legendary
*
Offline Offline

Activity: 2856
Merit: 3071


https://bit.ly/387FXHi lightning theory


View Profile
June 27, 2020, 01:16:15 AM
 #7


What are your other reasons not to use nested SegWit addresses? I have switched completely to native SegWit addresses and I didn't encounter any major inconveniences. If I need to sign a message using one of my addresses then I include an information in the message that it can be verified using Electrum.


The signing issue was mainly a problem in case you needed to prove ownership to an exchange or something, it's also more effort than it's worth to me... I could use it temporarily but I normally use native segwit (other than those exchanges where you can't - sometimes for random reasons where they pick when they want to accept native segwit or not)...

If you set up an Electrum wallet using your Trezor device, you can use it to sign messages just as if you were using a standard Electrum wallet. They can only be verified in Electrum, though. Messages signed using legacy addresses can be verified by Electrum, Trezor Wallet and any other software. Let me know if that's not what you wanted to know.


Yeah this is the only way I use trezor with bitcoin but it might be a good idea to suggest we all use it for signing this addresses in the hope it gets accepted as the standard as its more widely available than trezor...


I didn't think it'd be possible to create a signature without electrum then wanting to verify it before displaying it...

Could you rephrase this sentence? I don't get what you mean.

Oh it was just meant to mena like a sanity check at run time. Electrum takes so long to generate a signature that it seems likely it'd also spend time verifying the signature with the message and address in the process...
Chikito
Legendary
*
Offline Offline

Activity: 2604
Merit: 2090


Top-tier crypto casino and sportsbook


View Profile WWW
June 27, 2020, 04:45:11 AM
 #8

then the only way to verify it is to use the trezor's own verification tool.
^ Is that correct?
Can use another tool > > https://jhoenicke.github.io/brainwallet.github.io/#verify
yes, if use brainwalletx and electrum to verify I got wrong signature, but got verified using trezor and jhoenicke brain wallet.

 
 BETFURY .....
██████▄██▄███████████▄█▄
█████▄█████▄████▄▄▄█
███████████████████
████▐███████████████████
███████████▀▀▄▄▄▄███████
██▄███████▄▀███▀█▀▀█▄▄▄█
▀██████████▄█████▄▄█████▀██
██████████▄████▀██▄▀▀▀█████▄
█████████████▐█▄▀▄███▀██▄
███████▄▄▄███▌▌█▄▀▀███████▄
▀▀▀███████████▌██▀▀▀▀▀█▄▄▄████▀
███████▀▀██████▄▄██▄▄▄▄███▀▀
████████████▀▀▀██████████
 
..... UP TO 60% APR BTC STAKING .....

 
 Exclusive 200% APR in USDT
& Extra Bonus
▬▬▬▬▬ ◤◤
█▀▀











█▄▄
CODE: BTSTAKE
 
...STAKE NOW...
▀▀█











▄▄█
TheBeardedBaby (OP)
Legendary
*
Offline Offline

Activity: 2254
Merit: 3150


₿uy / $ell ..oeleo ;(


View Profile
June 27, 2020, 11:09:27 PM
 #9

Thank you guys for the answers. Seems like I still have a lot to learn but I will reveal my plan to you.

I am going to write a guide on how newbies can verify messages for any type of address.
So I guess I will have more questions during the process.
I'm doing it basically for myself, because I learn new stuff that way and someone can actually benefit from what I have learned Smiley

Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!