Community Council Term 2 Budget Proposal
Summary
We’re requesting 8,000,000 PYTH over 12 months (~666,667 PYTH/month or $328,000 as of March 25th, 2026) for Community Council Term 2.
Term 2 matches the budget to real program costs AND adds the unified content creation engine as the major new initiative, replacing Kaito and Impact Awards for a more direct, value added content creation mechanism that is more in line with the development of the broader crypto ecosystem.
Why 8M PYTH?
Term 1 Proved the Model Worked, but Required Refinement
Council term #1 burn rate was relatively low and reflected the real cost of operating community programs (Impact Awards, Kaito, council stipends, experiments). With Kaito winding down, the council has collectively researched and built a new Kaito-esque program that is better designed and refined to achieve very specific reach goals on socials.
Key cost drivers that grew during Term 1:
-
Kaito: Grew from 35,000 → 234,000 PYTH/month as the platform received more attention. The platform crashed and burned, and no longer exists.
-
Impact Awards: Consistent monthly distribution to 40+ contributors. Quality diminished over time as ‘farmers’ discovered ways to take advantage of the system.
-
Experiments Lab: Funded community development (Community Ops, Pythentity)
Term 2 Consolidates and Scales
The old budget categories — Role Stipends, Impact Awards, Kaito, Experiments Lab — are being replaced by a unified system. Impact Awards, the Clipping Program, and MissionMonitor are no longer separate line items. They’re one content creation engine:
Missions (MissionMonitor) → Content Creation → Clipping (PythClippers) → Referrals → Rewards
6M of the 8M PYTH budget flows through this unified engine. This is a consolidation of many different programs under a single unified banner that can be closely monitored. Three programs that previously had separate budgets, separate tracking, and separate oversight now run through one system with automated tracking, judging, and treasury export.
Term 2 Budget Breakdown
| Category | Monthly PYTH | Annual PYTH | Description |
|---|---|---|---|
| Content Program | 500,000 | 6,000,000 | Unified Content Creation Program |
| Ongoing Hackathon | 200,000 | 400,000 | Promoting ongoing Pyth Development and Content Showcases with community builders |
| Pythentity | TBA | 200,000 | Gamified Community identity layer & Rewards system for Pyth evangelists. |
| Role Stipends | ~46,000 | 560,000 | Role stipends, covering core content and community lore creators. |
| Council Stipend | 10,000 | 840,000 | Council Member Payments for ongoing management. |
What Term 2 Funds
1. MissionMonitor Content Engine (Primary Allocation)
The unified system for community content creation, distribution, and rewards.
-
Missions: Campaign briefs distributed via Telegram + Discord. Community creates content around Pyth milestones, launches, partnerships, and product updates.
-
Clipping Program: MissionMonitor bot handles submission tracking and leaderboards for socials content. 134+ video transcripts ready for clipping alongside a comprehensive content guidebook.
-
Referrals: Built-in referral system with attribution tracking, 10% referrer split, and 90-day expiry. Incentivizes community growth through content participation.
-
Soft Identity Gating: All programs can be gated through Pythentity for sybil resistance. Verified contributors & Pyth evangelists receive preferential treatment.
Infrastructure already built: MissionMonitor (live), Referrals System (90% complete), Pythentity (MVP live), Google Sheets export (live).
2. Pyth Playground (Vibecodeathon)
Recurring 6-week community hackathon for builders of all skill levels. AI-assisted “vibe coding” format lowers barriers. Each submission creates public content pieces (GEO requirements built in).
-
Round 1 currently live with active submissions
-
Target: 3–5 rounds in Term 2
-
Prize pool: ~200,000 PYTH per round
-
Confirmed judges from Community Council
3. Pythentity (Identity Layer)
Community-native identity and reputation system. Wallet verification + Discord OAuth + NFT gating + behavioral scoring. Gates all incentive programs for sybil resistance.
Term 2 scope:
-
Cross Chain & additional wallet support.
-
Cross-platform identity bridge (Discord + Telegram + Forum)
-
Integration with PythClippers and MissionMonitor for automatic score updates
-
Domain migration + repo transfer
-
Process remaining grant funds
Term 1 Financial Transparency
Full actuals from Google Sheet — Full breakdown.
Cycle 1 (April – September 2025)
| Category | Budget | Spent | Remaining |
|---|---|---|---|
| Role Stipends | 120,000 | 155,718 | -35,718 |
| Impact Awards | 210,000 | 224,396 | -14,396 |
| Kaito | 1,000,000 | 477,887 | 522,113 |
| Experiments Lab | 90,000 | 44,180 | 45,820 |
| Council Stipend | 420,000 | 420,000 | 0 |
| Total | 1,840,000 | 1,322,181 | 517,819 |
Cycle 2 (October 2025 – March 2026)
| Category | Budget | Spent | Remaining |
|---|---|---|---|
| Role Stipends | 120,000 | 284,140 | -164,140 |
| Impact Awards | 210,000 | 189,524 | 20,476 |
| Kaito | 600,000 | 1,015,871 | -415,871 |
| Experiments Lab | 480,000 | 403,800 | 76,200 |
| Council Stipend | 420,000 | 420,000* | 0 |
| Contingency | 60,000 | 35,050 | 24,950 |
| Total | 1,890,000 | 2,348,384 | -458,384 |
*Council Stipend is paid directly from the DAO treasury to council members — not from the council multisig. This avoids a conflict of interest (council members don’t pay themselves). Cycle 2 stipend is committed but not yet disbursed.
Key takeaway: Kaito alone consumed 53% of total Term 1 spend and exceeded its Cycle 2 budget by 415K PYTH. Role Stipends also exceeded budget in both cycles as the community role system expanded. Council Stipend shows 0 spent because stipends are paid directly by the DAO to avoid a conflict of interest — council members don’t pay themselves from their own multisig.
Governance & Accountability
Reporting
-
Quarterly budget reports posted to forum with PYTH spent per category
-
Quarterly reviews with program metrics (participation, content output, community growth)
-
All operational tooling (MissionMonitor, PythClippers) produces auditable logs
-
Google Sheets treasury tracker publicly viewable
Unused Funds
-
All unused funds return to the DAO treasury. No rollover, no discretionary holdback.
-
Term 1 wallet currently holds 376,480.91 PYTH. Remaining funds may be used during the interim period to bridge into Term 2 content programs, avoiding dead time between budget approval and program launch. Any balance beyond interim operations returns to the DAO.
Funding Source
-
DAO treasury, executed via binding governance proposal
-
Funds transfer is automatic upon proposal execution
What’s Different About Term 2
| Term 1 | Term 2 |
|---|---|
| Built MissionMonitor | Run missions at scale on MissionMonitor |
| Built PythClippers | Launch clipping program with dedicated PYTH pool |
| Built Pythentity MVP | Gate all incentive programs through Pythentity |
| Separate budgets for Impact Awards, Kaito, Experiments Lab | Unified content creation engine — one system, one budget |
| 35K PYTH/month approved budget | Right-sized to actual operational costs |
| Programs built | Programs running |
The infrastructure is built. The strategy is documented. The tools are operational. Term 2 is about making these systems produce results at scale.
Conclusion
Term 1 built the infrastructure. Term 2 runs the machine.
The Community Council exists to make Pyth’s community a genuine competitive advantage — verified contributors who know the product, build with the data, and produce content that compounds in value. The unified content creation engine (MissionMonitor + PythClippers + Pythentity) is how we do that at scale with proper accountability.
Requesting approval for a 12-month budget of 8,000,000 PYTH (4,000,000 PYTH per 6-month cycle). Cycle 2 allocation may be adjusted based on PYTH price at the time of renewal.
Questions? Tag the Community Council in Discord or comment on this proposal.