📅 Original date posted:2014-04-22
📝 Original message: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.
- 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.
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.
- Jan
On Fri, Apr 11, 2014 at 12:31 AM, Nikita Schmidt <
nikita at megiontechnologies.com> wrote:
> > What do you think a big-integer division by a word-sized divisor *is*?
> Obviously rolling your own is always an option. Are you just saying that
> Base58 encoding and decoding is easier than Shamir's Secret Sharing because
> the divisors are small?
>
> Well, yes, to be fair, in fact it is. The small divisor and lack of
> modulo arithmetic make base-58 encoding and decoding noticeably
> smaller and easier than Shamir's Secret Sharing over GF(P256).
>
>
> ------------------------------------------------------------------------------
> Put Bad Developers to Shame
> Dominate Development with Jenkins Continuous Integration
> Continuously Automate Build, Test & Deployment
> Start a new project now. Try Jenkins in the cloud.
> http://p.sf.net/sfu/13600_Cloudbees
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20140422/1ba69db4/attachment.html>;
Jan Møller [ARCHIVE] /
npub1sv…jg7a4
2023-06-07 15:17:10
in reply to nevent1q…qty5
Author Public Key
npub1sv4psc5psjztuewa8xzcxrdsm743zl3lvje7ha36xp3da86hmpyqdjg7a4Published at
2023-06-07 15:17:10Event JSON
{
"id": "c7516cd95104724531dc5a445b873015b8bfe1c5acfa521bcbd3d1cdf40011c5",
"pubkey": "832a1862818484be65dd3985830db0dfab117e3f64b3ebf63a3062de9f57d848",
"created_at": 1686151030,
"kind": 1,
"tags": [
[
"e",
"ec3db7ea61043d2181c683590cc6472afc1e727a155c1437be680d2ee4f9939c",
"",
"root"
],
[
"e",
"3ca22aa25ad9807329f79448d3ab4233b89ff5019807c7ef50b28a041fe7f5be",
"",
"reply"
],
[
"p",
"ee72be6617b6118354dee0b3e02f3d01e8d2b6b83d8437181b3014394ff468f7"
]
],
"content": "📅 Original date posted:2014-04-22\n📝 Original message:This is a very useful BIP, and I am very much looking forward to\nimplementing it in Mycelium, in particular for bip32 wallets.\nTo me this is not about whether to use SSS instead of multisig\ntransactions. In the end you want to protect a secret (be it a HD master\nseed or a private key) in such a way that you can recover it in case of\npartial theft/loss. Whether I'll use the master seed to generate keys that\nare going to be used for multisig transactions is another discussion IMO.\n\nA few suggestions:\n - I think it is very useful to define different prefixes for testnet\nkeys/seeds. As a developer I use the testnet every day, and many of our\nusers use it for trying out new functionality. Mixing up keys meant for\ntestnet and mainnet is bad.\n - Please allow M=1. From a usability point of view it makes sense to allow\nthe user to select 1 share if that is what he wants.\n\nI have no strong opinions of whether to use GF(2^8) over Shamir's Secret\nSharing, but the simplicity of GF(2^8) is appealing.\n\n - Jan\n\n\nOn Fri, Apr 11, 2014 at 12:31 AM, Nikita Schmidt \u003c\nnikita at megiontechnologies.com\u003e wrote:\n\n\u003e \u003e What do you think a big-integer division by a word-sized divisor *is*?\n\u003e Obviously rolling your own is always an option. Are you just saying that\n\u003e Base58 encoding and decoding is easier than Shamir's Secret Sharing because\n\u003e the divisors are small?\n\u003e\n\u003e Well, yes, to be fair, in fact it is. The small divisor and lack of\n\u003e modulo arithmetic make base-58 encoding and decoding noticeably\n\u003e smaller and easier than Shamir's Secret Sharing over GF(P256).\n\u003e\n\u003e\n\u003e ------------------------------------------------------------------------------\n\u003e Put Bad Developers to Shame\n\u003e Dominate Development with Jenkins Continuous Integration\n\u003e Continuously Automate Build, Test \u0026 Deployment\n\u003e Start a new project now. Try Jenkins in the cloud.\n\u003e http://p.sf.net/sfu/13600_Cloudbees\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-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20140422/1ba69db4/attachment.html\u003e",
"sig": "7ecb33b76e3999384220adeee366958ec1e7136f4790d68ea1b63b731431a1902cd9a1b182b4afc7a758a918b01aa4a2a00adfa6fc283f93158994e123afbd3c"
}