Topic: Sign message with another wallet (Read 101 times)
While the old code uses a random r, new code in the dev branch uses RFC6979 meaning the sigs will always be same (if generated from Armory for the same message and address). IDK whether other wallets us that or not. I know Core does.
will that message be equal with the message from armory?
It's not the "message"... but the "signature" that you need to worry about... and chances are that the signature created for an identical message in a different wallet will actually be different (sometimes even if you sign the same message twice in the same wallet) due to the "random nonce" used when creating the signatures.Message signed in Armory:
Code:
-----BEGIN BITCOIN SIGNED MESSAGE-----
HCP Test signing a message in Armory and Electrum
Date: 2020/08/20
-----BEGIN SIGNATURE-----
1FFv3G8N1XLGrYcz1QeU8tA4KPCzWGjAJh
G1kswQr0+uoeNYWwb8wxz4tiGSjpU8R+VGxldtdxrNckM0YYe4Pm9u8F+sKvm3iAJCQGUvL4hQejAEyw6xx+f9M=
-----END BITCOIN SIGNED MESSAGE-----
Identical message signed in Electrum with identical address/private key, but results in different signature
Code:
-----BEGIN BITCOIN SIGNED MESSAGE-----
HCP Test signing a message in Armory and Electrum
Date: 2020/08/20
-----BEGIN SIGNATURE-----
1FFv3G8N1XLGrYcz1QeU8tA4KPCzWGjAJh
HEguJMI9sQVEIDwR80pMzSq4GetnE5eaRGCOUDhPPv+ZS8JmwGicbHHH04qtVdPBTHFI3rKL/qvJcLwCe4xlM84=
-----END BITCOIN SIGNED MESSAGE-----
However, even though the signatures will be different, anyone will be able to verify that they were still signed by the same address/private key
Unfortunately I need to change wallet to a non full node wallet. But I still need to have the possibility to verify that I'm the owner of the wallet/transactions. I guess I do that by verify a message? However if I "Export key list" and import it to another wallet, will that message be equal with the message from armory?
Jump to: