[bisq-network/proposals] Integrate transaction proof verification for Monero (#86)

Manfred Karrer notifications at github.com
Mon May 13 08:59:07 UTC 2019

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

The Monero seller need to be able to provide a transaction proof (tx key) in case of a dispute as the XMR transfer cannot be verified on the blockexplorer like with other altcoins. There are at least 2 online services available to verify the tx key [1](http://xmrchain.net), [2](https://xmr.llcoins.net/checktx.html). 

We could integrate that the XMR seller need to provide the tx key in the trade process (after sending XMR) so that the buyer receives the tx key and can make an API call to one of those services (or better both).

It can be assumed that those services will not support Tor connections so we will need a relay solution similar to our price and fee estimation nodes. Those relay nodes provide a hidden service to the Bisq nodes and do the request to the http service in clearnet.

As soon the XMR buyer's Bisq app can verify the tx the trade can be completed. This would speed up the trade process and only requires that the buyer's app is online but not the manual interaction.

Alternatively a monerod integration with RPC could be used. Then the tx proof is not required as the buyer's wallet will know anyway once the tx arrived. Though that require that the buyer runs a monerod while having Bisq open, which might be a more narrow requirement as the above solution with using an API. Also integrating monerod will add new security risks. 

To avoid risks with those services we could also provide our own service for providing the tx proof. Multiple services should be used and only if all match the result is considered trustworhty. 


You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20190513/3c5ac576/attachment.html>

More information about the bisq-github mailing list