[bisq-network/proposals] Content of the proposal details should be committed when proposal phase is over (#43)

[Manfred Karrer]

When a contributor files a proposal in the Bisq app they have to add the link to the Github issue where the content of the proposal is described.

Once the proposal period has ended the content of that link should be persisted and frozen so it cannot be changed or deleted. 

It would be good if we can use the Github API to snapshot the issue and then commit it. It would be also good if the data is still readable (html) but I think that is not a hard requirement. It can be expected that there are no conflicts anyway which require to lookup an old proposal.
Not sure what would be the best and easiest way how to implement that. A special service which gets triggered by the first block after the proposal phase to snapshot the issues and then make a commit of that data. Multiple nodes (e.g. seed nodes) could do that and before committing they check if there is already a commit with that hash.

I am not sure if that feature is really important at least for the start probably not. But I wanted to write it down here for discussion and to for maybe implementing it later.   

-- 
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/43
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20181006/4671ca81/attachment.html>