DAO Global Hackathon 2023

Each industry has different needs when building out their DAOs. Investment DAOs need vesting tools and more advanced asset management tooling, than say Social DAOs, who may want more community metrics and integrations.

Pick your favorite industry (DeFi, creator economy, NFT projects, boards, investment DAOs, metaverse, you name it) and build a tool that bundles the plugins and integrations that industry will need to get started running their DAOs without much hassle.

Criteria: Build a dApp allowing users to quickly spin up DAOs based on their specific use case or industry. Judging will be based on use of Aragon OSx, easy-to-use user experience, and real-world usefulness.

Prize will be split between one or two projects based on submissions.

Resources: Developer Portal, ideas, SDK docs

Point of Contact: Juliette Chevalier, Developer Advocate (juliette@aragon.org) or

The goal of this bounty is to create the most seamless integration between two or more DAOs, enabling cross-DAO collaboration, communication, and data sharing. With the proliferation of DAOs in various sectors, it's becoming increasingly essential to create interoperability between them. The successful integration of multiple DAOs will foster collaboration, innovation, and community growth and help advance the adoption of DAO technology.

Submission Requirements: Create a new workspace on DAO Manager with a clear name that describes the project. Create a new Github account and record the work there. Include a detailed README file that explains the project, its features, and how it enables DAO interoperability. Include a working demo of the project, such as a video or a live website, to demonstrate its functionality. Include a detailed description of the technical implementation, such as the programming languages, frameworks, and tools used. Include a detailed description of the interoperability mechanism between the DAOs, and how it enables cross-DAO communication, collaboration, and data sharing. Include a section that explains the user experience of the project, including screenshots and a description of how users interact with the project. Provide clear instructions on how to deploy and run the project in a local or remote environment. Include a license file that describes the terms of use of the project.

Judging Criteria: (a) Functionality: How well does the project enable interoperability between DAOs? Does it allow for seamless communication, collaboration, and data sharing? (b) Technical Implementation: How well is the project implemented from a technical perspective? Is the code clean and well-organized? Is the project secure and scalable? (c) User Experience: How easy is it for users to interact with the project? Is the project intuitive and user-friendly? Innovation: Does the project demonstrate a unique or innovative approach to DAO interoperability? Does it push the boundaries of what's currently possible?

The two best bounty winners will receive a combined prize of $3000.

The goal of this bounty is to create a mobile notification system for multi-community members that will keep them updated about important events. The winning project will be selected based on the quality, usability, and effectiveness of the notification system created. The system should be user-friendly and allow for customization based on the user's preferences.

Deliverables: The deliverables for this bounty should include a functional mobile notification system that provides timely and accurate updates to multi-community members. The system should include the ability to customize notifications based on the user's preferences and allow for easy navigation and accessibility. The system should also include clear instructions and be intuitive for users who need to become more familiar with complex technical systems.

Evaluation Criteria: Quality and usability of the mobile notification system Effectiveness and timeliness of the notifications Customization and accessibility of the system Creativity and innovation in design and functionality

Resources: RobinAI

The winning project will receive a bounty of $3000 and will be featured on DAO Manager as a top mobile notification system for multi-community members. The project will also be able to work with DaoLens to promote community engagement and participation further. There will be two winners for this bounty

Point of Contact: balu@daolens.com

The goal of this bounty is to encourage participants to develop innovative and secure blockchain-based storage mechanisms that can be used in various decentralized applications. The winning submissions will demonstrate the ability to store data in a decentralized, tamper-proof, and scalable manner.

Requirements: Develop a working prototype of a blockchain-based storage mechanism that can be integrated into decentralized applications. Demonstrate the ability to store and retrieve data in a decentralized, tamper-proof, and scalable manner. Submit a detailed report on DAO Manager outlining the technical specifications, implementation, and testing of the solution. Open source the code on a public repository such as Github.

Evaluation Criteria: (a) Security: The solution should be resistant to attacks and ensure the confidentiality and integrity of stored data. (b) Decentralization: The solution should leverage the blockchain's decentralized nature to ensure the availability and immutability of stored data. (c) Scalability: The solution should be able to handle a large volume of data and ensure high performance and low latency. (d) Innovation: The solution should be innovative and demonstrate a unique approach to blockchain-based storage mechanisms.

The winning project will receive a bounty of $1000 and will be featured on DAO Manager as a top 1-1 chat function for DAO Manager. The project will also be able to work with DaoLens to promote community engagement and participation further.

Resources: RobinAI

Point of Contact: balu@daolens.com, Marketing and Growth, balu.mtr#2280

We're seeking proposals for the creation of a gamification framework that will enhance community engagement in DAOs using DAO Manager. The framework should be designed to motivate users to participate in DAO activities and encourage collaboration among community members. The gamification framework should be flexible enough to work with various types of DAOs and should be scalable to accommodate growth in membership and activities.

Deliverables: A detailed proposal for a gamification framework that will enhance community engagement in DAOs using DAO Manager. A working prototype of the gamification framework that demonstrates its functionality and effectiveness in motivating users to participate in DAO activities. Documentation that outlines the technical details of the gamification framework, including its architecture, design, and implementation. A report that evaluates the effectiveness of the gamification framework in promoting community engagement in DAOs.

Requirements: The gamification framework must be designed to work with DAO Manager. The gamification framework must be flexible enough to work with various types of DAOs. The gamification framework must be scalable to accommodate growth in membership and activities. The gamification framework must be effective in motivating users to participate in DAO activities and encouraging collaboration among community members. The proposal must include a detailed timeline for the development of the gamification framework. The proposal must include a detailed budget for the development of the gamification framework.

The winning project will receive a bounty of $1500 and will be featured on DAO Manager as a top events-only version of DAO Manager. The project will also be able to work with DaoLens to promote community engagement and participation further.

Resources: RobinAI

Point of Contact: balu@daolens.com, Marketing and Growth, balu.mtr#2280

We are looking for innovative solutions that leverage artificial intelligence (AI) to enhance the capabilities of DAOs. Specifically, we are interested in solutions that use AI to improve insights, engagement, and compensation in DAOs. The goal of this bounty is to find new ways to make DAOs more effective and efficient by leveraging the power of AI.

The deliverables for this bounty are as follows: A detailed proposal outlining how AI can be used to improve insights, engagement, and compensation in DAOs. A working prototype that demonstrates the proposed solution's functionality and effectiveness. Documentation that outlines the technical details of the proposed solution, including its architecture, design, and implementation. A report that evaluates the effectiveness of the proposed solution in improving insights, engagement, and compensation in DAOs.

Requirements: The proposed solution must utilize AI to improve insights, engagement, and/or compensation in DAOs. The proposed solution must be designed to work with DAO Manager. The proposed solution must be scalable to accommodate growth in membership and activities. The proposal must include a detailed timeline for the development of the solution. The proposal must include a detailed budget for the development of the solution.

Resources: RobinAI

Point of Contact: balu@daolens.com, Marketing and Growth, balu.mtr#2280

Dispute resolution is the go-to-market branding of Kleros. However, at its core, Kleros is a Schelling-point oracle able to return rulings/answers to subjective questions directly on-chain. It's through this fundamental flow of [ask question -> get answer -> execute logic] that Kleros is able to address use cases such as escrow payment disputes, content moderation, decentralised data curation, and verification of real-world events on-chain.

