<p></p>
<p>Would be helpful to get advice from <a class="team-mention js-team-mention" data-error-text="Failed to load team members" data-id="3638643" data-permission-text="Team members are private" data-url="/orgs/bisq-network/teams/bisq-devs/members" data-hovercard-type="team" data-hovercard-url="/orgs/bisq-network/teams/bisq-devs/hovercard" href="https://github.com/orgs/bisq-network/teams/bisq-devs">@bisq-network/bisq-devs</a> on how limits are determined -- it seems like maximum trade limit is a DAO parameter, and all other limits are determined by multiplying <a href="https://github.com/bisq-network/bisq/blob/fdf7912bab39d74921505d04b02ee2048886b9c9/core/src/main/java/bisq/core/payment/payload/PaymentMethod.java#L55">this number with risk levels</a>. So if max limit is halved, for example, then all limits are halved...meaning if we seek to reduce fiat limits by half, then altcoin limits would need to be reduced by half as well? I assume minimum deposit (.006) and maximum unsigned trade size (.01) can be adjusted independently though.</p>
<blockquote>
<p>Reducing it to 0.005 BTC (150USD) should be a no brainer. The only con is that with current blockspace prices the total amount on mining fees for 0.005BTC trades is very high.</p>
</blockquote>
<p>As mentioned in the linked thread (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="447033781" data-permission-text="Title is private" data-url="https://github.com/bisq-network/proposals/issues/95" data-hovercard-type="issue" data-hovercard-url="/bisq-network/proposals/issues/95/hovercard" href="https://github.com/bisq-network/proposals/issues/95">#95</a>), fiat transfers used in the March 2019 scams were much smaller than the current fiat value of 0.01 BTC, so this one parameter in particular should be addressed quickly, ideally in the very next release. I realize fees make this look unattractive but I'm not sure it makes sense to keep them so high given the reason they exist in the first place.</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/295#issuecomment-761696347">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AJFFTNV7NO7WASW3SBIZV53S2INJ7ANCNFSM4WDZLCHA">unsubscribe</a>.<img src="https://github.com/notifications/beacon/AJFFTNSM5TTOZLUEESISXA3S2INJ7A5CNFSM4WDZLCHKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOFVTJAWY.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/295#issuecomment-761696347",
"url": "https://github.com/bisq-network/proposals/issues/295#issuecomment-761696347",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>