No, sry, I think you misunderstood. I can (with reasonable likelihood) have hardware-backed mechanism (prototype) in a couple of weeks, maybe one if dependency libraries work out and I allow myself to be very optimistic.
It's a small general-purpose security device, more of a prototype. Not with extreme hardware security (yet), but the necessary computations would be (protected and) executed in hardware. Also depends on design and expectations, given that device would need to be present for signing. I can think of variations in which device protects nsec at rest, then unlocking secret to load in client-app memory. We can prly support multiple varations for different purposes (simultaneously).
The problem is that support would need to be present in the clients to be useful, and it would require a considerable amount of time to also modify the clients. I am quite limited on time/resources so, with no support from any devs, I don't want to further divide my focus. I proposed this idea before, but got no response.
anonymous
npub1wp…hku55
2024-07-03 09:16:45
in reply to nevent1q…pwdj
Author Public Key
npub1wpu33h35ufrnxdhwmy82s3l3nk682xm3whvfxepxsjn24t6dnn8q0hku55Published at
2024-07-03 09:16:45Event JSON
{
"id": "7fc6a52cc5e4df2e9fea1fdd4f96d5ae046bdb539aee6e0943b195532c1cbe53",
"pubkey": "707918de34e2473336eed90ea847f19db4751b7175d893642684a6aaaf4d9cce",
"created_at": 1719998205,
"kind": 1,
"tags": [
[
"e",
"be78c2736d30023c34e2b91388a664bd92b43bd5e90f5922556fbfd0f0b4fc3d",
"",
"root"
],
[
"e",
"6fa14fbd945028388a0b343db358aea740b455a76f92b6f37a1a6ece8e952bcb"
],
[
"e",
"5a0c179dad70b1b48ae197e0aa145e8ed1c9bdd8964ec914de0c38c8fc214e80",
"",
"reply"
],
[
"p",
"707918de34e2473336eed90ea847f19db4751b7175d893642684a6aaaf4d9cce"
],
[
"p",
"9c53485849518fa429cca814ba10eea9599bdf4e183d8202c53bb4b719427d3c"
]
],
"content": "No, sry, I think you misunderstood. I can (with reasonable likelihood) have hardware-backed mechanism (prototype) in a couple of weeks, maybe one if dependency libraries work out and I allow myself to be very optimistic.\nIt's a small general-purpose security device, more of a prototype. Not with extreme hardware security (yet), but the necessary computations would be (protected and) executed in hardware. Also depends on design and expectations, given that device would need to be present for signing. I can think of variations in which device protects nsec at rest, then unlocking secret to load in client-app memory. We can prly support multiple varations for different purposes (simultaneously).\n\nThe problem is that support would need to be present in the clients to be useful, and it would require a considerable amount of time to also modify the clients. I am quite limited on time/resources so, with no support from any devs, I don't want to further divide my focus. I proposed this idea before, but got no response.",
"sig": "7d81ffced4d2547e5751232a00f41d1011cceaebf7d23513a4696f00391a58c2a328db8665ec5f8ba646f3d1194b04930db87c32f3720187afd18d7aa9c3e3bb"
}