Your mission is to further unlock the potential of this subjective oracle flow to solve problems, address use cases, or come up with entirely new solutions for DAOs. This can be done either through creating new arbitrable primitives using ERC-792, or using existing Kleros products like Escrow and Curate as building blocks for something new.

This is an open-ended bounty with the only strict requirements being that projects stay relevant and within the scope of DAOs.

Kleros runs in-house incubation and venture-building services, so we approach hackathons and other builder events with a "business first" approach. The winning submission will be chosen on the basis of whether the submission could be an actual winning product from an investment point of view.

Does your product have any demonstrable demand? Are you able to pinpoint a customer or user persona? Does your product support either a revenue or token model that could make it profitable/sustainable in the long term? How likely is your product to raise funds? These are a few examples of the questions that judges will ask amongst themselves while reviewing submissions.

Some things to think about adding to your submission that will help you stand out include (but are not limited to): 1. Lean Canvas: Even if it's a rough draft, this will give us a good sense of how you think about building winning product. 2. Documentation: You don't need to have a fully fleshed-out gitbook, but having some form of detailed, well-structured documentation is important when we assess submissions. This could be as simple as having a well-structured README.md or Notion page. 3. Demo: Using the screen recorder of your choice, present a concise demo of your product. 4. Pitch Deck: In the startup world, how you sell your idea is just as, if not more important than how you actually build the idea. Submissions that come with pitch decks will have a significant advantage over those without.

Resources: DAO Industry Guide , Integration Handbook , Arbitrable Development Guide

Point of Contact: DevRel & Venture Building Lead - xpriment626#2365 on Discord

At its core, Q enables organizations and protocols in Web3 to set human readable rules, enforce non-binary decisions and allows parties to access dispute resolution upon those rules. For the Q blockchain, this underlying ruleset is called the Q Constitution.

DAOs wanting to access this functionality will have the option and responsibility to create their own ruleset which fundamentally includes the DAO’s purpose and obviously name. Not surprisingly both are commonly defined by an emerging DAO at its creation.

While it is hard to define a specific jurisdiction for any blockchain, which is valid for all wallets addresses using it; Frontends are commonly hosted on centralized servers and maintained by companies or private individuals and thus commonly subject to any law.

With AI language models becoming more powerful and gaining traction, some legal prudence can be implemented and automated. By using an AI based plugin on a DAO-factory website, a provided free-text description of the DAO purpose shall be evaluated. Creating a DAO (using the factory-frontend) shall only be possible if no violation to the law (as defined by the frontend provider) is detected by the AI.

Requirements: The Q DAO Factory can be used like before, but moving on after describing DAO Name and Purpose can only be done if the bot approves. The same will be the case for describing Name and Purpose of any “Expert Panel”

Output expected: Documented code to be inserted into the repo provided. AI tool adapted/pre-trained to United Nations and Liechtenstein code of law.

Judging Criteria: Demo should be included. Code should be usable and tested. Bonus points for good UX/UI. Should be easy to plug into the existing code.

Resources:

https://gitlab.com/q-dev/q-gdk/factory-dapp

DAO Factory

DAO Governance Dashboard

Point of Contact: DAO Integration Lead – gerrit_b#1929

Governance requires decision making and thus can quickly become challenging in a decentralized setting. While a degree of autonomy among DAO members is required for the organization to stay agile, voting is commonly used to make important decisions. Especially if those decisions impact the whole DAO. If transaction costs of the native blockchain permit it, on-chain voting is often used for its transparency in the voting process and the immutability of the voting outcome. Therefore it is self-evident that whenever the DAO votes on issues involving on-chain execution there should be no gap between a successful vote and the execution of its outcome. The applications of on-chain execution are plenty, ranging from initializing a simple transaction, over signing a message on-chain, or calling any smart contract function.

On a user basis, proposal creators should have the option to include calling smart-contract functions as one possible “proposal type”, while selecting the function to call and (if applicable) which input parameter to call it with. The goal of this bounty is to enable proposals including arbitrary function calls within the Q GDK and DAO Factory as an option for DAO architects to choose from.

Requirements: The Proposal shall fit the existing structure of the Q GDK DAOVoting. It should be compatible with the existing voting frontend. If required, modifications shall be proposed to make the frontend and the smart contracts compatible.

Output expected: A Voting Contract that includes the option to include function calls. The ability to execute function calls through voting should be showcased using an example of a treasury smart contract which allows basic ERC-20 transactions and can only be managed/called through proposals/votings. Creating the proposal (including selecting which function to call), voting on it and executing the proposal should be able to be done through a frontend (existing frontend can be used as basis).

Judging Criteria: Demo should be included. Code should be usable and tested. Should be easy to plug into the existing code. UX/UI is crucial here to make it as “non-dev-friendly” as possible. Bonus points if the “Function Call Proposal” is selectable in the DAO Factory Frontend.

Resources: https://gitlab.com/q-dev/q-gdk/

https://gitlab.com/q-dev/q-gdk/gdk-contracts/-/blob/main/contracts/governance/DAOVoting.sol

https://gitlab.com/q-dev/q-gdk/factory-dapp

https://governance.q.org/

DAO Factory

DAO Governance Dashboard

Point of Contact: DAO Integration Lead – gerrit_b#1929

The Q Governance Framework allows for the creation of customized DAOs. By implementing Expert Panels, the DAO can set unique roles each with their own responsibilities, privileges, and limitations. Expert Panel members can be set upon creation of the DAO or be voted in-to and out-off their position by the DAO Community through on-chain voting.

Hats Protocol enables the revocable delegation of authority and responsibility for DAO-native roles and credentials, represented on-chain by non-transferable ERC1155 based tokens. An address with a balance of a given hat token "wears" that hat, granting them the responsibilities and authorities that are connected to the token.

We see immense potential in the combination of issuing or revoking a hat in correspondence to the membership of a given Expert panel, for example for the use of token gating on communication channels.

Issuance and revocation of the hat should thereby be done natively by the Expert-Membership proposal to reduce added complexity for DAO creators and users, as well as to ensure alignment of Expert-Membership and the privileges of a given hat.

Requirements: Use the hats protocol (V1). Don’t compromise on existing functions of the Q GDK. Hats should be issued or revoked automatically when membership votings are executed.

Output expected: (a) Added Smart Contract functionality without impairing existing functions. (b) Should include front-end compatibility for expert-membership-votes (existing frontend is ok).

Judging Criteria: Demo should be included. Code should be usable and tested. Ability to create a DAO ‘with hats’ using the Q DAO factory is a plus. Bonus points for good UX/UI.

Resources: https://gitlab.com/q-dev/q-gdk/gdk-contracts/-/tree/main/contracts

https://gitlab.com/q-dev/q-gdk/factory-dapp, https://governance.q.org/

https://github.com/Hats-Protocol/hats-protocol, https://docs.hatsprotocol.xyz/#hats-protocol-docs

https://app.hatsprotocol.xyz/

DAO Factory

DAO Governance Dashboard

Point of Contact: Q DAO Integration Lead – gerrit_b#1929; Hats Protocol Cofounder nintynick#2222

