[BIP-357] Enable GHO/LUSD Gauge [Ethereum]

PR with Payload


This pool uses the ComposableStablePoolFactory-v5 which addresses the reentrancy vulnerability disclosed during February 2023. This gauge is uncapped.

This proposal is for a new pool GHO/LUSD to be created on Ethereum.

References/Useful links:



Protocol Description:

Aave Protocol
The Aave Protocol is a decentralized liquidity protocol that is deployed across many EVM compatible networks including but not limited to Optimism, Arbitrum, Avalanche and Polygon. Currently, the Aave Protocol has a TVL of approximately $7.8 Billion.

Liquity Protocol
Liquity is a decentralized borrowing protocol that allows you to draw 0% interest loans against Ether used as collateral. Loans are paid out in LUSD - USD-pegged stablecoin and need to maintain a minimum collateral ratio of only 110%. LUSD has proved its impeccable resilience in time by getting through severe market crashes untroubled. Currently, the Liquity Protocol has a TVL of approximately $678m.


GHO is a decentralized multi-collateral stable coin that is fully backed, transparent and native to the Aave Protocol.

Further details relating to GHO can be found here.

LUSD is the Liquity protocol stable coin. It uses ETH only as collateral. And LQTY is the secondary token issued by Liquity, capturing the fee revenue. Furthermore, LQTY stakers earn ETH and LUSD as rewards. And LUSD Stability pool depositors that earn LQTY and ETH.

Further details relating to LUSD can be found here.


  1. Governance:
  • AAVE and stkAAVE serve as the governance tokens for the Aave DAO. Holders can vote on proposals at both a Snapshot level and through the Aave DAO on-chain governance portal.
  • Liquity has no governance. It is built to maximize trustlessness and decentralization.
  1. Oracles:
  • rateProvider0 (for GHO): 0x0 (none)
  • rateProvider1 (for LUSD): 0x0 (none)
  1. Audits:


Aave v3


  1. Centralization vectors:
  • Aave Governance is decentralized, and all changes must go through a transparent and well-tested governance process.
  • Liquity is built to have maximized resilience, so no centralization vectors.
  1. Market History:
  • GHO is yet to be released by the Aave DAO.
  • For LUSD, there can be a small premium on LUSD results from a structural unbalance between offer and demand. The situation led to a considerable demand surge for censorship-resistant stablecoins that only LUSD can answer since there is no other alternative with a significant TVL. Nevertheless, hard peg mechanisms are built into the system between $1 and $1.10, and soft peg incentives in between. Further, Chicken Bonds are also helping to reduce the stablecoin premium, and this effect will strengthen as the protocol grows.
  1. Value:
  • The BPT from this pool has the potential to be included in the Aave Safety Module which will provide a source of rewards encouraging users to deposit into the liquidity pool creating TVL and swap fee revenue for Balancer DAO.

Pool Details

Link to Pool: GHO / LUSD Pool - 0x3fa8c89704e5d07565444009e5d9e624b40be813
Link to Gauges: GHO / LUSD Gauge - 0x70892E4355d0E04A3d19264E93c64C401520f3A4

Transaction: 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): 0x70892E4355d0E04A3d19264E93c64C401520f3A4
gaugeType(string): Ethereum


This proposal is the sole work of Matthew Graham and Dydymoon from Tokenlogic. This proposal has been funded via the Butter Delegation Campaign.

Details on TokenLogics delegation platform can be found here.


The GHO token will not launch until this weekend, but we would like to support Aave in a smooth and rapid launch. Therefore, the payload in its current form is incomplete. This BIP will become obsolete in the event if the pool and gauge specifications are not added to the payload by July 17th 2023, 08:00 PM CET and successfully completes the Balancer Maxi review cycle.

A no vote will be considered a vote against the process, not the pools, and the votes will be rerun next week with a complete spec.

1 Like


1 Like