📅 Original date posted:2014-03-29 📝 Original message:The comparison with ...

Jeff Garzik [ARCHIVE] /

npub1kf0…3f58

2023-06-07 15:16:36

in reply to nevent1q…8yzh

📅 Original date posted:2014-03-29
📝 Original message:The comparison with multisig fails to mention that multi-signature
transactions explicitly define security at the transaction level.
This permits fine-grained specificity of what a key holder may
approve.

Shamir is much more coarse-grained. You reconstitute a private key,
which may then be used to control anything that key controls. Thus,
in addition to Shamir itself, you need policies such as "no key
reuse."

My first impression of Shamir many moons ago was "cool!" but that's
since been tempered by thinking through the use cases. Shamir has a
higher D.I.Y. factor, with a correspondingly larger surface of
things-that-could-go-wrong, IMO.

(None of this implies making an informational BIP lacks value; I'm all
for an informational BIP)

On Sat, Mar 29, 2014 at 7:54 AM, Chris Beams <chris at beams.io> wrote:
> Enlightening; thanks, Matt. And apologies to the list for my earlier inadvertent double-post.
>
> On Mar 29, 2014, at 12:16 PM, Matt Whitlock <bip at mattwhitlock.name> wrote:
>
>> On Saturday, 29 March 2014, at 10:08 am, Chris Beams wrote:
>>> Matt, could you expand on use cases for which you see Shamir's Secret Sharing Scheme as the best tool for the job? In particular, when do you see that it would be superior to simply going with multisig in the first place? Perhaps you see these as complimentary approaches, toward defense-in-depth? In any case, the Motivation and Rationale sections of the BIP in its current form are silent on these questions.
>>
>> I have added two new sections to address your questions.
>>
>> https://github.com/whitslack/btctool/blob/bip/bip-xxxx.mediawiki
>
>
> ------------------------------------------------------------------------------
>
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>

--
Jeff Garzik
Bitcoin core developer and open source evangelist
BitPay, Inc. https://bitpay.com/

Author Public Key

npub1kf0ppcjaguxekg24yx6smgxlu73qn0k8lm0t2wrqc0scpl7u3sgsmf3f58

Seen on

wss://relay.noswhere.com wss://relay.nostr.band

Show more details

Published at

2023-06-07 15:16:36

Kind type

1 Short Text Note

Event JSON

{ "id": "0de64f6f3bf6f4927935861cf7f0580e224e7163b46d7e2dde9e5295656b09ec", "pubkey": "b25e10e25d470d9b215521b50da0dfe7a209bec7fedeb53860c3e180ffdc8c11", "created_at": 1686150996, "kind": 1, "tags": [ [ "e", "cd470d06d90a3107c21da4b48b344ebdd3b4ab813362bb85b0e7a02311012700", "", "root" ], [ "e", "2cd29f52ed4909d48347a57aefaa4d7ad49cd00d6d88d841e189e82abbe32574", "", "reply" ], [ "p", "67d068d66210043001fce4b17d5084112d3e379c073f25548dfcfa3bb9b770bf" ] ], "content": "📅 Original date posted:2014-03-29\n📝 Original message:The comparison with multisig fails to mention that multi-signature\ntransactions explicitly define security at the transaction level.\nThis permits fine-grained specificity of what a key holder may\napprove.\n\nShamir is much more coarse-grained. You reconstitute a private key,\nwhich may then be used to control anything that key controls. Thus,\nin addition to Shamir itself, you need policies such as \"no key\nreuse.\"\n\nMy first impression of Shamir many moons ago was \"cool!\" but that's\nsince been tempered by thinking through the use cases. Shamir has a\nhigher D.I.Y. factor, with a correspondingly larger surface of\nthings-that-could-go-wrong, IMO.\n\n(None of this implies making an informational BIP lacks value; I'm all\nfor an informational BIP)\n\n\n\n\nOn Sat, Mar 29, 2014 at 7:54 AM, Chris Beams \u003cchris at beams.io\u003e wrote:\n\u003e Enlightening; thanks, Matt. And apologies to the list for my earlier inadvertent double-post.\n\u003e\n\u003e On Mar 29, 2014, at 12:16 PM, Matt Whitlock \u003cbip at mattwhitlock.name\u003e wrote:\n\u003e\n\u003e\u003e On Saturday, 29 March 2014, at 10:08 am, Chris Beams wrote:\n\u003e\u003e\u003e Matt, could you expand on use cases for which you see Shamir's Secret Sharing Scheme as the best tool for the job? In particular, when do you see that it would be superior to simply going with multisig in the first place? Perhaps you see these as complimentary approaches, toward defense-in-depth? In any case, the Motivation and Rationale sections of the BIP in its current form are silent on these questions.\n\u003e\u003e\n\u003e\u003e I have added two new sections to address your questions.\n\u003e\u003e\n\u003e\u003e https://github.com/whitslack/btctool/blob/bip/bip-xxxx.mediawiki\n\u003e\n\u003e\n\u003e ------------------------------------------------------------------------------\n\u003e\n\u003e _______________________________________________\n\u003e Bitcoin-development mailing list\n\u003e Bitcoin-development at lists.sourceforge.net\n\u003e https://lists.sourceforge.net/lists/listinfo/bitcoin-development\n\u003e\n\n\n\n-- \nJeff Garzik\nBitcoin core developer and open source evangelist\nBitPay, Inc. https://bitpay.com/", "sig": "df4545812ac04847d5fc3450d3067be79b511b4ac465537a128df97970c9668d1356fcc141f4b0daf5f00e8f18712d1a02666f9ef8e270475dd9550983cbc5f1" }