The goal of this hackathon is to encourage innovation and development around Uniswap governance. Participants will focus on creating tools, services, and applications that enhance the efficiency, transparency, and inclusiveness of the decision-making process in the Uniswap community. This can involve working to improve the governance experience for delegates and the broader community, such as implementing smart notification systems, streamlining communication channels, and promoting greater engagement in governance-related activities.

Some potential areas to explore include:

Smart notifications for delegates: Develop a system that provides real-time notifications to delegates about important governance events, such as new proposals, votes, temperature checks, and relevant discussions in the forum.

Enhanced communication tools: Create tools that facilitate communication and collaboration between community members, delegates, and stakeholders, fostering an inclusive and transparent governance process.

Data visualization and analytics: Build user-friendly dashboards and analytics tools that help community members to better understand the current state of governance, the impact of decisions, and areas for improvement.

The success of this hackathon lies in creating solutions that empower the Uniswap community to make more informed decisions, promote collaboration, and ultimately strengthen the decentralized nature of the platform.

Submission Requirements: 1. A functional prototype of the proposed tool, service, or application that integrates with the Uniswap governance system and, if applicable, Aragon's platform. 2. Building using the Uniswap API/SDK and/or Aragon's development tools, as needed. 3.A clear and concise written explanation of the project, detailing its purpose, features, and how it enhances the efficiency, transparency, and inclusiveness of the Uniswap governance process. 4. A demo video or presentation, no longer than 5 minutes, showcasing the functionality and user experience of the project, including a demonstration of the integration with Uniswap governance and, if applicable, Aragon's platform.

Resources: V3 SDK Overview, Dev Docs , Getting Started Book, Whitepaper, Analytics, Subgraph 1 & Subgraph 2 , TWAP Documentation , TWAP library

General Tooling: Hardhat Getting Started Guide, v3 Hardhat Plugin, v3 Liquidity Mining/Staking Contract, Testnet Faucet, v3 TWAP cli, TWAP Hardhat Plugin

Prizes: 1st Prize: $6,000 2nd Prize: $3,000 3rd Prize: $1,000

Point of Contact: Tyllen Bicakcic - Dev Rel Lead - tyllen.uni#8894

Notifying interested parties about governance proposals or working group meetings can be a tedious task. With the governance community spread across Twitter, email, and Telegram it would be great to give people the option to get reminders where they prefer. Not everyone hangs out in governance forums to stay up to date with notifications.

Criteria: This site should be a working demo. Please share a video demo. Incorporate a major messaging platform or social media platform. Functionality is more important than aesthetics (UI).

Resources: https://ens.domains

Point of Contact: alisha.eth / alisha.eth#0001 – Governance Lead at ENS

There are over 400k DAO voters using ENS. Build something that helps improve the governance experience for ENS users or onboard more governance participants to ENS. Ideas include improving the social discoverability of governance participants with ENS, or tools to help build out profiles/identities for ENS users, or easy ENS registration tools.

Criteria: Functioning app or code OR figma mockups with demo video/walkthrough.

Point of Contact: alisha.eth / alisha.eth#0001 — Governance Lead at ENS

Build a plugin to make the Discourse forum experience more delightful for DAO forum users. Ideas include building integrations for Snapshot, Tally, Gitcoin Passport, Sign in with Ethereum or ENS.

Criteria: Functioning code repo OR Figma mockups + a demo video/walkthrough will be used for judging.

Point of Contact: alisha.eth / alisha.eth#0001 — Governance Lead

The problem: At present many cryptocurrency payments end up being sent into the nether, or to the wrong recipient, by mistake. There are many reasons for this, but it doesn’t help that in the world of blockchain we almost always deal with complex wallet addresses that can be entered or copy/pasted erroneously.

Wouldn’t it be nice if there was a means to post payments that could still be reversed in the event of a mistake?

The goal: The goal for this challenge is to develop a mechanism that makes it possible for someone to send cryptocurrency (ETH and ERC20) to a recipient, but for the transaction to not be finalized until the recipient takes an explicit action to claim the payment.

This could potentially be achieved by sending funds to a smart contract that can act as a payment intermediary (escrow) which holds on to the funds intended for a recipient, but to notify the recipient via an alternate communications channel, in order to let them know that they’ve been sent funds (that they need to claim).

Example scenarios: (a) A user sends a payment to a wrong address and realizes that they sent it to the wrong address. Up until the recipient claims those funds, the sender has an opportunity to cancel the payment and to have the funds returned to them. (b) A user sends a payment to a wrong address (e.g. a smart contract), and doesn’t even realize it. After a certain number of days the payment has gone unclaimed, and because it has gone unclaimed, it will automatically be reversed even if the sender didn’t explicitly request cancellation of payment.

Criteria: An EVM compatible smart contract with the escrow logic. A frontend where both the recipient and sender can execute required functions (e.g. initiate payment, claim payment). A notification / alert of some sort for the recipient ( ex: an email and/or metamask snap notification)

Considerations: Evaluate what communication channel(s) might work best for sending payment-related alerts/notifications. Think of how the payment mechanism might be exposed via some kind of website widget. Investigate MetaMask “snaps” to see if they might play a role in sending payments or receiving notifications. Consider how to automate certain functions like reversal of unclaimed funds after X days

Judging criteria: We value functionality over aesthetics. We want something simple and intuitive. Although you don't need to obsess over corner cases, we expect something that is relatively free of bugs. If you detect corner cases that your solution hasn't solved for, document them and suggest potential remedies.

Resources: https://metamask.io/snaps

Winner - $2,000, Runner up - $1,000

Point of Contact: Sebastian Zambrano Arango - Blockchain Developer - Sebas-aran16#0317

Build an app with social features using Lens Protocol.

Best social app built with Lens Protocol APIs, SDKs, and / or smart contracts. Judging criteria includes originality, UX, and real-world usefulness.

Resources: https://docs.lens.xyz/docs

1st Place: 2000 USD, 2nd Place: 1000 USD

Point of Contact: nader@aave.com, @naderdabit on Telegram

Best implementation of a social feature with Lens Protocol

Criteria: Any integration of Lens into an existing app will qualify. Design, UX, and originality will be some of the main criteria.

Resources: https://docs.lens.xyz/docs

$1,000 x 2 (two prizes, each $1,000)

Point of Contact: nader@aave.com, @naderdabit on Telegram

Building good and scalable DAOs requires tooling that supports multi-player use cases like storing contributor credentials, contribution scores or managing user generated content. We built ComposeDB on Ceramic to enable developers to build applications using composable and interoperable data. For this hackathon, we are challenging developers to build DAO tools using ComposeDB on Ceramic. We want to see DAO tools that would make it easier to facilitate discussions and collaboration, tools that would make it easier to track user contributions and rewards members for their work, and any other tools that would make it easier to create, manage and scale DAOs.

Judging criteria: Must use ComposeDB on Ceramic. Must use at least one data model with relations. Must be a working tool or a demo. Judging will be based on how well the tool utilises ComposeDB features like composability and interoperability as well as what impact the tool will have on the growth and scalability of DAOs.

Resources: Documentation, Create Ceramic App tool, Configure Ceramic Node on AWS

Top 3 best projects will be rewarded $500 each.

Point of Contact: justina@3box.io

The purpose of this bounty is to create an algorithm for understanding which governance participants are best for doing an airdrop.

While there are many factors and considerations for an Ideal Wallet to airdrop to, for the purpose of this analysis we define the ideal wallet as one that does not sell airdropped tokens right after claiming. Please choose at least 2 of these cool-off periods: 1 week, 2 weeks, 1 month, and 2 months.

We will provide you with two lists of 10,000 governance participants. One of them will be a list of the top 10k addresses, as ranked by DeepDAO’s DAO Participation Score. A 2nd list is a control group of other 10k wallets. The algorithm, which does not have to be formalized in code at this point, should point to the better list: is List A better for a future airdrop, or is it List B?

Bonus points will be awarded to submissions that can pinpoint predicting individual addresses best suited for airdrops.

DeepDAO API:

In addition to the two lists, which will be provided in CSV format, we will grant free access to our Profiles API endpoint, which returns the addressee's DAO Participation Score, the number of Organizations it has voted in, the number of proposals it created, and number of votes.

Additional tools that DeepDAO provides are available on our site at https://deepdao.io, in the form of DAO categorization, DAO treasuries, and many other data points that could be relevant for this exploration.

The task is to check if there is a correlation between some of these metrics and the behavior of a wallet in an airdrop. For example, is a wallet that is ranked in the top 10k on DeepDAO less likely to sell airdropped tokens? Is a wallet that never participated in DAOs more likely to sell? Are there special categories of DAOs (for example, Infrastructure, or NFTs), that generate ideal wallets?

Participants can choose one or more of the past airdrops (preferably one of the Arbitrum, or Optimism airdrops) to do an airdrop post-mortem of sorts.

*The submission is expected to be a max 2-page report summarizing the methodology, data collection, and main findings. *You are also required to come up with an algorithm that can be used for determining the best group, or wallets. *You are also required to attach all the raw data used in the report.

Judging criteria: submissions will be evaluated on the quality of your report (significance of findings and interest to the DAO community, analysis validity, research reproducibility). Extra parameters analyzed in scoring/analyzing ideal wallets may be awarded extra points.

Resources: https://deepdao.io/organizations, https://deepdao.gitbook.io/deepdao-products/governance-list-the-top-daoists/dao-participation-score

Prize is $2000 in USDC. There can be at most 3 winners, and in cases of multiple winners, the prize money will be split between them.

This bounty is a marketing challenge.

1. Go to DeepDAO, connect your wallet, and customize your profile. In the About section add the following: #deepdaoing_with_yourname. For example, if your name on DeepDAO is
   ""Erica"", your tag would be #deepdaoing_with_erica.

2. We encourage you to add a few meaningful lines about yourself, and your skills and interests. DeepDAO's users are some of the most influential in the ecosystem and it's your opportunity to let them know who you are.

3. Using your network, get more people to complete steps 1 & 2. Each time a new person completes their profile using your referral, get them to add your hashtag to their bio. This must be the same hashtag used in step 1.

On the submission date, we’ll award prizes to the top 3 participants according to these criteria:

1. Who got the most number of people to complete their profiles. Note that you need to have a minimum of 20 referrals to qualify for a prize.

2. Profiles with a higher DAO Participation Score will get bonus points based on their ranking. The top DAO score is ranked 1, 2, 3, etc and so the bonus points formula will be 1/dao_ranking * 0.15. The weight of .01 was chosen so that heavy participants get incentivized, but not so much so that a couple of top voters will become impossible to overcome.

Deliverable: Please submit a list of the people you referred along with wallet addresses and links to their DeepDAO profiles.

Judging criteria: 1. The Number of referrals is counted on our db for the referred profiles. Referrals that do not have your hashtag on their DeepDAO profile will not be counted. 2. The minimum number of referrals required to qualify for a prize is 20. You are free to use any social media platform to promote this task.

$1000 in ETH/USDC/DAI, divided as $500 (first prize), $300 (second prize) & $200 (3rd prize); Marketing position: In addition to the bounty payments, the winners may be considered for a part-time marketing position at DeepDAO. Creative initiatives, like designing and distributing memes encouraging people to customize their profiles and use your tag will definitely attract our attention.

Point of Contact: Aman, aman@deepdao.io, amanwithwings#0165

This bounty is for creating a dApp/frontend to showcase the various kinds of middlewares supported by the CyberConnect protocol.

There are two types of middlewares: 1. CollectMiddleware 2. SubscribeMiddleware. They are smart contracts with logic executed before and after collect and subscribe happens.

The intention is to clarify the concept of middleware to users/developers and easily have them see the various options currently supported and how to use them.

The application should cover all currently supported middlewares (found here).

A webapp/dapp that allows users to sign in with their wallet and 1. Set/Update their ccProfile’s with any of the supported Subscribe middlewares 2. Create essenceNFTs with any of the supported Essence middlewares.

Coverage of all 11 middleware contracts as options — this includes 3 Subscribe middleware & 8 Essence middleware Intuitive and responsive UI/UX for setting middleware on one’s ccProfile and for creating new essences with custom middleware.

Resources: Docs , Guides / Articles

Point of Contact: Nazih Kalo, devrel, unknownuknowns#6454

Create a forum dApp (like reddit) powered by CyberConnect protocol.

Publishing onto the forum should require users to own a ccProfile. All posts should be minted as EssenceNFTs. Every profile should also have its own page with its posts and option to Subscribe/follow/unfollow.

Bounty requirements: A webapp with all the expected functionalities of a forum (post, tree-like comment/reply structure, like/dislike posts, etc). Specific routes/pages should be gated based on ownership of a specific CyberConnect EssenceNFT and/or SubscribeNFT. Posts should be minted as EssenceNFTs.

The type of output expected: Functioning & deployed dApp demo with link. (1) Should be able to sign in with wallet and execute main features requested in the bounty requirements section. (2) Github Repo with README documentation on: (a) Apps main features (b) How to deploy/run dev environment (3) [optional] Any features that are WIP / you didn’t have time to implement

Judging criteria: Main feature of NFT gated forums must be met. UI/UX: A clean and intuitive forum experience (what you’d expect from a Web2 experience) but with added on-chain features supported by CC protocol / API. Bonus Points for adding multiple features from the CC protocol/API (including ability to collect posts as EssenceNFTs, like/dislike posts using CyberConnectSDK V2, follow/unfollow profiles, and whatever else you can come up with!)

Resources: docs.cyberconnect.me, cyberconnect.hashnode.dev

Point of Contact: Nazih Kalo, devrel, unknownuknowns#6454

Create one or more new middleware modules for either SubscribeNFT or EssenceNFT.

Some examples:

NftGatedSubscribeMiddleware: Only allow Subscribe if a user holds an NFT from a specifc contract or set of contracts (e.g., Only Pudgy Penguins, or Milady 9322, 2002, 20)

SharedAccountSmartContract: A smart contract that will hold a ccProfileNFT, which has 2 roles, (1) admin: which can set SubscribeMiddleware, transfer the ccProfileNFT to another address, and add/remove publishers (2) Publishers: only able to create essenceNFTs.

TokenGatedMiddleware: Must Have X Amount of a given token in order to collect/subscribe.

Bounty requirements: - Contract(s) deployed on BNB testnet with the new supported module/middleware For an example see this SubscribePaidMw

Type of output expected: - Link to new deployed contract on tesnet - repository with — 1) contract code (solidity) — 2) instructions on how it works/ how to deploy provided in README — 3) Example use-case for the new middleware contract

Judging criteria: (a) Must meet all requirements in output section (b) Creativity: How original is the middleware contract? Does it introduce new functionality not included in existing middleware contracts? (c) Utility: How useful is this middleware contract? How many different use-cases can it cover?

Resources: docs.cyberconnect.me, cyberconnect.hashnode.dev

Point of Contact: Nazih Kalo, devrel, unknownuknowns#6454

User experience in web3 is currently far from perfect. A few reasons why it needs to be improved:

Complexity: Web3 is still in its early stages, and many of the tools and platforms are not yet user-friendly. The technology is complex, and the learning curve can be steep for new users. This can be a major barrier to adoption and prevent people from fully engaging with the decentralized ecosystem.

Security: Decentralized applications (dApps) in web3 require users to manage their own private keys, which is essential for security but can be intimidating and confusing for many users. If users don't understand how to secure their private keys properly, they risk losing their assets. Improving the user experience for managing private keys can help mitigate this risk, one way is through Lit's decentralized key management solution. Learn more here

Interoperability: Web3 is built on a wide range of protocols and standards, which can make it difficult for dApps to work together seamlessly. This can lead to a fragmented user experience and make it challenging for users to move assets and data between different platforms. Improving interoperability can help create a more cohesive and user-friendly ecosystem.

Improving the user experience in web3 is essential for the long-term success and adoption of decentralized technology. By making it easier and more intuitive for users to engage with the ecosystem, we can help create a more open, transparent, and user-centric internet for everyone.

Some ways that you can utilize Lit in order to create seamless onboarding or governance is through programmatic signing . Lit is the underlying infrastructure where developers can set up programmable signing based on on-chain and off-chain information.

Bounty requirements: Must utilize Lit Actions and Programmable Key Pairs.

Output expected: dApp.

Judging criteria: UI/UX is top priority! Output should include tests, a demo and documentation of how it utilizes Lit.

Resources: https://litprotocol.com/, https://developer.litprotocol.com/, https://developer.litprotocol.com/pkp/wallets/intro, https://developer.litprotocol.com/LitActions/intro

Point of Contact: Debbie (Developer Relations Lead), Discord handle: debie#4240

NFTR is the NFT naming standard on Ethereum. It's also the only NFT-centric identity protocol; meaning the NFT is at the center of everything, instead of the wallet.

NFT names are registered in our registry and can be traded in our name marketplace.

Names are bound to the NFT, so they travel with them if they change wallets. If you think of ENS as names for houses (addresses), NFTR is names for the people inside the houses (NFTs).

Identity starts with naming, but continues with: NFT Profiles, NFT Banking (NFT 2 NFT money transfers), and NFT Messaging.

One of the features we plan to launch on NFTR is what we call NFT Timeline. Timeline can be compared to social media for NFTs. It's a place to see every action the NFT has ever taken on chain in a timeline.

This requires significant developments, starting with indexing every NFT's on chain event.

Events can be generic, such as what Opensea does to index bids, offers, sales and transfers. They can also be generic events that marketplace platforms don't index and show, such as: contract deploy date, mint date (NFT age), NFT enhancements / metadata adjustments.

Or they can be app-specific events like: naming of the NFT, selling of the NFT's name, transfer of the NFT's name, airdrop claims, uses of the NFT as collateral, using the NFT for some utility (ex: birthing a mutant from an Ape with the serum, etc.), staking the NFT for yield (e.g. pixel vault, eulerbeats, etc.)

The task at hand is to build a proof of concept indexer that indexes and displays examples of the events above, and anything else the developer might find interesting.

Should: 1. Output a working event indexer 2. With a simple front-end allowing to select a collection address and token id and see the NFT's lifetime events 3. Include simple documentation

Please see an example of an NFT profile here, and the project's link.

Point of Contact: NFTR Founder, @0xDigitalOil

It means that user’s voting power should not be calculated on the basis of the tokens they hold but by other metrics like badges received upon attending events, Github contributions, participation in Discord / Discourse discussions - possibilities are endless!

The bounty is open ended - it's up to the contributor's creativity to come up with an idea.

Voting strategies requirements and test they need to pass are defined here: https://github.com/snapshot-labs/snapshot-strategies/blob/master/README.md

Assessment will be based on: (a) Originality of the idea. (b) Relevancy - are there spaces that might want to use the strategy, are there users whose voting power will be affected by the strategy? (c) Code style and functionality - the code shouldn’t require many reviews to be merged into the main repository.

Resources: Learn about what voting strategies are, Create a new voting strategy , Existing strategies on Snapshot .

Point of Contact: Zuz, DevRel at Snapshot, zuz#9791

You can find an existing dashboard here

The existing dashboard has been a valuable resource for users, but we believe that there is room for additional innovation and insights.

The goal of this hackathon is to create a new data dashboard that provides a deep dive into the DAO ecosystem.

We're open to a wide range of topics, but some potential areas of focus could include: Analyzing voting patterns and trends in specific DAOs. Examining the performance of specific protocols over time. Evaluating the effectiveness of specific voting and validation strategies. Analyzing the impact of whales on the voting process.

Snapshot data on Dune

In order to query Snapshot data, you can use the snapshot.proposals, snapshot.votes and snapshot.spaces tables. You can find them by creating a new query, selecting the v2 Dune SQL and typing "snapshot" into the searchbar.

Assessment will be based on: (a) Selected research area - does the dashboard provide new information and goes into areas that were not analyzed on the existing dashboard? (b) Data correctness - are queries providing correct results? (c) Presentation - is the dashboard easily to follow and does it provide results in a visual way?

Resources: You can find an existing dashboard here. You can also explore our data via the GraphQL API here . Dune documentation .

Point of Contact: Zuz, DevRel at Snapshot, zuz#9791

Create a plugin which enhances the voting process for Snapshot users.

Voting is a critical aspect of governance, and we want to make sure that users have the best possible experience when making decisions.

However, we understand that users don't always have the time to read long proposal descriptions or participate in Discourse discussions around proposals. Additionally, users may not be aware of the potential consequences of their votes and it might be difficult for them to find the opinions of the most active members of the DAO communities.

That's why we're looking for innovative solutions that will help users make informed decisions without spending a lot of time on research. We recommend that participants consider incorporating AI technology into their projects, but it's not a requirement.

Assessment will be based on: (a) JS Framework: Vue.js (b) Creativity - the bounty is an open ended project and is flexible in terms of dependencies and used APIs, we will assess the creativity of the idea and technical implementation. (c) User experience - will users benefit from the new plugin? Is it easy to use and fits into the current UI? (d) Code style and functionality - the code shouldn’t require many reviews to be merged into the main repository.

Resources: Learn about what plugins are here. Create a new plugin here. Existing plugins on Snapshot here

Point of Contact: Zuz, DevRel at Snapshot, zuz#9791

This challenge is to build or extend useful and composable components for developers, powered by the Mailchain SDK, for native-communication features in web3 DAO tooling or platforms.

Components should be built as functional components supporting real-world use cases and incorporate the Mailchain SDK. Other developers should be able to easily integrate these components into their applications.

