PROJECT NAME: BountyArena
DESCRIPTION OF THE PROJECT
We are Web3 fanatics and developers, so why are we continuing to use a centralized platform to submit our project?
BountyArena is a platform to manage bounties (but everything similar like grants, requests for help or others can work). An entity (user or company) can publish a bounty and devs can apply and try to win the prize.
The bounty owner or the judges will launch a Snapshot proposal where the selected people (so in this case the judges) have to elect the best submission.
TELEGRAM USER NAME
REPOSITORY WITH PROJECT'S CODE (should be open and public)
VIDEO DEMO (3 min max)
- SpaghettiETH: we candidate BountyArena to SpaghettiETH bounty because it is a decentralized tool that can fit perfectly event organization needs;
- TalentLayer: we used TalentLayer StarterKit as a boilerplate and edited it for our goals. Plus, we used the TalentLayerReviews as an opportunity to build and increase user reputation on-chain;
- TheGraph: we used TalentLayer's GraphQL queries and created some different on our own for specific use cases to query their deployed subgraphs;
- ENS: we have thought about something that can increase ENS ecosystem and functionalities. For a lot of people, ENS is mainly a DNS to resolve a human-readable string to an on-chain address. So our idea is to save Verifiable Credentials inside text-records to make verifiable information directly accessible through ENS so that everyone can verify by himself. We think it is a creative way to use text-records and save something that has a lot of value.
- Interface: BountyArena has a great UX and we hope it will make Ethereum more accessible and easy to use for everyone.