PYTH COMMUNITY HACKATHON
ROUND 1
Program Report
Community Hackathon for AI-Assisted Builders
36 Projects | 200,000 PYTH | 4 Weeks
Prepared by Choppa (@ChoppaTheShark)
Community Lead, Pyth Network
April 7, 2026
Table of Contents
Executive Summary
Pyth Community Hackathon ran as a four-week community hackathon designed to test a thesis: if AI coding tools eliminate the programming barrier, what will the Pyth community build with our data?
The results exceeded expectations. 36 projects shipped across DeFi infrastructure, analytics, gaming, AI agents, and utility tools. Every Pyth product was utilized — Price Feeds, Entropy, Pyth Pro, and Benchmarks. Builders deployed across five blockchains (Solana, Base, Ethereum, FOGO, Optimism) covering crypto, forex, commodities, and equities.
I’ve written this report to provide a complete overview for the PDA, for whom this program benefits the most. It covers the strategic rationale, execution details, submission analysis, key findings, media distribution plan, and recommendations for continued hackathons in 2026 & 2027.
| Total Projects Submitted | 36 |
|---|---|
| Prize Pool | ~200,000 PYTH |
| Duration | 4 weeks (March 4 – April 1, 2026) |
| Judging Period | April 2–15, 2026 |
| API Keys Issued | 32 (36 projects shipped — community outran infra) |
| Pyth Products Used | Price Feeds (34), Entropy (15+), Pyth Pro (5), Benchmarks (4) |
| Chains Represented | Solana, Base, Ethereum, FOGO, Optimism |
| Asset Coverage | Crypto, Forex, Commodities, Equities |
| All Licenses | Apache 2.0 (open source) |
Strategic Context
The Pyth Community Hackathon does not exist in isolation. It is one execution layer within two converging strategic priorities for Pyth Network in 2026.
AI Discoverability — The #1 Priority
Pyth’s competitive position depends on whether AI systems recommend Pyth when developers ask how to get price data. As of February 2026, Bloomberg holds 33.7% LLM visibility versus Pyth’s 5.7%. That gap closes with content, not code. In this context, every hackathon submission generates a plethora of natural derivative content: forum posts, GitHub repos, Dev.to articles, Reddit threads, Twitter posts. 36 projects produced an estimated 100+ public-facing content artifacts — all mentioning Pyth usage, all crawlable by LLM training pipelines, all hosted on indexed domains. LLM Gold.
Strategic value: Pyth Community Hackathon is a GEO (Generative Engine Optimization) multiplier. Each builder creates content that teaches AI models what Pyth is, what it does, and why developers should use it. Every project is a concrete example and use case for Pyth data.
The Agent Economy — Positioning for the future.
Autonomous agents (bots, AI operators, automated trading systems) already drive a significant share of on-chain activity. They need real-time, oracle-grade price data to function. Pyth is that price layer.
The hackathon was designed to prompt and produce working examples. The Pyth MCP Server was included as a starter kit, which meant AI coding assistants (Claude, Cursor, Replit Agent) were pulling live Pyth data during the build process itself. Agents using oracle data to build applications that use oracle data. That loop happened organically, without anyone designing specifically for it.
Three submissions are themselves autonomous agents: NeuroTrade streams Pyth Pro data and executes trades through Jupiter with zero human input. SignalForge runs a 24/7 bot monitoring prediction markets against Pyth feeds with Kelly Criterion position sizing. Ouroboros takes a natural language description and autonomously generates, compiles, and deploys a Pyth-powered dApp.
These are working agent-to-oracle pipelines. Built in four weeks. By community members. Not a pitch deck — a proof point.
The Vibe Coding Thesis
The core bet behind Pyth Community Hackathon was that AI coding tools have collapsed the barrier between “I have an idea” and “I have a working application.” The traditional hackathon assumption — participants must know Solidity, Rust, or at minimum JavaScript no longer holds.
Results seem to have validated this thesis. Builders with no prior blockchain experience shipped DeFi primitives (Aletheia’s confidence-adaptive RFQ), research-grade analytics (RegimeIQ’s oracle microstructure analysis), and complex gaming systems (Tower of Entropy’s full RPG). AI tools wrote the code. Pyth provided the data. The builders provided the ideas.
This overlal projected has changed how the developer onboarding funnel works entirely (especially when considering future iterations of the hackathon). “Docs → Tutorial → Abandoned project” can now credibly be replaced by “Browse cool projects → Fork one → Make it yours.” Pyth Community Hackathon generates the a live project gallery that powers this new funnel for all future developers and builders.
Program Design & Execution
Structure
Pyth Community Hackathon Round 1 was organized by the Pyth Community Council (elected governance body) and coordinated by Choppa (@ChoppaTheShark, Community Lead). The organizing entity is PYTH DAO LLC (Marshall Islands).
| Submission Period | March 4 – April 1, 2026 |
|---|---|
| Judging Period | April 2–15, 2026 |
| Results Announcement | April 15, 2026 |
| Platform | dev-forum.pyth.network (submissions) + Discord (community) |
| Eligibility | 18+, excludes OFAC-sanctioned jurisdictions |
| Team Size | Max 2 per submission |
| KYC | PDA (Pyth Data Association) handles KYC for prize winners only |
Prize Structure
| Tier | Reward |
|---|---|
| 1st Place | 50,000 PYTH |
| 2nd Place | 30,000 PYTH |
| 3rd Place | 15,000 PYTH |
| 4th–10th Place | 5,000 PYTH each (35,000 total) |
| Community Choice Award | 10,000 PYTH |
| Best Pyth Pro Use | 10,000 PYTH |
| Best Educational Content | 10,000 PYTH |
| Participation (valid submission) | 500–1,000 PYTH |
| Upvote Bonuses | 10 upvotes (+500) to 100 upvotes (+5,000) |
Judging Criteria
| Criteria | Weight |
|---|---|
| Pyth Integration Depth | 30% |
| Creativity & Innovation | 25% |
| Execution Quality | 20% |
| User Experience | 15% |
| Documentation | 10% |
Resources Provided
Builders basic starter kits, 30 project ideas across 5 categories (HFT, DeFi, Analytics, User Tools, Infrastructure), three pinned forum guides (Official Rules, Submission Template, Judging Rubric & FAQ), and direct access to Pyth Pro API keys on request.
Complete Project Catalog
All 36 submissions are listed below, organized by the content priority tiers used for the media distribution plan. Every project is open-source (Apache 2.0) and most have live demos.
| Project | Builder | Category | Pyth Products | Chain / Demo |
|---|---|---|---|---|
| Market DVR | Wattson | Infrastructure | Price Feeds, Pyth Pro | VPS |
| Aletheia RFQ | pap0nt | DeFi | Price Feeds (on-chain) | Base |
| The Market Witness | Joestar | Creative/Education | Hermes, Benchmarks | Vercel |
| RegimeIQ | codeglitch | Analytics | Hermes SSE, Confidence | VPS |
| FOGO Pulse | theRoad | DeFi | Pyth Lazer, Hermes WS | FOGO |
| PythCorrelation | rustrell | Analytics | Hermes, Benchmarks, Entropy | Vercel |
| SignalForge | Smartbott | Trading | Hermes API + WS | Railway |
| Pirb.swap | Dera | DeFi | Price Feeds (Hermes V2) | Solana |
| NeuroTrade | SCP | Trading | Pyth Pro WS | Solana |
| Ouroboros | pstar | Infrastructure | Price Feeds, Entropy | Base |
| PythGuard | Sueno | Analytics | Price Feeds, Pyth Pro, Entropy | Solana |
| LiquidSense | MAYTH | DeFi | Hermes Price Data | Base |
| Terminal by nik0 | Nik0 | Analytics | Hermes, Benchmarks | Vercel |
| PythVision | Jaybrass | Analytics | Price Feeds, Entropy V2 | Ethereum/Base |
| PythReceipt | viperx | DeFi | Price Feeds, Pyth Pro Lazer | Solana |
| Pyth Sentinel | Investor_Daniel | Utility | Price Feeds, Entropy | Railway |
| Coindle | droober | Game | Hermes API | Vercel/Farcaster |
| PIRBGEN | mersault | Game | Price Feeds, Entropy | Base |
| Pyngo | enoo | Game | Price Feeds, Entropy | VPS |
| Pyth Defender | Khaleesi | Game | Hermes REST, Entropy | GitHub Pages |
| Pythian Peso Snake | totti | Game | Entropy (Optimism) | Netlify |
| Whac-a-Pythenian | RicardoReyes | Game | Entropy | Vercel |
| Tower of Entropy | Flint | Game | Entropy, Price Feeds | Base |
| Pyth Casino | surojitpvt | Game | Hermes Price Feeds | Solana/Base |
| Pyth Arcade | Agarwal | Game | Price Feeds, Entropy | Vercel |
| Sleeve | dexter | Game | Lazer Pro, Entropy | Base |
| Walk The Planck | Quintzor | Game | Entropy | Base |
| Orra | emjayrntr | Game | Price Feeds, Entropy | Base |
| PyPredict | Bam4bam | DeFi | Hermes API (17 feeds) | Vercel |
| PythPulse | Bankybemma | Analytics | Hermes REST (38 feeds) | Vercel |
| Oracle Flow | Sugoi | Analytics | Price Feeds | Vercel |
| RektoMeter | ranimth07 | Utility | Hermes API (500+ assets) | Vercel |
| Price Prediction Grids | Shubh | Game | Price Feeds, Entropy | Solana |
| PolyJackpot | joshjosh11 | Game | Entropy | Base |
| d1ckochart | oldtora | Creative | Hermes API | Vercel |
| QTCL Blockchain | shemshallah | Infrastructure | Price Feeds, Entropy | QTCL |
Category Analysis
The 36 submissions naturally cluster into six categories, revealing how the community thinks about oracle data utility.
Games & Entertainment (14 projects)
The largest category by volume. Ten of these use Pyth Entropy for verifiable randomness. Projects range from simple browser games (Pythian Peso Snake, Pyth Defender) to complex systems (Tower of Entropy’s full RPG, PIRBGEN’s competitive trading arcade). The Market Witness bridges gaming and education through AI-powered courtroom drama.
Key insight: Entropy is the entry drug. Provably fair randomness is an easy-to-understand value proposition that gets builders interacting with Pyth infrastructure. Many of these builders will graduate to Price Feed and Pyth Pro integrations.
Analytics & Monitoring (8 projects)
Professional-grade tools including PythCorrelation (28+ asset cross-correlation), PythPulse (38-feed anomaly detection), RegimeIQ (oracle microstructure analysis), and multiple market terminals. Several use Pyth Benchmarks for historical data alongside real-time feeds.
Key insight: The multi-asset coverage (crypto + forex + commodities + equities) was a major differentiator. Builders leveraged Pyth’s breadth in ways that single-asset oracles cannot support.
DeFi Infrastructure (6 projects)
The most technically sophisticated category. Includes confidence-adaptive settlement (Aletheia), liquidation monitoring with macro signals (PythGuard, LiquidSense), slippage protection (Pirb.swap), liquidation receipts (PythReceipt), and prediction markets (FOGO Pulse, PyPredict).
Key insight: Builders treated confidence intervals as functional infrastructure, not informational. Three separate projects independently arrived at “confidence as a gate” — a pattern worth elevating as a Pyth design principle.
Trading Agents & Tools (5 projects)
AI-powered trading systems including NeuroTrade (local-first agent streaming Pyth Pro), SignalForge (prediction market bot using the same oracle for signals and settlement), and Ouroboros (AI agent generating entire Pyth dApps from natural language).
Key insight: Direct validation of the agent economy thesis. These are working prototypes of autonomous systems paying for and consuming oracle data.
Infrastructure (3 projects)
Market DVR (Pyth Pro market replay), Ouroboros (AI dApp generator), and QTCL Blockchain (post-quantum price attestation). The most ambitious and differentiated submissions.
Utility (2 projects)
RektoMeter (airdrop P&L tracking with 500+ Pyth-priced assets) and Pyth Sentinel (price alerts with oracle-grade data). Practical tools demonstrating everyday use cases.
Pyth Product Usage Analysis
The hackathon served as a live stress test of Pyth’s product surface, and developer experience. The distribution of product usage reveals how builders naturally discover and adopt Pyth’s capabilities.
| Product | Usage | How Builders Used It |
|---|---|---|
| Price Feeds | 34/36 | Core data layer. Real-time crypto, forex, commodities, equities. Both on-chain and off-chain (Hermes) consumption. |
| Entropy | 15+/36 | Verifiable randomness for games, lotteries, prediction markets. Commit-reveal protocol for provably fair mechanics. |
| Pyth Pro (Lazer) | 5/36 | Sub-second institutional feeds. Used by most technically advanced projects (Market DVR, NeuroTrade, FOGO Pulse, PythReceipt, Sleeve). |
| Benchmarks | 4/36 | Historical OHLCV data for backtesting, charting, and correlation analysis. |
Discovery pattern: Price Feeds are the entry point. Entropy is the engagement hook (especially for games). Pyth Pro is discovered by advanced builders who need speed or historical depth. Benchmarks are used by analytics-focused projects.
Deliverable 1: Project Spotlight Tweets
36 individual project tweets from @CHOPPAtheSHARK (commentary, personality). Projects are tiered by quality: Tier 1 (7 deep features), Tier 2 (9 spotlight posts), Tier 3 (20 community/game posts). Posted with links, screenshots and callouts for the individual builders.
Deliverable 2: Hackathon Recap Article
A large-ish reflection article blending thesis (vibe doing supremecy) with evidence from each project. Covers the experiment, what got built (organized by category), and three key findings. Written as a complimentary ‘community strength’ blog. Posted to both Twitter and the Governance Forum as a review.
Communities Key Findings & Lessons Pyth can learn
1. Long live vibe coding
Builders with no prior blockchain experience shipped basic DeFi primitives, genuine research-grade analytics, and relatively complex gaming systems in under 4 weeks. The almost ALL of the code was AI generated. This should frame Pyth’s thinking significantly into the future as we lead the charge in subscription based first party financial data. This is particularly important as we open up the product suite to retail audiences. Proving what is possible with Pyth to the every day consumer is an important market segment.
2. Pyth’s Product Surface Is Deeper Than Perceived
There was significant diversity in products built. Each community member independently discovered that confidence intervals can serve as execution gates, oracle microstructure can function as a risk signal, Entropy enables entirely new game (and trading) mechanics, and Pyth Pro unlocks institutional-grade capabilities. Builders treated Pyth data as a premium product that would help inform their decision making processes, and allow them to execute with precision. This demonstrates the perception of Pyth as a premium product is well set.
3. Community Outran Infrastructure
34 API keys were issued. 36 projects shipped. More people submitted without keys than with them. The bottleneck was not interest or capability — it was awareness and distribution. Round 2 should solve for reach, not resources.
4. Entropy Is a great Onboarding Funnel
15+ projects used Entropy, making it the second most popular product after Price Feeds. Provably fair randomness is an easy-to-understand value proposition that gets builders interacting with Pyth infrastructure. The games category (14 projects) was the largest. Entropy-first onboarding could become a deliberate strategy for onboarding low level applications and developers to Pyth.
5. “Confidence as a Gate” Is an Emergent Pattern
Three separate projects (Aletheia, FOGO Pulse, PythReceipt) independently arrived at using confidence intervals as functional gates — blocking trades, refunding bets, or halting liquidations when oracle uncertainty exceeds thresholds. This framing does not appear in any of Pyth’s documentation and was not mentioned in any of the Hackathon onboarding materials. Builders discovered this ‘feature set’ organically. This pattern should be elevated as an official Pyth design principle with dedicated documentation and examples. It provides Pyth with a VERY clear point of difference against other price data solutions while also doubling as a monetisable feature of the product suite.
6. Content Generation Was Organic
Without requiring it, builders produced Dev.to articles, GitHub repositories, Reddit posts, and video demos. The hackathon generated 100+ public content artifacts mentioning Pyth — all indexed, all crawlable, all contributing to AI discoverability. Round 2 should formalize this with explicit content requirements for bonus rewards, and also show content examples from previous hackathon submissions.
7. Reframe Pyth Pro usage
Community was given ‘free access to Pyth Pro’. In the next iteration of the hackathon, framing for this event should instead be around Pyth giving away Pyth Pro credits to the tune of “X” amount of value that people can then use on a monthly basis. This promotes Pyth’s exclusivity whilst demonstrating the innate value of the data being used.
Coordinator’s Reflections
The following observations are editorial — drawn from running this program end-to-end as coordinator. They supplement the analytical findings above with operational and philosophical takeaways.
What This Hackathon Proved
1. We underestimate people’s willingness to contribute
My assumptions going in was that the Prize money was going to be too low to attract attention. It wasn’t. Builders showed up because they found the challenge interesting. Most importantly, they wanted a chance to use the same data institutions do, in order to ‘level the playing field’. Many submitted projects that clearly took more hours than the prize pool could justify on a purely economic basis. I think it’s quite clear that giving a community something genuinely interesting to work on and the tools to do it, the participation problem solves itself. The bottleneck was never motivation — it was mostly about access to the data and awareness of the program. This is exciting for future iterations of the Hackathon.
2. It’s not all about prizes
This was a very modest prize pool by crypto hackathon standards. Monad recently ran a hackathon with a 500k USD funding price. The Pyth Community Hackathon cost 100x less to run. What we received back in content, open-source code, product innovation, and ecosystem awareness far exceeded the cost. The ratio of value created to PYTH distributed is lopsided in our favor. Builders contributed because they were excited to build with PREMIUM financial data, not because the payout was life-changing. That’s a great signal for the Pyth brand — it means this model scales without requiring exponential budget increases, and that we have a ‘premium’ attached to our brand.
3. Novel ideas for Pyth data still exist beyond what we know
Multiple submissions genuinely surprised me with their breadth and creativity. Confidence intervals as trade execution gates (Aletheia), oracle microstructure as a risk signal (RegimeIQ), confidence-aware settlement refunds (FOGO Pulse), oracle speed as a competitive gameplay mechanic (PIRBGEN), a courtroom drama using price data as evidence (The Market Witness) — none of this stuff was in the project ideas list. The community found use cases for Pyth data that we, as the team closest to the product, had not considered. This means the surface area of what’s possible is larger than our internal imagination, and hackathons are the most efficient way to map that territory. We get to lean in to community and build a brand while ALSO pushing the boundaries of what Pyth data can do.
4. Running this is harder than it looks
The organizational requirements of a program like this are substantial: legal (T&Cs, KYC, jurisdiction compliance), infrastructure (forum setup, API key management, submission tracking), content scheduling (promotional cadence, builder communications, judge coordination), and community management (answering questions, troubleshooting, maintaining momentum over four weeks). This was running this alongside every other active workstream, which was quite difficult. Had this been my sole focus, I think Pyth would have have extracted significantly more value: better promotional cadence, more builder support, tighter content pipeline, and a much more polished showcase event. The biggest thing to learn here is that dedicated operational bandwidth for programs like this can multiply the already substantial output of the program.
5. Our products are intuitive
Of 36 submissions, only 4 required any form of technical support. Two were API-related issues easily resolved with a key refresh. The other two were users not fully grasping speed variance in select assets — a comprehension issue, not a product issue. That’s a 89% zero-support rate from builders who, in many cases, had never interacted with oracle/data/price infrastructure before. The MCP Server, Hermes API, and Entropy documentation are doing their job. The products work the way developers expect them to work. That’s not a given in this industry, and it’s worth recognizing.
Moving Forward — Strategic Vision
Beyond the tactical recommendations for Round 2, this hackathon opens several larger strategic opportunities for Pyth Network & the community.
A Community Hub for Live Projects
Many of these projects function as genuine public goods. The Entropy-powered games, price feed monitors, correlation dashboards, liquidation radar’s are all fantastic, simple consumer products. They deserve to live beyond the hackathon as a showcase of what the community & Pyth data can do.
I propose that we build a community hub (extension of Pythentity) that showcases select projects, provides them with full and free access to a single dedicated API key under the Pythenians banner, and keeps them running as permanent demonstrations of what Pyth data enables. Not a graveyard of demo links. A living gallery that everyone has access to, and the community owns.
A Living Library of What’s Possible
Each hackathon round adds to a growing library of what can be built with Pyth. Over time, this becomes an extremely powerful resource & tool in the ecosystem. Something distinctly different from documentation & tutorials. This would be a display of working applications that make people say “I could build that.” Community hackathons become the input layer for this library. Every round surfaces new patterns, new use cases, and new reference implementations that future builders (and Pyth users) can fork, extend, and improve.
Brand Positioning: Champions of Open Building
As an organization, hosting and leaning into community hackathons frames Pyth as champions of open building and democratized access to financial data. The only limiting factor is being a part of the community. Bloomberg charges $24,000 per year for data that Pyth makes available for free, regularly. Running hackathons and having 36 community members build working products in four weeks (using AI tools, no barriers to entry or coding expertise required) imbues the event with a lot more meaning. It becomes a proof point for Pyth’s entire forward looking thesis. The brand perception compounds: Pyth data allows anyone to build with institutional-grade financial data. The hackathon is evidence of this - and it is continually reinforced the more we lean in.
A Core Part of the Community Offering
In my opinion, Pyth would be well served by this program becoming a significant, recurring part of Pyth’s community offering. The appeal is twofold:
For retail and community builders: The opportunity to play with the same data that institutions pay for. To build something real with oracle-grade price feeds, verifiable randomness, and sub-second data — tools that were previously locked behind enterprise contracts and six-figure budgets. This is what makes a community sticky: not Discord roles, not airdrops, but the ability to create something meaningful with infrastructure that matters.
For builders and businesses: A testing ground for product ideas. A way to evaluate Pyth’s product surface without procurement cycles or sales calls. A gallery of reference implementations that demonstrate integration patterns. Several hackathon submissions are closer to MVPs than prototypes — businesses watching this space now have 36 open-source examples of what Pyth integration looks like in practice. That’s a sales pipeline built by people who love Pyth, for Pyth.
This creates a pretty obvious feedback loop: run hackathons, surface innovation, showcase the results, attract more builders, run more hackathons. Each round generates content (AI discoverability), demonstrates products (sales pipeline), rewards contributors (community flywheel), and produces open-source code (ecosystem infrastructure). Pyth doesn’t have a program or touchpoint that touches all four simultaneously. The Community Hackathon does.
Tactical Recommendations for Round 2
Scale Distribution
Round 1 relied primarily on the developer forum and Discord for awareness. Round 2 should include more Twitter/X promotion from @PythNetwork, partnership with Superteam Earn for distribution, university outreach (three warm academic leads are active), and very specific collaboration with chain partners who may also be able to offer incentives or comarketing.
Formalize Content Requirements
Require each submission to create at least one public-facing content artifact (Reddit post, Dev.to article, or GitHub example). Offer bonus PYTH for additional content. This transforms the hackathon from a builder event into an AI discoverability multiplier.
Introduce ‘Track’ System
Round 1 was open-ended. Round 2 should offer themed tracks (DeFi Infrastructure, Agent Economy, Analytics, Gaming/Consumer) with track-specific prizes. This enables more targeted judging and produces cleaner content narratives. Alternatively, Pyth makes theme specific Hackathons that only look to reward and incentivise certain product verticles (eg; agentic trading)
Integrate with Content Incentive Stack
Pyth Community Hackathon should feed into the broader content incentive pipeline: MissionMonitor (live) for post-hackathon content missions for ongoing builder engagement. Round 2 participation should grant access to these systems and reward users for the deeper participation in community events.
Increase Pyth Pro Adoption — Reframe Access as a Grant
Only 5 of 36 projects used Pyth Pro in Round 1. Round 2 should fix that — not by making it “free,” but by making the value visible.
The marketing frame: Pyth makes available $X worth of Pyth Pro credits to the community over the hackathon period. Builders receive access to institutional-grade, sub-second data (the same feeds that paying subscribers use) as a community grant. The dollar value is stated explicitly. Every participant knows what they’re getting and what it normally costs.
This does three things simultaneously.
First, it positions the hackathon as a gratuity event — Pyth giving real value to its community, not handing out free trials.
Second, it anchors Pyth Pro’s market price in every builder’s mind. They experience the product, see the price tag, and understand the value proposition without a sales call.
Third, it creates a natural conversion pipeline — builders who used Pyth Pro credits during the hackathon are the warmest leads for paid subscriptions after it ends.
Pair this with a dedicated Pyth Pro starter kit (sub-second data consumption, historical benchmarks, bid/ask spread analysis) and a “Best Pyth Pro Use” bonus track with a higher reward to incentivize deeper integration.
Dedicate Operational Bandwidth
Round 1 was coordinated alongside all other active workstreams. Round 2 should either be the coordinator’s primary focus during the active period, or have a second operator handling promotional cadence, builder communications, and content scheduling. The program delivers — but dedicated bandwidth from others within the community council would multiply the output.
Budget & Resource Utilization
| Item | Amount |
|---|---|
| Total Prize Pool | ~200,000 PYTH (from Community Council allocation) |
| Top 3 Prizes | 95,000 PYTH (50K + 30K + 15K) |
| 4th–10th Place | 35,000 PYTH (7 × 5,000) |
| Special Awards | 30,000 PYTH (3 × 10,000) |
| Infrastructure Costs | Minimal (forum hosting, API keys) |
The program represents strong ROI: 36 open-source projects, 100+ content artifacts, 5+ working DeFi primitives, and a validated program template for future rounds — all from a single community council budget allocation. Cost per project: approximately 5,500 PYTH.