# \[RFC\] Kill WBTC/DIGG/graviAURA Gauge

**URL:** <https://forum.balancer.fi/t/rfc-kill-wbtc-digg-graviaura-gauge/3493>\
**Category:** General Proposal\
**Created:** [July 21, 2022, 7:07pm UTC](https://forum.balancer.fi/t/rfc-kill-wbtc-digg-graviaura-gauge/3493 "2022-07-21T19:07:32Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![Tritium](https://yyz1.discourse-cdn.com/flex027/user_avatar/forum.balancer.fi/tritium/32/2011_2.png) [@Tritium](https://forum.balancer.fi/u/Tritium)\
**Post date:** [August 7, 2022, 11:20am UTC](https://forum.balancer.fi/t/rfc-kill-wbtc-digg-graviaura-gauge/3493/8 "2022-08-07T11:20:38Z")

</div>

I had proposed a starting point for a basic framework here:

> [@\[RFC\] Simple Framework for veBAL gauge voting](https://forum.balancer.fi/t/rfc-simple-framework-for-vebal-gauge-voting/3520/5):
>
> Desired State: No gauge should take over 10% of all veBAL unless it granted an exception by balancer governance. I think any policy that’s based on a set % of veBAL emissions is doomed to fail. For example, what stops a large veBAL holder from voting for a tokenX/ETH gauge, getting it delisted, trading it along the way, and moving on to the next victim? Who would want to enter the ecosystem, rely on it for providing sustainable liquidity, and build things on top of it - if their gauge can…

I was basing it more on % of veBAL voting. We could also do ROI, but that fluctuates a lot more, is harder to calculate as a fixed number, and in the end a whale could just add more deposits and still capture more veBAL.

For example, how would you set this 100% ROI rule on the DIGG pool? Including AURA or not? Max boost or min boost? Take using what measurements? At what time? Remember that the ROI of a small pool can quickly be lowered by just depositing more assets (which whales can do).

I would rather discuss general frameworks than more individual requests to kill gauges though, so maybe we can resume a conversation over here: [https://forum.balancer.fi/t/rfc-simple-framework-for-vebal-gauge-voting](https://forum.balancer.fi/t/rfc-simple-framework-for-vebal-gauge-voting). Get something implemented, and then apply it consistently? If the DIGG gauge gets killed with nothing else done, we just move onto the next one and spend all our time doing this over and over again.

---

_[View the full topic](https://forum.balancer.fi/t/rfc-kill-wbtc-digg-graviaura-gauge/3493)._