Earlier quoted context omitted.
There are a few geocaching approaches: Sunken chest / mysterious treasure map Beacon of high gamma radiation / undesirable to approach for many half lives USB key in Jimmy Hoffas pocket
My inner devil likes the "too dangerous to approach" idea :) About the last idea, I had to look up that name: > James Riddle Hoffa (born February 14, 1913; disappeared July 30, 1975; presumed dead July 30, 1982) was an American labor union leader who served as the president of the International Brotherhood of Teamsters (IBT) from 1957 until 1971. Do I read it correctly if I understand "Jimmy Hoffas pocket" to be one…
Show HN: Timelock.dev – Send a secret into the future using timelock encryption
41–50 of 149 posts
Re: Show HN: Timelock.dev – Send a secret into the future using timelock encryption
#42for robustness, the message should include the decrypt algorithm what about integrity and time travelers? i.e., can decrypt but just messing around with time
Re: Show HN: Timelock.dev – Send a secret into the future using timelock encryption
#43[flagged]
I know a guy that worked on this same problem leveraging TEEs (trusted execution environments). This enables 3rd parties to run the software and join the network and take part without having access to the data. Unless they find a flaw in the TEE that can be exploited.
Re: Show HN: Timelock.dev – Send a secret into the future using timelock encryption
#44Re: Show HN: Timelock.dev – Send a secret into the future using timelock encryption
#45What does this solve that couldn't be solved by simply disclosing the decryption key oneself at the specified date?
Re: Show HN: Timelock.dev – Send a secret into the future using timelock encryption
#46Re: Show HN: Timelock.dev – Send a secret into the future using timelock encryption
#47Whats the point of this if it's not decentralized/algorithmic based. Who knows if this service will go down or something? Might aswell just do this with one entity m
There is no decentralized algorithm for timelock encryption. No such scheme exists. Distributed is the best you're going to get without a radical breakthrough, and that's exactly what TFA is.
Even with some corrupted nodes, the message would still be secret, the only issue would be if the last nodes are corrupted : your message would be distributed too soon. But with enough layers and enough nodes to go through, you could mitigate this risk.
The network could even detect corrupted nodes if other nodes received the message too soon.
Re: Show HN: Timelock.dev – Send a secret into the future using timelock encryption
#48Re: Show HN: Timelock.dev – Send a secret into the future using timelock encryption
#49What does this solve that couldn't be solved by simply disclosing the decryption key oneself at the specified date?
Re: Show HN: Timelock.dev – Send a secret into the future using timelock encryption
#50Paper: https://docs.google.com/document/d/e/2PACX-1vQe-OF0Lw9lutf6a...