You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 17, 2021. It is now read-only.
Saying 1%(10%) throws users off because we display the inverse of the c-ratio setting which is .1333 so 100/.1333 = 750 and the 1% threshold is 1/.1333 = making it 7.5 off 750 = 742.5. Where as it was previously 10% 10/.1333 = 75 so you could be as low as 10/.1333-750=674 before you were blocked from claiming fees which was far too low. The 1% (or 7.5%) depending which way you look at is there to protect you from immediate price fluctuations after burning to claim fees.
Ideally the DApp should be showing a field for the Fee Claim Threshold calculating it from on chain 100/SynthetixState.issuanceRatio-FeePool.targetThreshold/SynthetixState.issuanceRatio = 100/.1333-1/.1333=742.5%. If we change the c-ratio back to 500% it would be 100/.2-1/.2=495 for the Fee Claim Threshold
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Saying 1%(10%) throws users off because we display the inverse of the c-ratio setting which is .1333 so 100/.1333 = 750 and the 1% threshold is 1/.1333 = making it 7.5 off 750 = 742.5. Where as it was previously 10% 10/.1333 = 75 so you could be as low as 10/.1333-750=674 before you were blocked from claiming fees which was far too low. The 1% (or 7.5%) depending which way you look at is there to protect you from immediate price fluctuations after burning to claim fees.
Ideally the DApp should be showing a field for the Fee Claim Threshold calculating it from on chain 100/SynthetixState.issuanceRatio-FeePool.targetThreshold/SynthetixState.issuanceRatio = 100/.1333-1/.1333=742.5%. If we change the c-ratio back to 500% it would be 100/.2-1/.2=495 for the Fee Claim Threshold
The text was updated successfully, but these errors were encountered: