Author: Alan Reiner 2013-04-14 18:24:34
Published on: 2013-04-14T18:24:34+00:00
Peter Todd and Alan Reiner discuss the extension of message signing by adding a proper ASCII-armored format to it. The new format will encode the signed message next to the signature, so there's no ambiguity about what was signed. It will be primarily offered as an option for users to copy an ASCII-armored block of text into the client app. The app pops up with a window that says "The following message has a valid signature from address 1XKjf32kJbf...". The format to follow should be RFC2440, section 7 "Cleartext signature framework". This method doesn't need to be done before other signmessage changes. There may be an issue passing \r's through the RPC interface; the RFC specifies CRLF line endings. Alan will lead by example and implement the format in Armory.
Updated on: 2023-06-06T14:57:02.650941+00:00