Dework User Manual

Dework is a Web 3 native collaboration tool where decentralized autonomous organizations (DAOs) can organize internal and external teams to manage tasks and rewards transparently, and help new members join, aiming to become the Trello and LinkedIn of the Web3 space.

Paradigm researcher Anish Agnihotri stated, “Dework provides Web 3 builders with all the tools and talent needed for DAOs to reach their full potential, creating a decentralized solution for a range of decentralized challenges.”

Potential DAO contributors can choose from a list of DAOs and open bounties using Dework, launched in December. They can also see recommended DAOs by connecting their personal Discord to the Dework platform and answering a few questions, after which they can create a Dework profile, essentially a resume, including wallet information to receive payments.

Bounty programs unleash the power of decentralized work for DAOs. Bounties are tasks and projects shared by DAOs with their contributors and communities to complete. These tasks can range from document translation and meeting notes to building products on Layer 2 chains like Optimism and Polygon.

DAOs are discovering how bounty programs empower current and potential contributors to engage, organize, and complete value-added tasks. While there is no fixed template for an effective bounty program, many DAOs are experimenting with different types of bounties, structures, and platforms.

Types of Bounties

In most bounty programs, there are three broad types of bounties—DAO-created, contributor-driven, and sponsored. Bounty programs can utilize a combination of these three types to achieve their specific goals.
DAO-Created

Some guilds or teams within DAOs create bounties for specific tasks and projects. In this hands-on approach, teams take the time to define the project scope, develop a vision and goals, and screen contributors to determine fit. This may also require DAOs to appoint members to oversee and manage the entire bounty process.

At Raid Guild, client managers manage bounties. They are experienced managers who clarify the project's vision and goals, assess the fit of contributors with the bounty, and create a positive onboarding experience. Aragon uses a similar framework through a one-on-one screening process to evaluate contributor fit with bounties.
Contributor-Driven

Decentralization creates opportunities for contributors to proactively propose projects that may add value to the DAO. Some DAOs, like Bankless and Forefront, offer open bounties for contributors to write proposals around specific areas of interest. Members review and vote to fund specific proposals that meet these open bounty criteria.

For example, Bankless and Forefront generate high-quality content through contributor-driven bounties. They adopt an open content solicitation approach for contributors to write and submit articles. These articles are reviewed and compensated by the members of each DAO.

Contributor-Driven

Hackathons gather talented individuals and teams around large bounties sponsored by Web3 companies and protocols. In many cases, companies concentrate resources to incentivize teams to organize themselves to compete for bounties within a set timeframe. These bounties are a way to attract developers to build on emerging protocols and services.

Gitcoin offers two types of hackathons—open and exclusive. In open hackathons, the Gitcoin event team contacts sponsors to fund the bounties and the event's execution. For exclusive hackathons, Web3 companies reach out to the Gitcoin event team to produce the hackathon. In both cases, Gitcoin develops the hackathon's instructions, bounties, and prizes, promoting them to a network of over 30,000 developers.

Permissioned and Permissionless

The scope, skills, and rewards of bounties vary. Many DAOs have developed different levels of access for specific bounties based on requirements. Some bounties will require explicit approval from the DAO to be completed (permissioned), while others do not require approval (permissionless).
Permissionless

Permissionless bounties create a lower barrier to entry for potential contributors to the DAO. These allow people to express interest by completing small bounties that provide value to the DAO in exchange for compensation. Permissionless bounties do not require prior approval from the DAO and may include routine tasks such as taking meeting notes, translating pages, and completing small Pull Requests.

For example, Juicebox and Aragon use permissionless bounties to complete routine tasks like taking meeting notes and translating pages. DAOhaus also has a permissionless GitHub filled with issues that new contributors can tackle. Permissioned

Permissioned bounties allow DAOs to add a layer of security for bounties with higher complexity and greater compensation. In many cases, these bounties are completed by current DAO members with established records. Token gating is a common technique used to gate permissioned bounties by requiring specific tokens and Discord roles.

Gitcoin's bounty platform leverages permissioning by requiring people to connect their GitHub profiles before viewing bounties posted by companies. This allows companies to verify developers' skills and intentions by reviewing their GitHub before accepting their bounty work, establishing a layer of trust.

Components of a Good Bounty Post

A good bounty post sets up potential contributors for success. It succinctly outlines expectations, deliverables, deadlines, and compensation. Many posts are optimized for readability and share all relevant information and resources needed to complete the task. 1Hive's bug bounty program is a great example.
Overview

The beginning of the post should provide a high-level overview of the bounty. The 1Hive Bug Bounty post succinctly introduces the bounty program, including scope, evaluation process, compensation structure, and the wallet where funds are held.

Tasks/Requirements

The next section outlines the specific tasks or requirements needed to complete the bounty. This should make it easier for potential contributors to complete and submit the bounty. 1Hive uses bullet points to build its requirements area for easy navigation and outlines its expectations.

Compensation

Every bounty should have compensation. Many DAOs use Web2 market rates to determine bounty compensation. 1Hive provides a detailed compensation structure based on the CVSS risk rating scale, along with scoring examples from previous bug bounties. This transparency helps potential contributors determine if they are willing to complete the bounty.

Compensation Examples

Providing examples of previously compensated submissions can guide people on formatting and claiming bounties. This can also reduce friction for those wanting to complete their first bounty. 1Hive provides two examples for potential contributors.

Bounty Program Tech Stack

The tools used for bounty programs in DAOs are still in their early and developing stages. While there is no specific tech stack, DAOs utilize several common platforms. These include Discord, Notion, Dework, and GitHub. In addition to these platforms, Gitcoin has created its own bounty platform for developers, and Bankless has developed its own internal platform to share with the broader Web3 community in the future.

Discord

Discord is essentially the communication platform for DAOs. Discord can serve as a hub for bounty communications. This may include sharing new bounties, team organization, submitting content, and token gating for permissioned bounties.

In the DAOhaus Discord, those who select the "Contributor" role unlock a specific channel dedicated to potential and current contributors. This channel allows people to communicate with members, ask questions about specific permissionless bounties, and share completed bounties.

Notion

Notion is a project management and note-taking software that DAOs can use to manage bounty programs. Notion allows DAOs to publish, track, and share open bounties. Clarity and Charmverse are two Web3 solutions that use an interface similar to Notion, with features like wallet connections, token gating, and bounty payments.

Forefront is an example of a DAO using Notion for open community bounties. The page shares permissionless bounties that anyone can tackle and submit via a form for compensation in FF tokens.
Dework

Dework is a Web3 native project management platform with token payments, certifications, and bounties. The platform specifically addresses bounty program management issues and can easily manage the entire workflow from start to finish.

Many DAOs have begun experimenting with Dework when launching bounty programs. BanklessDAO Marketing Guild and Aragon Network DAO are examples of DAOs testing Dework for both technical and non-technical bounties.
GitHub

GitHub is a code hosting platform for version control and collaboration. GitHub is a way for developer-focused DAOs to manage bounty programs, review and accept fixes, and share necessary documentation.
Gitcoin

Gitcoin is a platform where developers are rewarded for working on open-source software in Python, Rust, Ruby, JavaScript, Solidity, HTML, CSS, Design, and more. Gitcoin is designed for organizations to post developer rewards on its platform. Gitcoin requires developers to connect their GitHub profiles to allow organizations to review developers before using or accepting bounty submissions.

Building a Bounty Program

Bounty programs are a powerful tool that allows contributors to apply their skills to create value for the DAO. Building an effective bounty program requires careful consideration of the types of bounties, processes, and platforms that bring the most value to the DAO. While there is no one-size-fits-all bounty program, many DAOs can benefit from planning and implementing bounty programs.

Ecosystem Need: Is there a need?

Currently, many blockchain projects primarily rely on Twitter and Discord as project carriers; while centralized platforms are convenient, they ultimately feel un-Web3. How to reward participants has also become a significant issue. In the Web3 world, participants and builders come from all over the globe, and a decentralized ecosystem needs a blockchain-native application that integrates task publishing, management, and rewards. Dework attempts to recreate the usability of Web2 software in a Web3 form, combining mature Web2 software with the functionalities needed in Web3 to become an easy-to-use tool.

Advantages:

Self-publishing tasks, self-checkout: supports a wide range of public chains and tokens.
Compatible with GitHub, Notion, and Discord, allowing users to browse task summaries and directly jump to third-party platforms for more information.
Provides a wealth of information; a task bar can offer all the information users need.
From the admin side of task publishing to the user side of applying for and claiming tasks, both workflows are complete.

The DeWork team is currently small, and the entire platform is still under construction, making the current level of completion quite challenging.

Disadvantages:

Some function key settings are strange and do not align with user habits; for example, the commonly used "favorite function" is placed in an inconspicuous bottom right corner.
The current interface is quite monotonous, with a lot of text, which can lead to visual fatigue for users.
Lacks some core functionalities; for instance, the absence of a search function makes it quite time-consuming and labor-intensive to find specific tasks among numerous DAOs and bounties.
The navigation logic between user interfaces requires new users to learn and adapt, with many steps to complete a task, often leading to getting lost on the way to a certain page.

Overall, Dework's user experience is somewhat rigid; the entire platform's information architecture centers around tasks and information, compromising user browsing experience and operational convenience for functionality. However, this is not an impossible trade-off; how to present information hierarchies and enhance user experience will make Dework more popular.

Community, Development, and Team

The Dework community is harmonious with many constructive discussions; there are resident individuals on Discord to answer questions.

Lonis Hamaili is the founder of Dework, having graduated from Stockholm University in Sweden, with many years of experience in business operations and research.

Dework's official Twitter frequently publishes updates about the platform, and Lonis himself often shares insights and reflections on Web3 on his personal Twitter.

How to Create Tasks#

Note: Tasks can only be created by those with Manage Space or Create Tasks permissions for that space/project.

Checklist View: Click the + button next to the status name.

Then, you will see a pop-up window that provides options for customizing tasks and details about the content that participants need to generate to execute the task.

This is what a useful bounty looks like in Dework, clear at a glance compared to a simple task.

Setting the Task as a Bounty
Basic Task Input
It is advisable to include useful details in the task to help participants understand the expected content. You can accomplish this with the following simple elements of the task:
Job Title: An action-oriented statement that briefly outlines the expected outcome.
Usage Permissions: Set how participants can engage; for more details, see

Skills: Add these so that participants can

Due Date: Click ... then Set due date to set a deadline for the bounty.
Project Name: A Markdown-supported input area for adding all relevant details to help contributors achieve good results. Image and file drag-and-drop are also supported.
Priority: Indicate the urgency of the task by setting it from the options list.
Task Points: It is helpful to use task points as a measure of the workload required to complete this task; this is also helpful if you are pre-token and want to easily measure contributions.
Tags: Create your own tags to help participants quickly identify what type of task it is; this is also helpful when filtering tasks later.

Adding Task Rewards
Step One: To convert the task into a bounty so that participants can easily discover the rewards for completing the work, click Add Bounty.

Step Two: You will then see a pop-up window to customize your bounty type.

Step Three: Choose:

Set Amount: Define the tokens and amount you wish to pay.

Open to Bids: Allow contributors to bid the amount of reward they hope to receive for completing the bounty using the tokens you set.

Note: For more information, please visit

Managing Payments#

Utilize various options to pay rewards on Dework.
You can use any of the supported methods to make payments on Dework:

Currently, you can make two types of payments on Dework. Access the page link you are interested in using in your organization:

Note: The following steps must be executed to connect the wallet to the correct account and network.
Step One: The responsibility must be marked as Done to pay the reward. Then click Pay on the bounty card.

Step Two: If you have not set a payment method, the system will prompt you to set one (otherwise, skip to step seven). Then click Setup Payment, followed by Add Payment Method (see next page).

Batch Payments#

Streamline your contributor payments or simply save on transaction fees.
Overview
In each space on Dework, you have the ability to make batch payments for bounty rewards. This allows you to queue payments for multiple tasks, rewards, competitions, compensations, etc., and pay for all tasks in that space at once.

Important Information: Currently, you can only use Gnosis Safe for batch payments; this is not possible for MetaMask/Phantom/Hiro wallets.

Advantages
Do not pay each transaction separately; save time.
If using a network like Ethereum, save on transaction fees.
You can pay multiple approved competition submissions simultaneously or in batches.
Set up payment schedules to reduce the headache of organizing Gnosis safe signers.

Setup
Important Information: These steps must be completed by signers of the Gnosis Safe, and their MetaMask must be connected to the correct account and network.
Step One: Queue the tasks you want to pay within the space.