Builder Season Playbook

A practical framework for long-form hackathons with weekly accountability, visible progress, and lightweight operations.

Public progress - clear rules - real output

Build in public. Qualify through consistency.

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

A builder season for visible work.

The season gives builders enough time to ship real software while keeping public proof simple enough for organizers to verify.

Season 1 by Gimbalabs
1

Build consistently

Use the full season to make steady progress instead of rushing toward a single demo day.

2

Share publicly

Post weekly updates so the community can see what changed, what shipped, and what is blocked.

3

Ship real products

Aim for a public product that people can use, pay for, test, or give feedback on.

4

Verify with evidence

Qualification depends on public repos, weekly updates, final presentation links, and clear track requirements.

How it works

The season runs on a simple operating loop.

Register once, build in public every week, collect evidence, and present the public record at the end.

01

Register the project

Submit one project, name every contributor, and declare the official public repository.

02

Build in the open

Keep the repo active and use public updates to show visible progress each week.

03

Use feedback

Ask for recorded feedback sessions and help other builders improve their work.

04

Present the evidence

Show the demo, repo, deployed product, and weekly updates during final verification.

Rewards

How the pie gets shared.

Each pool rewards a different kind of contribution: building consistently, shipping in the sponsor ecosystem, proving real-world value, and helping other teams get better.

33,000 ADA available qualification beats judging

Builder Pie - 10,000 ADA

Build one project through the season and share progress publicly each week. Qualified builders split this pool equally.

Sponsored Pie - 20,000 ADA

Qualify for the sponsor track by meeting Builder requirements plus the ecosystem-specific requirements. This replaces the Builder Pie for qualifying teams.

Real User Pie - 2,000 ADA

Show at least one real paying user, payment evidence, and a public story of how you acquired that user.

Feedback Pie - 1,000 ADA

Give live, recorded feedback to other builders. This pool is distributed proportionally by valid feedback credits.

Rules

Core rules.

Read this before anything else. These rules define what can qualify and what evidence builders need to preserve.

Top priority
Key principle

Qualify through consistent, verifiable participation, not competition.

Automatic disqualification triggers
  • Missing a required weekly update.
  • Joining more than one project.
  • Failing to provide verifiable public evidence.

The Builder Track

1

Build something real users can use

Your project must be a user-facing software product with a clear payment gate or business model.

2

Work solo or form a team

Solo projects and team projects are both welcome.

3

Register every contributor

Every person contributing to the project must be named during registration.

4

Commit to a single project

Each participant may only join one project during the season.

5

Maintain one official public repo

The repository is the public source of truth and must remain public through verification.

6

Start with an empty repo

The official repository must start empty for the event.

7

Post weekly public progress

Every required week needs at least one public update that shows progress and includes the required tags and mention.

8

Deploy the product

By the end of the event, the product must be publicly accessible on its intended platform.

9

Deliver a complete final presentation

Final verification needs a demo, public repo, weekly update links, and deployed product link.

Sample Weekly Progress Update

Copy this structure, then replace the body with real progress for the week.

Week X update - Piece of Pie Hackathon
Built: ...
Learned: ...
Next: ...
#pieceofpie, #hackathon @gimbalabs

Cardano Pie

Real User Track

1

Qualify as a builder first

Real User qualification starts with a valid Builder or sponsor-track qualification.

2

Gain a real paying user

The paying user cannot be family or friends, and payment evidence must be verifiable.

3

Publish the acquisition story

Share how you found the customer and why the product created enough value for payment.

Feedback Track

1

Participate with or without a project

The feedback track is open even if you are not submitting a builder project.

2

Use recorded live sessions

Feedback must happen in a live recorded session with the builder present.

3

Earn credits with evidence

Each valid recorded session earns one feedback credit up to the season limit.

Timeline

Timeline.

Start with enrollment, then keep momentum through build weeks, feedback, final presentations, and payouts.

Enrollment period April 12, 2026 to May 3, 2026. Register the project, list every participant, and submit the official public repo.
Build period Ends July 19, 2026. Build in public, keep the repo updated, and post weekly public progress.
Final presentations July 13, 2026 to July 19, 2026. Show the demo, public repo, all weekly update links, and deployed product.
Payout window July 19, 2026 to July 26, 2026. Qualified participants receive shares according to the published rules.

Registration

Registration.

Submit one registration form per project during the enrollment window.

Step 1 - prepare your project info Finalize your project title and team members, create an empty public GitHub repo, and keep the repo link ready.
Step 2 - complete the form Submit the official registration form with accurate participant and project information.
Step 3 - keep proof public Keep the repository, weekly updates, and final evidence public until verification and payouts are complete.

FAQ

Questions builders usually ask.

Can I work alone?

Yes. Solo and team projects are both allowed.

Can I join more than one project?

No. Each participant may only join one project.

Can we use a private repository?

No. The official repository must be public and remain public until final payouts are complete.

What happens if I miss a weekly update?

Missing a required weekly update is disqualifying for Builder qualification.

Do I need a deployed product?

For Builder qualification, yes. By the end of the event, the product must be publicly accessible.

Do I need to be a Builder to participate in the Feedback Pie?

No. You may participate in the Feedback track without a builder project.

Official source of truth.

Detailed rules, clarifications, FAQs, dashboard data, and official updates should stay easy to find throughout the season.