📅 Original date posted:2022-05-03
📝 Original message:Hi Vjudeu,
Perhaps this could make sense in some setting. e.g. instead of a hardware
device which protects your secret key via pin you use a pinless device but
you create a strong password and use a proper password hash to create
another key and put them in a 2-of-2. But make sure you don't use sha256 to
hash the password. Use a proper password hash. Keep in mind there's also
bip39 passwords which do a similar but this does involve entering them into
the possibly malicious hardware device.
Cheers,
LL
On Mon, 2 May 2022 at 03:56, vjudeu via bitcoin-dev <
bitcoin-dev at lists.linuxfoundation.org> wrote:
> It seems that Taproot allows us to protect each individual public key with
> a password. It could work in this way: we have some normal, Taproot-based
> public key, that is generated in a secure and random way, as it is today in
> Bitcoin Core wallet. Then, we can create another public key, just by taking
> password from the user, executing SHA-256 on that, and using it as a
> private key, so the second key will be just a brainwallet. Then, we can
> combine them in a Schnorr signature, forming 2-of-2 multisig, where the
> first key is totally random, and the second key is just a brainwallet that
> takes a password chosen by the user. By default, each key can be protected
> with the same password, used for the whole wallet, but it could be possible
> to choose different passwords for different addresses, if needed.
> Descriptors should handle that nicely, in the same way as they can be used
> to handle any other 2-of-2 multisig.
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev at lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20220504/f39b25f0/attachment.html>;
Lloyd Fournier [ARCHIVE] /
npub1kh…y05yp
2023-06-07 23:08:56
in reply to nevent1q…gx4s
Author Public Key
npub1khlhcuz0jrjwa0ayznq2q9agg4zvxfvx5x7jljrvwnpfzngrcf0q7y05ypPublished at
2023-06-07 23:08:56Event JSON
{
"id": "c4d2db1b67c03a4dbe5640ec64eb92f70d79a566eae102781beb11e8b0e85b05",
"pubkey": "b5ff7c704f90e4eebfa414c0a017a84544c32586a1bd2fc86c74c2914d03c25e",
"created_at": 1686179336,
"kind": 1,
"tags": [
[
"e",
"6dac99bf2d30e83c0268eaf216f0fb5f083a1f1497342149b6365c90614e5ed4",
"",
"root"
],
[
"e",
"6d09849ad4e4b292dbc9097eab43f2c3c4426562b4db8f6529b05117a3d09f1e",
"",
"reply"
],
[
"p",
"8d3cf7eba921036409f1fec074cf8cfd8925bc7cb18e35d358b1ccc89752ee32"
]
],
"content": "📅 Original date posted:2022-05-03\n📝 Original message:Hi Vjudeu,\n\nPerhaps this could make sense in some setting. e.g. instead of a hardware\ndevice which protects your secret key via pin you use a pinless device but\nyou create a strong password and use a proper password hash to create\nanother key and put them in a 2-of-2. But make sure you don't use sha256 to\nhash the password. Use a proper password hash. Keep in mind there's also\nbip39 passwords which do a similar but this does involve entering them into\nthe possibly malicious hardware device.\n\nCheers,\n\nLL\n\nOn Mon, 2 May 2022 at 03:56, vjudeu via bitcoin-dev \u003c\nbitcoin-dev at lists.linuxfoundation.org\u003e wrote:\n\n\u003e It seems that Taproot allows us to protect each individual public key with\n\u003e a password. It could work in this way: we have some normal, Taproot-based\n\u003e public key, that is generated in a secure and random way, as it is today in\n\u003e Bitcoin Core wallet. Then, we can create another public key, just by taking\n\u003e password from the user, executing SHA-256 on that, and using it as a\n\u003e private key, so the second key will be just a brainwallet. Then, we can\n\u003e combine them in a Schnorr signature, forming 2-of-2 multisig, where the\n\u003e first key is totally random, and the second key is just a brainwallet that\n\u003e takes a password chosen by the user. By default, each key can be protected\n\u003e with the same password, used for the whole wallet, but it could be possible\n\u003e to choose different passwords for different addresses, if needed.\n\u003e Descriptors should handle that nicely, in the same way as they can be used\n\u003e to handle any other 2-of-2 multisig.\n\u003e _______________________________________________\n\u003e bitcoin-dev mailing list\n\u003e bitcoin-dev at lists.linuxfoundation.org\n\u003e https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev\n\u003e\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20220504/f39b25f0/attachment.html\u003e",
"sig": "ffc525dfe5ab2fe77bc34ec23c20a277b2c3e221c526dce14d8991c466066be463944b31817ba62e05bce59ceeb4d0376e9cb22acdb3a3d750ed9859e15fb972"
}