Executive Summary
This proposal introduces a next-phase evolution of VeBetterDAO governance: a Community Execution Framework designed to expand participation, unlock developer contribution, and strengthen decentralisation while preserving security and delivery discipline.
The purpose of this proposal is to formalise a scalable and decentralized execution structure that:
-
Opens the DAO to a broader developer community
-
Encourages builders to actively participate in governance-driven innovation
-
Aligns execution incentives with long-term ecosystem growth
-
Maintains strict security oversight through VeChain review and deployment
VeBetterDAO is entering a stage where governance must evolve from decision-making alone into structured, community-driven execution. This proposal represents a meaningful step toward that future.
Long-Term Vision and Rationale
VeBetterDAO’s long-term ambition is to become a truly community-driven ecosystem where governance decisions translate into high-quality, production-ready implementations without creating internal bottlenecks.
To achieve that, three elements must coexist:
-
Clear Governance Authority— The DAO defines what should be built and approves budget caps.
-
Open Builder Participation— Developers across the ecosystem can contribute directly to DAO growth.
-
Strong Security and Delivery Guarantees— VeChain retains final review and deployment authority.
This framework is designed to strengthen all three pillars.
Rather than concentrating execution within a single internal team, this model invites the community to build alongside the Foundation. Proposal authors step into leadership roles, developers are incentivised through clear budget alignment, and VeChain ensures technical integrity.
The ambition is not incremental improvement; it is to establish VeBetterDAO as a governance system that is:
-
Scalable
-
Accountable
-
Secure
-
Decentralised in participation and execution
-
Clear in financial discipline
By embedding execution responsibility into governance itself, VeBetterDAO moves closer to the spirit of decentralisation: decisions are made by the DAO, and delivery is enabled by the ecosystem.
This proposal represents a structural evolution in how VeBetterDAO operates, positioning it for sustainable long-term growth.
Proposal Requirements (New Standard)
Every governance proposal that requires technical implementation must include:
-
Maximum Implementation Budget
-
Denominated in B3TR
-
Paid from the VeBetter treasury
-
Acts as a hard cap
-
Ideal Development Timeline
-
Estimated duration to complete the implementation
Proposals without a defined maximum budget and timeline will not be eligible for execution under this framework.
If additional funding is required beyond the approved maximum, a new governance proposal must be submitted.
Execution Process
Step 1 — Governance Approval
-
Proposal is submitted with scope, maximum budget, and timeline.
-
The DAO votes.
-
If approved, the proposal moves into execution.
Step 2 — Proposal Author Becomes Execution Lead
Once approved:
-
The proposal author becomes responsible for execution coordination.
-
The author must:
-
Identify and select a developer or development team
-
Oversee implementation progress
-
Ensure delivery aligns with approved scope
The proposal author effectively acts as the product owner for that proposal.
There is no centralized Foundation-controlled developer selection mechanism under this model.
Step 3 — Development
The selected developer may implement:
-
Smart contracts
-
Frontend components
-
Integrations
All development must strictly follow the approved proposal scope. In case of development or changes needed on other VeChain services that VeBetter relys on, such as Lambdas, Indexer etc., the developer should get in touch with VeChain who will provide support.
Step 4 — Technical Review and Audit by VeChain
All code must be submitted to VeChain via pull requests.
VeChain acts as:
-
Technical reviewer
-
Security auditor
-
Final approver for merge and deployment
If the implementation meets standards:
-
VeChain approves the PR
-
Code is merged
-
Deployment to production is executed
If the implementation does not meet standards:
-
VeChain provides technical or security feedback
-
The developer must revise and resubmit
-
Approval occurs only once all requirements are satisfied
Step 5 — Treasury Payment Mechanism
The treasury payment process is status-driven and tied to proposal lifecycle updates on VeBetter.
1. Marking as “In Development”
Once governance has approved a proposal, the proposal author must:
-
Mark the proposal as“In Development”on VeBetter
-
Specify the final implementation budget, which must not exceed the maximum cap approved during the voting phase
-
Provide the selected developer’s:
-
Wallet address (to receive payment)
-
Developer nickname / identifier
No payment configuration may exceed the originally approved maximum budget.
2. Development and Review
The developer completes the implementation and submits PRs to VeChain.
VeChain conducts technical and security review. If revisions are required, the developer must update the code until it satisfies VeChain’s requirements.
3. Marking as “Completed” and Triggering Payment
Once:
-
The PR is approved
-
Code is merged
-
The implementation is deployed to production
VeChain will mark the proposal as“Completed”on VeBetter.
Marking the proposal as “Completed” automatically triggers payment from the VeBetter treasury in B3TR to the developer wallet address previously registered by the proposal author.
4. Developer Address Changes
If the developer wallet address needs to be modified during the implementation process, the proposal author must formally request the change to VeChain.
VeChain must approve and execute the address update before completion. No unilateral address changes are permitted by the proposer without VeChain validation.
This structure ensures:
-
Budget discipline (cap enforced at governance level)
-
Clear proposer accountability
-
Security validation before funds release
-
Automated payment only after successful deployment
-
Protection against unauthorized payout modifications
Governance and Neutrality Principles
-
Governance defines scope, budget, and timeline.
-
Proposal authors own delivery coordination.
-
Developers execute implementation.
-
VeChain ensures security and protocol integrity.
There is no execution priority for VeChain team.
If a proposal presents significant technical constraints or complexity, VeChain may propose itself as the implementing party under the same governance-approved budget.
Accountability Structure
-
Proposal Author → Responsible for delivery coordination.
-
Developer → Responsible for implementation quality and code integrity.
-
VeChain → Responsible for technical review, audit, merge, and deployment.
Final legal responsibility allocation will be aligned with legal counsel where necessary.
Proposal Implementation Guidelines for Proposers and Developers
To ensure long-term sustainability and architectural consistency, all proposers and developers must follow these principles when designing and implementing proposals:
1. Preserve Decentralization
Solutions must avoid introducing unnecessary intermediaries, centralized control layers, or single points of failure. Architectures should align with VeBetterDAO’s decentralized ethos and minimize trust assumptions.
2. Keep It Simple
Avoid over-architected systems, excessive abstraction, or unnecessarily complex mechanics. Implementations should be understandable, maintainable, and realistically deployable. Simplicity is preferred over sophistication.
3. Improve the System Structurally, Not Incrementally
Proposals should aim to improve the DAO framework holistically rather than repeatedly adjusting minor parameters or single variables. The focus should be on durable structural improvements that reduce the need for frequent rule changes.
Benefits
-
Scalable execution model
-
Clear treasury discipline through upfront budget caps
-
Incentive alignment via post-delivery payment
-
Reduced internal bottlenecks
-
Maintained security and deployment control
Considerations and Clarifications
Budget Definition and Developer Coordination
Proposal authors may not always know the exact implementation budget or developer from the start. In practice, proposers are encouraged to collaborate with developers during the discussion phase on Discourse to estimate scope, timeline, and costs before submission. This process aims to strengthen collaboration between idea creators and builders.
Technical Review and Auditing
At this stage, VeChain Foundation will act as the primary technical reviewer to guarantee security and protocol integrity, given that parts of the stack are not yet fully open sourced. As the ecosystem matures and more components become open, the review layer can expand to include additional independent auditors.
Conclusion
VeBetterDAO was created to pioneer a better model for incentivised, community-driven impact. As governance matures, our execution model must mature with it.
This proposal is about expanding participation, aligning capital with delivery and accountability and about stepping forward into a more decentralised, scalable future.
By embedding budget discipline into governance, empowering proposal authors to lead execution, opening the door to ecosystem developers, and maintaining VeChain’s uncompromising security oversight, we establish a governance system that is both ambitious and responsible.
This framework means:
-
VeBetterDAO is open to builders.
-
Governance decisions lead to real, production-grade outcomes.
-
Decentralisation is not theoretical, it is operational.
This will mark a meaningful evolution in how VeBetterDAO operates, transforming governance from a voting mechanism into a structured engine for ecosystem growth.
This is the next step toward a DAO that is not only participatory in decision-making, but powerful in execution.