[bisq-network/bisq] Propose how to integrate Monero wallet into Bisq (#1863)

antoinebechamp notifications at github.com
Mon Jan 14 17:56:33 UTC 2019


a random thought on this:  perhaps a daemon could be implemented that sits between bisq and monerod and emulates the specific bitcoind RPC calls that are used by bisq.

as I understand it, bisq now has a mode that can utilize bitcoind running on localhost via RPC (instead of bitcoinj library).  So, if a piece of software can implement those RPC calls and translate/forward them instead to a running monerod instance, neither bisq nor monerod would need to be modified.  

It's an open question (area for research) how closely the bitcoind RPCs can be emulated for monerod.  Many concepts are similar though.  I found this [mapping of api calls](https://monero.stackexchange.com/questions/8451/wallet-json-rpc-methods), as a basic starting point.  Since that time, monero now supports subaddresses, which work a bit more like getnewaddress.

The main benefits I see to this approach (if feasible) are that:
* anyone can implement it in any language.  no need to be familiar with bisq code, java, or monero code.
* the RPC proxy daemon can be useful to other software/devs.  There is a large ecosystem of code that uses bitcoind RPCs.     A monero compatibility layer could make monero easier to integrate.
* possibly the fastest way to get basic monero functionality into bisq.

The main drawback is that some features of the monero api would not be accessible from bisq this way, for example options related to mixin, ring size.  Configurable defaults would be used in daemon.

If bisq devs find this approach interesting, I think a next step would be to list here all the bitcoind RPC calls used by bisq, and then an on-paper mapping of calls, params, and return values could be attempted to judge the feasability and identify any problem areas.

-- 
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/bisq/issues/1863#issuecomment-454099601
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20190114/2686ae92/attachment.html>


More information about the bisq-github mailing list