DAO & Governance9 min read•Published 2026-10-22

What a DAO Should (and Should Never) Govern: Separating Core Software Engineering from Community Treasury

Why DAOs fail when they try to manage software engineering sprints—and how FWB, Optimism, Jupiter, and ONTON Constitution v2.1 separate core product companies from community treasuries.

M
Mahdi Farimani
Founder & Lead Architect, ONTON
🏛️ ONTON DAO & Telegram Governance Knowledge Base

This analysis is part of our 12-part research series benchmarking global DAOs and TON governance architecture.

Key Takeaways for Web3 Founders & DAO Architects:

  • Committees Cannot Ship Great Software: Every DAO that tried to manage daily product engineering, UI design, and server operations through token-holder votes failed to ship on time.
  • How the Best Ecosystems Solved It: Friends With Benefits ($FWB) spun out Scene Infrastructure Co., the Optimism Collective separated OP Labs from the DAO Houses, and Jupiter kept core product execution inside the founding company while giving the DAO control over the 50% Litterbox Buyback Trust.
  • The ONTON Constitution v2.1 Boundary: ONTON Platform retains 100% ownership of software IP, servers, domains (onton.live), and bots (@theontonbot) plus 75% of net fee revenue, while ONTON DAO governs the 25% Net Revenue Buyback & Yield Warchest, Co-Host Event Grants, and the 200M $ONIT Community DAO Reserve.

Part of the Everything About DAOs on Telegram & TON Master Guide.


1. The Myth of the "Do-Everything" DAO

In 2021, a dangerous myth swept through Web3: the idea that a decentralized autonomous organization should replace the startup engineering team entirely. Founders dissolved product teams into loose Discord "working pods," requiring a 7-day Snapshot vote just to hire a frontend developer, fix a checkout bug, or redesign a landing page.

The results were predictable:

  • Paralyzed Shipping Velocity: As we documented in our Friends With Benefits ($FWB) Analysis, FWB's internal software pods struggled with seasonal budget politics until FWB finally spun out Scene Infrastructure Company (SIC) as a focused software business.
  • Security & Operational Risk: When server keys, database migrations, and emergency hotfixes require public committee debates, attackers move faster than defenders.
  • Web2 Customer Alienation: Mainstream enterprise and university event organizers want a reliable software vendor—not a chaotic token forum arguing over ticket checkout buttons.

2. How Top Ecosystems Draw the Line Between Company and DAO

When we benchmarked five leading DAOs across Ethereum, Solana, and Base, a clear constitutional pattern emerged: keep product engineering centralized and fast; make revenue sharing, grant allocation, and priority signaling decentralized and verifiable.

Ecosystem Core Product & Engineering Entity Community DAO & Treasury Layer
Optimism OP Labs: Builds the OP Stack, sequencer software, and core infra Optimism Collective: Token House + Citizens' House governing Retro Funding & Superchain buybacks
Jupiter Jupiter Core Team: Builds jup.ag aggregator, mobile app, and perps Jupiter DAO: Governs the 50% Litterbox Buyback Trust, Active Staking Rewards, and working group grants
FWB Scene Infrastructure Co. (SIC): Builds social and event software tools FWB DAO: Governs FWB Cities, cultural editorial, and community treasury
ONTON (v2.1) ONTON Platform: Owns 100% of code, IP, servers, onton.live & @theontonbot (75% of net fee revenue) ONTON DAO: 3 Chambers governing the 25% Revenue Buyback Warchest, Co-Host Event Grants & 200M $ONIT DAO Reserve

3. What a DAO Should Govern vs. What It Should Never Touch

If you are designing a DAO on Telegram and TON, use this clear separation of powers from the ONTON Brand & Ecosystem Wiki:

What the Core Company Must Always Control (100% Sovereignty)

  1. Software Architecture, Code & Databases: Shipping weekly features, fixing bugs, and maintaining 99.9% uptime.
  2. Security, Keys & Abuse Moderation: Enforcing rotating TOTP QR check-in security, protecting user data, and quarantining scam events.
  3. Zero-Crypto Mainstream UX (Layer 1): Ensuring any Web2 organizer or attendee can use onton.live and @theontonbot with Google, Email, or Telegram login and Telegram Stars without ever touching a crypto wallet.

What the DAO Is Uniquely Built to Govern

  1. The Revenue Buyback & Yield Warchest (OIP-4 Regimes):
    In ONTON DAO, Chamber 3 (Genesis ONION Senate) governs how the 25% Net Revenue Buyback Covenant is split between open-market $ONIT buybacks on STON.fi and JVault staking yield (60/40 Balanced, 80/20 Growth, or 30/70 Yield).
  2. Ecosystem Co-Host Event Grants & City Chapters:
    Chamber 2 (Organizer Council)—composed strictly of organizers who have proven real attendance via Proof-of-Gathering—ranks and allocates co-host event sponsorships and regional city chapters.
  3. Community Bounties & Priority Ranking:
    Through weekly Event-Driven Priority Polls, all three chambers rank which ecosystem integrations and community initiatives should be prioritized next.

4. Why This Boundary Protects Both Web2 Users and $ONIT Holders

When the boundary between the software company and the DAO is crystal clear:

  • Mainstream Organizers Win: They get a fast, clean, Nordic-minimalist event platform (Luma vs. ONTON Comparison) with 0% fees on free events and zero forced crypto jargon.
  • $ONIT & Genesis NFT Holders Win: Every paid ticket and on-chain SBT upgrade across the entire mainstream platform feeds 25% of net fee revenue directly into the DAO's audited buyback and staking yield warchest (0144_dao_buyback_ledger.sql).

Continue Exploring the ONTON DAO Knowledge Base

Ready to host your event inside Telegram?

1-tap Free RSVPs, Telegram Stars payments, and automated chat gating with 0 wallet friction.

Start in Telegram →

Related Tactical Guides & Resources

DAO & Governance

Friends With Benefits ($FWB) DAO Analysis: Why Event Communities Must Separate Software from Token Gates

An honest teardown of Friends With Benefits ($FWB) DAO: what worked with FWB Cities and Local/Global tiers, why mandatory token gates and DAO software pods failed, and lessons for ONTON.

Read Now →
DAO & Governance

DAO Treasury & Staking Economics: Why Revenue Buyback Covenants Beat Inflationary APY

Why inflationary staking APY destroys shallow DEX pools—and how DAO Revenue Buyback Covenants, FDV-gated FairLock vesting, and cooldown unstaking build lasting token economies on TON.

Read Now →
DAO & Governance

How to Build a DAO on Telegram & TON: Jettons, SBTs, Mini-App Polls & Automated Chamber Groups

The complete engineering and product guide to building a DAO on Telegram and the TON Blockchain using TEP-74 Jettons, TEP-85 SBTs, cSBTs, TonProof, JVault, ton.vote, and automated Telegram groups.

Read Now →