As discussed in the recent thread on Vote2Earn2Earn mechanisms, I’d like to formally propose a rule to be added to the VeBetterDAO framework to ensure fair and sustainable participation for all dApps.
Background
VeBetterDAO already incentivizes voter participation through its Vote2Earn model. However, some dApps have introduced additional incentive loops, encouraging users to vote through their dApp in order to farm allocation rewards—what we’ve come to call “Vote2Earn2Earn.”
This structure allows certain dApps to gain a disproportionate share of allocation by layering incentives on top of existing Vote2Earn rewards, which creates:
- Unfair advantages over dApps focused on utility and long-term value
- Systemic risks of low-quality, engagement-farming projects
- A dilution of governance intent, turning votes into tools for reward maximization rather than ecosystem signaling
Proposed Rule
Any dApp that builds a reward model directly on top of the VeBetterDAO Vote2Earn mechanism—specifically by incentivizing users to vote through the dApp for its own benefit—should be ineligible for dApp Allocation.
This rule aims to preserve the integrity and sustainability of the VeBetterDAO reward system, while ensuring a level playing field for all participants.
Clarification – What’s Not Considered Abuse
This rule does not apply to dApps that:
• Integrate VeBetterDAO voting or delegation features to improve user accessibility
• Do not offer extra incentives for voting for themselves
• Use delegation or preset voting purely as a facilitation mechanism, not as a reward engine
• Allow users to retain full control of their voting decision (i.e. the voting path is not locked or coercive)
• Considering the complexity of the full voting UI, it is not required for the auto-vote interface to support voting for other dApps, as long as users retain the ability to choose whether to vote at all
Important: Any dApp that restricts user choice by locking delegation, obscuring how votes are cast, or coercing users into voting for a specific dApp will be considered non-compliant and ineligible for allocation.
Implementation Notes
-
Retroactive Application:
If this rule is passed, any existing dApps that are found to violate it will be removed from the dApp Allocation. -
Enforcement via dApp Lifecycle Process:
Since this rule cannot be enforced automatically, it should be incorporated into the VeBetterDAO dApp lifecycle process.
Community review will be necessary to evaluate whether a dApp’s structure aligns with the rule.
Next Steps
I’m posting this thread to gather community feedback, refine the rule language, and ultimately move toward a formal VeBetterDAO proposal.
Looking forward to your thoughts.
—Ben