1–10 of 149 posts
Show HN: Timelock.dev – Send a secret into the future using timelock encryption
timelock.dev
[flagged]
The website's implementation is this:
> A group of [orgs] holds the keys. There are 18 separate organizations running a total of 22 nodes, with a threshold of 12 needed to release a secret.
[flagged]
[flagged]
Ergh, could you explain how did you come to this conclusion?
The only way that I know to encrypt something into the future is generating an N-bit key and hoping someone will go through the trouble of cracking it when that becomes feasible. That involves lots of assumptions (e.g., how computing power develops and how much that person cares). The website's implementation is this: > A group of [orgs] holds the keys. There are 18 separate organizations running a total of 22 nodes,…
Who knows if this service will go down or something?
Might aswell just do this with one entity m