1. Do I need to pay to register for the hackathon?

No, registration for the “Build with Celo Hackathon” is free on HackerEarth.

2. Do I need to have specific qualifications to participate in the hackathon?

If you love to code, you are welcome to participate!

3. How do I submit what I have made for the hackathon?

You must submit a video-recorded pitch no longer than 4 minutes in length. In the README.md of the project, you must include a link to your project’s GitHub repo that includes the project source code, all necessary graphics, or assets, and instructions to run the application.

4. Do I need to have my entire idea fully operational?

The idea need not be fully implemented; however, the submission should include a demo so that it can be reviewed by the judges.

5. What is the recommended development environment?

We recommend utilizing open-source tooling that aligns well with the language support you need to develop your project. A popular and free IDE is Visual Studio Code.

6. Can I bring in an existing application that was previously built for another hackathon?*

Yes, you can bring an existing application if you build a new component for it responding to the monthly challenge prompt and if you develop this new component during the timeframe of the hackathon.

7. Does the project repository and developer activity within Github need to be public?

Yes, your project should be a public GitHub repository.

8. Do I need to give a demo of the product that I have built?

You must submit a small recorded presentation or video that demonstrates and/or explains your submission. If you are judged a winner, you may be invited to demo your application at a live event (details of that event will be shared with sufficient advance notice.)

9. A fully developed application may require a backend for data storage like SQL, etc. Since it’s online, is it acceptable to show only the application prototype?

Yes, you can submit just the prototype, but it must interact with Celo testnet or mainnet. If you use any database, such as MySQL or PostgresSQL, you must submit a database dump with your submission. If you provide a database, then there should be sufficient steps taken to automate the configuration of your application database. It may make sense to instead use a browser cache to simplify configuration steps and increase the likelihood that your project can be run by the technical review team and judges.

10. Will all team members have access to work on the project at the same time?

Yes, all team members can log in and work simultaneously on HackerEarth & Github platforms.

11. Who owns the IP (Intellectual Property) rights to the product I build during the hackathon?

The developer(s) of the smart contract/dApp/web/mobile application own all rights. Your project code must be open-sourced and accessible for evaluation by judges. Further refinements to the project are recommended before pitching.