Protocol and infrastructure tooling
Reliability, core primitives, and upgrades that improve the Ethereum builder stack.
Hackathons
A repeatable participation model for builders, mentors, and judges.
The 2026 hackathon is a focused shipping sprint. Public pages explain how the program works, what teams must produce, and how the work continues afterward.
- Build Window
- April 6 to 18, 2026
- Focus
- Useful technical output with credible follow-through
- Output
- Repo, demo, scope statement, and next steps
Core Tracks
Public tracks should be broad enough to be durable and specific enough to shape submissions.
The launch site explains the categories teams can build toward without freezing sponsor-specific track mechanics into public copy.
Security and resilience
Auditable improvements, better guardrails, and operational quality that holds up after the demo.
Developer experience and onboarding
Tools, workflows, and teaching surfaces that make the ecosystem easier to enter and contribute to.
Real-world use cases for LATAM
Projects that connect Ethereum infrastructure to practical local needs without collapsing into generic fintech theater.
Participation Model
A build sprint needs clear checkpoints.
This is where the page stops being marketing copy and becomes operationally useful.
Kickoff
Program framing
Teams align on tracks, judge expectations, and the difference between a concept deck and a credible submission.
During the sprint
Mentor checkpoints
Mentors provide architecture feedback and technical unblock support. Sponsors can back tracks, but public rules stay uniform.
Submission
Structured demo output
Each team submits a repository, short demo, scope summary, dependency list, and a candid implementation status.
After judging
Follow-on paths
Promising teams move into incubator support, partner intros, grants, or contributor pipelines.
Submission Expectations
Demo day should not be a black box.
Teams need to know what must be submitted and how quality will be judged before they start.
Required outputs
- Public repository link and commit history
- Short product or technical demo
- Clear scope statement and implementation status
- Explicit dependencies, assumptions, and next steps
Judge principles
- Technical quality and maintainability
- Clarity of execution
- Usefulness to builders or operators
- Alignment to the chosen track and stated constraints