Pages:
Author

Topic: How to sign a message?! - page 6. (Read 141318 times)

newbie
Activity: 2
Merit: 0
January 25, 2020, 02:45:50 PM
hi , when i want to sign massege from blockchain .com  This error occur (The signature does not match the message.) please help me .
legendary
Activity: 2352
Merit: 2049
January 02, 2020, 09:02:48 PM
I have been a practising to try sign and verify message use electrum console

Sign message

1. Open Electrum wallet
2. Console [when disappear, go to view then click show console]
3. The Following code is:
Code:
signmessage("address","Message")
example:
Code:
signmessage("bc1qvsgr8aq0hzaqwwlvvycrk8lahn9s9zrc7x2jws","Happy new year for all member, today 02 January 2019")
When click enter, your signature will appear below
Code:
"H2k73XDekL4+glAPSgUMjVUuBJaa35BvpFQOcNHgbYY2UJ/SvGuc8kmL0UzlrC8ZWdWWePzAmrIRcuItqHxVVAM="
complete sign message
Code:
-----BEGIN BITCOIN SIGNED MESSAGE-----
Happy new year for all member, today 02 January 2019
-----BEGIN SIGNATURE-----
bc1qvsgr8aq0hzaqwwlvvycrk8lahn9s9zrc7x2jws
H2k73XDekL4+glAPSgUMjVUuBJaa35BvpFQOcNHgbYY2UJ/SvGuc8kmL0UzlrC8ZWdWWePzAmrIRcuItqHxVVAM=
-----END BITCOIN SIGNED MESSAGE-----


Verify message

The following code is
Code:
verifymessage("address","signature","Message")
example 1:
Code:
verifymessage("bc1qvsgr8aq0hzaqwwlvvycrk8lahn9s9zrc7x2jws","H2k73XDekL4+glAPSgUMjVUuBJaa35BvpFQOcNHgbYY2UJ/SvGuc8kmL0UzlrC8ZWdWWePzAmrIRcuItqHxVVAM=","Happy new year for all member, today 02 January 2019")
When your signature valid, true will appear after clicked enter
Code:
true

example 2:
Code:
verifymessage("1KoFPRMnegmvGCPef1YNienLh1wy71UmRc","IGjLVlWHKaQaClF4+HWnt0t9xK1Mb54iz/hUv33shY11DvxuRqcnZXbanaZPUNcMtdPz9/I+inlsly7O5fDFXfU=","Hi, This is HiDevin on BTCTalk and it's 8/2/18")
Code:
true

example 3:
Code:
verifymessage("3GmamfBzmhcSa2jixAV8dQnuJmm3zbJ7pM","H9a1+ti12Bm7TnX3PIo+csxtojCv7D4lBNVo8Z2MTYcXe6eCSCgEg/TO/t4NLkpOqNJpcvNDTZnFUqfE75Hp68U=","This is efialtis from bitcointalk, please verify my adress, todays date is 28/12/2019")
Code:
true



source: An Introduction to the Electrum Python Console
legendary
Activity: 2590
Merit: 2348
October 01, 2019, 01:42:11 PM
does anyone know "how to sign a message!! on the latest Blockchain.info (now Blockchain.com)??
looks like I missed the Post!!
Yes you must import your private key first.

Quote
This feature is currently only available for your Imported Addresses, but will be implemented for all addresses in the future. To sign a message, go to Settings > Addresses, and scroll down. Choose which address you want to sign, and click More Options > Sign Message.

A small window will display allowing you to provide a unique message or signature that identifies you as the owner.
https://support.blockchain.com/hc/en-us/articles/210353833-What-is-message-signing-and-how-can-I-do-that-
sr. member
Activity: 2044
Merit: 329
October 01, 2019, 01:19:10 PM
does anyone know "how to sign a message!! on the latest Blockchain.info (now Blockchain.com)??
looks like I missed the Post!!
legendary
Activity: 2394
Merit: 5531
Self-proclaimed Genius
September 18, 2019, 09:18:26 AM
sorry for the late response. This is strange, in the other thread he could verify it?
HCP added the word "basically" because Bitcoin Core still doesn't have an official way of signing messages using P2SH addies,
Most of those clients that were able to sign, are using their own (non-standard) implementation.

P.S: I also successfully verified the message using Electrum.
legendary
Activity: 1750
Merit: 1363
www.btcgosu.com
September 18, 2019, 09:06:56 AM
Test:

