News for hackers. Stuff that matters.

A comment on Timelock Encryption made possible and easy to use. Parent comment

Re:Timelock Encryption made possible and easy to use by wslh on Monday August 15, 2022 @07:07PM (#32476714)
That is right and it is not explained in the README file. Timelick based on Blockchain is not a security primitive.
[ Parent | on HN ]
Re:Timelock Encryption made possible and easy to use by h0h0h0h0111 on Monday August 15, 2022 @09:01PM (#32477929)
there is no blockchain involved at all
[ Parent | on HN ]
Re:Timelock Encryption made possible and easy to use by wslh on Tuesday August 16, 2022 @06:26AM (#32481119)
I used the term blockchain with liberty, it is based on a consensus mechanism so you need to assume the consensus is right which is different of timelock encryption usage in classic ways. The README was edited after the HN posts.
[ Parent | on HN ]
Re:Timelock Encryption made possible and easy to use by h0h0h0h0111 on Tuesday August 16, 2022 @06:34PM (#32489877)
It's not really a consensus mechanism either really - the randomness in some sense is deterministic, it just requires participation. I'm unsure which 'classic ways' you're referring to - in principle it's not that different to having a notary, except the notary is a distributed network rather than a single entity.

> The README was edited after the HN posts.

You can see from that the tlock git history the README.md hasn't been updated in 13 days and the tlock-js one hasn't been updated in 4 days - both before the HN post. Are you talking about another README?

[ Parent | on HN ]