unitaryHACK Rules

Eligibility

• Registration: All participants must register here to be eligible for cash bounties.
• Participation: unitaryHACK is open to any individuals not employed by Unitary Foundation, no matter their citizenship or nationality, as long as they are not organized or ordinarily resident at the time of participation in Cuba, Iran, North Korea, or the Crimea region of Ukraine (or where otherwise prohibited by U.S. law). For more info on what countries might be impacted, please see the US Treasury.
• Teams: You may work in teams, but one designated person must receive the bounty disbursement.
• Maintainers: Maintainers may participate but cannot claim bounties for their own projects.

Submission Requirements

• How to Enter: Submit a Pull Request (PR) directly to a participating project’s repository. Your PR description must link to the specific bountied issue (e.g., "Closes #123") to be tracked.
• Winning Bounties: Bounties are awarded to the first functional PR accepted and merged by the project maintainers. This means that submitting your issue first DOES NOT guarantee that you win the bounty. Acceptance is at the sole discretion of the maintainers.
• Timeline: Contributions must be made between June 3 and June 17, 2026. Submissions after 5:00 PM AoE on June 17 will not be considered without prior approval from the Unitary Foundation team.
• Public Activity: To ensure transparency and verification, your GitHub contribution activity must be set to public for the duration of the event. Failure to do so may result in disqualification from specific bounties or the full hackathon.
• No Squatting: Commenting on an issue does not "reserve" it. Only a submitted PR counts as a valid entry. We recommend checking for existing open PRs before you start working.
• Quality & Testing: PRs must be substantive and pass all existing automated tests (CI/CD). Maintainers reserve the right to reject low-effort or "spammy" PRs that do not provide meaningful value.
• AI Policy: NO AI SLOP. While we allow LLMs as collaborative tools, fully AI-generated PRs are prohibited. Maintainers have the right to reject any contribution that appears to be automated or lacks human oversight. Check out the full unitaryHACK AI policy here.

Code of Conduct and Disciplinary Action

All participants must adhere to the specific project’s Code of Conduct and the Unitary Foundation Community Code of Conduct.

Violations of any Codes of Conduct associated with unitaryHACK will be addressed by the Unitary Foundation team, with disciplinary actions determined at their discretion and based on the severity of the offense, up to and including a permanent ban. Those who are reinvited to unitaryHACK for the subsequent year will be placed on probation, with their participation contingent upon adherence to further conditions, again at the discretion of the UF team.

Support

Questions? Email us at hack@unitary.foundation or join the conversation on Discord!