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

[Manfred Karrer]

Just an update from our last discussion:
For the notification only version we can use a simple relay node which has the same structure like the price node. A Http server over Tor to the Bisq nodes and it is calling the Apple notification server.
The Apple ID of the mobile should be exchanged via QR code with the Bisq app directly. The Bisq app sends then the encrypted message and the Apple ID over Tor to the Proxy node with a http request. The proxy node relays that message to the Apple notification server. That way the proxy does not learn about a mapping of the Bisq node to the mobile ID and there is no need to register anything at the proxy node.

In the version 2 with bidirectional messaging between Bisq and mobile we should try first to get Tor hidden services support for mobile. On Android it should be not a big issue (Bernhard did that 2-3 years ago). For iOS we need to check out if there is a native Tor app ([there is no official Tor browser](https://blog.torproject.org/tor-heart-onion-browser-and-more-ios-tor)). It seems that on iOS you cannot create a sub process which makes the model we use in Bisq impossible (start native Tor and communicate over TCP). So it might be that the challenge to get Tor working on iOS will be too hard. Then we have to decide if we support Android only, or if we use the above discussed solution to communicate over a proxy node which has a Tor API between Bisq and the node and a http API to the mobile.

-- 
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-396935241
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20180613/b35a44d9/attachment.html>