rich1.0npub1e7vdq905zr4xjr5nxuz58l9jcvffxq728ysl6m2xxgr024mjy5vq4fg307https://nostr.ae/npub1e7vdq905zr4xjr5nxuz58l9jcvffxq728ysl6m2xxgr024mjy5vq4fg307njumphttps://nostr.ae📅 Original date posted:2018-03-14 📝 Original message:Hello, I am considering writing a replacement for the message signing tools that are currently broken for all but the legacy 1xx addresses. The approach (suggested by Pieter Wuille) is to do a script based approach. This does not seem to require a lot of effort for implementing in Bitcoin Core*. Below is my proposal for this system: A new structure SignatureProof is added, which is a simple scriptSig & witnessProgram container that can be serialized. This is passed out from/into the signer/verifier. RPC commands: sign <address> <message> [<prehashed>=false] Generates a signature proof for <message> using the same method that would be used to spend coins sent to <address>.** verify <address> <message> <proof> [<prehashed>=false] Deserializes and executes the proof using a custom signature checker whose sighash is derived from <message>. Returns true if the check succeeds, and false otherwise. The scriptPubKey is derived directly from <address>.** Feedback welcome. -Kalle. (*) Looks like you can simply use VerifyScript with a new signature checker class. (h/t Nicolas Dorier) (**) If <prehashed> is true, <message> is the sighash, otherwise sighash=sha256d(message).