[bisq-network/proposals] Use Opentimestamps for timestamped p2p data (#246)

chimp1984 notifications at github.com
Fri Aug 21 00:00:46 UTC 2020


@sqrrm Thanks for sharing the idea.

We could split the publication of the timestamp and the verification. Publication has costs and some complexity. Bonded Bisq nodes could do that. Verification could be done by each Bisq node if they get the relevant transaction (opReturn data). They would need more meta data to verify but I guess the basic idea is that one cannot backdate data. Worst case would be that verification data is not provided and therefor data might be invalidated even if it was valid. For account age data it would mean worst case is that some valid data would be ignored as verification is not possible. But if data was verified it is guaranteed that it was not backdated.

Also not aware of the details of OTS, but I think its a good idea to reduce weak spots in the current system.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/bisq-network/proposals/issues/246#issuecomment-677963998
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20200820/d087b442/attachment.html>


More information about the bisq-github mailing list