Cowrie Research

dework

4 min read

Dework

  • Name: Dework
  • URL: https://dework.xyz/
  • Category: web3 work-coordination platform / contributor-discovery and admission layer / grants-and-bounty operations infrastructure
  • Summary: Dework is workflow software with real admission power. What matters is not the board. It is the combination of task gating, role surfacing, application routing, and grant workflow defaults that decides who gets seen, who gets in, and how contributor reputation becomes legible.
  • What it does:
    • Lets crypto-native teams run work openly or privately through tasks, bounties, grants boards, projects, and milestones
    • Supports multiple task-admission modes including manual assignment, open applications, multiple submissions, and direct claiming
    • Exposes a Roles Center where organizations can feature roles, attach application links and compensation, and surface those roles on a global role board
    • Routes applicants either through Dework-native forms or external application flows while still using Dework as the discovery and intake layer
    • Shows bounties and grant opportunities on global discovery surfaces so outside contributors can find work across organizations
    • Adds a beta reputation-staking system where stakers back a contributor’s pool and receive a share of that contributor’s Dework revenue according to a configurable revenue split
  • Key claims:
    • The docs describe Dework as a platform for web3 teams to engage contributors, pay them, and boost their reputation for completed work. That framing matters because Dework is not only project management software; it is also a contributor-legibility and hiring funnel.
    • The task-permissions system is the most analytically important primitive. Managers choose whether work is manually assigned, application-gated, open to multiple submissions, or directly claimable, which means practical authority starts at task admission rather than at payout time.
    • The application-routing docs are especially revealing because Dework can keep the discovery surface while offloading the actual application flow elsewhere. Under “Open to Applications,” teams can use a custom Dework form or redirect contributors to an external form. That makes Dework a routing and visibility layer even when it is not the final system of record.
    • The Roles Center adds another control surface: organizations can feature roles, sync or fetch Discord-linked roles, attach compensation and application links, and surface those roles on a global board. In practice, role configuration and featured placement help determine which contributors become legible and how they enter an org.
    • The grants-workflow docs show Dework positioning itself as more than bounty intake. Teams can source grant applicants through a global board, collect RFP ideas through community suggestions, track approved grants in milestone-based projects, and expose progress publicly for transparency. That makes Dework a credible comparison point for grants operating systems, not only for task boards.
    • Reputation Staking is the most unusual sub-mechanism in the corpus pass. Reputation Credits back a contributor-specific pool, contributors choose a revenue-share percentage, and stakers receive a proportional share of the contributor’s Dework earnings. That turns contributor reputation from a soft profile signal into a quasi-income-sharing market.
    • Dework belongs in the active corpus because it clarifies a distinct control plane inside crypto work coordination: not peer-allocation like Coordinape, not builder scoring like Talent Protocol, and not shared marketplace settlement like TalentLayer, but hosted admission, workflow, and reputation-financialization infrastructure for DAO and grants operations.
  • Whitepaper: No canonical standalone Dework whitepaper surfaced in this pass. The strongest primary materials were the official site plus docs pages on platform framing, task gating, role surfacing, grants workflows, and reputation staking; see ../whitepapers/dework-primary-sources-2026-05-10.md.
  • Sources:

Internal linkages

Control surface

  • Practical authority sits in task-admission settings, role curation, featured listings, and the reputation-staking layer.

  • So treat Dework as hosted contributor-routing infrastructure, not just a DAO-flavored kanban board.

  • Last reviewed: 2026-05-26 UTC

Graph View