Colony

• Name: Colony
• URL: https://docs.colony.io/colonynetwork/
• Category: reputation-mediated organization protocol / onchain work coordination / DAO operating system / treasury and labor management infrastructure
• Summary: Colony is worth cataloging as a protocol for internet organizations, not merely as a DAO app or payroll tool. Its primary materials keep several layers distinct that many later products separate or hide: domain-based budget structure, task-native work management, non-transferable reputation earned from work, a global skill tree, offchain reputation mining rooted in onchain events, and dispute escalation through increasingly broad peer groups. That makes Colony a useful comparison point for Dework, TalentLayer, Coordinape, SourceCred, Hats, and Moloch-style governance systems: it turns work assignment, budget routing, influence, and dispute resolution into one integrated organizational control plane instead of treating them as separate add-ons.
• What it does:
  • Lets organizations create colonies composed of domains, sub-domains, and associated funding pots
  • Represents work through tasks and payments, with explicit task roles for Manager, Evaluator, and Worker
  • Records task specifications, deliverables, due dates, payouts, ratings, and domain / skill associations in or alongside the protocol workflow
  • Awards non-transferable reputation based on onchain work events, internal-token payouts, disputes, and Meta Colony mining activity
  • Maintains a global skill hierarchy across the network while keeping domain structures local to each colony
  • Uses offchain reputation mining with staked CLNY and onchain root-hash submission / challenge cycles to keep global reputation state synchronized
  • Allows disputes and collective decisions to escalate from narrower domains or skills to broader parent groups through reputation-weighted voting
  • Maintains the network through the Meta Colony, which holds special permissions and governs upgrades and shared structures
• Key claims:
  • Colony’s clearest contribution is that it treats the organization itself as protocol state. Domains, pots, tasks, roles, payouts, and reputation are all first-class objects rather than being left to an offchain tool stack.
  • The most reusable mechanism insight is Colony’s separation between domains and skills. Domains are local organizational and budget containers; skills are a global work taxonomy. That makes it easier to ask whether influence should follow where work happened, what kind of work was done, or both.
  • Reputation is not an ERC-20-style transferable asset. The docs emphasize that it is deterministic, non-transferable, and computed from onchain events, with offchain miners competing to submit the correct root hash. That makes influence portable through history, not through trade.
  • Reputation mining is especially important because it turns labor history into a consensus-maintained but mostly offchain state machine. Colony therefore sits between pure onchain governance and offchain workplace software.
  • Colony’s task system is more opinionated than many later coordination tools. Manager / Evaluator / Worker role splits, multi-signature task modifications, commit-reveal ratings, and payout-linked reputation make work acceptance and labor evaluation part of the governance surface.
  • The dispute model is also worth retaining: escalation does not go to a permanent managerial apex, but to progressively larger peer groups defined by domains and skills. That is a useful comparison point for hierarchical org charts, jury systems, and token-holder governance.
  • The durable governance insight is that Colony’s real power sits in domain design, skill taxonomy maintenance, Meta Colony permissions, reputation-mining participation, and task-role assignment. Those layers decide who becomes legible, funded, and influential long before any formal vote result appears.
• Whitepaper: See ../whitepapers/colony-whitepaper.pdf and ../whitepapers/colony-primary-sources-2026-05-12.md.
• Sources:
  • https://colony.io/
  • https://docs.colony.io/colonynetwork/
  • https://docs.colony.io/colonynetwork/tldr/tasks/
  • https://docs.colony.io/next/colonynetwork/tldr/reputation-mining/
  • https://docs.colony.io/next/colonynetwork/tldr/domains-skills/
  • https://colony.io/whitepaper.pdf
  • https://github.com/JoinColony/colonyNetwork

Internal linkages

• Treasury-first DAO baseline that keeps the center of gravity on membership and exit rather than protocol-native labor history: molochdao

• Contribution-legibility descendant that extracts the reward loop without trying to be a full org operating system: sourcecred

• Permission and execution contrast where roles and authority stay more modular than Colony’s task-and-domain structure: aragon

• Last reviewed: 2026-05-24 UTC