<p></p>
<p><a class="user-mention" data-hovercard-type="user" data-hovercard-url="/users/chimp1984/hovercard" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/chimp1984">@chimp1984</a> I agree that, having BTC Bisq can use, reimbursement should be done in BTC, at least most part of it. But I don't understand why do we have to change the way Bisq deals the BTC it still manages. What has changed since the attack regarding the DAO address holder that needs to be changed? This model, although we know it's fragile and requires trust, is not what failed. Software implementation of donation addresses did.</p>
<p>This new implementation, although it's supposed to be easy and secure, is still a new complexity layer at software level and, also (if we use it for other use cases) for DAO management.</p>
<p><a class="user-mention" data-hovercard-type="user" data-hovercard-url="/users/ifarnung/hovercard" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/ifarnung">@ifarnung</a> I'd like to know your reasons for rejecting this proposal.</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/205#issuecomment-611394279">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AJFFTNWGW3KYZMG2HEZAUSTRLV7JLANCNFSM4MEJXL2A">unsubscribe</a>.<img src="https://github.com/notifications/beacon/AJFFTNT3R47V2DNIR46HYN3RLV7JLA5CNFSM4MEJXL2KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOERYSFZY.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/205#issuecomment-611394279",
"url": "https://github.com/bisq-network/proposals/issues/205#issuecomment-611394279",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>