[BIP-122] Retire OHM/DAI/WETH Gauge & Add OHM-ETH + OHM-DAI Gauges [Ethereum]

Summary:
Enable gauges for the OHM-ETH & OHM-DAI pools.

References/Useful links:

• Website: https://www.olympusdao.finance/

Protocol Description:
Olympus is building OHM, a community-owned, decentralized and censorship-resistant reserve currency that is asset-backed, deeply liquid and used widely across Web3.

Motivation:
As part of the Olympus RBS launch, the OHM-DAI-ETH pool has been equally split into two new pools, OHM-DAI & OHM-ETH as to simplify the conduction of market operations by the Olympus Treasury under this new Range-Bound System. Since migrating the bulk its liquidity onto Balancer, the OHM pool has been one of the top pools in terms of volume generated, greatly contributing to the total revenues accruing to veBAL holders. Olympus DAO would like to explore different ways to attract additional and/or external liquidity for these two pools by enabling gauges. The gauge for the OHM-DAI-ETH pool should also be disabled as the Olympus Treasury is expecting to migrate fully out of it in the coming days.

Specifications:

  1. OlympusDAO is currently using snapshot for Governance: Snapshot
    Treasury multisig 4 of 8: Holds Olympus Treasury assets
    DAO multisig 4 of 8: Holds DAO funds
    Policy multisig 3 of 5: Changes to policy (reward rate adjustments, turn on/off bond markets)

  2. Oracles:
    No oracles used

  3. Audits:
    Audit Reports

  4. Centralization vectors:
    No centralization vector

  5. Market History:
    OlympusDAO expects these two new pools to remain one of the highest revenues drivers for the Balancer ecosystem.

OHM-ETH

OHM-DAI

OHM-ETH Gauge address: 0x5f2c3422a675860f0e019Ddd78C6fA681bE84bd4
OHM-DAI Gauge address: 0x107A2209883621aFe2968da31C03190e0B2782C2

Additional Specification

Included in this proposal is the removal of the OHM/DAI/WETH gauge.

If approved, the DAO Multisig 0x10A19e7eE7d7F8a52822f6817de8ea18204F2e4f will interact with the AuthorizerAdaptor at 0x8F42aDBbA1B16EaAE3BB5754915E0D06059aDd75 and call performAction using 0xab8f0945 for the data(bytes) argument and 0x852CF729dEF9beB9De2f18c97a0ea6bf93a7dF8B for the target(address) argument.

0x852CF729dEF9beB9De2f18c97a0ea6bf93a7dF8B corresponds to the gauge contract for OHM/DAI/WETH.

3 Likes

updated the proposal to include gauge addresses and the specification for retiring ohm/dai/weth gauge. good to go for next week

1 Like

Thanks, will you put it up on Snapshot ?

we will on Thursday, yes

1 Like

https://snapshot.org/#/balancer.eth/proposal/0xa94c523cd286f12a1a96f797d05fe39e3fa6cc47489e8a415eca1132d1b73d5e