SuperHunt

SuperHunt is a decentralized platform that lets users post/submit bounties projects. It uses passkeys to get users to sign in to the platform, and let them add some accounts (i.e. WorldID, Farcaster ID). What makes it different from others is that it is trustless, i.e., neither the bounty sponsor nor the hunter have to trust each other. Usually, sponsors have the advantage of first viewing the solution/submission of the bounty they asked for and then paying the respective amount only and only if they want to. Moreover, all submissions are public, so it's not a big deal to copy another, make some worthy tweaks, and submit it again. That's what SuperHunt avoids and it doesn't reveal any codebase provided by the hunter until he/she gets paid and even providing the proofs that he actually created a project. To understand this in detail, let's dive into how the Bounty is posted, submitted, and then validated:

Bounty Creation:

• Sponsors or users who seek to post a bounty can describe it well by specifying the desired amount. They are free to post the bounty on any Superchain - Optimism, Base, Celo, Metal L2, Fraxtal according to the availability of assets and the fees each chain costs. (Will try to include a small interface that shows live gas fees which helps bounty sponsors to make a better decision).
• The specified amount is locked inside the smart contract upon listing a bounty, ensuring funds are secured and preventing potential disputes.
• Bounty creators can specify required proofs (e.g. Video, web-app link, etc.) and also mention verification criteria (i.e. World ID) for the hunters if they want. This means that only the hunters who have added World ID are eligible for that bounty.
• They can even share the bounties on Warpcast social using Farcaster frames.

Bounty Submission:

• Only hunters meeting the verification criteria can submit, and World ID makes sure that it's a real human.
• One can submit the links asked i.e video, website, and the GitHub repository. The repo won't be shared with the bounty creator/sponsor until the hunter gets paid. There will be certain conditions while he/she is submitting the repository, such as, the repository should be public at the time of submission, the Website should be attached to the GitHub repository, and deployments made should be visible, No changes should be done after the repository is submitted (in other words, Don't touch it).
• The bounty hunter will attest his proofs using EAS regarding the submissions making sure that he doesn't change anything within the GitHub Repository after submission. Behind the scenes, the proof will consist of a collective hash consisting of the repo's latest commit, latest deployment, site attached, etc.

Bounty Validation:

• On reaching out to the submission, the sponsor/creator can find several details such as the demo video, site attached, number of commits made so far, the original deployment attached to the repo, etc.
• Based on these, it's all in the hands of the creator/sponsor whether to approve the submission or not.
• Upon approval, the repository is checked again for verification of its attested proof to make sure nothing has changed. Then the funds are unlocked within the smart contract and transferred to
• If the submission got approved, the hunter can make a final confirmation after making his repo public (as he can easily make the repo private after making the initial submission).
• The platform verifies the attested proof again with the current state of the Repository and if everything looks fine (i.e. Hunter hasn't changed anything within the repository) then the funds within the smart contract are unlocked and transferred to the bounty hunter whereas the codebase is provided to the sponsor (i.e he can now clone the repo, and take a look).

Most of the details have been provided in the above section. Let's come to the technologies being used within this project:

1. thirdweb: Thirdweb in-app/Smart wallets integration which requires a passkey to login.
2. Worldcoin: World ID and Farcaster ID are allowed to be added. Moreover, World ID can be helpful for bounty creators for extra verification.
3. EAS: For attesting the proofs related to bounties.
4. Blockscout: Act as blockchain explorers for various networks.
5. Celo: Using Opera Mini for mobile devices.
6. Pyth: Grabbing up the price feeds for various tokens/currencies.
7. Farcaster: Using farcaster frames for sharing on warpcast.
8. Testnets: Several testnet networks will be used for contract deployment, like Optimism Sepolia, Base Sepolia, Celo Alfajores, Celo Dango, Metal L2 testnet, and Fraxtal testnet.
9. Tenderly: Testing the app on virtual testnets and also integrating it within the Dapp if any user wants to test the platform without taking care of the faucet.

Anything hacky in particular?

Well, that's for you all to decide. According to me, letting the bounty hunters prove their worthy submissions without even revealing the exact codebase is hacky for sure. That's possible with the magic of EAS and GitHub API. We can even call it Zero Knowledge Proof, but it's not even that exactly. It's different!