[bisq-network/proposals] Three-party lightning escrow trade protocol for Bisq 2 (Issue #373)

[chimp1984]

Great thanks for the detailed and well explained write-up!

Regarding:
> In that case, it is necessary to send the message to a backup notary. This could simply be a timestamped broadcast to the Bisq P2P network, or for greater security we may use the Bitcoin blockchain as the notary, with confirmation of an OP_RETURN with the relevant message before the cutoff block height.

For Bisq 2 we intend to either use OpenTimeStamp or run such a service ourself for timestamping data like identity creation time (used for reputation purposes). The currently intended use cases do not require a fine grained timestamp (roughly 1 day is good enough) but if we have use cases like in this protocol where a timestamp should be created at block granularity, we might consider that in the design. As far I understand its an exceptional case anyway, so it could be used as a form or "flush" for the OTS service to create a tx immediately instead of waiting for the next trigger event.
Though to add a dependency to such a service might lower the security of the protocol, so maybe it would be better that the escrow is doing it themself.



-- 
Reply to this email directly or view it on GitHub:
https://github.com/bisq-network/proposals/issues/373#issuecomment-1112655109
You are receiving this because you are subscribed to this thread.

Message ID: <bisq-network/proposals/issues/373/1112655109 at github.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20220428/d30ed1d3/attachment.htm>