Governance Overview

Token holders govern Fanbase through voting on protocol changes, treasury spending, and platform direction—true community ownership.

Your Platform. Your Rules.

$FAN token holders control Fanbase through decentralized governance. Vote on protocol changes, direct treasury spending, and shape the platform's future.

Governance Powers:

  • Protocol parameter changes

  • Treasury allocation ($150M)

  • Feature development priorities

  • Economic model adjustments


What You Govern

Protocol Parameters

Economic Settings:

  • Fee rates for non-stakers

  • Staking reward adjustments

  • Emission curve modifications

  • Buyback/burn programs

Platform Rules:

  • Content moderation policies

  • Creator verification requirements

  • Payment processing rules

  • Multi-chain expansion decisions

Treasury Management

$150M Treasury Spending:

  • Marketing budget allocation

  • Partnership development

  • Developer grants

  • Operational expenses

  • Community initiatives

Large spends require community approval (e.g., >$100K threshold).

Feature Development

Roadmap Prioritization:

  • Which features built first

  • Resource allocation

  • Third-party integrations

  • Platform improvements

Community decides what matters.

Strategic Decisions

Major Changes:

  • Multi-chain expansion (add new blockchains)

  • Exchange listing approvals (CEX or DEX)

  • Major partnerships (strategic alliances)

  • Tokenomics adjustments (if needed)


Voting Mechanics

Voting Power: 1 Token = 1 Vote

Simple model:

  • Hold 10,000 $FAN = 10,000 votes

  • Hold 1,000,000 $FAN = 1,000,000 votes

No special classes or complex formulas. Straightforward ownership-based voting.

Who Can Vote:

  • Any $FAN holder (amount in wallet at snapshot)

  • Don't need to be staking (but staking recommended)

  • No minimum holding (1 token = 1 vote)

Proposal Process

Step 1: Submission (Day 1)

  • Community member submits proposal

  • Requires minimum $FAN holding (e.g., 100K tokens - anti-spam)

  • Includes description, rationale, execution plan

Step 2: Discussion (Days 2-8)

  • 7-day discussion period

  • Community debates in forum

  • Amendments suggested

  • Sentiment gauged

Step 3: Voting (Days 9-16)

  • 7-day voting window

  • Token holders vote Yes/No/Abstain

  • Real-time tally visible

  • Voting power = tokens held at snapshot

Step 4: Tally (Day 17)

  • Check quorum (10% of circulating must vote)

  • Check threshold (>50% yes votes required)

  • Result finalized

Step 5: Execution (Days 18+)

  • If passed: 48-hour timelock, then execute

  • If failed: Proposal archived, no action

Total timeline: ~18 days from submission to execution

Governance Parameters

Parameter
Value
Purpose

Quorum

10% of circulating

Minimum participation required

Threshold

>50% yes votes

Simple majority

Voting Period

7 days

Time to cast votes

Discussion Period

7 days

Debate before voting

Timelock

48 hours

Safety delay before execution

Proposal Cost

100K $FAN held

Anti-spam mechanism

All parameters adjustable via governance itself.


Governance Examples

Example 1: Treasury Spending

Proposal: "Allocate $5M from treasury for creator acquisition marketing campaign"

Arguments For:

  • Drives platform growth

  • Attracts high-profile creators

  • Increases token demand

Arguments Against:

  • $5M too expensive

  • Organic growth better

  • Better uses for capital

Community votes. Majority decides.

Outcome: If >50% vote yes and >10% participate → $5M allocated. If no → Treasury preserved.

Example 2: Fee Adjustment

Proposal: "Reduce non-staker fee from 5% to 3%"

Arguments For:

  • More competitive with traditional platforms

  • Attracts users hesitant to stake

  • Increases transaction volume

Arguments Against:

  • Reduces platform revenue

  • Diminishes staking incentive

  • Race to bottom

Vote Result: Community decides platform economics.

Example 3: Multi-Chain Expansion

Proposal: "Deploy $FAN to Arbitrum network"

Arguments For:

  • Lower fees for users

  • Tap into Arbitrum ecosystem

  • More accessibility

Arguments Against:

  • Development distraction

  • Fragments liquidity

  • Focus better on Ethereum/Base

Community controls strategy.


Voting Rights Distribution

Community vs. Insiders:

  • Community: 600M tokens (60%)

  • Insiders: 400M tokens (40%)

Community has majority. Insiders can't unilaterally control.

