<p></p>
<p>I updated the title of this proposal to fix a typo and to make it more explicit.</p>
<p>I'm upvoting this because further incentivizing makers makes sense from the perspective of increasing liquidity. The 10% increase in overall fees makes sense to me as well, though I am generally uncomfortable with this kind of "ad-hoc" fee change. We need something more systematic and predictable, like what was proposed in <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>. That proposal was ultimately downvoted, but we should take another shot at it based on the feedback provided, particularly with regard to putting a per-cycle / per-release cap in place, so that no one fee increase is too great a shock. There should at a minimum be a spreadsheet somewhere that codifies the formula, reflects what current rates are (in the app) and should be (in the next release). It will be important to show over time that fees go down as well as up based on this systematic approach. <strong>Could someone raise their hand here to own putting that spreadsheet and proposal together?</strong> I think the proposal will be much more actionable and likely to be approved if we have the spreadsheet in hand and everyone can review it and provide feedback on it ahead of voting time.</p>
<p>Finally, I'm upvoting this with the assumption that we will make the change known in an effective manner to our audience of current and potential makers. <a class="user-mention" data-hovercard-type="user" data-hovercard-url="/users/m52go/hovercard" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/m52go">@m52go</a>, if this is approved, could you ensure that happens?</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/181#issuecomment-602486767">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AJFFTNV42NY6V7XKP6XUYHTRI4VLBANCNFSM4LBFQRPA">unsubscribe</a>.<img src="https://github.com/notifications/beacon/AJFFTNQOR3TTNDFJ3ELIJS3RI4VLBA5CNFSM4LBFQRPKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEPUTP3Y.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/181#issuecomment-602486767",
"url": "https://github.com/bisq-network/proposals/issues/181#issuecomment-602486767",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>