BIP 65: Dogfooding - Deposit Collected Fees into Setts, blacklist the funds for native returns


Treasury Management

Scope: Deposit Treasury BTC’s from the Dev Multisig into our own setts and blacklist the deposits for Badger emissions so user APY is undiluted.


Pending (Following up on a post by @gosuto a week and a half ago and recent work by @Tritium)


Generate further returns for Treasury Bitcoin by depositing into Badger Setts, begin to build a framework for agile deployment of DAO Treasury assets.


Dogfooding is the idea of using your own products whenever possible, it can not only provide insight into user experience but can also solidify market trust in the product or products.

This proposal would take assets from the Dev Multisig and deposit them into Badger Sett products, the code having now been battle tested for 7 months.

At current prices just depositing in our own Setts (blacklisting native yield for those assets) could very conservatively net the DAO $1000 of extra income per day. We run these products, we should use them.

If the votes below all pass, the core team will have discretionary power over reallocation to any of Badger’s Sett products, as well as the power to deploy further assets from revenue as they are accrued.

Below is a list of target Setts with allocations we believe provide the best risk profile:

Further, the team will explore using the harvester to auto-invest in our own Setts. This could be the beginning of a number of treasury and utility focused Setts built upon our forthcoming V2 infrastructure.

Below are the funds (minus native balances and liquidity positions) that are eligible under this BIP.

Considerations have been made to simplicity of operations, the proposed plan gives the team the mandate to get funds working ASAP and is low opportunity cost. More complex procedures and dynamic management can and will eventually be built on top to maximize DAO performance.

Additionally the CVX the DAO will acquire from these strategies will not only hold value, but provide voting weight Sett product returns.

Moving Forward:

The first vote allows the team to deposit currently held revenue assets to any of our Sett products.

Do you approve of dogfooding our Setts with currently held revenue assets?

  • Yes
  • No

0 voters

The second vote gives the team the right to periodically deposit new revenues to our Setts and further explore and implement an automation for the process

Do you approve team discretionary power over dogfooding with future collected fees?

  • Yes
  • No

0 voters

The third vote gives team discretion over like-kind exchanges of assets to maximize performance.

Do you approve of the core team moving treasury assets between curve Setts to optimize yields?

  • Yes
  • No

0 voters

1 Like

Won’t this dilute trading fees rewards for users quite a bit?

Our treasury does very well and I’d rather see increasing APY for users/lps instead of cannibalizing any returns to itself.

I don’t think our treasury tokens make up more than 5% of any pool that we are in, and the deposits will not change the badger emissions.

We could also just stake the bitcoin in curve, but that has the same dilution effect, and it just seems to be the best place to stake single asset bitcoin right now. If there were somewhere better and SAFU, we’d build vaults for it before thinking about making treasury investments.


We would blacklist from Badger rewards at a contract level so it won’t dilute user deposits.

1 Like

Alright, if TVL isn’t impacted significantly and rewards blacklisted… my counter arguments fall kinda short.

1 Like

You can see the theoretical Convex pool share noted in the screenshots.

In other words, the biggest dilution would take place in the tBTC/sBTC Curve pool, where instead of Convex having $53.5m locked they would now have $54.6m locked after treasury’s deposit.

This would dilute Convex’s rewards by 53.5/54.6-1=-2%. E.g. cvxCRV rewards of 7.45% APY would turn to 7.3% APY. All other setts would see an even less noticeable dilution. BADGER rewards will not be affected.

So although users are practically unaffected, in the long run this extra acquired cvxCRV and CVX could be used strategically for gauge voting, boosting yield like we saw happen last week.


If Badger ever withdraws from dogfood setts, any withdraw fees instead of going to the DAO, should be distributed to Badger holders.

I mean, this could be an interesting BIP, but it seems kind of hard to track. In the end withdraws just go back to the dev-mutlisig (where the funds came from in the first place). Revenue sharing or an other form of tokenholder claim to the treasury is another topic, that I agree is long overdue, but not part of this BIP.