{"componentChunkName":"component---src-pages-sips-sip-markdown-remark-frontmatter-sip-tsx","path":"/sips/sip-56/","result":{"data":{"markdownRemark":{"fileAbsolutePath":"/vercel/path0/content/sips/sip-56.md","frontmatter":{"sip":56,"sccp":null,"title":"Differential Fees","network":"Ethereum","author":"Clinton Ennis (@hav-noms)","type":"Governance","proposal":null,"implementor":null,"release":null,"created":"2020-05-01T00:00:00.000Z","updated":null,"status":"Implemented"},"html":"\n

Simple Summary

\n\n

Ability for the protocol DAO to configure different exchange fee rates for each Synth.

\n

Abstract

\n\n

Currently there is one universal exchange rate for exchanging synths which is set onchain in the FeePool.

\n

Upgrading the FeePool to allow an array of Synths exchange rates to be set allowing unique pricing per asset or class.

\n

There could be multiple pricing options TBD such as;

\n
    \n
  1. Charge the fee rate of the synth being exchanged into.
    2. \n
  2. Charge the sum of the pair.
    3. \n
  3. Charge the lowest of the pair.
    4. \n
\n

UPDATE: The proposed pricing method is 1.

\n

Motivation

\n\n

With a universal exchange fee rate the protocol is limited in its ability to price markets fairly or apply incentive mechanisms. To deter front runners setting a high exchange rate was used to reduce profiitability affecting all Synth markets and discouraging good actors from trading.

\n

Unique pricing per synth would allow potential outcomes such as;

\n

a) Different price categories such as fiat, crypto, inverse, indices, commodities or stocks.

\n

b) Used as a configurable protocol mechanism via SCCP to increase rates to deter new trades exchanging into a synth where there is an oversupply or potential debt risk to the system.

\n

c) Configure a synth's exchange rate such as sUSD as low as possible to encourage traders to move into it or for SNX stakers to return to sUSD at no cost to be able to burn it to maintain the systems target c-ratio.

\n

Specification

\n\n

Storage of the rates should use the uint mappings in the FeePoolEternalStorage contract so FeePool logic can be upgraded maintaining the exchange fee rate state.

\n

New functions required in the upgradable FeePool contract.

\n

setExchangeFeeRateForSynths

\n

Will allow the protocol DAO to set n number of exchangeFeeRates for n number of synths in one transaction.

\n

Function signature

\n

setExchangeFeeRateForSynths(bytes32[] synthKeys, uint256[] exchangeFeeRates) onlyOwner

\n\n

exchangeFeeRateForSynth

\n

Return the exchange fee rate for a synth

\n

Function signature

\n

exchangeFeeRateForSynth(bytes32 synth) public view returns (uint)

\n\n

deleteExchangeFeeRateForSynths (optional)

\n

Will allow the protocol DAO to delete n number of synth rate entries freeing up the storage of removed / deprecated synths

\n

Function signature

\n

deleteExchangeFeeRateForSynths(bytes32 [synthKeys]) onlyOwner

\n\n

New functions required in the upgradable Exchanger contract.

\n

exchangeFeeForTrade

\n

Returns the exchange fee in sUSD.

\n

Deprecate existing fee view function FeePool.exchangeFeeIncurred(uint value) public view returns (uint)\nand move to Exchanger.getAmountsForExchange\nto accept the Synth trading pair as arguments to determine the exchange fee for the trade.

\n

Function signature

\n

getAmountsForExchange(uint sourceAmount, bytes32 sourceCurrencyKey, bytes32 destinationCurrencyKey) public view returns (uint)\nParameters

\n\n

Returns

\n\n

Rationale

\n\n

It was considered that a Synth should store its own rate by having a setter for exchangeFeeRate. However the rate storage would be lost on each upgrade and need to be reset again adding overhead to the upgrade process. Also each Synths external TokenState is already immutable and not upgradable.

\n

Test Cases

\n\n

FeePool

\n
    \n
  1. Given the pDAO needs to set multiple rates. When owner sends an array of x Synths and rates then store in the FeePoolEternalStorage on chain
    2. \n
  2. Given the pDAO needs to set a single rate. When owner sends an array of x Synths and rates that are already stored then the synth rates are updated.
    3. \n
  3. Given the pDAO needs to update multiple rates. When owner sends an array of 1 Synths and rates then store in the FeePoolEternalStorage on chain
    4. \n
  4. Given the pDAO needs to update 1 rate. When owner sends an array of 1 Synths and rates that are already stored then the synth rates are updated.
    5. \n
  5. Given a synthKey, anyone can view the exchange fee rates for the synthKey
    6. \n
  6. When owner sends a rate greater than MAX_EXCHANGE_FEE_RATE then revert
    7. \n
\n

Exchanger

\n
    \n
  1. Given I have a balance of Synth A and want to exchange into Synth B then I can view the exchangeFeeRate, fee and amountReceived
    2. \n
  2. Given I exchange Synth A into Synth B and then the exchange fee rate applied should be the rate of Synth B
    3. \n
  3. Given I exchange into a Synth then the exchange rate is stored for fee reclaimation, when I return x seconds later and have a settlement owed to the debt pool or rebate owing to me the exchange fee rate at the time of my exchange is used for settlment and not the current rate in case it has changed.
    4. \n
\n

Implementation

\n\n

https://github.com/Synthetixio/synthetix/releases/tag/v2.22.4

\n

Copyright

\n

Copyright and related rights waived via CC0.

"}},"pageContext":{"id":"fef94e66-e8d5-59e8-827c-8fed66d3d0fd","frontmatter__sip":56,"__params":{"frontmatter__sip":"56"}}},"staticQueryHashes":[]}