According to your link you only need to place the message and signature to verify it's signed (but that doesn't guarantee it's the correct wallet unless you do some digging deeper)
No, the link is not saying that I only have to input the Signature and the Message.
First, you have to go https://slowli.github.io/bech32-buffer/ where you need to decode bc1 address to binary data (in hex), then you have to go https://bitcoinvalued.com/tools.php where you convert the binary data to bitcoin address which is started with 1. Then copy the bitcoin address and try to verify it in brain wallet or other sites which has these services. [im g width=800 height=270]https://i.postimg.cc/prv7KwKR/Screenshot-9.png[/img]
Actually, there's a shortcut to this!
Just get your original message,
Then
remove the address from the message (
copy this):
-----BEGIN BITCOIN SIGNED MESSAGE-----
I'm Lulucrypto on Bitcointalk. And normally, I'm Luluwebmaster. I sign this message at 9 Aug 2019.
-----BEGIN SIGNATURE-----
IAIAMSyjMV62EttLm3HltwmQK0HEchc80OfXKJGPEo1pIvq/st/kgWvLmREfByk3/TSbdrWLmfzoExivGSxzTOo=
-----END BITCOIN SIGNED MESSAGE-----
And paste to
https://brainwalletx.github.io/#verifyIt'll automatically recognize the legacy address used for that signed message.
Because either way, the message was verified using the address: 1NtMnD5BQrRvVeHDk4HXaGvXiVkUuTjhXf, not bc1q7qgn8zw75n26hd60a8ay42482mukdjrdv3cyp7.
But both can be derived from the same prv key, so there wont be a serious problem with future verification.
The only difference is: those extra steps are some kind of proof that the result legacy address was based from your SegWit address.
I did actually read your link.