📅 Original date posted:2017-12-21
📝 Original message:In all seriousness, being able to sign a message is an important feature whether it is with Bitcoin Core or, with some other method. It is a good feature and it would be worthwhile IMHO to update it for SegWit addresses. I don't know about renewing it altogether, I like the current simplicity.
Regards,
Damian Williamson
------------------------------------
Sometimes I like to sign a message just to verify that is what I have said.
-
Bitcoin: 1PMUf9aaQ41M4bgVbCAPVwAeuKvj8CwxJg
------------------------------------
Signature:
HwJPqyWF0CbdsR7x737HbNIDoRufsrMI5XYQsKZ+MrWCJ6K7imtLY00sTCmSMDigZxRuoxyYZyQUw/lL0m/MV9M=
(Of course, signed messages will verify better usually with plain text and not HTML interpreted email - need a switch for outlook.com to send plaintext.)
________________________________
From: bitcoin-dev-bounces at lists.linuxfoundation.org <bitcoin-dev-bounces at lists.linuxfoundation.org> on behalf of Mark Friedenbach via bitcoin-dev <bitcoin-dev at lists.linuxfoundation.org>
Sent: Wednesday, 20 December 2017 8:58 AM
To: Pavol Rusnak; Bitcoin Protocol Discussion
Subject: Re: [bitcoin-dev] Sign / Verify message against SegWit P2SH addresses.
For what it’s worth, I think it would be quite easy to do better than the implied solution of rejiggering the message signing system to support non-P2PKH scripts. Instead, have the signature be an actual bitcoin transaction with inputs that have the script being signed. Use the salted hash of the message being signed as the FORKID as if this were a spin-off with replay protection. This accomplishes three things:
(1) This enables signing by any infrastructure out there — including hardware wallets and 2FA signing services — that have enabled support for FORKID signing, which is a wide swath of the ecosystem because of Bitcoin Cash and Bitcoin Gold.
(2) It generalizes the message signing to allow multi-party signing setups as complicated (via sighash, etc.) as those bitcoin transactions allow, using existing and future tools based on Partially Signed Bitcoin Transactions; and
(3) It unifies a single approach for message signing, proof of reserve (where the inputs are actual UTXOs), and off-chain colored coins.
There’s the issue of size efficiency, but for the single-party message signing application that can be handled by a BIP that specifies a template for constructing the pseudo-transaction and its inputs from a raw script.
Mark
> On Dec 19, 2017, at 1:36 PM, Pavol Rusnak via bitcoin-dev <bitcoin-dev at lists.linuxfoundation.org> wrote:
>
> On 08/12/17 19:25, Dan Bryant via bitcoin-dev wrote:
>> I know there are posts, and an issue opened against it, but is there
>> anyone writing a BIP for Sign / Verify message against a SegWit address?
>
> Dan, are you still planning to write this BIP?
>
> --
> Best Regards / S pozdravom,
>
> Pavol "stick" Rusnak
> CTO, SatoshiLabs
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev at lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
_______________________________________________
bitcoin-dev mailing list
bitcoin-dev at lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20171221/2ae67657/attachment.html>;
Damian Williamson [ARCHIVE] /
npub1sp…8lz2h
2023-06-07 18:08:34
in reply to nevent1q…2ef2
Author Public Key
npub1spe4rkz350zpn7h2pz07t8sdwgt440zmx9k530afwj6gmq7q0lksh8lz2hPublished at
2023-06-07 18:08:34Event JSON
{
"id": "5fccc2621899e39fd46d29ee243f857388be62f58b27dcd6e8bdb1cce7db914b",
"pubkey": "807351d851a3c419faea089fe59e0d72175abc5b316d48bfa974b48d83c07fed",
"created_at": 1686161314,
"kind": 1,
"tags": [
[
"e",
"4906415372c36d75e1516dbda339366413e39baccb7415b861a058c35dd3d801",
"",
"root"
],
[
"e",
"c74c97ce68fdaa78a08faaaf422205fd146306db8f8ab43c7681034a358cd0e7",
"",
"reply"
],
[
"p",
"1c61d995949cbfaf14f767784e166bde865c7b8783d7aa3bf0a1d014b70c0069"
]
],
"content": "📅 Original date posted:2017-12-21\n📝 Original message:In all seriousness, being able to sign a message is an important feature whether it is with Bitcoin Core or, with some other method. It is a good feature and it would be worthwhile IMHO to update it for SegWit addresses. I don't know about renewing it altogether, I like the current simplicity.\n\n\nRegards,\n\nDamian Williamson\n\n\n------------------------------------\n\nSometimes I like to sign a message just to verify that is what I have said.\n\n-\n\nBitcoin: 1PMUf9aaQ41M4bgVbCAPVwAeuKvj8CwxJg\n\n------------------------------------\n\nSignature:\nHwJPqyWF0CbdsR7x737HbNIDoRufsrMI5XYQsKZ+MrWCJ6K7imtLY00sTCmSMDigZxRuoxyYZyQUw/lL0m/MV9M=\n\n(Of course, signed messages will verify better usually with plain text and not HTML interpreted email - need a switch for outlook.com to send plaintext.)\n________________________________\nFrom: bitcoin-dev-bounces at lists.linuxfoundation.org \u003cbitcoin-dev-bounces at lists.linuxfoundation.org\u003e on behalf of Mark Friedenbach via bitcoin-dev \u003cbitcoin-dev at lists.linuxfoundation.org\u003e\nSent: Wednesday, 20 December 2017 8:58 AM\nTo: Pavol Rusnak; Bitcoin Protocol Discussion\nSubject: Re: [bitcoin-dev] Sign / Verify message against SegWit P2SH addresses.\n\nFor what it’s worth, I think it would be quite easy to do better than the implied solution of rejiggering the message signing system to support non-P2PKH scripts. Instead, have the signature be an actual bitcoin transaction with inputs that have the script being signed. Use the salted hash of the message being signed as the FORKID as if this were a spin-off with replay protection. This accomplishes three things:\n\n(1) This enables signing by any infrastructure out there — including hardware wallets and 2FA signing services — that have enabled support for FORKID signing, which is a wide swath of the ecosystem because of Bitcoin Cash and Bitcoin Gold.\n\n(2) It generalizes the message signing to allow multi-party signing setups as complicated (via sighash, etc.) as those bitcoin transactions allow, using existing and future tools based on Partially Signed Bitcoin Transactions; and\n\n(3) It unifies a single approach for message signing, proof of reserve (where the inputs are actual UTXOs), and off-chain colored coins.\n\nThere’s the issue of size efficiency, but for the single-party message signing application that can be handled by a BIP that specifies a template for constructing the pseudo-transaction and its inputs from a raw script.\n\nMark\n\n\u003e On Dec 19, 2017, at 1:36 PM, Pavol Rusnak via bitcoin-dev \u003cbitcoin-dev at lists.linuxfoundation.org\u003e wrote:\n\u003e\n\u003e On 08/12/17 19:25, Dan Bryant via bitcoin-dev wrote:\n\u003e\u003e I know there are posts, and an issue opened against it, but is there\n\u003e\u003e anyone writing a BIP for Sign / Verify message against a SegWit address?\n\u003e\n\u003e Dan, are you still planning to write this BIP?\n\u003e\n\u003e --\n\u003e Best Regards / S pozdravom,\n\u003e\n\u003e Pavol \"stick\" Rusnak\n\u003e CTO, SatoshiLabs\n\u003e _______________________________________________\n\u003e bitcoin-dev mailing list\n\u003e bitcoin-dev at lists.linuxfoundation.org\n\u003e https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev\n\n_______________________________________________\nbitcoin-dev mailing list\nbitcoin-dev at lists.linuxfoundation.org\nhttps://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20171221/2ae67657/attachment.html\u003e",
"sig": "de50916bb74b9e10d357749c920b92ad584c7c34f04bb8e99346679a283ba20f44a34dcecbd023a900b3792cb728de7585b20ae534aa7c97a545db77d2aadd7a"
}