Examples include: notification configuration and handling for DAO events, a module to directly compose and send mail to member(s), a delegate-to-delegatee governance update component. We welcome any innovative ideas for useful communication components in web3 DAO tooling or platforms.

Submission Requirements: 1. Include a summary (text description) of your component, its features, functionality, and the intended use case(s). 2. Must incorporate the Mailchain SDK for sending messages to web3 identities or blockchain addresses. 3. Provide a link to a GitHub, GitPod, or similar repo for your component code. The repository must include all relevant Project code and a README with getting started instructions. 4. Must be open source, licensed under any recognised open source license, e.g. MIT, Apache 2.0 or GPL-2.0, etc. 5. Must be the original work of the submitter and not violate the IP rights of any other person or entity.

Multiple Submissions: An entrant may submit more than one submission, however, each submission must be unique and substantially different from each of the entrant’s other Submissions.

Optional (but very welcome): brief feedback on how you found working with the Mailchain SDK.

All valid submissions that meet the challenge description and submission requirements will be evaluated based on the following equally weighed criteria: (a) Use Case: Validity and relevance of the component’s communication use case (e.g. How critical is the problem being solved?). (b) Technical Implementation: The difficulty of the problem being solved and the design and implementation of the component (e.g. Is it built in an efficient, secure manner?). (c) User Experience: The ease of use for developers who want to integrate the component (e.g. How well structured is the code and is it easy to use?). (d) Originality: Innovative use of the Mailchain SDK (e.g. Has this project been done before?).

Resources: Mailchain Developer Docs, Mailchain for ENS, Mailchain for Lens, Mailchain Hack Pack

Bounty Prize Pool: $1500 USDC: 1st Prize: $900 USDC / 2nd Prize: $400 USDC / 3rd Prize: $200 USDC

Anyone is welcome to reach out to the Mailchain team via Discord to discuss any projects or components for early feedback, brainstorming or development help. Join our Discord - CEO, tim_#8472; CTO, Rob_#3642; Partnerships, mdv66#2926

This challenge is to build or extend DAO tools or platforms to include web3 communication features using the Mailchain SDK.

The communication features should support real-world uses cases for communicating with DAO members using their web3 identities (e.g. ENS or Lens) or EVM addresses.

For example, extending a DAO CRM system to include direct-to-member mail, integrating notifications for different calls-to-action, or building a web3-native invoice system for DAO treasury management tools. We welcome any innovative ideas for useful communication features in web3 DAO tooling or platforms.

Submission Requirements: 1. Include a summary (text description) of your Project, the web3 communication features, functionality, and the intended use case(s). 2. Must incorporate the Mailchain SDK for sending messages to web3 identities or blockchain addresses. 3. Provide a link to the Project application or platform. 4. Provide a link to a GitHub, GitPod, or similar repo for your Project code. The repository must include all relevant Project code. 5. Must be open source, licensed under any recognised open source license, e.g. MIT, Apache 2.0 or GPL-2.0, etc. 6. Must be the original work of the submitter and not violate the IP rights of any other person or entity.

Optional (but very welcome): brief feedback on how you found working with the Mailchain SDK.

All valid submissions that meet the challenge description and submission requirements will be evaluated based on the following equally weighed criteria: (a) Use Case: Validity and relevance of the web3 communication use case (e.g. How critical is the problem being solved?). (b) Technical Implementation: The difficulty of the problem being solved and the design and implementation of the communication feature (e.g. Is it built in an efficient, secure manner?). (c) User Experience: The ease of use for the users of the tool or platform to send or receive web3 communications (e.g. How well structured is the code and is it easy to use?). (d) Originality: Innovative use of the Mailchain SDK (e.g. Has this project been done before?).

Resources: Mailchain Developer Docs. Mailchain for ENS. Mailchain for Lens. Mailchain Mailto Links. Mailchain Hack Pack.

Bounty Prize Pool: $600 USDC: 1st Prize: $300 USDC / 2nd Prize: $200 USDC / 3rd Prize: $100 USDC

Anyone is welcome to reach out to the Mailchain team via Discord to discuss any projects or components for early feedback, brainstorming or development help. Join our Discord - CEO, tim_#8472; CTO, Rob_#3642; Partnerships, mdv66#2926

This challenge is open to anyone building applications that enable and improve Web3-Native DAO communication and coordination.

The application should support real-world use cases for DAO coordination and must include the option of communicating direct to DAO members’ web3 identities (e.g. ENS or Lens) or EVM addresses using the Mailchain SDK.

For example, a governance proposal manager that sends updates direct to contributors. We welcome any innovative ideas for useful communication and coordination apps and we also love to see the use of other hackathon partners in the tech stack. For example, an application built on ComposeDB with event-driven notifications sent via Mailchain, or an application that uses Lens’ social graph to find new DAO members who can be contacted using their Lens handle via Mailchain.

Submission Requirements: 1. Include a summary (text description) of your Project, the web3 communication features, functionality, and the intended use case(s). 2. Must incorporate the Mailchain SDK for sending messages to web3 identities or blockchain addresses. 3. Provide a link to the Project application or platform. 4. Provide a link to a GitHub, GitPod, or similar repo for your Project code. The repository must include all relevant Project code. 5. Must be open source, licensed under any recognised open source license, e.g. MIT, Apache 2.0 or GPL-2.0, etc. 6. Must be the original work of the submitter and not violate the IP rights of any other person or entity.

Optional (but very welcome): brief feedback on how you found working with the Mailchain SDK.

All valid submissions that meet the challenge description and submission requirements will be evaluated based on the following equally weighed criteria: (a) Use Case: Validity and relevance of the application use case and web3 communication use case (e.g. How critical is the problem being solved?). (b) Technical Implementation: The difficulty of the problem being solved and the design and implementation of the application (e.g. Is it built in an efficient, secure manner?). (c) User Experience: The ease of use for the users of the application to send or receive web3 communications (e.g. How well structured is the code and is it easy to use?). (d) Originality: Innovative use of the Mailchain SDK (e.g. Has this project been done before?).

Resources: Mailchain Developer Docs. Mailchain for ENS. Mailchain for Lens. Mailchain Mailto Links. Mailchain Hack Pack.

Bounty Prize: $600 USDC

Anyone is welcome to reach out to the Mailchain team via Discord to discuss any projects or components for early feedback, brainstorming or development help. Join our Discord - CEO, tim_#8472; CTO, Rob_#3642; Partnerships, mdv66#2926

This challenge is open to anyone who would like to write a developer tutorial with code samples that demonstrates how to use the Mailchain SDK for DAO-specific use cases.

Example Topics: a. How to send multi-sig event notifications direct to multi-sig owners. b. How to use web3 magic links for DAO member whitelists.

We welcome any innovative ideas for useful developer tutorials that cover real-world DAO use cases and include the Mailchain SDK.

Submission Requirements: Must include a description of the problem being solved, the intended use case(s) and what developers are expected to have achieved on completion of the tutorial. Must incorporate the Mailchain SDK for sending messages to web3 identities or blockchain addresses. Provide a link to the unpublished article with working code samples where applicable. Permission for Mailchain to publish the article as a guest post on the Mailchain blog or other social channels, with appropriate attribution to the author.
Must be the original work of the submitter and not violate the IP rights of any other person or entity. Only 1 submission will be accepted per entrant. Must be written for English readership.

Optional (but very welcome): brief feedback on how you found working with the Mailchain SDK.

All valid submissions that meet the challenge description and submission requirements will be evaluated based on the following equally weighed criteria: (a) Use Case: Validity and relevance of the tutorial use case and web3 communication use case (e.g. How critical is the problem being solved?). (b) Technical Implementation: The difficulty of the problem being solved and the design and implementation of the tutorial (e.g. Is it built in an efficient, secure manner?). (c) User Experience: The ease of use for developers to understand and implement the tutorial (e.g. How well structured is the sample code and is the tutorial easy to use?). (d) Originality: Innovative use of the Mailchain SDK (e.g. Has this tutorial been done before?).

Resources: Mailchain Developer Docs. Mailchain for ENS. Mailchain for Lens. Mailchain Mailto Links. Mailchain Hack Pack.

Bounty Prize Pool: $300 USDC: Bounty Prizes: 3x 100 USDC

Anyone is welcome to reach out to the Mailchain team via Discord to discuss any projects or components for early feedback, brainstorming or development help. Join our Discord - CEO, tim_#8472; CTO, Rob_#3642; Partnerships, mdv66#2926

Goal: Enable Gateway credentials in Snapshot voting strategies

Gateway is a protocol for issuing and managing verifiable credentials. Pocket Network plans to use Gateway for the next generation of our proof-of-participation governance model. A key building block for this is enabling Gateway credentials to be weighted in Snapshot strategies. This integration will enable Pocket Network to level up the UX of our governance model and make it easy for any DAO to emulate our approach.

Requirements: The developer will be responsible for:

• Researching and understanding the Gateway API
• Implementing the Gateway API into the Snapshot Voting Module
• Testing and debugging the integration
• Providing documentation on how to use the Snapshot integration

Criteria:

• The user is able to create and modify a Snapshot voting strategy that references Gateway credentials using the Gateway API.
• The user is able to create and modify a Snapshot validation strategy that references Gateway credentials using the Gateway API.
• The above can be done through a UI in the Snapshot settings.
• The UI fetches all of the latest credentials to make it easier for the user to search and add credentials to the strategy. You need to allow admins of the strategy to search and filter by “IssuerID” and then more specifically “DataModel ID”. This will read those credentials that have been issued by that particular organization using that specific Data Model.
• Clear documentation is provided explaining how to use the Snapshot integration. This should include step-by-step instructions on how to access and use the integration, as well as any limitations or restrictions that may apply.
• Tests are provided proving that the integration works as intended.

Resources:

• Gateway Docs
• Snapshot Docs
• Snapshot Voting Strategies

Point of Contact: Sanket Jain — CEO MyGateway — Sanket#8142

Goal: Integrate Gateway credentials with Discourse.

Gateway is a protocol for issuing and managing verifiable credentials. Pocket Network plans to use Gateway for the next generation of our proof-of-participation governance model. Integrating Gateway credentials with Discourse will make credentials a more integral part of a DAO’s social fabric and ultimately drive more engagement.

Requirements:

The main objectives of this integration are as follows:

• Enable linking a wallet on Discourse for users to opt in for credentials
• Allow admins to opt in to credential Discourse Activity
• Create a variety of different types of activity to track and for admins to credential for (more details below)
• Display the credentials on the profile page that have been earned within that forum
• Allow users to opt in to display credentials they have earned from other forums
• Ensure user profile information is properly synced between Gateway's system and Discourse to maintain consistency across platforms.

Criteria:

The winner of the bounty will be the developer who completes the most of the following tasks:

1. Create a UI to allow users to link their wallet onto their Discourse profile (opt in to earn credentials).
2. Ideate and create different activities that can be credentialed. The number should be flexible and there should be a UI to allow admins to configure what the requirements are. Some ideas:
   1. Receive X likes
   2. Post X times
   3. View X posts
   4. Read X days worth of content
   5. Visit the forum daily for X days
   6. Anything that already has a Discourse badge associated to it
3. Create data models (schema structures) on Gateway once the activity you wish to credential is decided. Use the Gateway API docs for guidance on this.
4. Pass the wallet information and claim (using data model) to credential a user once the activity occurs. For example, once a user’s post receives 15 likes, the Gateway API will be triggered to issue a credential to that user.
5. Create a UI to showcase all the credentials a user has earned on their forum profile. Allow them to opt in to showcase credentials from other DAOs as well. Use Gateway’s API to pull all this information.

Resources:

• Gateway Docs
• Discourse Docs
• Discourse Plugins

Point of Contact: Sanket Jain — CEO MyGateway — Sanket#8142

Goal Build token gated videos for DAOs. Livepeer's new token gated video feature has the potential to help DAOs help monetize their content and engage members through access control. This latest release offers token gating for video uploads and streams allowing users to determine who can access video based on what's in their wallet. You can use the feature with LitProtocol, UnlockProtocol, guildxyz, Collab_Land_ or your own custom logic. We'd love to see builders integrate Livepeer's token-gating feature into a frontend media application or tool that's easy for DAO community managers to use in their existing workflow.

Criteria: The winner must successfully integrate with the Livepeer API as part of a functioning and ready to use frontend application or tool.

Resources:

Livepeer Studio Developer Quickstart Guide

Access Control for Token Gated Video Streaming

Awesome Livepeer

1st place: 4000, 2nd place: $2500, 3rd place: 1500, Honorable mentions: $1000 each

About: A common problem faced by DAOs is the lack of participation in DAO governance and voting by the majority of community members. Build a solution (a tool, a dApp, a protocol, etc) that activates DAO participants using gamification strategies.Some ideas to get you started:

1. Create a mobile app that incentivizes DAO members to vote on proposals through rewards and badges. The more proposals they vote on, the more rewards they earn.

2. Develop a DAO-based prediction market platform where users can bet on the outcome of proposals, creating a financial incentive for community members to participate in governance.

3. Create a leaderboard system that publicly displays the top community members who have participated in DAO governance, incentivizing others to increase their own participation and climb the leaderboard.

4. Develop a reputation-based governance system where users' reputation and influence within the DAO is tied to their participation in governance and voting,

5. Design a game-based DAO governance platform where community members can compete in challenges related to proposal voting and governance, earning rewards and points for their achievements.

Requirements: All submissions must be deployed on Mantle testnet A video demo and GitHub repo must be submitted Link to your contract on the Mantle Explorer Output expected A tool A dApp A protocol

Criteria: Overall quality of the submission, including innovation, impact on the web3 ecosystem, and technical feasibility

Resources:

Mantle Docs

Mantle Links

About

Gitcoin's Passport is a great tool for defending applications from bots and sybil attacks, developed and honed over years of protecting Gitcoin's Quadratic Funding rounds. Now that the Scorer API is generally available, this functionality is available for everyone to gate and protect what matters.

Use the new Scorer API to take this bot protection to new frontiers by building a plugin that integrates Passport - Discourse, Discord, Snapshot, etc.

Criteria

Build and publish a plugin to a widely used service in web3 that uses the Passport Scorer API to protect communities on that service Judging will be based on how complete the plugin is and how important the service

Resources

Passport Docs

Quickstart Guide

Scorer API

Awesome Gitcoin Passport

Point of contact Developer Relations Lead at Gitcoin — 0xZakk (zakk@gitcoin.co)

