Bitcoin Forum
November 22, 2019, 02:06:41 AM *
News: 10th anniversary art contest
 
   Home   Help Search Login Register More  
Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 [39] 40 »
  Print  
Author Topic: How to sign a message?!  (Read 134584 times)
mjammer
Newbie
*
Offline Offline

Activity: 4
Merit: 0


View Profile
June 06, 2019, 09:55:56 PM
 #761

I'm just learning about this Bitcoin Signature thing. I've read Shorena's thread tutorial from the beginning and want to go ahead and sign a message and have it verified. I'm kinda confused on which Address to use. Do I just use one from my list?  I'm using Electrum as my wallet. Also, do I just copy and paste the completed signed message from the Electrum page here?
To sign a message, you can use any address in your Electrum wallet to do it. However, before signing a message, you should remember to back up seeds of your wallet for later recovery. It sounds ridiculous if you sign a message from a wallet that you don't have control of its seeds. Then, in worst situation (such as computer broken) the sign message has zero value for your account here.
Moreover, if you have more than one devices, I suggest you to sign at least 2 messages from two different wallets - that stored on two devices. It is the way to decentralize risks of losing wallet control from technical issues of your devices and your backups.

Note:
- Don't include email in your message (to avoid phising links later)
- Place to sign your message: Stake your bitcoin address here. Please use the format in the OP of that topic.


Yes, just choose one address from the list to sign a message from it. It's a very friendly use in Electrum on sign/verify messages.

Yes, you have to copy and paste the following three elements so another user can verify it:
- Signed message.
- Address used.
- Signature.

Don't forget to add actual date to your message; it's the proof that you just did it now, not in the past. This is just a recommendation, not a must-do.

Hello again,

Ok I followed everything to the letter, Wrote a specific message in that section with date and time, Inserted one of my bitcoin addresses in the the Address section, proceeded to the Signature section of my Electrum messaged and clicked Sign, got the pop up window requesting my password, I entered my password and clicked, "ok", but instead of adding the signature, I got this pop up.


"Cannot sign messages with this type of address: p2sh
Signing with an address actually means signing with the corresponding private key, and verifying with the corresponding public key. The address you have entered does not have a unique public key, so these operations cannot be performed.
The operation is undefined. Not just in Electrum, but in general."


I'm using one of my Addresses that says "receiving" just to the left of the Address. There are about 20 of them and I used one that has not been previously used before.

Also, at the bottom of the list of Address, there are 6 that say "Change" to the left of the Addresses instead of  "Receiving".

I tried one of those and got the same pop up window as before.

Am I missing something here or entering something incorrectly? I have no idea what "p2sh" means.

I'm using Electrum version 3.3.4 and have had no problems receiving 3 different deposits of bitcoin and my balance total is showing correctly.

Any help would be greatly appreciated.
Thanks again.  Smiley
The Bitcoin Forum is turning 10 years old! Join the community in sharing and exploring the notable posts made over the years.
1574388401
Hero Member
*
Offline Offline

Posts: 1574388401

View Profile Personal Message (Offline)

Ignore
1574388401
Reply with quote  #2

1574388401
Report to moderator
1574388401
Hero Member
*
Offline Offline

Posts: 1574388401

View Profile Personal Message (Offline)

Ignore
1574388401
Reply with quote  #2

1574388401
Report to moderator
HCP
Legendary
*
Offline Offline

Activity: 1162
Merit: 1899

<insert witty quote here>


View Profile
June 06, 2019, 10:08:40 PM
 #762

"Cannot sign messages with this type of address: p2sh
Signing with an address actually means signing with the corresponding private key, and verifying with the corresponding public key. The address you have entered does not have a unique public key, so these operations cannot be performed.
The operation is undefined. Not just in Electrum, but in general."
P2SH = Pay to Script Hash... These addresses will start with a "3".

As per the error message, P2SH addresses aren't necessarily created based on a single "private/public key"... Because of this, you cannot sign a message using these addresses as there is not public/private key to be able to sign the message with.


Given that you're using Electrum, I would guess that you're either using a MultiSig wallet or, more likely, a "2FA" wallet (which is a special type of multisig)... these are actually created by combining multiple keys together to create the P2SH scripts.

You need to use "Legacy" ("1"-type addresses) or Native Segwit (aka bech32 aka "bc1"-type addresses) to be able to sign messages.

mjammer
Newbie
*
Offline Offline

Activity: 4
Merit: 0


View Profile
June 06, 2019, 10:24:17 PM
 #763

"Cannot sign messages with this type of address: p2sh
Signing with an address actually means signing with the corresponding private key, and verifying with the corresponding public key. The address you have entered does not have a unique public key, so these operations cannot be performed.
The operation is undefined. Not just in Electrum, but in general."
P2SH = Pay to Script Hash... These addresses will start with a "3".

As per the error message, P2SH addresses aren't necessarily created based on a single "private/public key"... Because of this, you cannot sign a message using these addresses as there is not public/private key to be able to sign the message with.


Given that you're using Electrum, I would guess that you're either using a MultiSig wallet or, more likely, a "2FA" wallet (which is a special type of multisig)... these are actually created by combining multiple keys together to create the P2SH scripts.

You need to use "Legacy" ("1"-type addresses) or Native Segwit (aka bech32 aka "bc1"-type addresses) to be able to sign messages.

Hi and thanks for your reply.

When I initially download and set up my wallet, I did set it up as "2FA", which is 2 factor authentication I believe, and used the Google Authentication app with the QR type code. My old computer hard drive crashed and I used my 12 word seed to recover my wallet and update to to the latest version.

When I set up my wallet up on my new computer, I got a message stating that 2 factor Authentication (2FA) was turned off or not available because this wallet was recovered from seed.

Can you explain to me what I need to do to use "Legacy" or "Native Segwit" type Addresses to get this message signature thing to work?

Thanks.  Smiley   
HCP
Legendary
*
Offline Offline

Activity: 1162
Merit: 1899

<insert witty quote here>


View Profile
June 06, 2019, 10:45:37 PM
 #764

Basically, you would need to create a completely new wallet... with a completely new seed.

"File -> New\Restore -> Standard Wallet -> Create a new seed"

You can choose "SegWit" or "Legacy" during setup:


Be aware that using Native SegWit (aka Bech32 aka "bc1") addresses *may* cause issues (as noted on the dialog) with some services and wallets (block explorers, exchanges, gambling sites etc) that do NOT as yet support "bc1" addresses Undecided

Using "Legacy" addresses means you won't have any compatibility issues, but can result in slightly "larger" transactions that may mean you pay more in transaction fees.

mjammer
Newbie
*
Offline Offline

Activity: 4
Merit: 0


View Profile
June 07, 2019, 12:29:29 AM
Last edit: June 07, 2019, 01:03:40 AM by mjammer
 #765

Basically, you would need to create a completely new wallet... with a completely new seed.

"File -> New\Restore -> Standard Wallet -> Create a new seed"

You can choose "SegWit" or "Legacy" during setup:
https://i.imgur.com/Yy4gGGU.png

Be aware that using Native SegWit (aka Bech32 aka "bc1") addresses *may* cause issues (as noted on the dialog) with some services and wallets (block explorers, exchanges, gambling sites etc) that do NOT as yet support "bc1" addresses Undecided

Using "Legacy" addresses means you won't have any compatibility issues, but can result in slightly "larger" transactions that may mean you pay more in transaction fees.

I've read a little about SegWit, so you're saying it's still kinda new and those addresses (Bech32 & bc1) may not be supported at certain cites, Legacy is the standard, but might result in higher transaction fees? Which one would you recommend?

I've planned on using "Replace By Fee" RBF option, so as to not have transactions get stuck or unconfirmed. I've also seen now that Electrum has a "mempool" option. Would it be better to use one or both of these in conjunction with SegWit or Legacy?

So when I create a new Electrum wallet, will I be able to transfer my bitcoin from the old one to the new one and then delete the old one, without issues? Sorry for all the noob questions, just trying to figure this thing out. I'm just kinda concerned if I download a new Electrum wallet, will it conflict or replace the old one?

Thanks again for your kind help.
HCP
Legendary
*
Offline Offline

Activity: 1162
Merit: 1899

<insert witty quote here>


View Profile
June 07, 2019, 03:22:52 AM
Merited by Halab (2), xandry (1), LoyceV (1)
 #766

I've read a little about SegWit, so you're saying it's still kinda new and those addresses (Bech32 & bc1) may not be supported at certain cites, Legacy is the standard, but might result in higher transaction fees? Which one would you recommend?
Personally, I'm using a "nested" SegWit (another type of "3" address) wallet... it's backwards compatible, so no issues with services saying "invalid address" etc and has most of the same SegWit benefits as "bc1"... but that doesn't help with the "signing" a message thing.

Luckily, I have an "old" wallet with Legacy addresses available... and I staked one of those. You realise there is no reason that you can't simply use a new legacy or bc1 address for anything other than simply signing a message to stake the address right? You don't HAVE to actually use it to send/receive coins... You just need to make sure that you retain the appropriate private keys (backup wallet file or seed mnemonic etc) so you can re-sign later to prove "ownership" etc. [see below]

Quote
I've planned on using "Replace By Fee" RBF option, so as to not have transactions get stuck or unconfirmed. I've also seen now that Electrum has a "mempool" option. Would it be better to use one or both of these in conjunction with SegWit or Legacy?
My advice, is always use RBF regardless of the address type... Legacy, Nested or Native SegWit... it'll save you one day when you get caught out by a massive spike in fee rates and you need to get your transaction pushed through. TBH, I don't pay much attention to the mempool/ETA thing in Electrum... as, I set fees manually after checking what is happening with fees on:
https://jochen-hoenicke.de/queue/#0,24h
and
https://btc.com/stats/unconfirmed-tx


Quote
So when I create a new Electrum wallet, will I be able to transfer my bitcoin from the old one to the new one and then delete the old one, without issues? Sorry for all the noob questions, just trying to figure this thing out. I'm just kinda concerned if I download a new Electrum wallet, will it conflict or replace the old one?
Electrum allows you to have multiple different wallet files... you can even have them all open at the same time... so you don't need to re-download or replace anything... And I certainly wouldn't delete anything.

Simply use the following menu option: "File -> New\Restore"

You'll be able to create another wallet (different name)... and you can do this as many times as you like. You just want to make sure you give each wallet a meaningful name, so you know which wallet is which... and be very careful that when copying a "receive" address, that you copy it from the correct wallet! Wink



Ok... so having said all that, in your instance, I'd simply create a new "Legacy" wallet called something like "StakedAddress"... take the first "receive" address from this wallet, stake it and sign a message with it over in the "staked address" thread.

Then never use that wallet for anything but signing messages as required from your staked address... and you can continue to use your current wallet, until you decide which way you want to go (Legacy or SegWit etc).

MrFreeRoMan
Full Member
***
Offline Offline

Activity: 126
Merit: 170



View Profile
June 10, 2019, 11:57:10 AM
 #767

-----BEGIN BITCOIN SIGNED MESSAGE-----
This is MrFreeRoMan from bitcointalk.org and today is an amazing day
2019/06/10
-----BEGIN BITCOIN SIGNATURE-----
Version: Bitcoin-qt (1.0)
Address: 1MrFreeSjoKQonYC24p3VRd8A23xKbu6eP

G2k1k2RWLgejhiVe08mEGF4Hj9v95nCtnwSToQ1c+Cg1Bld/k1LrMvDOiJst7dokSEtCY0ErTl0oP7YtM54zH/M=
-----END BITCOIN SIGNATURE-----
Lucius
Legendary
*
Offline Offline

Activity: 1610
Merit: 1396


Fortis Fortuna Adiuvat


View Profile WWW
June 10, 2019, 01:58:42 PM
 #768

MrFreeRoMan, you sign message from your address and you do it in proper way, but you post it in wrong board / thread. We have thread in Meta (check HCP post above yours) for posting signed message, and this is especially important if you need to prove ownership of your account. To check signed message use this link : http://brainwalletx.github.io/#verify

HCP
Legendary
*
Offline Offline

Activity: 1162
Merit: 1899

<insert witty quote here>


