📅 Original date posted:2014-04-22
📝 Original message:On Tuesday, 22 April 2014, at 10:06 am, Jan Møller wrote:
> This is a very useful BIP, and I am very much looking forward to
> implementing it in Mycelium, in particular for bip32 wallets.
> To me this is not about whether to use SSS instead of multisig
> transactions. In the end you want to protect a secret (be it a HD master
> seed or a private key) in such a way that you can recover it in case of
> partial theft/loss. Whether I'll use the master seed to generate keys that
> are going to be used for multisig transactions is another discussion IMO.
>
> A few suggestions:
> - I think it is very useful to define different prefixes for testnet
> keys/seeds. As a developer I use the testnet every day, and many of our
> users use it for trying out new functionality. Mixing up keys meant for
> testnet and mainnet is bad.
A fair point. I'll add some prefixes for testnet.
> - Please allow M=1. From a usability point of view it makes sense to allow
> the user to select 1 share if that is what he wants.
How does that make sense? Decomposing a key/seed into 1 share is functionally equivalent to dispensing with the secret sharing scheme entirely.
> I have no strong opinions of whether to use GF(2^8) over Shamir's Secret
> Sharing, but the simplicity of GF(2^8) is appealing.
I'll welcome forks of my draft BIP. I don't really have the inclination to research GF(2^8) secret sharing schemes and write an implementation at the present time, but if someone wants to take my BIP in that direction, then okay.
Matt Whitlock [ARCHIVE] /
npub17q…upwet
2023-06-07 15:17:10
in reply to nevent1q…8zg7
Author Public Key
npub17qxssk9sj2r7jswvh3y32e7vwz7mcckhz33gk9nurdmw0lhsfkgswupwetPublished at
2023-06-07 15:17:10Event JSON
{
"id": "606d2ad25cab21886dc853643411c0cc99c3a9262f362f32cc51292fbda27d73",
"pubkey": "f00d0858b09287e941ccbc491567cc70bdbc62d714628b167c1b76e7fef04d91",
"created_at": 1686151030,
"kind": 1,
"tags": [
[
"e",
"ec3db7ea61043d2181c683590cc6472afc1e727a155c1437be680d2ee4f9939c",
"",
"root"
],
[
"e",
"c7516cd95104724531dc5a445b873015b8bfe1c5acfa521bcbd3d1cdf40011c5",
"",
"reply"
],
[
"p",
"832a1862818484be65dd3985830db0dfab117e3f64b3ebf63a3062de9f57d848"
]
],
"content": "📅 Original date posted:2014-04-22\n📝 Original message:On Tuesday, 22 April 2014, at 10:06 am, Jan Møller wrote:\n\u003e This is a very useful BIP, and I am very much looking forward to\n\u003e implementing it in Mycelium, in particular for bip32 wallets.\n\u003e To me this is not about whether to use SSS instead of multisig\n\u003e transactions. In the end you want to protect a secret (be it a HD master\n\u003e seed or a private key) in such a way that you can recover it in case of\n\u003e partial theft/loss. Whether I'll use the master seed to generate keys that\n\u003e are going to be used for multisig transactions is another discussion IMO.\n\u003e \n\u003e A few suggestions:\n\u003e - I think it is very useful to define different prefixes for testnet\n\u003e keys/seeds. As a developer I use the testnet every day, and many of our\n\u003e users use it for trying out new functionality. Mixing up keys meant for\n\u003e testnet and mainnet is bad.\n\nA fair point. I'll add some prefixes for testnet.\n\n\u003e - Please allow M=1. From a usability point of view it makes sense to allow\n\u003e the user to select 1 share if that is what he wants.\n\nHow does that make sense? Decomposing a key/seed into 1 share is functionally equivalent to dispensing with the secret sharing scheme entirely.\n\n\u003e I have no strong opinions of whether to use GF(2^8) over Shamir's Secret\n\u003e Sharing, but the simplicity of GF(2^8) is appealing.\n\nI'll welcome forks of my draft BIP. I don't really have the inclination to research GF(2^8) secret sharing schemes and write an implementation at the present time, but if someone wants to take my BIP in that direction, then okay.",
"sig": "6a0644f6542b948c21e1b42a52b63b9913517114ac41c310e5ca45958eaf31c117b5415d1d3cd5b4936c2f953f0371c8d389af40269b1f1cfa1616633fe5b7c7"
}