-----BEGIN BITCOIN SIGNED MESSAGE-----
December 06, 2019 | AakZaki | UID: 839568 at bitcointalk.org
-----BEGIN SIGNATURE-----
1AaZakiav6yomY8BVwhkv8kkVhP4kuyyKe
G59ZYhkL4r13Icn+U3L0Rcwzmamwl8u5eCj82A6J9wdQfwcYQSsbi9aquoi3bTMlzpNdew8uFKx3/b7vta3vuFE=
-----END BITCOIN SIGNED MESSAGE-----
-----BEGIN BITCOIN SIGNED MESSAGE-----
this is AakZaki u=839568 belong to this address
-----BEGIN SIGNATURE-----
3KVZnwwaeZrxk93uTg7ZfAGJ44JCp7Bwa2
JGYRcIkN0RlYAL+sYO2v8aldpxy8fX9ffq9dPvkqlS1TR3ldaDY+VBOZvWPfVikpl9E1yO/ZKCRyxMenicP+EPo=
-----END BITCOIN SIGNED MESSAGE-----
AFAIK, Trezor implements it differently than Electrum's method.
It signs the legacy format of the address using the same private key of the SegWit address.
I'm not sure if it's Trezor or another Hardware wallet though.
For the meantime, here's an open-source "
verifyer" of messages signed to SegWit addresses using Trezor wallet (
not mine).
https://jhoenicke.github.io/brainwallet.github.io/#verify <- Different than the regular brainwallet/#verify link.
I already tried it, and it worked.
1.
2.