Rule 1: User-Affirmed Governance & UI
User Confirmation: Any modification of user vote preferences must be executed through a clear, user-signed transaction. Background updates without a dedicated user-confirmed transaction are prohibited.
Visibility of Choice: The UI must display all endorsed dApps, ensuring users can modify selections for any project before confirmation.
Opt-Out Requirement: dApps must provide a visible UI component to opt out of the governance service at any time.
Conversion Allowance: dApps may include a function to convert B3TR to VOT3 when a user initiates in-app voting as long as such transaction is disclosed and confirmed by the user.
Rule 2: Self-Promotion
dApps may prioritize themselves in the interface and pre-fill vote preferences as follows:
New Users: If no existing preferences exist, the dApp may pre-fill with 100% weight toward itself.
Existing Users: The dApp may add itself to the list, provided its pre-filled weight is lower than or equal to any individual dApp in the user’s new selection.
Rule 3: True Neutrality
If a dApp provides governance services and the user opts in without specifying preferences, or preferences become ineligible, the following defaults apply:
App Allocation: No vote shall be cast until the user explicitly confirms a selection through a signed transaction.
Proposal Voting: DAO-wide proposals must be set to “Abstain.”
Rule 4: Vote Redistribution
Weight Redistribution: If a dApp in a user’s preference becomes ineligible, its weight must be redistributed equally among the user’s remaining selected dApps.
Redirection Prohibition: dApps cannot redirect weight from ineligible projects to the host dApp or any project not explicitly included in the user’s most recent confirmed selection. If all projects become ineligible in the user’s selection, Rule 3 applies.
Vote modifying: dApps are prohibited from modifying a user’s existing vote preferences—including the addition or removal of eligible projects—except where explicitly required by the redistribution logic defined in Rule 4 (Weight Redistribution and Redirection Prohibition), and according to self-promotion described in Rule 2.
Rule 5: Anti-Bribery Measures
dApps may not offer manual rewards, “x2earn” multipliers, or any perks that assist in unlocking them if such incentives are conditioned on the user voting for that specific dApp.
Rule 6: Fund Neutrality
dApps are prohibited from using allocation and grant funding received from the VeBetter DAO Treasury to vote in weekly dApp allocation rounds.
Exemption: dApps maintain the right to use Treasury grant funds and allocation to support and vote on proposals.
Universal Exclusion
These rules apply to all in-app voting integrations unless limited by the functional logic of the Native VBD Auto-Voter, as its automation and logic are subject to DAO governance and community contributions.