[bisq-network/proposals] Bisq remote (#25)

[Manfred Karrer]

Thanks @joachimneumann for the proposal!

I think the notification server should be a Bisq node with both the P2P network layer as a normal Bisq node and a HTTP server interface as the price node. 
The bi-directional communication between the Bisq node and the notification node would be pure Tor hidden service traffic. 
The communication to the Apple server would be HTTP. 
The communication from the mobile app back to the notification node would be HTTP as well (encrypted payload).
With that model the Bisq user do not need any setup for port forwarding or the like as his Bisq node is accessible via Tor. The notification node would run anyway as server and is operated by Bisq contributors so the user don't need to care about that.
The model would work the same if a user wants to runs his Bisq app on a cloud service (though there are other security constraints - e.g. wallet should be always encrypted).

I am working atm on integration for the APIs and we planned to support a HTTP API and a gRPC API. I think it would make sense to add another API layer which is Tor hidden service based only for supporting the communication between the notification node and the Bisq App. 

-- 
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/25#issuecomment-394167527
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20180603/af73335d/attachment-0001.html>