A permissionless task coordination and incentivization protocol. A staking based mechanisms powers task coordination through proposition, prioritization, contribution and validation on chain. Incented enables autonomous coordination and equitable rewards.

Incented is a protocol for permissionless task coordination and incentivization. With our staking based proof-of-contribution mechanisms, Incented is powering task propositions, prioritization, execution and validation on chain. It's designed to bring autonomy to community coordination and empower every individual to make an impact while receiving equitable rewards for their contributions.

Introduction

The Incented Protocol introduces a novel approach to coordination of tasks in community-driven organizations. It leverages staking mechanisms to enable a proof-of-contribution system.

The Incented Protocol is designed to empower community-driven organizations and decentralized autonomous organizations (DAOs) by providing a robust coordination and incentive mechanism. Every community possesses its distinct character, objectives, and goals. To enable community members to contribute meaningfully while being rewarded fairly for their efforts, we have developed the Incented Protocol. This protocol incorporates a suite of smart contracts that facilitate task proposal submissions, task prioritization, task contributions tracking, and the validation of contributions.

Terminology

Carrots 🥕 The protocols native token used to power the protocol as well as for reward

Rabbits 🐰 Individuals or teams that are participating in the Incented protocol. Rabbits are simply accounts (wallets or multisigs on the blockchain in web3)

Rabbit-Hole 🐰🕳️ A specific community using the incented protocol

Admin Admins of the Rabbit-Hole. Wallets or multisigs on the blockchain

Staking A core interaction performed with 🥕 to prioritize, submit contributions or validate tasks

Protocol Fee A fee that is required from the users when they interact with the protocol in the form of 🥕. The protocol fee goes to the Carrot-Pot ****(the Community Wallet).

Carrot-Pot The treasury of a community. This is where rewards come from.

Claim-Stake The stake a user needs to put at risk if they want to reserve the right to execute the task (aka Claim the task). Unless otherwise specified by the community, this defaults to the reward amount assigned to a task.

Personas

The below personas interact within Incenteds ecosystem, each playing a unique and vital role. From Proposers, who envision and initiate tasks, to Prioritizers, who guide task significance, and Contributors, the primary executors of tasks, the protocol embodies a collaborative spirit. Validators uphold standards as critical gatekeepers, while Admins and Super Admins orchestrate and oversee the protocol's functionality. This rich tapestry of personas ensures that every aspect of a task, from conception to validation, is effectively managed, reflecting the dynamic interplay of skills and motivations within the Incented community.

Proposer (The Visionary):

• Characteristic: Innovators with a keen sense for community needs, Proposers are the initiators of tasks. They identify gaps or opportunities within the community and articulate them into concrete proposals.
• Motivation: Proposers are driven by the desire to see their vision realized and to contribute meaningfully to the community, with the added incentive of a potential reward share.

Prioritizer (The Influencer):

• Characteristic: Engaged and proactive, Prioritizers have a strong understanding of what the community values. They wield their influence by staking 🥕, shaping the direction of community efforts.
• Motivation: Their goal is to ensure that the most beneficial tasks receive attention and resources, motivated by the opportunity to earn rewards and guide community focus.

Contributor (The Executor):

• Characteristic: Skilled and action-oriented, Contributors are the backbone of task execution. They turn proposals into reality through their skills and dedication.
• Motivation: Contributors are motivated by the challenge of solving real problems, earning the majority of the task rewards, and gaining recognition within the community.

Validator (The Gatekeeper):

• Characteristic: Critical and analytical, Validators ensure the integrity and quality of contributions. They act as gatekeepers, maintaining the protocol's standards.
• Motivation: They are driven by a commitment to quality and the fairness of the process, alongside the chance to earn rewards for their validation efforts.

Admin (The Organizer):

• Characteristic: Admins are the orchestrators who configure and manage the protocol settings for their respective communities. They have a deep understanding of their community's unique needs and dynamics. The admin role can be filled by individuals, groups or even other protocols or multisigs.
• Motivation: Their primary drive is to create an environment that aligns with their community’s goals, ensuring smooth operation and addressing any specific requirements or challenges.

Super Admins (The Overseer):

• Characteristic: Super Admins, typically part of the Incented team, have overarching control and oversight over the protocol.
• Motivation: Super Admins aim to maintain the overall health and integrity of the protocol, ensuring it serves the diverse needs of different communities while adhering to its core principles and values.

Tasks

In the Incented protocol, tasks are the fundamental units of activity, driving the entire system's functionality. Every interaction, decision, and progression within the ecosystem revolves around these tasks. The protocol meticulously defines each task through a set of attributes largely determined by the proposer, with the exception of the deadline, which dynamically adjusts based on community engagement. These attributes encompass aspects like Title, Description, Effort, Reward, and Type, providing a comprehensive framework for task creation and management. As tasks advance through various stages of the lifecycle, they embody the dynamic interplay of community collaboration, embodying the essence of the Incented protocol's innovative approach to decentralized task coordination.

Task Attributes:

Each Task has the following attributes. All but one attribute is user defined by the user that submits a proposal as a New task, with the exception for the deadline, which is calculated automatically.

Title:

• User Defined: YES
• Effective Titles: Titles should be succinct yet descriptive, capturing the core of the task. Use action verbs and specific details. For instance, "Develop Marketing Plan for Q3 Product Launch" is preferable over "Marketing Work".

Description:

• User Defined: YES
• Structured Approach: Follow a template: Begin with objectives, then detail the expected outcomes and necessary background. Example: For a software development task, outline the desired features, user flow, and any integration requirements.

Effort:

• User Defined: YES
• Flexible Estimation: Estimate effort in hours or days. For instance, specify that a task might take '10 hours' or '3 days', offering a more precise and adaptable estimation. This attribute should reflect the best estimate to the best of the proposers knowledge.

Reward:

• User Defined: YES
• Equitable & Fair: When estimating the effort for a task, consider an equitable approach. Reflect critically on the time and resources required to complete the task effectively. An equitable effort estimation not only ensures fairness but also encourages realistic expectations and contributions. Consider the complexity, skill level required, and the potential impact of the task, ensuring the estimated effort aligns fairly with the proposed reward. This thoughtful approach helps maintain a balanced and rewarding environment within the Incented protocol. For more details and an example calculation see the Reward Section.

Type:

• User Defined: YES
• Define a type (or multiple types) the task falls under. For example for the task "Find a location for the EthBerlin Conference," the appropriate types could be: Event Planning, Research Operations and Administrative.
• List of Types with examples:

Task Lifecycle