🌊Waveprotocol

Hackathons are the best way to create a developer community for a project, but there are still challenges.

However, there is still a challenge: It is difficult to establish an ongoing relationship with developers after a hackathon.

The AKINDO protocol is based on the concept of an ongoing hackathon, where projects are evaluated and prizes are distributed after a certain period of time.

A hackathon is represented as a Wave, which can last for a week, a day, 12 hours, etc., as determined by the organizers. After the first Wave, Wave 2 begins, which runs automatically until it is stopped.

Once the Wave Hackathon is turned on, it runs automatically and is a sucker for developers.

We used the UMA protocol from Safe's zodiac to implement this protocol.

We also use Snapshot to evaluate submissions to hackathons. We utilize UMA as the oracle for converting the voting information to this Snapshot into an on-chain Transaction.

We implemented a custom extension because it was not possible to inject voting results into the contract with the existing Snapshot. We added a button that allows injection of voting results if there is a uint[] argument in the transaction submitted to UMA.

The snapshot repository (branch: feature/inject_votes) can be found at: https://github.com/akindo-io/snapshot

Test environment: http://54.250.78.147/#/

Example proposal http://54.250.78.147/#/akindotest.eth/proposal/0x6548cf07e3c8afc7af5b9c15149e7ec00955061f7e99b818e31060d7a9fc05a4

Transactions approved through UMA will be distributed to hackers according to the percentage of prior votes. This distribution of Transactions will utilize a proprietary contract.

First, off-chain voting data is oracleed to the on-chain data, second, it is automatically distributed through a unique contract, and third, the Wave is automated and continuous, so the hackathon is continuous. We used our own technology.