79%· model self-report 90% · first seen 2026-09-30 · v1
Verified
2026-09-30 · by extraction
A hackathon challenging developers to build dApps using zero-knowledge technology on the Aleo blockchain to advance digital privacy. Open to individuals or teams who are approved members of the Strobe Hacker House SBC’24 or approved guests, with a novelty requirement for projects new to the Aleo ecosystem. Participants must build projects during the hackathon period (August 6–16, 2024) and submit a complete project, presentation, GitHub repository, and README via DevPost. Aleo Credits are awarded as prizes, payable after mainnet launch within 30 business days of the hackathon end.
Eligibility: Open to individuals or teams. All team members must meet eligibility criteria. Participants must be approved members of the Strobe Hacker House SBC’24 or approved guests. Aleo grant recipients are not eligible. Projects must be novel and built during the hackathon only.
Pipeline
Funder track record · does Aleo actually pay grants?
🟡 Some payout evidence · 1 grantee found · last payout 2026-10-22 · checked 2026-10-29 · 0 forum reports, 9 web pages read, 2 unverifiable claims dropped
Proven payer: at least 3 named grantees and one payout in the last 90 days. Every grantee below is quoted word for word from its source. When a source does not date a grant, the date is when that page or post was published.
Grantee
Amount
Date
Evidence
Town Council of Sant Quirze de Besora
—
2026-10-22
“The Town Council of Sant Quirze de Besora received on Thursday, October 22nd, the ALEO 2026 Award for Pioneering Action, presented by the Osona Local Energy Agency (ALEO), for the public recovery project of the Can Trinx”source
Trust breakdown (2/3 checkable facts verified)
Signal
Weight
Result
Note
deadline
0.35
100%
quoted in source
apply link
0.075
0%
link not in source
funder
0.075
100%
named in source
source quality
0.15
50%
social or search hit
model confidence
0.1
90%
model self-report
Fit breakdown (against the ORG_* profile)
Signal
Weight
Result
Note
model fit
0.5
70%
model rated 70%
ecosystem overlap
0.25
100%
aleo vs aleo
category overlap
0.15
33%
privacy, zk vs zk, privacy, infra, dev_tooling, security, interoperability
Aleo zKompete (SBC24): Develop dApps leveraging zk technology to advance privacy in our digital world. - Devpost
#### Rules
**Dates**
* **Project Start Date**: Aug 6, 12:01 AM EST
* **Submission Deadline**: Aug 16, 10:00 AM EST
* **Winners Announced:** Aug 19, 12:01 AM EST
**Eligibility**
* **Aleo Grant Recipients**: Projects that previously received an Aleo grant are not eligible.
* **Novelty Requirement:** Projects should be novel and new to the Aleo ecosystem.
* **Team Composition:** Open to individuals or teams. All team members must meet the eligibility criteria if participating as a team. Participants must be approved members of the Strobe Hacker House SBC’24 or approved guests.
* **No Pre-Built Solutions:** Eligible projects must be built during the hackathon only to ensure fairness.
**Project and Submission Requirements**
* **Project** **Timeline**: Work on projects can begin as early as August 6, 2024. All projects must be submitted via DevPost by the deadline.
* **Submission** **Components**: Complete project, presentation, GitHub repository, and README file.
**Code of Conduct (For In-Person Participation)** A comprehensive code of conduct will ensure a safe, respectful, and inclusive environment for all participants. This will be shared with all attendees before the event.
**Legal Considerations** Participants should consult their legal advisors to understand their rights and obligations. Hackathon organizers are recommended to consult a lawyer to finalize the rules and ensure compliance with all applicable laws and regulations. Aleo Credits (rewards) will be paid after the mainnet. All US residents will be required to have a holding period. Payments will be made within 30 business days of the hackathon end date. If there are not enough qualified projects for the initial prize, consolation prizes will be awarded at the discretion of the judges.
**Judging Criteria and Winner Selection**
**Innovation and Creativity**
* Assessing how the project introduces fresh ideas and solutions using zk proofs on the Aleo Blockchain.
* Innovation in leveraging zk technology for novel applications.
**Technical Implementation**
* Evaluating project functionality, security, and code quality, including its integration with the Aleo Blockchain.
* Focus on robustness, efficiency, and scalability of the solution.
**User Experience**
* Examining user-friendliness, accessibility, and the navigational ease of the project's interface, considering the time constraints of the hackathon.
* Importance of intuitive design and seamless interaction.
**Practicality and Real-World Use Case**
* Gauging the project's real-world applicability and potential impact on a global audience.
* Relevance and potential for implementation in practical scenarios.
**Bounty Implementation**
* Ensuring bounties are used correctly, in accordance with their rules and adequately explained to participants.
* Proper utilization of resources and alignment with hackathon objectives.
**zk Proof Usage**
* Analyzing the effective use of zk proofs for scalability, privacy, and computational efficiency.
* Emphasis on innovative applications of zk proofs for enhancing privacy and security.