What this means:

  • Insiders must convince community

  • Good proposals pass (aligned incentives)

  • Bad proposals blocked (community protection)

Power to the people.

Preventing Whale Manipulation

Concern: Single whale with 20% could dominate

Protections:

  • Need >50% to pass (no single entity has this Day 1)

  • Quorum requirement (10% must participate)

  • Timelock delay (community can react)

  • Multiple large holders balance each other

Future: Delegation

  • Small holders delegate votes to trusted members

  • Retain tokens, transfer voting rights

  • Increases participation

  • Revocable anytime


Off-Chain Voting (Gas-Free)

Snapshot Integration:

  • Vote off-chain (no gas fees)

  • Proves token holdings without on-chain transaction

  • Results published on-chain for transparency

  • Makes voting accessible to small holders

How it works:

  1. Proposal created on Snapshot

  2. You sign vote with wallet (free)

  3. Snapshot verifies you hold tokens

  4. Vote recorded off-chain

  5. Result tallied and published

No gas fees = more participation.


Governance Activation Timeline

Phase 1: Foundation (Months 1-3)

  • Governance contracts deployed

  • Initial parameters set

  • Test proposals (non-binding)

  • Community practice voting

Phase 2: Soft Launch (Months 4-6)

  • Governance goes live (binding votes)

  • Start with low-risk proposals

  • Build community experience

  • Refine processes

Phase 3: Full Power (Month 7+)

  • All governance active

  • Treasury spending votes

  • Protocol changes

  • Strategic decisions

Gradual rollout ensures stability.


Treasury Oversight

$150M Treasury (15% of supply)

Governance Role:

Small Spends (<$100K):

  • Team executes (operational flexibility)

  • Monthly reports published

  • Community monitors

Large Spends (>$100K):

  • Requires governance proposal

  • Community votes yes/no

  • If approved: Team executes

  • If rejected: Funds stay in treasury

Emergency Spends:

  • Multisig can act quickly (security issues)

  • Community notified immediately

  • Retroactive vote (community can override)

Transparency:

  • All treasury movements on-chain

  • Monthly spending reports

  • Wallet addresses public

  • Auditable by anyone


Your Governance Responsibilities

As Token Holder:

1. Stay Informed

  • Read proposals carefully

  • Participate in discussions

  • Understand implications

  • Vote on every proposal

2. Vote Your Interests

  • Support good proposals

  • Reject bad proposals

  • Think long-term (not just short-term price)

  • Protect community

3. Hold Team Accountable

  • Monitor treasury spending

  • Verify execution of passed proposals

  • Raise concerns publicly

  • Use governance to correct course

Governance requires active participation.


Governance Best Practices

For Voters

Do:

  • ✅ Research proposals thoroughly

  • ✅ Participate in discussions

  • ✅ Vote on every proposal

  • ✅ Think long-term

  • ✅ Verify execution

Don't:

  • ❌ Vote blindly (DYOR)

  • ❌ Skip governance (your voice matters)

  • ❌ Only focus on price (governance ≠ trading)

  • ❌ Trust team blindly (verify decisions)

For Proposal Authors

Create Good Proposals:

  • Clear objective (what you want)

  • Strong rationale (why it matters)

  • Execution plan (how it works)

  • Risk analysis (what could go wrong)

  • Cost breakdown (if spending required)

Engage Community:

  • Pre-proposal discussion (gauge sentiment)

  • Respond to feedback (improve proposal)

  • Build consensus (convince skeptics)

Good proposals pass. Bad proposals fail. That's how it should work.


Governance Protections

Against Team Abuse:

  • Community can block bad team proposals

  • Treasury spending requires approval

  • Protocol changes need votes

  • Multisig removable via governance

Against Whale Manipulation:

  • Need >50% to pass (no single whale)

  • Quorum requirement (can't pass with 3% turnout)

  • Timelock delay (48 hours to react)

  • Community can organize against whales

Against Spam:

  • Proposal cost (100K $FAN required)

  • Discussion period filters bad ideas

  • Community downvotes waste of time

Balanced system protects all parties.


The Governance Advantage

Why Fanbase Governance Wins:

vs. Traditional Platforms:

  • Traditional: Company decides unilaterally

  • Fanbase: Community votes

vs. Other Crypto Projects:

  • Others: Governance theater (founders control majority)

  • Fanbase: Real power (60% community allocation)

vs. No Governance:

  • Others: Trust team forever

  • Fanbase: Verify and vote


Continue to Roadmap →

Last updated