In an organization of any type, reputation is an essential heuristic for people to keep track of each other's perceived merit in an environment of limited information. Reputation within Colony is meant to stay close to the concept of reputation as it is commonly understood. Reputation is a representation of merit, which in Colony implies an immutable record of contributions to a shared goal.
In the Colony Protocol, reputation is a number that quantifies a particular individual’s influence, calculated from the sum of work that has been completed within the colony.
Every Colony has its own internal token which complements reputation. Tokens, when earned as a task payout, create reputation for the recipient.
The Reputation System in Colony is a tool for governance in a decentralized context: It allows for members of an organization to have different amounts of influence over the organization, without the use of a management hierarchy or frequent voting.
Reputation confers influence in a colony by mediating a member's ability to adjust various aspects of the organization. Whether it is the ability to move funds to fund tasks, to create new domains and skills, or to settle disputes, reputation determines influence by degrees.
It is important to note that in the first deployed version of the Colony Network, reputation will play a more passive role in a colony. Reputation will still determine payouts during the rewards cycle, but influence over domain/skill creation, funding tasks, and other important functions will instead be mediated by a permissioned authority role.
Unlike a token, reputation cannot be transacted between accounts. Reputation can only be gained or lost through interactions with other members of a colony.
The most straightforward way of gaining reputation is by completing tasks within the colony. Tasks funded with internal tokens generate reputation for their recipient upon payout.
The amount of reputation gained or lost through a task is determined by the task's rating:
Unsatisfactory. The work done did not meet the expectations established by the manager. The worker is penalized reputation equal to the internal token payout.
Satisfactory. The work done met the established expectations. Worker is awarded reputation equal to the internal token payout.
Excellent. The work done exceeded the expectations of the manager. Reputation is awarded at 1.5 times the internal token payout.
When a payout is received for the completion of a task, reputation is awarded within the task's domain, as well as all its parent domains. If the task is tagged with a skill, reputation is awarded in the skill, as well as all its parent skills.
See Tasks for more information about the task workflow and ratings.
See the colonyJS task lifecycle for implementation examples.
Almost every interaction with a colony requires that the user stake some amount of reputation. How much reputation is required to stake depends on how important the interaction is. Actions like the creation and funding of tasks require a nominal amount of reputation, while things like creating a new domain require comparatively more.
Staked reputation has the potential to be both lost and gained in the event of an objection or a dispute.
If an objection to any action is raised by another member, the reputation stake is given to the objector (objections pass automatically if they are not challenged).
If an objection is escalated to a dispute, a reputation-weighted vote is called within the objection's domain, in which both sides must stake reputation. The amount of reputation gained/lost by each side is determined by the vote's outcome ('landslide' outcomes punish the losing side harshly, while more contentious decisions have only small penalties for the losing side).
See Objections and Disputes for more information about reputation-weighted voting and the dispute resolution process.
After a colony is created, reputation can only be gained and lost through normal interactions within a colony. But at the colony's beginning, we are presented with a bootstrapping problem: When a colony is new, no-one has yet completed any work in it and so nobody will have earned any reputation.
During a colony's creation, the creator of the colony is granted the ability to designate an initial set of addresses to receive internal tokens and an equivalent amount of reputation. Users receiving reputation are presumably the colony creator and their colleagues, and this starting reputation should be seen as a representation of the existing trust within the team.
One of the unique characteristics of reputation is that it decays over time. This is meant to incentivize frequent and consistent contributions to a colony, and to ensure that reputation represents recent contributions.
Every 600000 blocks, a user’s reputation in every domain or skill decays by a factor of 2. This implies a 'reputation half-life' of about 3.5 months.
Questions? Problems? Existential dilemmas? We’re here to help!
Improve this doc.
All improvements to documentation are welcome and encouraged. Submit a PR for documentation on GitHub.