Community Council Term #1 Exit Report

Community Council
1

Community Council Term 1 Exit Report

Summary

This is the full Term 1 wrap-up for the Community Council — covering 12 months of operations. We established the foundation (role structures, reward systems, governance processes), shipped operational tooling (MissionMonitor, PythClippers, Pythentity, PythWheel), ran programs (Impact Awards, community missions, Vibecodeathon), and developed the strategic framework for Term 2.

The honest assessment: strategy outpaced execution in the back half. The systems are built and operational; scaling them is the Term 2 mandate.

What We Delivered

Programs & Initiatives

Impact Awards (ongoing)

  • 12 months of continuous operation

  • Coverage: Discord engagement, content creation, governance participation, community support, educational content

Community Missions (MissionMonitor)

  • Campaign brief distribution system: Notion campaigns → mission briefs → Telegram + Discord

  • 30+ missions posted, over 500 submissions received

  • Judges vote via Discord reactions, results tracked automatically

  • Google Sheets export for treasury tracking

Vibecodeathon / Pyth Playground (Live)

  • Recurring 6-week community hackathon — currently live with active submissions

  • GEO (Generative Engine Optimization) requirements built into submission criteria — each submission creates public content

  • Judging rubric, prize structure (~200,000 PYTH Round 1), T&Cs framework established

  • Confirmed judges: Arguer, Lowkeigh (Community Council members)

  • Active submissions: Pythian Peso Snake, FOGO Pulse, Pyngo, d1ckochart, Market DVR

Infrastructure Built

MissionMonitor Bot (Shipped & Live)

  • Discord bot for campaign distribution, submission tracking, judge voting, deadline enforcement

  • Auto-creates submission threads, tallies judge votes, exports results to Google Sheets

  • Hosted on VPS, tested end-to-end with Community Council

  • First mission posted and completed successfully

  • Referrals system built: code generation, deep link attribution, 10% referrer split, 90-day expiry

  • GitHub: Chop-Kampfire/MissionMonitor

PythClippers Bot (6/8 Phases Complete)

  • Clip submission tracking across Discord and Telegram

  • Reward calculation engine, leaderboard system, dashboard UI

  • Pending: production API keys, VPS deployment, T&Cs legal sign-off

  • Designed to power the Clipping Incentive Program

Pythentity (MVP Live)

  • Community-native identity and reputation system

  • Wallet signature verification, Discord OAuth linking, Pythenians NFT gating

  • Score cards based on contribution history

  • Funded through DAO governance grant (80K PYTH, processed at 100%)

  • Extensive bugfixing and testing completed with Pythenian community members

  • Built by 4–5 community contributors — community-owned, not third-party

Pythenians NFT Acquisition

  • 8+ month negotiation completed — $15,950 USDC (paid from Pythenians Treasury - not Community Council)

  • Collection acquired as community identity asset.

  • Twitter credentials, subscriptions, and multisig handover completed.

PythWheel (Live on Monad)

  • Community-built random rewards system powered by Pyth Entropy

  • Wallet signature verification, Whitelist manually uploaded by Admins (Community Council). Discord roles determine the amount of spins per week.

  • Rewards wheel (41.5K/month) funded through experiments lab budget (To be budgeted elsewhere in future)

  • Funded through Experiments Lab (100K PYTH, processed at 60%, remaining 40K Pyth reserved for educational content creation)

  • Multiple bug fixes and feature upgrades have been shipped.

  • Built by 4 community members (paid), Project Managed by 1 community member (unpaid)

  • Entropy PythWheel raffle wheel can be used in future to fairly distribute any kind of reward in future, with ability to filter by role, usernames, wallets etc.

Strategy & Research

Clipping Incentive Program Spec

  • Full technical specification: submission flow, reward calculation, tiered distribution

  • T&Cs framework pending legal review

Pyth Related Dune Dashboards

Discord & Community Operations

  • Discord server restructure: merged Temple & Waiting Room, added Intelligencia bot

  • Role system maintained: Chirons (20 members), Mensarius (14 members)

  • 67,000 server members

  • 366 active members (monthly)

External Engagement

Content Pipeline

  • 130+ video transcripts indexed and ready for clipping

  • 12 evergreen blog posts written by Pierre (ready to publish)

  • XAU (gold) Asset Info Pack produced — blog, FAQ, fact sheet

  • Asset blog template created for future asset classes

Financial Report

