DFX Finance’s proposal to (1) add a gauge for the DFX(L2)/ETH 50/50 on Arbitrum (2) deprecate the gauge for the DFX/ETH 50/50 on Arbitrum
• Github Page: Github
DFX Finance is a decentralized foreign exchange (FX) protocol that facilitates the seamless exchange of fiat-backed stablecoins denominated in a growing number of currencies. Using a hyper-efficient AMM, optimized for low volatility trading, DFX provides FX swaps with rates that will beat any bank, money changer, or FX platform. DFX is the governance token of DFX Finance which allows users to vote on protocol changes and initiatives of the DAO, and also allows users to receive boosted emissions on deposits within the DFX ecosystem.
Price History DFX:
Price History for DFX can be found on Coingecko
The DFX token on L2s such as Arbitrum and Polygon is migrating from a bridged token to a Chainlink CCIP token. As well, DFX Finance is committed to continue to engage in the Hiddenhand Finance ecosystem in a meaningful way to further deepen DFX liquidity onchain.
- Governance: DFX tokens serve as the governance token for the DFX Finance protocol. DFX token holders can vote on governance proposals through DFX’s snapshot. DFX forum is also used to discuss potential protocol changes and improvements.
- Oracles: DFX token does not rely on any external oracles. The DFX stablecoin pools uses Chainlink for its real world forex price feeds to facilitate efficient stablecoin swaps close to the spot price. The feeds can be found here: Decentralized Price Reference Data | Chainlink
- Audits: DFX has engaged with multiple auditors including engagements with Trail of Bits, Haechi, and Zellic to audit the DFX smart contracts.
- Centralization vectors: Treasury functions are controlled by a 2/4 multisig including treasury yield farming, and paying bribes.
- Market History: DFX has been transferable since March 2021.
- Value: This pool will be the primary source of liquidity for DFX on Arbitrum and Polygon
The Balancer Maxi LM Multisig eth:
0xc38c5f97B34E175FFd35407fc91a937300E33860 will interact with the GaugeAdderv4 at
0x5DbAd78818D4c8958EfF2d5b95b28385A22113Cd and call the addGauge function with the following arguments:
2 weeks after execution of the above
The DAO Multisig
0x10A19e7eE7d7F8a52822f6817de8ea18204F2e4f will interact with the AuthorizerAdaptorEntrypoint at
0xf5dECDB1f3d1ee384908Fbe16D2F0348AE43a9eA and call performAction using
0xab8f0945 for the
data(bytes) argument and the
0x8f7a0f9cf545db78bf5120d3dbea7de9c6220c10 list for the