Proposed by: gianni.veworld.vet
Date: July 15, 2025
Category: Governance, Transparency, dApp Ecosystem
This proposal introduces an automatic rule to remove dApps that receive a “Lost” endorsement status for two consecutive rounds, keeping the VeBetterDAO ecosystem clean, active, and focused on supported projects.
Detailed Description:
Currently, dApps that fail to receive enough endorsements are labeled as “Lost”, but they can remain visible in the DAO list indefinitely—even if they show no signs of activity. This creates clutter and reduces visibility for new or more promising projects.
Proposal:
- If a dApp receives the “Lost” status for 2 consecutive rounds, it will be automatically removed from the list of active dApps.
- Once removed, the project team will have the opportunity to reapply as a new dApp, going through the same submission and endorsement process as any new project.
- This ensures a fair and dynamic environment where visibility is earned through continued engagement and support.
Objectives:
- Keep the dApp list clean and focused on active initiatives.
- Improve the user experience by reducing clutter.
- Motivate project teams to remain engaged and maintain visibility.
- Automate a currently manual process, reducing administrative burden.
Benefits for VeBetterDAO:
- A more efficient and merit-based ecosystem.
- Easier discovery of new and active projects.
- Improved DAO transparency and project rotation.
- Clear rules for inactive or unsupported initiatives.
Implementation Approach:
- Add backend logic to monitor the endorsement status history of each dApp.
- If a dApp receives a “Lost” status for two consecutive rounds, it will:
- Be marked as “Removed”
- Be hidden from the public dApp list
- Trigger a notification to the project team via email or dashboard
- The team can reapply from scratch at any time, using the standard new dApp submission process.
Requested Budget:
None.
This proposal requires a simple technical update that can be implemented by the VeBetterDAO core dev team with minimal effort.
Timeline:
- Effective starting from the next round after approval
- Estimated development time: within 2 weeks
Optional: Exception Mechanism
An optional “exception request” may be submitted by the project team (via form or direct contact), in case of temporary downtime due to technical upgrades, rebranding, or other valid reasons. Final discretion remains with the core team.