PR with Payload
Summary:
This is a proposal to enable the root gauge Address: 0xc77AC1AE...49392D12d | Etherscan
on Ethereum, [which redirects rewards to the child gauge Address: 0x39d71EE5...60ee66B1b | Arbitrum One
on Arbitrum,] for the pool Address: 0x21f132ad...2678ebd80 | Arbitrum One
(surge yUSD/ waArbUSDCn).
References/Useful links:
Link to:
• Website: https://yield.fi/
• Documentation: https://docs.yield.fi/
• Github Page: YieldFi · GitHub
• Twitter: https://x.com/getyieldfi
Motivation:
We have recently upgraded our architecture and have deployed new pools with v2 yUSD tokens on Balancer. Users are migrating from our old pool to new ones.
This pair on Arbitrum has historically grown to $700k as compared to current $150k across new and old pools and by enabling gauge rewards, this pool will attract additional TVL, benefiting both protocols while creating one of the highest-yielding stable opportunities on Arbitrum.
This integration creates synergies between YieldFi, Balancer, and Aave, boosting activity across all three ecosystems.
Protocol Description:
yUSD is the yield bearing token by YieldFi deployed on Base and is backed by stablecoins like USDC/USDT/USR/wstUSR that strategically allocates assets across blue-chip DeFi protocols to generate 10-20% yields (currently 10.24% APY). The product features daily yield distribution, institutional-grade security, and full on-chain transparency.
waArbUSDCn is the wrapped version of Aave’s interest-bearing aBasUSDC on Arbitrum, which allows users to earn yield from USDC deposits in Aave.
Specifications:
Governance: YieldFi operates with a MPC wallet
Oracles: Oracles | YieldFi
Audits: Audits | YieldFi
Centralization vectors: The primary centralization vectors include the MPC custody and professional team management of yield strategies (necessary for optimal returns)
Market History: yUSD has maintained a perfect positive yieldcurve with no drawdown since launch with zero instances of depegging.
https://dune.com/queries/4785783/7937254
Technical Specifications:
Transaction: The Balancer Maxi LM Multisig eth:0xc38c5f97B34E175FFd35407fc91a937300E33860 will interact with the GaugeAdderv4 at 0x5DbAd78818D4c8958EfF2d5b95b28385A22113Cd and call the addGauge function with the following arguments:
gauge(address):
0xGaugeAddress: https://arbiscan.io/address/0x39d71EE5c97Ff25c3812790f1129Ab060ee66B1b
0xRootGaugeAddress: Address: 0xc77AC1AE...49392D12d | Etherscan
0xPoolAddress: Address: 0x21f132ad...2678ebd80 | Arbitrum One
gaugeType(string): Arbitrum
Edit Maxis:
- added payload