📅 Original date posted:2020-03-24
📝 Original message:Hi Dustin,
That sounds interesting but I can't follow your email to be honest.
On Mon, 2020-03-23 at 07:38 -0700, Dustin Dettmer via bitcoin-dev
wrote:
> This mitigates, I believe, all leak vectors besides k/R hacking and
> prechosen entropy.
Hm, so what vectors is this supposed to mitigate? Leaking through the
generated public keys? Anything else?
Here are a few questions:
- What are you trying to achieve? You seem to describe how you get
from the setup to the goal in four steps but I don't understand what
the setup is or what the goal is. (What's a storage solution?)
- "all SW being compromised" do you mean "SW and HW compromised"? Note
that SW and HW are parties in Pieter's writeup, not just abbreviations
for software and hardware.
- Where are the two stages? You mention four steps.
- Where do you run the external software? On a second SW? Is this the
second stage?
- Do you use unhardened derivation?
- What's a k commitment?
Best,
Tim
Tim Ruffing [ARCHIVE] /
npub1cm…dwkls
2023-06-07 18:23:14
in reply to nevent1q…pr7w
Author Public Key
npub1cmt6gqyfw3sdngkq0wadtpe3kmgyyeld6ad0g2h5tar3kpzcrmpqddwklsPublished at
2023-06-07 18:23:14Event JSON
{
"id": "2e01368e199be14c8d6fad4cc006ccb7ca35ef99e0a17b26d297d8a8e1d29245",
"pubkey": "c6d7a400897460d9a2c07bbad58731b6d04267edd75af42af45f471b04581ec2",
"created_at": 1686162194,
"kind": 1,
"tags": [
[
"e",
"dc57ed046dd17bfbde2b48ae5c93b4197f33cb78e8d235e283ed60bfa1fc7219",
"",
"root"
],
[
"e",
"08b29e533d10317c4f5599e7ceb00bdaab17051830c1cbf933aeff876ef2a72c",
"",
"reply"
],
[
"p",
"352b35538b75bcd1384cb298feda615e454419aec1066329c8c3ff3ba18ee794"
]
],
"content": "📅 Original date posted:2020-03-24\n📝 Original message:Hi Dustin,\n\nThat sounds interesting but I can't follow your email to be honest.\n\nOn Mon, 2020-03-23 at 07:38 -0700, Dustin Dettmer via bitcoin-dev\nwrote:\n\u003e This mitigates, I believe, all leak vectors besides k/R hacking and\n\u003e prechosen entropy.\n\nHm, so what vectors is this supposed to mitigate? Leaking through the\ngenerated public keys? Anything else?\n\nHere are a few questions:\n - What are you trying to achieve? You seem to describe how you get\nfrom the setup to the goal in four steps but I don't understand what\nthe setup is or what the goal is. (What's a storage solution?)\n - \"all SW being compromised\" do you mean \"SW and HW compromised\"? Note\nthat SW and HW are parties in Pieter's writeup, not just abbreviations\nfor software and hardware. \n - Where are the two stages? You mention four steps.\n - Where do you run the external software? On a second SW? Is this the\nsecond stage?\n - Do you use unhardened derivation?\n - What's a k commitment?\n\n\nBest,\nTim",
"sig": "c1753ac85c57cd935e8eb65b0c6d21d390f0455dfb21bfd528b1ed5bfcb2f0a569b4126828aa32219329bd3f6adc39c70de96d3f9ff0b073608ee18a5558354d"
}