Posted by Damian Williamson
Mar 15, 2018/10:15 UTC
In a Bitcoin-dev mailing list, Karl Johan Alm proposed to write 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. The proposal is to add a new structure called SignatureProof which is a simple scriptSig and witnessProgram container that can be serialized. The structure is passed out from or into the signer/verifier with two RPC commands: sign and verify. Luke Dashjr suggests that the signature format should not only support "proof I receive at this address" but also "proof of funds" since it is a popular misuse of the current message signing which does not actually prove funds at all. It needs to be capable of signing for multiple inputs. Preferably, it should also avoid disclosing the public key for existing or future UTXOs. However, it may not be possible without something MAST-like first.
TLDR
We’ll email you summaries of the latest discussions from authoritative bitcoin sources, like bitcoin-dev, lightning-dev, and Delving Bitcoin.
We'd love to hear your feedback on this project?
Give Feedback