OIP-103 (Balancer migration) execution

OIP-103 was approved on Jul 12, 2022 to:

Designate Balancer as the main liquidity hub

Designate Balancer OHM-DAI-ETH as the main liquidity pool

Create a managed OHM-DAI-ETH pool initialized with pool weights at 50/25/25

Migrate the current Sushi OHM-DAI and OHM-ETH liquidity to the Balancer pool in five batches, adding ETH and OHM from reserves to match the DAI amount in each batch

The OIP text specifies that the five batches are to be executed over ten weeks.

The ideal Balancer setup for Olympus is to have all liquidity in a managed pool, initially with OHM-ETH-DAI with 50/25/25 weights. This pool should have an asset manager attached, in order to mint & sync into the pool, and the pool needs to be whitelisted to receive veBAL votes.

All interaction with Balancer pools are done via the Balancer router to find the most efficient trade at that moment. This means that a future internal Balancer migration will not be disruptive to users.

As the current Balancer pool has the right tokens and weights, and is whitelisted migration can start as soon as possible.

Proposal Prepare a migration script that will draw a given amount of Sushi OHM-DAI (e.g. 20% of the initial size of the pool), Sushi OHM-WETH and Treasury OHM and WETH to bring the ratio up to 50/25/25 and deploy to the Balancer pool.

Repeat this 4 times, 2 weeks apart with the first execution on July 29 at the latest.

The 5th (last execution) will be for the remainder of the pool.