[GIP-83] Gearbox V3 Reserve Fund

With GIPs 79-80 governance revamp, it was voted to move the fees accumulated so far into a separate fee guard. That is to separate development work from the fees the protocol earns. Those are for holders to decide what to do with. So this is what we need to decide on.

Previously, those fees (all fees) were taken in the form of dTokens of old pools. They functioned as Reserve Fund for V2, by default as the protocol architecture entails. By moving them away from the designated previous address, V2 won’t have a Reserve Fund anymore. Which is totally logical, because migration is being done in favor of V3, so it’s perfectly correct.

Anyway, back to the point. There is no reason to keep those assets ($600K) in the form of old V2 dTokens. They should either be unwrapped to their underlying assets or instead be repurposed for V3 Reserve Fund as intended. Either of those approaches require an action, and thus, a vote. There are a few ways to go about it without overcomplicating.

• Unwrap all of them and keep them as idle assets for now. Simple. No Reserve Fund to start with, let it accumulate from the start as before starting from nothing.
• Unwrap all of them and deposit to v3 dTokens passive side. This bootstraps liquidity of V3 as well as creates approximately a ~$600,000 Reserve Fund.

There are other ways to go about this. In case number 1 wins the vote, further ideas can be discussed. In case number 2 wins the vote, then it’s a settled-and-done matter.

As always, DAO is able to vote to unwrap incoming fees (in dTokens) to limit its treasury exposure to the Reserve Fund. For example, in case the DAO earns $5M and doesn’t want all the fees to be on the line of Reserve Fund. Gearbox has always worked this way, in fact. This extra note is simply to remind holders of such mechanisms. You can read more in the docs: 1. Protocol Fees 2. Insurance Fund