<p></p>
<p>I like this idea. It requires a full client that uses the daemon over the network, and for the client-daemon communications to be secure. Seems a very sensible direction for Bisq to go in, whether having Bisq on a remote machine is a goal or not. The keep-offer-alive thing makes Bisq a server-like application anyway, so treating it as such makes sense.</p>
<p>I'd add that setting up Bisq on a local machine will probably still be easier than setting it up on a VPS.</p>

<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">—<br />You are receiving this because you are subscribed to this thread.<br />Reply to this email directly, <a href="https://github.com/bisq-network/proposals/issues/174#issuecomment-645450122">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AJFFTNVBQANHBDAL7SGORNTRXDUD5ANCNFSM4KLYCPWA">unsubscribe</a>.<img src="https://github.com/notifications/beacon/AJFFTNWBQFXN37RC5SULY6LRXDUD5A5CNFSM4KLYCPWKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEZ4MTCQ.gif" height="1" width="1" alt="" /></p>
<script type="application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/bisq-network/proposals/issues/174#issuecomment-645450122",
"url": "https://github.com/bisq-network/proposals/issues/174#issuecomment-645450122",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>