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

[sqrrm]

> _This is a Bisq Network proposal. Please familiarize yourself with the [submission and review process](https://docs.bisq.network/proposals.html)._

<!-- Please do not remove the text above. -->

Some data in the Bisq network is timestamped and we're currently allowing any data with a timestamp less than 24 hours old. All older data has to come from a seednode or it will be rejected. This means we trust seednodes for this data, typically the account age witness and signed witness data.

This proposal suggests a way to rid Bisq of this reliance on trusted nodes but still not allow for injection of backdated data.

### Opentimestamps
[Opentimestamps](https://opentimestamps.org/) is a time stamping service using the bitcoin blockchain. Each Bisq node could use this service independently to stamp new data, voiding the need for relying on seed nodes for this data. Verifying the timestamps could either be done through a Bisq service, or by including this service in the Bisq client for users with their own bitcoind.

### Considerations
1. This exercise might just be moving the reliance on seed nodes to the reliance on Opentimestamps. This is then another service that needs to work for the Bisq network to function properly.

1. There is a cost to adding data to the block chain. Opentimestamps is free for now, and can reasonably be expected to continue to be free as long as tx fees to increase to unreasonable levels. Data is commited as the root of a merlke tree, socializing the cost of commitments.

1. The new service needs to be accessible when data is created on for the Bisq p2p network, any downtime would cause usability issues for Bisq users.

1. A new data format might be needed, or some way to verify the timestamps of distributed data. Adding the verification details from the .ots file would likely add too much data so this would have to be solved.

### Conclusion
I think this is possible to implement but not urgent. There are likely many more considerations, these are just the immediate ones that popped up my head. This is meant to document some thoughts on distributing the timestamping aspect of Bisq and to promote discussion in case it becomes more urgent one day.

-- 
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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20200820/948930b7/attachment.html>