🥧 Builder Pie — 10,000 ADA (equal split)
Build one project over 12 weeks and share your progress publicly each week. Earn an equal share of the pie by showing up consistently and shipping something real.
How the Pie Gets Shared
13,000 ADA available!
Core Rules
This is the top priority of the site. Read this before anything else.
Top priority
Key principle
Qualify through consistent, verifiable participation — not competition.
Automatic disqualification triggers
- Missing a required weekly tweet.
- Joining more than one project.
- Failing to provide verifiable public evidence.
The Builder Pie
1
Real Users Can Pay for and Use
Your project must be a user-facing software product (such as a SaaS app, web2/web3 platform, or tool) that includes a clear payment gate, such as a subscription, one-time purchase, usage-based pricing, etc.
2
Work Solo or Form a Team
You can build on your own or collaborate with others. Both solo entries and team entries are completely welcome.
3
Register Every Team Member
Every single person contributing to the project must be explicitly listed during registration. No unnamed or anonymous teammates are permitted.
4
Commit to a Single Project
To ensure focus and quality, participants may only join one project. If you are found to be involved in multiple projects, the projects will be disqualified.
5
Maintain One Official Public Repo
Each project requires a single public repository. This link will serve as the official source of truth for your work and must display a visible commit history.
6
Start With an Empty Repo
Your repository must start entirely empty. It must be made public at the time of registration and remain public until the final payouts are completed.
7
Post Weekly Progress Tweets (Mandatory)
You must post at least one public tweet every week demonstrating your progress. More tweets are encouraged, but missing even a single week will result in disqualification. To be verified, weekly tweets must:
- Clearly show project progress.
- Include the hashtags: #gimbalabs, #pieceofpie, and #hackathon.
- Mention @gimbalabs.
8
Make Your Product Publicly Accessible
By the end of the event, your app or product must be publicly usable and deployed to its intended platform (e.g., a live web URL, a downloadable mobile app, a browser extension, etc.). Projects that only run locally (localhost) will not qualify.
9
Deliver a Complete Final Presentation
Qualification is based on your final presentation. To pass verification and prove your work, your presentation must include:
- A live demo of your product.
- Your official public repo link.
- Links to all of your required weekly progress tweets.
- Link to deployed project
Sample Weekly Progress Tweet
Copy this template, then change the body to reflect your real progress for the week.
Week [X] update for [Project Name]
[Share what your team shipped this week]
[Add your live link or demo update]
[Share what you will build next]
#gimbalabs #pieceofpie #hackathon @gimbalabs
#gimbalabs
#pieceofpie
#hackathon
@gimbalabs
The Real User Pie
1
Meet the Builder Requirements
To be eligible for this track, your project must first fully qualify for the Builder Pie requirements listed above.
2
Gain Your First Paying User
You must secure at least 1 paying customer (excluding family and friends). You are required to provide proof of payment along with the story of how you acquired this user.
3
Share Your Proof Publicly
Both your proof of payment and your customer acquisition story must be published publicly for verification.
The Feedback Pie
1
Participate With or Without a Project
You do not need to be a participating Builder to join this track! It is open to anyone, though Builders are highly encouraged to participate as well.
2
Recorded Feedback Sessions
All feedback must be given via live, recorded video sessions (using tools like Zoom, Google Meet, etc.) with the builder present. No unsolicited feedback.
3
Share Evidence & Earn Credits
You will earn 1 credit for every recorded feedback session you complete, up to a maximum of 15 credits per qualified participant. Evidence must be shared for verification. Use this template
Timeline
Start with enrollment, then keep the momentum with steady build sessions and receiving feedback.
Weeks 1–2 — Enrollment period - April 13th - 26thRegister the project, list every participant, and submit the official public repo.
Weeks 1–12 — Build period - April 13th - July 5thBuild in public, keep the repo updated, and post at least one public progress tweet every week.
Week 12 — Final presentations - June 29th - July 5thShow the live/recorded demo, public repo, all weekly tweet links, etc. for verification.
Post-hackathon — Payouts - July 5th - 12thQualified participants receive shares within their pool based on the published rules.
Registration
Submit one registration form per project during the enrollment window.
Step 1 — Prepare your project infoFinalize your project title and team members, create an empty public GitHub repo, and keep the repo link ready before you begin.
Step 2 — Complete the registration formSubmit the official registration form with accurate information.
Step 3 — Keep your proof publicEnsure your repository and weekly progress tweets remain public for verification throughout the hackathon.
Official Source of Truth
All detailed rules, clarifications, FAQs, and official updates live in the Piece of Pie official channels. Please review them regularly to stay aligned throughout the hackathon.