📅 Original date posted:2014-03-29
📝 Original message: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.
On Mar 29, 2014, at 9:05 AM, Matt Whitlock <bip at mattwhitlock.name> wrote:
> Abstract: A method is described for dividing a Bitcoin private key into shares in a manner such that the key can be reconstituted from any sufficiently large subset of the shares but such that individually the shares do not reveal any information about the key. This method is commonly known as Shamir's Secret Sharing Scheme. Additionally, an encoding methodology is proposed to standardize transmission and storage of shares.
>
> Complete BIP: https://github.com/whitslack/btctool/blob/bip/bip-xxxx.mediawiki
>
> I am looking to have this BIP assigned a number and added to the bitcoin/bips repository. I invite any comments, questions, or suggestions.
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 841 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20140329/f9a99d19/attachment.sig>;
Chris Beams [ARCHIVE] /
npub1vl…69gsv
2023-06-07 15:16:35
in reply to nevent1q…t8j3
Author Public Key
npub1vlgx34nzzqzrqq0uujch65yyzyknuduuqulj24ydlnarhwdhwzlsx69gsvPublished at
2023-06-07 15:16:35Event JSON
{
"id": "30c59b9ce255d028bf68167ffe025f1dd9bbc70e87431efe325797f2cbac5be8",
"pubkey": "67d068d66210043001fce4b17d5084112d3e379c073f25548dfcfa3bb9b770bf",
"created_at": 1686150995,
"kind": 1,
"tags": [
[
"e",
"cd470d06d90a3107c21da4b48b344ebdd3b4ab813362bb85b0e7a02311012700",
"",
"root"
],
[
"e",
"f1ba9fa317af3301f74fd2e1fd9921e66984f3dde9aa5121a786d743310a9391",
"",
"reply"
],
[
"p",
"c632841665fccdabf021322b1d969539c9c1f829ceed38844fea24e8512962d7"
]
],
"content": "📅 Original date posted:2014-03-29\n📝 Original message: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\nOn Mar 29, 2014, at 9:05 AM, Matt Whitlock \u003cbip at mattwhitlock.name\u003e wrote:\n\n\u003e Abstract: A method is described for dividing a Bitcoin private key into shares in a manner such that the key can be reconstituted from any sufficiently large subset of the shares but such that individually the shares do not reveal any information about the key. This method is commonly known as Shamir's Secret Sharing Scheme. Additionally, an encoding methodology is proposed to standardize transmission and storage of shares.\n\u003e \n\u003e Complete BIP: https://github.com/whitslack/btctool/blob/bip/bip-xxxx.mediawiki\n\u003e \n\u003e I am looking to have this BIP assigned a number and added to the bitcoin/bips repository. I invite any comments, questions, or suggestions.\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\n-------------- next part --------------\nA non-text attachment was scrubbed...\nName: signature.asc\nType: application/pgp-signature\nSize: 841 bytes\nDesc: Message signed with OpenPGP using GPGMail\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20140329/f9a99d19/attachment.sig\u003e",
"sig": "e70fcd6966c8d9c1d9eaf80f42015433cdf7da5eb56d2bb3571d2bd18515827d8c51a0d0a5aa51f2346a115462ebb4c1fe887b7e1c166384528ee8aa613b3456"
}