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. The rules have been updated multiple times, based on research. The rules shall not only cover the issue described, but also prevents other extreme but possible scenarios.
Proposed Rule
To preserve the integrity of the weekly allocation system and prevent circular or redundant rewards, the following practices are prohibited for any dApp seeking or receiving allocations from VeBetterDAO:
1. Direct Double Dipping
A dApp must not use its own allocation to reward users for actions that are already directly incentivized by the protocol-level vote2earn mechanism (e.g. casting votes in proposals).
2. Recursive Rewarding (Incentive Layering)
A dApp must not reward users for interacting with another dApp where:
• The rewarded interaction is already subject to incentive allocation, and
• The primary behavior being incentivized (e.g., usage, voting, staking) is effectively the same action or result, now compensated multiple times.
This includes:
• Building a dApp that wraps or mirrors an existing incentivized dApp to harvest additional rewards
• Creating a reward structure that stacks incentives for the same on-chain action across multiple layers or interfaces
• Establishing cross-dApp partnerships that indirectly reward the same behavior via mutual or looped incentives
3. Fragmentation for Reward Multiplication
Splitting core functionality into multiple dApps solely to multiply weekly allocations or reward accruals is not allowed. If multiple dApps share infrastructure, execution paths, or are co-dependent, they may be evaluated jointly.
4. Social Amplification Loops
Rewarding users solely for broadcasting, proxying, or relaying incentivized actions (e.g., being a vote proxy, sharing vote results, inviting voters) is not allowed if those same base actions are already part of the vote2earn mechanism.
⸻
Rationale and Ecosystem Impact
The proposed rules are not just theoretical — they respond to real behavioral patterns we are already seeing in the ecosystem.
One of the examples is the widespread adoption of auto-voting features across several dApps. While these tools improve accessibility and user convenience, they have also introduced unintended consequences:
- Passive Voting Behavior: Once users enable auto-voting, they often stop actively evaluating dApps or updating their preferences. This entrenches existing vote flows, making it harder for new or evolving dApps to gain fair exposure and support.
- Governance Distortion through Automatic Abstention – In recent governance votes, we’ve seen a high number of “Abstain” votes, many of which may come from passive auto-voting.
It’s important to note that abstaining itself is a valid choice — users may genuinely decide not to take a position.
However, automatically voting “Abstain” is different. When a user has to manually open and review a proposal, they are more likely to engage, reflect, or even reconsider their stance. Automation bypasses this, inflating quorum without meaningful governance participation.
These issues weaken both the competitive fairness of dApp Allocation and the DAO governance. By addressing redundant incentive loops, this proposal aims to preserve an environment where participation is both meaningful and merit-based.
⸻
Healthy Competition is Welcome
We recognize that multiple dApps may naturally adopt similar X2Earn models — and that’s okay. Competition is part of the ecosystem, and users should have the freedom to choose. This rule does not prevent parallel dApps offering similar utilities or targeting similar use cases. It only applies when the same user action is being repeatedly rewarded across layers, creating circular incentive abuse.
⸻
Clarification & Enforcement
• The community may audit reward structures to detect violations.
• Upon successful voting, the DAO authorizes the Admin Team to enforce the Fair Use Rules as part of the dApp lifecycle management process.
• dApps may seek clarification via a public discourse thread prior to implementation.
⸻