<p>Thank you for chiming in <a class="user-mention" data-hovercard-type="user" data-hovercard-url="/hovercards?user_id=54558767" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/chimp1984">@chimp1984</a>, now i have the situation much more clear, but i see the possibility of stagnation very real.</p>
<p>Bisq is moving away from integrated wallets because of the new trade protocol and i think it's cool, (and make sense to not have a "full" Monero wallet integrated if we are stirring away from base currencies anyway) but what worries me is the timeline. How long do you guys think will take before the new protocol goes live?<br>
If it's still in discussion and a broad timeline is not set, would make sense to give XMR trader a better integration in the meantime.</p>
<p>The incubator could help, but needs to be voted in the DAO and then developed. Correct me if i'm wrong but i think this will require a decent amount of time as well.</p>
<p>We have a ready proposal here, i understand the pushbacks and the reasons behind them, but i think waiting for the incubator and then for the new off-chain protocol for having a better xmr UX is not feasible. So the questions i think we should answer are: how can we have a better Monero integration without stirring too much away from the long term goals (off-chain protocol)? Would <a class="user-mention" data-hovercard-type="user" data-hovercard-url="/hovercards?user_id=232186" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/wiz">@wiz</a>'s suggestion be the best solution in this case? (since it only requires the PR with the API to be merged AFAIU), or should the integration proposed by <a class="user-mention" data-hovercard-type="user" data-hovercard-url="/hovercards?user_id=20237127" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/niyid">@niyid</a> be further trimmed, to reduce the amount of dependencies and therefore security risks?</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/110?email_source=notifications&email_token=AJFFTNS2XAAILLIGHMFRWQ3QKXXLVA5CNFSM4IO7EFUKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD7IO2RQ#issuecomment-533785926">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AJFFTNWQBB7RHN7C643EP5DQKXXLVANCNFSM4IO7EFUA">mute the thread</a>.<img src="https://github.com/notifications/beacon/AJFFTNVKY6C6FB63BZUOORTQKXXLVA5CNFSM4IO7EFUKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD7IO2RQ.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/110?email_source=notifications\u0026email_token=AJFFTNS2XAAILLIGHMFRWQ3QKXXLVA5CNFSM4IO7EFUKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD7IO2RQ#issuecomment-533785926",
"url": "https://github.com/bisq-network/proposals/issues/110?email_source=notifications\u0026email_token=AJFFTNS2XAAILLIGHMFRWQ3QKXXLVA5CNFSM4IO7EFUKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD7IO2RQ#issuecomment-533785926",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>