Build consistently
Use the full season to make steady progress instead of rushing toward a single demo day.
A practical framework for long-form hackathons with weekly accountability, visible progress, and lightweight operations.
Piece of Pie Hackathon is a 12-week, participation-driven builder season. This is not about judges picking favorites. It is about meeting clear requirements, showing visible effort, and earning your slice by doing the work.
Overview
The season gives builders enough time to ship real software while keeping public proof simple enough for organizers to verify.
Use the full season to make steady progress instead of rushing toward a single demo day.
Post weekly updates so the community can see what changed, what shipped, and what is blocked.
Aim for a public product that people can use, pay for, test, or give feedback on.
Qualification depends on public repos, weekly updates, final presentation links, and clear track requirements.
How it works
Register once, build in public every week, collect evidence, and present the public record at the end.
Submit one project, name every contributor, and declare the official public repository.
Keep the repo active and use public updates to show visible progress each week.
Ask for recorded feedback sessions and help other builders improve their work.
Show the demo, repo, deployed product, and weekly updates during final verification.
Cardano Foundation, Gimbalabs support this season's reward pools and builder-facing incentives.
Rules
Read this before anything else. These rules define what can qualify and what evidence builders need to preserve.
Qualify through consistent, verifiable participation, not competition.
Your project must be a user-facing software product with a clear payment gate or business model.
Solo projects and team projects are both welcome.
Every person contributing to the project must be named during registration.
Each participant may only join one project during the season.
The repository is the public source of truth and must remain public through verification.
The official repository must start empty for the event.
Every required week needs at least one public update that shows progress and includes the required tags and mention.
By the end of the event, the product must be publicly accessible on its intended platform.
Final verification needs a demo, public repo, weekly update links, and deployed product link.
Copy this structure, then replace the body with real progress for the week.
Sponsor-track projects must qualify as builders first and then satisfy the sponsor-specific rules.
Real User qualification starts with a valid Builder or sponsor-track qualification.
The paying user cannot be family or friends, and payment evidence must be verifiable.
Share how you found the customer and why the product created enough value for payment.
The feedback track is open even if you are not submitting a builder project.
Feedback must happen in a live recorded session with the builder present.
Each valid recorded session earns one feedback credit up to the season limit.
Timeline
Start with enrollment, then keep momentum through build weeks, feedback, final presentations, and payouts.
Registration
Submit one registration form per project during the enrollment window.
FAQ
Yes. Solo and team projects are both allowed.
No. Each participant may only join one project.
No. The official repository must be public and remain public until final payouts are complete.
Missing a required weekly update is disqualifying for Builder qualification.
For Builder qualification, yes. By the end of the event, the product must be publicly accessible.
No. You may participate in the Feedback track without a builder project.
Detailed rules, clarifications, FAQs, dashboard data, and official updates should stay easy to find throughout the season.