Application

Only hackers who have received email acceptance can participate in the hackathon.

Hacking Rules

• Hacker teams are made up of a maximum of 5 people;
• All projects developed during ETHRome must be open-source;
• At least 2 members of the team must physically be at ETHRome in order to present the submission to the judges;
• The hackathon has a 40-hour duration: from 6:00 PM CET on Friday to 09:00 AM CET on Sunday. Judging and award ceremonies to follow;
• Each project should adhere to one of the two tracks (check below for more details about each track)
  • Account Abstraction Track
  • Privacy Track
• In addition to the track, hackers will be able to select sponsor bounties to apply to. All bounties can theoretically be used in both tracks (AA or Privacy). The allocation of bounties depends solely on the sponsors. No judge or ETHRome organizers are responsible for their allocation and the way they are awarded.

Pre-existing projects allowed

Our policy on existing projects is that a team may bring in an existing project provided that:

• The team must explicitly communicate in the Taikai submission that they are working on an existing project;
• The team must develop new functionalities or extensions of the project, and that part only will be considered during the judging process;
• The team must not create a new repository and "single commit" all their code: instead, the team must make their existing repository public and work on it. Only the commits after the ETHRome starting period will be considered during the judging process;
• The team's project must be born at another hackathon and all previous iterations of the same project at previous hackathons must be linked in the submission. Existing projects that did not come into existence during previous hackathons are not allowed

<aside> ⚠️ If these conditions are not met the team will be categorically excluded from the hackathon and will not be eligible for the hackathon prizes or sponsor bounties.

</aside>

<aside> 🚫 Hackathon organizers, mentors, judges, and those involved will take extreme care to avoid fraudulent behavior by exploiting work already done that does not respect other hackers and the previously quoted rules.

</aside>

Prizes and Bounties

There are two tracks proposed:

• Account Abstraction
• Privacy

Both of them follow the same submission and judging process. All the projects selected as finalists will be able to do a live demo on stage during the Closing ceremony on Sunday afternoon. Judges preserve a 7-day period to make the results of the two hackathon tracks official. If irregularities are found in the code repositories of any winning teams, the judges may exclude the team from the hackathon competition and not award the prize.