The problem Bravo solves

Currently, hackathon award-management is a time-intensive, highly manual and ad hoc process requiring organizers to individually track down sponsors and winners for payments—Bravo changes this.

Time-consuming and inefficient: Organizers individually collect sponsorships and distribute awards to each team, an inefficient process that increases organizer responsibilities. This takes significant manpower and time away from organizing the hackathon, as people need to individually solicit, track, and organize sponsorship payments and awards payments. Organizers need to send their payment information to each sponsor, collect the payment information of each award winner, and follow up with all parties regularly.

Lack of validation: As payments to and from organizers are ad hoc, insufficient funds or early payouts make hackathons less fair. For instance, especially at hackathons where sponsor money is aggregated and then distributed for different prizes, if sponsors who do not send in money before the distribution begins, the last person to receive their award may not receive a full amount. There is simultaneously a first-come-first-serve problem as well as a problem with payment delays. Bravo will not pay out awards until the required amount is deposited, which means that organizers can more easily track down delinquent sponsors and award winners are treated fairly.

Lack of transparency: Award payments are conducted behind the scenes. Attendees and sponsors have no confirmation about when and where payments were made, as well as if organizer misused or forget to send out award money. The one-click system provides transparency regarding payment.

Challenges we ran into

This is Alice's first hackathon, so everything was new. Specifically, integration with the front end was most challenging given the specific vision we had and the platform requirements. We got past it via numerous Google searches.

The Avalanche launch process was broken for us and caused our team to be unable to deploy. To resolve this, we found and deployed on another EVM with similar functions and capabilities.