Governance

DAO Constitution

Version 1.0 · April 2026 · Ratified at genesis

This Constitution establishes the principles, structure, and operating rules of CaveBro DAO. It is a living document — amendments may be made by supermajority governance vote. The version number and ratification date are updated on each amendment.

ARTICLE I — FOUNDING PRINCIPLES

Nothing leaves your device. This is the non-negotiable rule for membership in the CaveBro ecosystem.

Holders signal. Devs execute. Neither role overrides the other.

The cave is dark by design. No tracking, no ads, no pivot to surveillance.

We do not ask for trust. We publish contracts.

Any proposal that contradicts these principles is invalid regardless of vote outcome. The founding principles may not be amended.

ARTICLE II — MEMBERSHIP

2.1 Token Holders

Any wallet holding $LOCAL tokens is a member of CaveBro DAO with governance rights proportional to their token balance at the time of a governance snapshot.

2.2 Genesis NFT Holders

Wallets holding CaveBro Genesis NFTs have additional governance weight as specified in the NFT Terms. NFT governance weight is additive to any $LOCAL-based voting weight.

2.3 Developers

Developers whose apps have been approved by governance vote are members of the CaveBro DAO developer tier. They have no special voting rights beyond their token holdings, but they have the right to receive ecosystem fund allocations as approved by governance, and to submit proposals without a minimum token holding requirement.

2.4 Founding Team

The founding team holds 15% of total $LOCAL supply subject to vesting as described in the Token Disclaimer. The founding team participates in governance as token holders. No special founding team veto or override power exists after TGE.

ARTICLE III — GOVERNANCE MECHANICS

3.1 Platform

Phase 1 (genesis): Off-chain voting via Snapshot. Gasless for all participants. Snapshot space: TBD at launch.

Phase 2: Migration to on-chain governance (target: after 1,000 unique token holders and $500K TVL in staking contract). Timeline subject to governance vote.

3.2 Voting Weight

Source Weight
1 $LOCAL token 1 vote
1 Genesis NFT 1,000 votes

Voting weight is calculated at the snapshot block height for each proposal. Weight is non-transferable during an active vote — tokens moved after snapshot do not affect the vote.

3.3 Proposal Types and Thresholds

Proposal type Quorum Approval Discussion Vote period
New app / dev onboarding 5% circulating Simple majority 7 days 5 days
Dev allocation size 5% circulating Simple majority 7 days 5 days
Treasury spending 5% circulating Simple majority 7 days 5 days
App / dev removal 10% circulating 67% supermajority 14 days 7 days
Fee split change 10% circulating 67% supermajority 14 days 7 days
Emission schedule change 10% circulating 67% supermajority 14 days 7 days
Constitution amendment 15% circulating 75% supermajority 21 days 7 days
DAO wind-down 20% circulating 80% supermajority 30 days 14 days

3.4 Proposal Submission

To submit a standard proposal, a wallet must hold a minimum of 10,000 $LOCAL at the time of submission, or be a registered DAO developer.

Proposals must include:

Proposals that are unclear, incomplete, or that contradict the founding principles will be rejected by the founding team during Phase 1. Once Phase 2 onchain governance is active, rejection requires a separate governance vote.

3.5 Quorum Failure

If quorum is not reached by the end of the voting period, the proposal fails. It may be resubmitted after a minimum 7-day cooling-off period. The resubmitted proposal may not materially change its substance — to change substance, a new proposal must be filed with a fresh discussion period.

ARTICLE IV — DEVELOPER ONBOARDING

4.1 The Rule

Any app proposed for inclusion in the CaveBro ecosystem must satisfy the founding principle: nothing leaves the user's device. This is a hard requirement. No proposal for an app that transmits user data externally will be accepted for a vote.

4.2 Proposal Requirements

A developer proposing app inclusion must provide:

  1. App name, platform, and brief description.
  2. Technical explanation of how the on-device requirement is satisfied.
  3. Link to a working build or TestFlight/beta access for community review.
  4. Requested ecosystem fund allocation (amount and schedule).
  5. Developer wallet address for fund receipt.
  6. Commitment to open-source the app's smart contract interactions (if any).

4.3 Allocation Structure

Approved developers receive ecosystem fund allocations as voted. Allocations are released on a schedule determined per proposal (typically monthly over 6–12 months). Allocations are held in the ecosystem fund multisig and released automatically per the approved schedule, subject to the developer not being removed by governance.

4.4 Developer Obligations

Approved developers commit to:

ARTICLE V — DEVELOPER REMOVAL

5.1 Grounds for Removal

A developer may be subject to removal from the CaveBro ecosystem if:

5.2 Process

  1. Any holder submits a removal proposal with documented evidence of the grounds.
  2. 14-day mandatory discussion period. The developer has the right to respond publicly.
  3. 7-day vote. Requires 67% supermajority of participating voting weight.
  4. If passed: app removed from gift code redemption infrastructure, future allocation payments cease.
  5. Amounts already paid to the developer are not clawed back.

ARTICLE VI — TREASURY AND FEES

6.1 Revenue Sources

The DAO treasury receives revenue from the following sources:

6.2 App Revenue Share Rate

The initial contribution rate is set by the founding team prior to the first app onboarding and published in the governance forum. Subsequent changes require a simple majority governance vote. To reduce friction for early-stage apps, governance may vote to apply a reduced rate for the first 12 months of an app's membership. The rate applies to net revenue received by the developer after deducting platform marketplace fees (e.g. Apple App Store, Google Play Store cuts).

6.3 Treasury Allocation

Source Staking rewards Ecosystem fund Operations
App revenue share 30% 50% 20%
LP fees 40% 40% 20%
NFT royalties 20% 60% 20%

6.4 Treasury Multisig

All treasury funds are held in a Safe multisig on Base. Signers and threshold are published on-chain and in the official Discord. Treasury transactions above a defined threshold require governance approval before execution.

6.5 Seasonal Reporting

The founding team publishes a treasury report each season (every 3 months) covering: revenue received, distributions made, ecosystem fund balance, and staking rewards emitted. Reports are posted to the governance forum and Discord.

ARTICLE VII — EMISSION SCHEDULE

$LOCAL emission follows a burn-linked seasonal model:

Emission occurs at the start of each season. The burn count for the reference season is locked at the end of that season and is verifiable on-chain.

Changes to the emission schedule require a 67% supermajority governance vote.

ARTICLE VIII — AMENDMENTS

This Constitution may be amended by a 75% supermajority governance vote with a minimum 15% circulating supply quorum, following a 21-day discussion period and 7-day voting window.

The founding principles in Article I may not be amended under any circumstances.

All amendments are recorded with version number, date, and the on-chain vote result. The full amendment history is maintained in the public governance forum.

This Constitution was ratified at the CaveBro DAO genesis. It is a living document subject to amendment by the community it governs.


CaveBro DAO · $LOCAL · Base · Nothing leaves your device