[BIP-359] Enable GHO/OHM Gauge [Ethereum]

PR with Payload


This pool uses the Weighted Pool and the gauge is uncapped.

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

References/Useful links:

Protocol Description:

Olympus is a protocol on the Ethereum blockchain with the goal of establishing OHM as a crypto-native reserve currency. It conducts autonomous and dynamic monetary policy, with market operations supported by the protocol-owned Olympus Treasury.

OHM serves a need in the market gap between fiat stable coins and volatile crypto assets, providing relative stability and scalability underpinned by the protocol’s Range Bound Stability (“RBS”) system. RBS is the flagship system of Olympus’ autonomous monetary policy and has resulted in low volatility and stability for OHM since its launch.


Olympus currently has multiple large pools on Balancer, most notably the OHM/ETH and OHM/DAI pools on Mainnet and OHM/ETH and OHM/USDC pools on Arbitrum. These pools drive significant value to veBAL holders, both through fees earned as well as third parties pairing against OHM to route into these pools (e.g. BTRFLY, FDT, BOND, PAL). It is our intention to keep growing the number and size of OHM pools with new partners and we want to continue to host these pools on Balancer.

A few months ago, Olympus DAO launched a new product launch, and deployed a OHM/wstETH pool on Balancer in cooperation with Lido. The newly launched product is a novel liquidity solution that allows for effective scaling of select LSDs and stable coins in an OHM pair. In a nutshell, this liquidity vault accepts third party deposits of LSDs or stable coins and mints an equivalent amount of protocol-owned OHM against this as a counter asset. The OHM side of the LP does not accrue any rewards, so it cuts down the incentivization costs by half for partners.

The first liquidity vault has shown promising results and so this gauge request is for the second launch of the product, an OHM/GHO pool.


  1. Governance:
  • OlympusDAO is currently using Snapshot for governance
  • DAO multisig 4 of >8: Holds DAO funds, executes governance proposals
  • Policy multisig 3 of 5: Changes to policy (reward rate adjustments, turn on/off bond markets)
  1. Oracles:
  • rateProvider0 (for OHM): 0x0 (none)
  • rateProvider1 (for GHO): 0x0 (none)
  1. Audits:


Aave v3

  1. Centralization vectors:
  • No centralization vectors
  1. Market History: See OHM and GHO.

  2. Value: Balancer will earn the protocol fee on the yield generated by Aave v3 on Ethereum via bb-a-wETH.

Link to Pool: OHM / GHO Pool - 0xb2b918f2d628b4c8ff237b0a1c6ac3bea222fedc
Link to Gauges: OHM / GHO Gauge - 0x73f49a29F91e016CC9BdE5cdF6f5DC049280e5A9

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


This proposal is the sole work of Matthew Graham and Dydymoon at 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