📅 Original date posted:2017-12-09
📝 Original message:I would like to see this specifically for P2SH-PWPKH and/or native SegWit bech32 addresses.
Use cases I can think of are "I'm the whale in charge of these funds, listen to me" and some form of polling.
It's nice if funds aren't excluded from these type of functionalities just because they have a complicated redeem script. So something more generic like the Elements implementation / suggestion Greg Maxwell referred to in the Github thread would be nice too.
Is it also useful or possible to sign a message proving you are able to redeem some arbitrary branch in a MAST-like tree of scripts? What about being a minority part of a multisig?
All these features have privacy trade-offs, as well as perhaps security trade-offs, e.g. when you reveal a public key that was otherwise hidden behind a hash (i.e. if someone were to break secp256k1, they'd first organize a popular poll).
There's no BIP for the current message signing mechanism either afaik.
Sjors
> Op 8 dec. 2017, om 19:25 heeft Dan Bryant via bitcoin-dev <bitcoin-dev at lists.linuxfoundation.org> het volgende geschreven:
>
> 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?
>
> I realize it is not a feature in wide use, but I think it still serves an important purpose, such as when proof of assets are requested.
>
> ref: https://github.com/bitcoin/bitcoin/issues/10542 <https://github.com/bitcoin/bitcoin/issues/10542>;
>
> _______________________________________________
> 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/20171209/621ffb05/attachment.html>;
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: Message signed with OpenPGP
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20171209/621ffb05/attachment.sig>;
Sjors Provoost [ARCHIVE] /
npub1ux…7wq7p
2023-06-07 18:08:33
in reply to nevent1q…ves2
Author Public Key
npub1uxks6rvrzqljyfp92sffgqypf8fpts0pv2dshvmmnrse76v0avlqy7wq7pPublished at
2023-06-07 18:08:33Event JSON
{
"id": "c011a4c9fe4e672d761ee0b3cffc55c830af2604fb45de2cea10da4b0591b877",
"pubkey": "e1ad0d0d83103f222425541294008149d215c1e1629b0bb37b98e19f698feb3e",
"created_at": 1686161313,
"kind": 1,
"tags": [
[
"e",
"4906415372c36d75e1516dbda339366413e39baccb7415b861a058c35dd3d801",
"",
"root"
],
[
"e",
"1d0c4e546678aff9c1b449ec74e808b411115e2033b0018b6eed7a7a19e8ad39",
"",
"reply"
],
[
"p",
"bbe41ddf98a712e588455717ec8f3f0893c530699af0a98cbe86c0af0138b25d"
]
],
"content": "📅 Original date posted:2017-12-09\n📝 Original message:I would like to see this specifically for P2SH-PWPKH and/or native SegWit bech32 addresses.\n\nUse cases I can think of are \"I'm the whale in charge of these funds, listen to me\" and some form of polling.\n\nIt's nice if funds aren't excluded from these type of functionalities just because they have a complicated redeem script. So something more generic like the Elements implementation / suggestion Greg Maxwell referred to in the Github thread would be nice too.\n\nIs it also useful or possible to sign a message proving you are able to redeem some arbitrary branch in a MAST-like tree of scripts? What about being a minority part of a multisig?\n\nAll these features have privacy trade-offs, as well as perhaps security trade-offs, e.g. when you reveal a public key that was otherwise hidden behind a hash (i.e. if someone were to break secp256k1, they'd first organize a popular poll).\n\nThere's no BIP for the current message signing mechanism either afaik.\n\nSjors\n\n\u003e Op 8 dec. 2017, om 19:25 heeft Dan Bryant via bitcoin-dev \u003cbitcoin-dev at lists.linuxfoundation.org\u003e het volgende geschreven:\n\u003e \n\u003e 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?\n\u003e \n\u003e I realize it is not a feature in wide use, but I think it still serves an important purpose, such as when proof of assets are requested.\n\u003e \n\u003e ref: https://github.com/bitcoin/bitcoin/issues/10542 \u003chttps://github.com/bitcoin/bitcoin/issues/10542\u003e\n\u003e \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-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20171209/621ffb05/attachment.html\u003e\n-------------- next part --------------\nA non-text attachment was scrubbed...\nName: signature.asc\nType: application/pgp-signature\nSize: 833 bytes\nDesc: Message signed with OpenPGP\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20171209/621ffb05/attachment.sig\u003e",
"sig": "2a38314e5537c0097cb3f7e6511995071714d178019bfcde58e768d50e6ea658c5bec2f1ca7f2ffb0850f8002ea8f654499a68cb5c77c05e2a8d3226dd752fbf"
}