Term 1 Budget Actuals

Period Budget (PYTH) Spent (PYTH) Remaining (PYTH) Utilization
Cycle 1 (Apr–Sep) 1,840,000 1,322,181 517,819 71.9%
Cycle 2 (Oct–Mar) 1,890,000 2,348,385 -458,385 124.3%
Total Term 1 ~3,730,000 ~3,670,566 ~59,434 98.4%

Why the utilization gap between cycles: Cycle 1 underspent because programs were still being designed and built. By Cycle 2, programs were operational — Impact Awards running monthly, Kaito costs scaling (35K → 234K PYTH/month), Experiments Lab funding active development. The Cycle 2 overspend was absorbed by the Cycle 1 surplus, resulting in 98.4% total utilization across the full term.

Spending by Category

Category Cycle 1 Budget Cycle 1 Spent Cycle 2 Budget Cycle 2 Spent Term 1 Total Spent
Role Stipends 120,000 155,718 120,000 284,140 439,858
Impact Awards 210,000 224,396 210,000 189,524 413,919
Kaito 1,000,000 477,887 600,000 1,015,871 1,493,758
Experiments Lab 90,000 44,180 480,000 403,800 447,980
Council Stipend 420,000* 420,000* 420,000* 420,000* 840,000*
Contingency — — 60,000 35,050 35,050
Total 1,840,000 1,322,181 1,890,000 2,348,385 3,670,565

*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 observations:

  • Kaito was the largest spend category, growing from ~80K PYTH/month in Q2 2025 to 234K PYTH/month by December 2025 as the platform scaled. This single line item consumed 53% of total spend.

  • Role Stipends exceeded Cycle 1 budget as the role system expanded, then grew further in Cycle 2 with more active community roles.

  • Experiments Lab funded community-built infrastructure: MissionMonitor, PythClippers, Pythentity.

  • Council Stipend shows 0 spent from the council treasury because stipends are paid directly by the DAO to avoid a conflict of interest — council members don’t pay themselves from their own multisig.

Funds Remaining

  • Current wallet balance: 376,480.91 PYTH + 4.62 SOL. This includes ~317,000 PYTH in committed payments not yet disbursed, including Pyth Playground Round 1 prizes (~200K PYTH). Effective remaining after all commitments: ~59,400 PYTH — consistent with the budget vs. actuals totals above.

  • Wallet: GKuPcXtNRJwZGrJ8tV25jSbLHZe71BUdUXVzjGLXkSt9

  • Note: Remaining funds are to cover API & Claude code development costs, in addition to the Pyth Community Hackathon. After all committed disbursements, the effective remaining balance is ~59,400 PYTH — consistent with the budget vs. actuals totals above.

  • Disposition: Any unused funds return to the DAO treasury. No rollover beyond the interim bridge period.

What We Learned

1. Content Quality From Genuine Contributors > Volume From Anonymous Accounts

Contributors who actually use Pyth — who’ve integrated the price feeds, participated in governance, engaged with the data — produce fundamentally different content than anonymous accounts grinding for rewards. That quality difference matters for domain authority and long-term content value.

2. Build the Tools, Then Scale the Programs

The biggest lesson: infrastructure before programs. We spent significant time building MissionMonitor, PythClippers, and Pythentity because scaling community programs without operational tooling creates manual bottlenecks that don’t compound. The tools are now built or near-complete. Term 2 is about running programs on that infrastructure at scale.

What Comes Next

The Community Council is seeking Term 2 renewal. See companion posts:

  • Community Council Election #2 — Election Guide: [FORUM URL TBD]

  • Community Council Term 2 Budget Proposal: [FORUM URL TBD]

Term 1 built the infrastructure. Term 2 runs the machine.

Questions? Tag the Community Council in Discord or comment on this post.

6 Likes
Guide for the Community Council Election #2
2

The Community Council has done a stellar job this term. The foundation is solid, everything feels a lot more structured, and there is true alignment with the community, it doesn’t feel forced.

Now it’s about taking everything that’s been built and executing at scale. Excited to see what Term 2 looks like.

2 Likes
3

This is nothing short of spectacular. The community council have always made sure pyth community is fluid and well aligned for the next level of defi. Great work guys and Thank you for your service for the past 12 months.

1 Like
4

Term 1 was absolutely amazing. Thank you to everyone on the CCs. The next phase is all about scaling and expansion

1 Like