Re:Show HN: Timelock.dev – Send a secret into the future usi...
by pjerem on Monday March 11, 2024 @02:36AM
(#39665409)
Because each node generates its own key pair and when encrypting a message you choose a random route and you use the keys of the nodes of your route to encrypt each layer.
[ Parent
| on HN ]
Re:Show HN: Timelock.dev – Send a secret into the future usi...
by adastra22 on Monday March 11, 2024 @03:39AM
(#39665657)
What the person you're replying to is talking about is a Sybil attack. You pick random nodes, yes, but what if the list of nodes to pick randomly from is 99.5% the attacker? This is a real world attack that has been used against Tor, for example.
Re:Show HN: Timelock.dev – Send a secret into the future usi...
by pjerem on Monday March 11, 2024 @04:20AM
(#39665819)
Thank you, I understand !
Re:Show HN: Timelock.dev – Send a secret into the future usi...
by victorbjorklund on Monday March 11, 2024 @03:37AM
(#39665648)
So you can only decrypt the message if all the same nodes are still up? If anyone goes down you cant decrypt?
Re:Show HN: Timelock.dev – Send a secret into the future usi...
by pjerem on Monday March 11, 2024 @04:23AM
(#39665832)
Yes.
However, you could mitigate this by calculating hundreds of routes.
But yes, you are right, that was just an interesting thought experiment before going to bed, I wasn't trying to revolutionize timelock encryption ;)