Code:
-----BEGIN BITCOIN SIGNED MESSAGE-----

-----BEGIN SIGNATURE-----
<33su7w86rwrm2w2iQGCwA242sYyuoVrqde>

-----END BITCOIN SIGNED MESSAGE-----

Quoted, but fails to verify... Note that generally, you cannot sign messages from "P2SH" (aka "3"-type) addresses. Also, you shouldn't include the <'s and >'s... it confuses most of the verification systems.

Were you using a Trezor to sign that message? (It's one of the few systems I know of that will sign using a "3"-type address)

Hey mate,

sorry for the late response. This is strange, in the other thread he could verify it?

Code:
-----BEGIN BITCOIN SIGNED MESSAGE-----

-----BEGIN SIGNATURE-----
<33su7w86rwrm2w2iQGCwA242sYyuoVrqde>

-----END BITCOIN SIGNED MESSAGE-----
Quoted, verified with mycelium, archived see below.
http://archive.fo/XSzt5
http://imgur.com/gallery/lvnkqGn


Btw I had to alter the message a little to verify it. I remove the "<>" and it went well.
legendary
Activity: 3430
Merit: 10505
August 28, 2019, 11:56:36 PM
Test:

Code:
-----BEGIN BITCOIN SIGNED MESSAGE-----

-----BEGIN SIGNATURE-----
<33su7w86rwrm2w2iQGCwA242sYyuoVrqde>

-----END BITCOIN SIGNED MESSAGE-----

Quoted, but fails to verify... Note that generally, you cannot sign messages from "P2SH" (aka "3"-type) addresses. Also, you shouldn't include the <'s and >'s... it confuses most of the verification systems.

Were you using a Trezor to sign that message? (It's one of the few systems I know of that will sign using a "3"-type address)

i am still surprised that after 2 years of this type of address (nested SegWit) being around they still haven't done anything about it. the change is super easy too! every code has 2 parts: recover public keys and derive the address from them to compare with the given one. they just have to change the second one from GetP2PKH address to an "if" where it derives P2WPKH-P2SH one if the address started with 3.
by the way neither one of the derived public keys seem to work here:
Code:
027695a6b442074738985a72c8b7995fc6bd83000932a650825729196415e188c3
3KmE6TJpVnq619Pyc7qv77M4tqXoTFzdbx

022a190476fd852260e2e5b196ae3f119378ec1a9ce162843806076c7fe7f70a1f
3KBqUw9TYirYtckcmq21PiT5SJ8S92supb
jr. member
Activity: 243
Merit: 9
August 28, 2019, 09:10:17 PM
This thread would have saved me some hardship and I wish I saw it  Undecided
Very imformative and thank you for the step by step.
HCP
legendary
Activity: 2086
Merit: 4314
August 28, 2019, 08:20:00 PM
Test:

Code:
-----BEGIN BITCOIN SIGNED MESSAGE-----

-----BEGIN SIGNATURE-----
<33su7w86rwrm2w2iQGCwA242sYyuoVrqde>

-----END BITCOIN SIGNED MESSAGE-----

Quoted, but fails to verify... Note that generally, you cannot sign messages from "P2SH" (aka "3"-type) addresses. Also, you shouldn't include the <'s and >'s... it confuses most of the verification systems.

Were you using a Trezor to sign that message? (It's one of the few systems I know of that will sign using a "3"-type address)
legendary
Activity: 1750
Merit: 1363
www.btcgosu.com
August 26, 2019, 03:44:40 PM
Test:

Code:
-----BEGIN BITCOIN SIGNED MESSAGE-----

-----BEGIN SIGNATURE-----
<33su7w86rwrm2w2iQGCwA242sYyuoVrqde>

-----END BITCOIN SIGNED MESSAGE-----
full member
Activity: 1589
Merit: 214
legendary
Activity: 2184
Merit: 3134
₿uy / $ell
August 14, 2019, 03:24:37 AM
This is simply for staking and marking my ownership of the address below.

Code:
-----BEGIN BITCOIN SIGNED MESSAGE-----
This is skywalker925 from bitcointalk.org and today is 2019.08.14 or as some of you might write it 08/14/2019. Time is 2:07 pm
-----BEGIN BITCOIN SIGNATURE-----
Version: Bitcoin-qt (1.0)
Address: 19EPcSbNqarpTcRYGLR1jCTa5Hh8zrGMM7

ILlfNzKYHN4KyzFOguRLbUqlIWOZR/VzK0+EVjofJLTDdIOyfPkRMSxu1R+OLD6R7XcVutjGoAFW+yuXUAS+sKA=
-----END BITCOIN SIGNATURE-----

This is a wrong place to stake an address. There is a designated thread for this so better post it here > Stake your Bitcoin address here
newbie
Activity: 4
Merit: 0
August 14, 2019, 02:19:00 AM
This is simply for staking and marking my ownership of the address below.

Code:
-----BEGIN BITCOIN SIGNED MESSAGE-----
This is skywalker925 from bitcointalk.org and today is 2019.08.14 or as some of you might write it 08/14/2019. Time is 2:07 pm
-----BEGIN BITCOIN SIGNATURE-----
Version: Bitcoin-qt (1.0)
Address: 19EPcSbNqarpTcRYGLR1jCTa5Hh8zrGMM7

ILlfNzKYHN4KyzFOguRLbUqlIWOZR/VzK0+EVjofJLTDdIOyfPkRMSxu1R+OLD6R7XcVutjGoAFW+yuXUAS+sKA=
-----END BITCOIN SIGNATURE-----
legendary
Activity: 3038
Merit: 1330
Slava Ukraini!
August 01, 2019, 12:07:46 PM
I have a few questions. I lost a Bitcointalk account to a hacker a while ago. People have suggested I sign a message from an old address to prove ownership, however, I'm wondering if giving away the signature will compromise my wallet's security.

What do I do after I've signed the message? Do I give away the signature, address, and message, then?
No, it won't compromise your wallet's security. Signed message just will confirm that you have control of that address. Just don't share your private key.
You can read more about recovery of hacked accounts here if you haven't saw it yet:
https://bitcointalksearch.org/topic/recovering-hackedlost-accounts-5089777
member
Activity: 136
Merit: 25
August 01, 2019, 10:06:01 AM
I have a few questions. I lost a Bitcointalk account to a hacker a while ago. People have suggested I sign a message from an old address to prove ownership, however, I'm wondering if giving away the signature will compromise my wallet's security.

What do I do after I've signed the message? Do I give away the signature, address, and message, then?
jr. member
Activity: 266
Merit: 4
July 27, 2019, 12:56:56 PM
You really tried by taking much of your time to put all this together for better understand and practice. There are many things bitcointalk gat to offer to her community that we don't know about. You've been on this forum since 2013 till now,that's lovely. Thanks for the tutorial
HCP
legendary
Activity: 2086
Merit: 4314
July 25, 2019, 07:02:31 PM
My address is
3EfqqrABD3EBw1okT3wftjUgTnM2xeWKpx
and i have error when i try to sign message:
"The entered address does not refer to a key. Please check the address and try again"

The address is correct because I already send and receive coins with it.
Your address is correct, but you can't sign a message using this address, because as I understand it's from multi-signature wallet.
Not quite correct... it *might* be a Multi-Sig address... but it could also be a nested SegWit address. Addresses that start with a "3" are a "Pay to Script Hash" address... commonly referred to as P2SH.

As these addresses are derived from a "script", there is no private key that is paired directly with that address that can be used to sign the message.

You would need to use a "Legacy" address (starts with a "1") to be able to sign a message.
newbie
Activity: 427
Merit: 0
July 24, 2019, 10:52:24 AM
This is George coffie and my address is
115YqcsHBZVkqGD88YaoLgSyg3XpmuvB3p
You ask me to send it for you emblem you recover  my hack account thanks very much.
newbie
Activity: 2
Merit: 0
July 24, 2019, 12:24:44 AM
My address is
3EfqqrABD3EBw1okT3wftjUgTnM2xeWKpx
and i have error when i try to sign message:
"The entered address does not refer to a key. Please check the address and try again"

The address is correct because I already send and receive coins with it.
Your address is correct, but you can't sign a message using this address, because as I understand it's from multi-signature wallet.
Thank you
legendary
Activity: 3038
Merit: 1330
Slava Ukraini!
July 23, 2019, 06:41:18 PM
My address is
3EfqqrABD3EBw1okT3wftjUgTnM2xeWKpx
and i have error when i try to sign message:
"The entered address does not refer to a key. Please check the address and try again"

The address is correct because I already send and receive coins with it.
Your address is correct, but you can't sign a message using this address, because as I understand it's from multi-signature wallet.
Pages:
Jump to: