New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bitcoin-qt Sign Message Feature -- Put header/footer around message. #2737

Closed
monohydroxy opened this Issue Jun 4, 2013 · 6 comments

Comments

Projects
None yet
5 participants
@monohydroxy
Copy link

monohydroxy commented Jun 4, 2013

It seems to me the Bitcoin-qt 'Sign Message' feature is a little harder to use than it should be. Once all of the fields are filled in, it would be more convenient to output a block of text that contains all of the information that should be pasted in to a message. Also a simple parser that expects this format should be put into the Verify Message side of things.

It's worth a note that Armory and MultiBit are working on this feature. It would be nice if they all were compatible.

Here's an example (taken from a PGP Signed message):

-----BEGIN BITCOIN SIGNED MESSAGE-----
Address: 1Bitcoinasdfasdfsadfsadfsadf

Because anyone can claim to be me. There's no validation of the user
name or email address when someone posts a comment. While I do try to
remove imposters, some may slip through. By signing my comments using
this technique, anyone can independently verify that I was the author of
the message by validating the signature.
-----BEGIN BITCOIN SIGNATURE-----
Version: Bitcoin-qt (1.0)

iD8DBQFFxqRFCMEe9B/8oqERAqA2AJ91Tx4RziVzY4eR4Ms4MFsKAMqOoQCgg7y6e5AJIRuLUIUikjNWQIW
-----END BITCOIN SIGNATURE-----

@luke-jr

This comment has been minimized.

Copy link
Member

luke-jr commented Jun 4, 2013

There is a standard for this format. It would be a shame to not use it.

@laanwj

This comment has been minimized.

Copy link
Member

laanwj commented Jun 5, 2013

Can you put a link to that standard?

@hasib145

This comment has been minimized.

Copy link

hasib145 commented Jun 12, 2013

I think its a standard format. Everybody can apply it.http://www.coinsigner.com

@jgarzik

This comment has been minimized.

Copy link
Contributor

jgarzik commented Aug 21, 2013

@luke-jr ping?

@luke-jr

This comment has been minimized.

Copy link
Member

luke-jr commented Aug 21, 2013

RFC 4880 describes many things, including signature formats.

@laanwj laanwj removed the Refactoring label Feb 9, 2016

@laanwj laanwj closed this Feb 9, 2016

@laanwj

This comment has been minimized.

Copy link
Member

laanwj commented Feb 9, 2016

Closing this, as it is extremely unlikely the signed message format will be changed anymore after all those years.

If you do intend to do this, it would make sense as a BIP proposal, especially as the goal is to coordinate between different software.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment