📅 Original date posted:2014-03-12
📝 Original message:On Mar 12, 2014, at 6:11 AM, Pavol Rusnak <stick at gk2.sk> wrote:
> On 03/12/2014 04:17 AM, Jean-Paul Kogelman wrote:
>> We've been hard at work updating the spec to include features that were requested. We've removed the Scrypt dependency that was present in the initial drafts, added new KDFs, added plausible deniability and have a reference implementation.
>
> Are you aware of BIP-0039?
>
> https://github.com/bitcoin/bips/blob/master/bip-0039.mediawiki
>
>
Yes I am. There are some differences between BIP 39 and my proposal though.
- BIP 39 offers an easy list of words, no gnarly string of case sensitive letters and numbers.
- BIP 39 only offers one fixed length of entropy, always 12 words, no option to increase or decrease the length.
- BIP 39 doesn't have a genesis date field, so no optimization during blockchain rescan.
- BIP 39 doesn't have password typo detection. No easy way to recover a password if you know most of it.
- BIP 39 does not have a user selectable KDF, only 2048 round PBKDF2-HMAC-SHA512.
- BIP 39 can't outsource the KDF computation to a 3rd party.
- BIP 39 wallet implementors can use their own word lists, breaking cross wallet compatibility.
jp
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 842 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20140312/0e89e648/attachment.sig>;
Jean-Paul Kogelman [ARCHIVE] /
npub1sa…8y304
2023-06-07 15:15:13
in reply to nevent1q…vy4t
Author Public Key
npub1sa86gng3pvs3jgyt5majwcrhn8ck5qxgy9pjqxkh79u638cd7dys28y304Published at
2023-06-07 15:15:13Event JSON
{
"id": "4bf869d1e1e16082c5c45e111a5cfdceb680c29a31e87a22b5a30d472c51225f",
"pubkey": "874fa44d110b2119208ba6fb27607799f16a00c82143201ad7f179a89f0df349",
"created_at": 1686150913,
"kind": 1,
"tags": [
[
"e",
"e2b06c13dda090fd765a6fae17847c84821995c150a37c86a1dca89140911552",
"",
"root"
],
[
"e",
"50ec7a6033b6b2b567a9e6ee939d72cc6a4cbe017cf9ff1b018d414fe029136d",
"",
"reply"
],
[
"p",
"7631397e469f47f3535567311f5f7c17129e0ff2cb253df015e3d92ddfd92c63"
]
],
"content": "📅 Original date posted:2014-03-12\n📝 Original message:On Mar 12, 2014, at 6:11 AM, Pavol Rusnak \u003cstick at gk2.sk\u003e wrote:\n\n\u003e On 03/12/2014 04:17 AM, Jean-Paul Kogelman wrote:\n\u003e\u003e We've been hard at work updating the spec to include features that were requested. We've removed the Scrypt dependency that was present in the initial drafts, added new KDFs, added plausible deniability and have a reference implementation.\n\u003e \n\u003e Are you aware of BIP-0039?\n\u003e \n\u003e https://github.com/bitcoin/bips/blob/master/bip-0039.mediawiki\n\u003e \n\u003e \n\nYes I am. There are some differences between BIP 39 and my proposal though. \n\n- BIP 39 offers an easy list of words, no gnarly string of case sensitive letters and numbers.\n- BIP 39 only offers one fixed length of entropy, always 12 words, no option to increase or decrease the length.\n- BIP 39 doesn't have a genesis date field, so no optimization during blockchain rescan.\n- BIP 39 doesn't have password typo detection. No easy way to recover a password if you know most of it.\n- BIP 39 does not have a user selectable KDF, only 2048 round PBKDF2-HMAC-SHA512. \n- BIP 39 can't outsource the KDF computation to a 3rd party.\n- BIP 39 wallet implementors can use their own word lists, breaking cross wallet compatibility.\n\n\njp\n-------------- next part --------------\nA non-text attachment was scrubbed...\nName: signature.asc\nType: application/pgp-signature\nSize: 842 bytes\nDesc: Message signed with OpenPGP using GPGMail\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20140312/0e89e648/attachment.sig\u003e",
"sig": "0d7bbf699cd9d8b86afa179a5c58f1179689caa32cddad9f4b24cbe765ee55f4cf6a75c59ff420644a6b9fb623c95a0a7245162d71083817237d90c9b7f330d8"
}