About

Faucets are often drained faster than they can be filled, making it very difficult for developers to get faucet funds to test their smart contracts on testnets. Gitcoin's Passport is a great tool for defending applications from bots and sybil attacks, developed and honed over years of protecting Gitcoin's Quadratic Funding rounds.

Now that the Scorer API is generally available, this functionality is available for everyone to gate and protect what matters. Go and integrate Gitcoin's Passport and the Scorer API into as many developer faucets as you can to protect testnet Eth from bots.

Criteria

Publish and get a PR merged onto testnet faucets Prize will be awarded to the developer who can protect the most number of faucets

Resources

Passport Docs

Quickstart Guide

Scorer API

Awesome Gitcoin Passport

Point of contact Developer Relations Lead at Gitcoin — 0xZakk (zakk@gitcoin.co)

About

Airdrops are often plagued by bot attacks, causing governance tokens to go to bots who drive pump and dumps. Communities launching DAOs want their tokens to go to their members. Gitcoin's Passport is a great tool for defending against bots and sybil attacks, developed and honed over years of protecting Gitcoin's Quadratic Funding rounds.

Now that the Scorer API is generally available, this functionality is available for everyone to gate and protect what matters.Build something (anything) that makes it easy to run an airdrop or token distribution and ensure that the majority of tokens go to real people.

Criteria

Build and publish a plugin to a widely used service in web3 that uses the Passport Scorer API to protect communities on that service Judging will be based on how complete the plugin is and how important the service is Resources

Passport Docs

Quickstart Guide

Scorer API

Awesome Gitcoin Passport

Point of contact Developer Relations Lead at Gitcoin — 0xZakk (zakk@gitcoin.co)

Goal

Create a Metamask snap that enables wallet users to cast votes on Snapshot through the wallet. Voting is a critical aspect of governance, and we want to make sure that users have the best possible experience when making decisions. MetaMask Snap should provide an easy and seamless way for users to connect their wallet and cast their votes on Snapshot proposals. Additionally, the Snap should be compatible with different blockchain networks, allowing users to vote on proposals for different projects. This will enhance the user experience by eliminating the need for users to switch between different wallets or platforms. The snap should also ensure the security of user funds and maintain their privacy.The successful completion of this project will not only benefit Snapshot and Metamask users, but it will also advance the growth of decentralized governance systems.

Criteria

User experience - is the snap self explanatory and easy to use for the end users? Different blockchain networks - is the solution compatible with different networks? Code style and functionality - the code shouldn’t require many reviews to be merged into the main repository.

Resources

Metamask Snaps Snapshot.js documentation Snapshot GraphQL API documentation

Point of contact Zuz - DevRel at Snapshot, zuz#9791

Goal

Integrate Vocdoni voting with the Q DAO structure by maintaining the security of tokens being locked in the Q Vault, while making the versatility of Vocdoni accessible to the community. At its core, Q enables organizations and protocols in Web3 to set human readable rules, enforce non-binary decisions and allows parties to access dispute resolution upon those rules. For the decision making process, DAOs built with the Q GDK natively use token-voting, with tokens being locked in a Vault during the voting period to prevent any token being counted twice for the same vote. Currently any Q token holder can act as an expert in an expert panel dedicated to a special topic. In order to become an expert, a Q token holder needs to be proposed to enter a panel and needs to be voted in by the token holder community[1]. This same voting structure is used for DAOs building with the Q GDK. DAO members can elect experts who then decide on selected subject matter decisions. Expert panel proposals work in a 1-person 1-vote fashion, while Q Token holder proposals are token based. If the DAO Community votes using an ERC-20 token, the tokens count as voting weight, while on expert decisions and for NFT-based DAOs, each member of the respective DAO Expert Panel or each address holding at least one NFT has one vote. Vocdoni is an open-source voting platform that has processed over 350,000 votes from more than 600 institutions. It allows users to choose voting mechanics that fit their needs, like weighted, quadratic, and single and multiple choice votes.

Tasks

View tasks and example voting flow

Requirements

Use the Vocdoni SDK to create, retrieve and fetch information, creating the census and the voting flow. Vocdoni voting shall fit the existing on-chain structure of the Q GDK. Primarily by maintaining the token lock during voting in the DAO Vault for DAO Community votings and using the on-chain status of Expert Panel Membership for Expert votings. Voting should be compatible with an existing voting frontend. If necessary, modifications shall be proposed to make it compatible. Redirecting between multiple frontends is acceptable. No Master keys to change the voting outcome from Vocdoni to logging on-chain. If absolutely required, an Expert Panel within the DAO can be used to serve as oracle between Vocdoni and Q

Output expected

Smart contract (amendments) to start a proposal with a transaction on chain. Smart contract implementation to log the voting result on chain (bonus execute a potential parameter change).

Criteria

Demo should be included. Code should be well documented, usable, and tested. UX/UI is crucial here to make it as “non-dev-friendly” as possible. Bonus points if completely automated transfer of information between Q and Vocdoni (both ways). Using “anyone can call” functions as a trigger is ok. Fully working proof of concept with one specific flow is preferred to multiple voting flows that are not finalized.

Resources

Q-gdk

DAOvault.sol

Vocdoni SDK (please use the latest version of the SDK)

Vocdoni docs

Point of contact

Q DAO Integration Lead: gerrit_b#1929 Vocdoni Product Manager: jpaulet#3269

About

It is very important to resolve issues within a DAO rapidly and privately, which is why DAOs need a light and rapid chat between holders of admin tokens and community tokens. For each DAO, basic members have to create a main chat for all members with tokens of their current DAO and a chat for admins.

Criteria

It should be able to integrate with Aragon DAO It should be a dApp for any test DAO on testnet and should dave 2 admins, and 2 basic members. After a new member gets community tokens, they get to use the special chat, therefore the application should: connect using an ethereum wallet, find community tokens or admin tokens, and allow messaging between members.

Resources

Aragon Github

Point of contact

Danila Yudin, Product Manager - forexel#4093 on Discord

About

Output will be similar to Tilda and Wordpress, wherein owners of crypto businesses who want to present their information using their own personal resources can do so. This would allow Founders to create websites or dashboards in a more corporate style with only a few clicks.

Criteria

It should be able to integrate with Aragon DAO It should be a dApp for any test DAO on testnet and should dave 2 admins, and 2 basic members. After a new member gets community tokens, they get to use the special chat, therefore the application should: connect using an ethereum wallet, create a website with DAO information, and customize the website with color and logo.

Resources

Aragon Github

Point of contact

Danila Yudin, Product Manager - forexel#4093 on Discord

About

For resolving disputes with trustless systems, customers should have a way of getting personal information of the sellers. This system (KYC Service) may contain 3 parts:

⁃ Service for encrypting personal Data

⁃ Service for storing personal Data

⁃ Service for decrypting personal Data ‍ The service should be based on ZK-proof client.

Criteria

It should be able to integrate with Aragon DAO It should be a dApp for any test DAO on testnet and should dave 2 admins, and 2 basic members. After a new member gets community tokens, they get to use the special chat, therefore the application should: connect using an ethereum wallet, have verification processes, encrypt, store, and decrypt personal data.

Resources

Aragon Github

Point of contact

Danila Yudin, Product Manager - forexel#4093 on Discord