<p></p>
<p>Maybe I did not explain right how the numbers are calculated, or they're calculated weird in the spreadsheet. I created a third sheet with the calculations of a sudden drop in BSQ price scenario to show how it would be.</p>
<p><a target="_blank" rel="noopener noreferrer" href="https://user-images.githubusercontent.com/50149324/78378609-7cc32580-75d1-11ea-9b3a-da3daaefd73a.png"><img src="https://user-images.githubusercontent.com/50149324/78378609-7cc32580-75d1-11ea-9b3a-da3daaefd73a.png" alt="imagen" style="max-width:100%;"></a></p>
<blockquote>
<p>fees could change by up to 20 percentage points per cycle</p>
</blockquote>
<p>The max discount difference of 5% variation means that if now the discount is 60%, for the next cycle it should be 55% for the nex. As it's calculated on the spreadsheet, implies that a maximum of a 13% BSQ increase is allowed.<br>
Going from 46 BSQ per BTC traded to 52 BSQ per BTC  from one cycle to next one looks high ennough to me.<br>
As I understand, you're proposing to be able to go from 46 BSQ to 55 BSQ,  which is not very far from the current proposal. One objective of this proposal is to make trading fee changes steady. The reason why <a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="554504785" data-permission-text="Title is private" data-url="https://github.com/bisq-network/proposals/issues/173" data-hovercard-type="issue" data-hovercard-url="/bisq-network/proposals/issues/173/hovercard" href="https://github.com/bisq-network/proposals/issues/173">#173</a> was rejected was because that change looked too abrupt.</p>
<blockquote>
<p>it would only be done when the discount is 10 percentage points off the 50% mark</p>
</blockquote>
<p>Fees would have to be checked periodically anyway, so I think that a 5% distance from the mark should be used. For the DAO it's a simple vote, as rules are already known and easy to check consulting the spreadsheet. For contributors and traders, keeping the discount the closer possible to 50% makes it easier to predict revenue and expenses.</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/202#issuecomment-608518257">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AJFFTNSR6RXE4WH2GK4Y5E3RKYAX7ANCNFSM4L3WTEGQ">unsubscribe</a>.<img src="https://github.com/notifications/beacon/AJFFTNQZHPNJNRR4AZF7EX3RKYAX7A5CNFSM4L3WTEG2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOERCUA4I.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/202#issuecomment-608518257",
"url": "https://github.com/bisq-network/proposals/issues/202#issuecomment-608518257",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>