View Profile
June 11, 2019, 08:46:01 AM
 #769

You can use any address you like... provided you have access to the private key.

Having said that, there is no real "standard" for signing using SegWit addresses at this point in time (even though Electrum will allow you to sign using Native Segwit "bc1" addresses)... so it will be easier for others to verify if you use an old legacy "1"-type address to sign with.

The generally accepted format for posting the signed message is:
Code:
-----BEGIN BITCOIN SIGNED MESSAGE-----
<This is where you put the Message, it should be dated, include your name and the reason for signing>
-----BEGIN BITCOIN SIGNATURE-----
<Address goes here>
<Generated Signature goes here>
-----END BITCOIN SIGNATURE-----

For instance... something like this:
Code:
-----BEGIN BITCOIN SIGNED MESSAGE-----
This is HCP, creating a demo signed message, todays date is 11/06/2019
-----BEGIN BITCOIN SIGNATURE-----
16qkTAUmtCdBYfXXKKGKqD8pAYtL1T5pqV
H+0dFKxjqu9Pbd3vgOKwu2s1zKI6LaTSvQ+4frC0Cg1ROKIDtn8J1Bdj0GKD1nIxvfzAGp9ODL/21nS4/02ghKE=
-----END BITCOIN SIGNATURE-----

Be careful with "newlines" and "spaces"... one extra and the signature verification will fail! If you follow this format, other people can easily verify your message here: https://brainwalletx.github.io/#verify
But it only works with "1"-type addresses. So, if you use Electrum and a "bc1" address, users cannot use brainwalletx to verify... it will only be verifiable using Electrum.


Once you have created your signed message... you should post it in the "stake your address" thread... someone will quote and verify (and possibly archive) it, so that there is a permanent record of it for future reference.

Quite
Full Member
***
Offline Offline

Activity: 378
Merit: 157


View Profile WWW
June 25, 2019, 04:04:54 PM
 #770

I'm on one of the most useful topics in the forum. Thank you for preparing this topic.

Is it possible to add the guide I prepared for Turkish users who are weak in English to the major topic?

https://bitcointalk.org/index.php?topic=5156948.0 (Mesaj İmzalama - Hacklenen veya Çalınan Hesapları Kurtarma Süreçleri)

Pacho Vladigerov
Newbie
*
Offline Offline

Activity: 2
Merit: 0


View Profile
July 23, 2019, 11:01:19 AM
 #771

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.
dkbit98
Hero Member
*****
Offline Offline

Activity: 602
Merit: 503


First 100% Liquid Stablecoin Backed by Gold


View Profile WWW
July 23, 2019, 09:48:59 PM
 #772

Thank you for very informative topic!

My question is:
In latest updates for Ledger Nano S wallet they changed interface and removed option to sign a message.
Can anyone please tell me is there any way to do it in latest versions of Ledger Nano S  ??


LTU_btc
Hero Member
*****
Offline Offline

Activity: 1428
Merit: 758



View Profile WWW
July 23, 2019, 10:41:18 PM
 #773

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.




▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄    ▄▄▄▄                  ▄▄▄   ▄▄▄▄▄        ▄▄▄▄▄   ▄▄▄▄▄▄▄▄▄▄▄▄    ▄▄▄▄▄▄▄▄▄▄▄▄▄▄   ▄▄▄▄▄▄▄▄▄▄▄▄▄▄   ▄▄▄▄▄▄▄▄▄▄▄
 ▀████████████████▄  ████                 █████   ▀████▄    ▄████▀  ▄██████████████   ████████████▀  ▄█████████████▀  ▄█████████████▄
              ▀████  ████               ▄███▀███▄   ▀████▄▄████▀               ████   ████                ████                   ▀████
   ▄▄▄▄▄▄▄▄▄▄▄█████  ████              ████   ████    ▀██████▀      ██████████████▄   ████████████▀       ████       ▄▄▄▄▄▄▄▄▄▄▄▄████▀
   ██████████████▀   ████            ▄███▀     ▀███▄    ████        ████        ████  ████                ████       ██████████████▀
   ████              ████████████▀  ████   ██████████   ████        ████████████████  █████████████▀      ████       ████      ▀████▄
   ▀▀▀▀              ▀▀▀▀▀▀▀▀▀▀▀   ▀▀▀▀   ▀▀▀▀▀▀▀▀▀▀▀▀  ▀▀▀▀        ▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀   ▀▀▀▀▀▀▀▀▀▀▀▀        ▀▀▀▀       ▀▀▀▀        ▀▀▀▀▀

