BAP Process
BOB’s governance process is designed to ensure the protocol remains decentralized, transparent, and community-driven. Every member of the community has a voice, and delegates play a central role in representing tokenholders and driving the DAO’s mission forward.
1. Discussion Phase
Community members can propose ideas and topics on this Community Forum. While not strictly mandatory before submitting a formal BAP, this phase offers a valuable opportunity to gather feedback and refine ideas. It’s especially useful for members who haven’t yet met the BAP submission threshold, giving them a space to share and discuss concepts with the community.
Please use the following discussion templates:
- Discussion Template: Spending BAP
- Discussion Template: Technical BAP
- Discussion Template: Governance & Structural BAP
2. Official BAP Drafting & Submission
Eligible delegates (including self-delegates) draft official BAPs. To submit a BAP, delegates must hold at least 0.07% of the total token supply (7M BOB).
All delegates should use the templates provided and include as much detail as possible. Clear, well-documented BAPs are easier for the community to understand and discuss. BAPs that are unclear may require additional clarification, cause execution delays, or even be vetoed.
BAP templates for submission on gov.gobob.xyz:
3. Voting
Voting is the mechanism through which the community decides which BAPs should be implemented.
| Parameter | Value |
|---|---|
| Quorum for passing | 0.5% of total supply (50M BOB) |
| Passing threshold | More than 50% + 1 (“AYE”) of participating tokens |
| Voting period | 7 days |
| Voting delay | 1 day after submission |
4. Implementation
Approved BAPs are executed by the responsible delegate(s) or parties explicitly designated in the BAP. Delegates ensure faithful execution aligned with tokenholder interests and the DAO’s mission.
Minimum timelock delay: 7 days