Community Council Term 2 Budget Request

[Chop]

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.

[Mersault]

Great news. I was incredibly frustrated with the farmers and I’d love to weed out everyone who’s just farming rewards. The larger budget provides more opportunities , everything built in Term 1 needs to be scaled, and it’s time to keep pushing forward.

The only thing that worries me is the referral program. For some reason, it’s an immediate red flag for me. It could potentially bring in people who will just abuse the system and invite low-quality users. But I think the scoring system will be able to handle it

[PilotSB]

getting hot on transperancy, another banger ser chop

[Pythian_151]

From April 2025 to March of 2026, we spent 3,670,655 PYTH on all marketing programs. How can we state that this has lead to greater adoption when the price of the token has fallen from approximately 0.40 cents to 0.04 cents. Now we are asking 8,000,000 PYTH from the DAO to spend on marketing more specificity, 6,000,000 for content creators equating to the whole amount of the DAO current reserve..

One of the purpose of conducting share buy backs in this case token buy backs is to reduce the pressure of dilution and improve EPS.

Since the marketing has shown not to be as successful as we thought it would be, should we be more careful with our spending and instead concentrate on letting the product speaks for itself i.e PYTH pro.

Someone creating a YouTube video content or retwitting on X is not going to incentivise big institutions to pay 10,000 per month, rather the quality of the price feed will.

May be we could spend 10-15 percent of the monthly DAO revenue on marketing with the rest of the earnings for continued buybacks.

Spending less and building up the DAO reserve will help conteract the selling pressures from staking rewards and unlocks and give the price a chance to move in a favourable direction ?

[Chop]

gm Pythian_151.

First off, banger reply. Quality FUD. I love an opportunity to respond to genuine feedback around the Community Council budget. I commend you for reading and absorbing it all - most people don’t. Your willingness to engage Pyth with critiques on programs like this is what makes our community great. Keep it coming!

A couple of points i think are worth noting on this portion of our spend;

• In our view, adoption is a lot more than just ‘token go up’. In fact, token go up (the council believes) has nothing to do with adoption. Pyth adoption (measured in subscription terms) is up considerably! Our Quarter on Quarter growth in subscriptions is well over 100%, and we’re growing above projections. To add to that; we have been actively expanding our revenue collection mechanics (see the Listing as a Service governance proposal as an example). Price Feeds are expanding aggressively and their usage is accelerating in line with adoption.
• The Community Council budget (which i believe is what you are referring to) serves many different purposes. The ‘why’ of the councils’ spending is not immediately obvious to those who dont directly participate, so let me break it down a bit;

  • Our recent Polymarket partnership exists partly because of our highly engaged and ‘loud’ community has made it known to Polymarket team that we are serious players within the space. Pyth’s Data Marketplace is also a direct beneficiary of community noise and our ability to provide retail data (also see the Polymarket $99 retail subscription). In this regard, the marketing spend is not necessarily visible directly in results, but is instead measured in aura.

  • Kaito - Now discontinued. This was our largest line item spend last year. Pyths’ spend when compared to most other Kaito budgets was much smaller. Moreover, our spend was HIGHLY targeted and rewarded only those who were making substantive contributions. We (the council) audited submissions meticulously and filtered low quality AI submissions as we reasonably could in order to make the spend as fair as possible.

    This allowed us to create a new Kaito-like system with larger safeguards, stricter contribution guidelines & gives us variability and control over our community rewards spend moving forward. You’ll hear more on this over the next couple of months as we report on its progress and efficacy. This will be run as a trial during the second term and adjusted as necessary, based on feedback from people such as yourself!

  • Pyth Community Hackathon - ongoing. The most successful Hackathon Pyth has ever participated in (including IRL based events). 35+ submissions that showcase what is possible leveraging Pyth Pro data, but make a significant dent in our AI Discoverability and referencing Pyth in builders’ channels such as Github. This hackathon has contributed immensely to our ability to deliver resources to the broader Pyth community;

    • Free Pyth Access to whoever wants it.
    • Open, discoverable ideas & developer community tools
    • current budget request has the hackathon as a big part of the Councils’ output in this next term due to its current success

  • Pythentity - this one is a long game on the community NFT’s. Our hope (as a council and as a community) is that we will be able to create an all inclusive platform for community participants that allows the following;

    • Access to Hackathon dApps built by community (we see the monitoring tools made using Pyth DAta and games on entropy as a public educational goods)
    • A ‘passport’ that functions as proof of your interaction across the Pyth Powered ecosystem.
    • A central ‘hub’ for community contributions, builder resources & educational content to help retail (and trader) participants wrap their head around Pyth WITHOUT the institutional an focus or formalized clutter.
    • An access point to Pyth that is retail focused (and community built) instead of institutionally minded.

  • Role Stipends - these are arguably our least obvious spend. However, we maintain a core group of highly engaged community members who contribute across multiple different channels using this mechanic as a buffer for the time they dedicate to Pyth. The 70% hold metric also applies to these stipends.
    Pyth one of the most engaged market Discord channels that i’m aware of, which constantly provides value to the broader community with its weekly streams, analysis and market dissections. Our Chirons are some of the most well educated retail consumers of Pyth in the space - they are the cultural heartbeat of our Brand that are ready and willing to refute FUD and bull post the virtues of Pyth at a moments notice.

    These mechanics are highly variable & subjective. The participants are reviewed monthly.

  • Impact Awards & Misc Spending - Used to create highly specific content across different platforms. This spans TikTok, Reddit, Discord & Telegram. We use this portion of the budget to build a library of ‘content’ that allows us to onboard new community members, populate forums and channels with educational content AND help us moderate disparate language communities and niche content channels. This includes the newly created Content Library here in the DAO forum, which will be expanded to Reddit and a soon to be created community blog.

To address your concerns about marketing spend and ‘adoption’ more directly; institutions are motivated by results, data efficacy and security more than anything else. Over the past 2 years Pyth has been has constant presence within the broader data market place and social channels (almost solely due to the Community Councils’ efforts). We have expanded our data offering (and data efficacy) significantly over that time, with more price feeds being added on a weekly basis, and usage increasing week on week. We have shown that the Pyth price does very little in way of us being able to deliver a world class product that institutions and retail consumers alike wish to use. You will notice that our community almost NEVER discusses the price of Pyth - and for good reason. It is not what motivates us, nor do we believe should it. We are dedicated to deliver a world class product that is changing the face of finance in real, measurable ways day in, day out. That, we believe, is our strongest asset and proof point which gets validated to us on a weekly basis. 95% of HIP-3 volume. 24/7/365 always-on markets and deep crypto & institutional adoption is what we grade ourselves on. In this regard, be believe price is a lagging indicator of where Pyth is headed. As long as our leading indicators (as above) are heading in the right direction (they are) we are happy.

finally; We think deeply about our token economics and how to better shape them for now and into the future. Rest assured, we believe the level of spending requested by the council is both reasonable and in line with expectations of future growth. We as community participants remain extremely bullish on what Pyth is able to achieve with the help of people such as yourself.

I will also look into your Discord ban (which you have mentioned elsewhere). This is an oversight on my behalf, and as long as you were conduction yourself respectfully and in line with our expectations of community members, you should not have been banned. I will get this revoked ASAP. I welcome discussion like this wherever possible!