#1 CRYPTO CASINO & SPORTSBOOK
 WELCOME
BONUS
.INSTANT & FAST.
.TRANSACTION.....
.PROVABLY FAIR.
......& SECURE......
.24/7 CUSTOMER.
............SUPPORT.
BTC      |      ETH      |      LTC      |      XRP      |      XMR      |      BNB      |     more
Pacho Vladigerov
Newbie
*
Offline Offline

Activity: 2
Merit: 0


View Profile
July 24, 2019, 04:24:44 AM
 #774

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
gesrhon7
Newbie
*
Offline Offline

Activity: 45
Merit: 0


View Profile
July 24, 2019, 02:52:24 PM
 #775

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.
HCP
Legendary
*
Offline Offline

Activity: 1162
Merit: 1899

<insert witty quote here>


View Profile
July 25, 2019, 11:02:31 PM
 #776

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.

Nnuego
Jr. Member
*
Offline Offline

Activity: 224
Merit: 2


View Profile
July 27, 2019, 04:56:56 PM
 #777

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

▀▀▀▀▀▀▀▀▀▀▀▀▀▀
Cannacor.io ║Cannacor:Cannabis Cultivation║ (https://cannacor.io/)
▄▄▄▄▄▄▄
TheRealAwesome31312
Member
**
Offline Offline

Activity: 140
Merit: 19


View Profile
August 01, 2019, 02:06:01 PM
 #778

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?
LTU_btc
Hero Member
*****
Offline Offline

Activity: 1428
Merit: 758



View Profile WWW
August 01, 2019, 04:07:46 PM
 #779

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://bitcointalk.org/index.php?topic=5089777.0




▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄    ▄▄▄▄                  ▄▄▄   ▄▄▄▄▄        ▄▄▄▄▄   ▄▄▄▄▄▄▄▄▄▄▄▄    ▄▄▄▄▄▄▄▄▄▄▄▄▄▄   ▄▄▄▄▄▄▄▄▄▄▄▄▄▄   ▄▄▄▄▄▄▄▄▄▄▄
 ▀████████████████▄  ████                 █████   ▀████▄    ▄████▀  ▄██████████████   ████████████▀  ▄█████████████▀  ▄█████████████▄
              ▀████  ████               ▄███▀███▄   ▀████▄▄████▀               ████   ████                ████                   ▀████
   ▄▄▄▄▄▄▄▄▄▄▄█████  ████              ████   ████    ▀██████▀      ██████████████▄   ████████████▀       ████       ▄▄▄▄▄▄▄▄▄▄▄▄████▀
   ██████████████▀   ████            ▄███▀     ▀███▄    ████        ████        ████  ████                ████       ██████████████▀
   ████              ████████████▀  ████   ██████████   ████        ████████████████  █████████████▀      ████       ████      ▀████▄
   ▀▀▀▀              ▀▀▀▀▀▀▀▀▀▀▀   ▀▀▀▀   ▀▀▀▀▀▀▀▀▀▀▀▀  ▀▀▀▀        ▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀   ▀▀▀▀▀▀▀▀▀▀▀▀        ▀▀▀▀       ▀▀▀▀        ▀▀▀▀▀

#1 CRYPTO CASINO & SPORTSBOOK
 WELCOME
BONUS
.INSTANT & FAST.
.TRANSACTION.....
.PROVABLY FAIR.
......& SECURE......
.24/7 CUSTOMER.
............SUPPORT.
BTC      |      ETH      |      LTC      |      XRP      |      XMR      |      BNB      |     more
skywalker925
Newbie
*
Offline Offline

Activity: 4
Merit: 0


View Profile WWW
August 14, 2019, 06:19:00 AM
 #780

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-----
Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 [39] 40 »
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!