Cowrie Research

common-primary-sources-2026-05-10

5 min read

Common primary sources

Collected: 2026-05-10 UTC

Primary sources reviewed

Selected excerpts and notes

1) Docs landing page

Source: https://docs.common.xyz/commonwealth

Selected excerpts:

Common is the coordination layer for communities, contributors, and AI agents.

It is an all-in-one product and protocol to launch a token, manage a DAO, or coordinate with agents.

Common was ideated and released by Commonwealth Labs. The core team at Common is actively working to decentralize the protocol for the community to manage.

Notes:

  • This page is the cleanest statement that Common sees itself as both product and protocol.
  • It also makes the present operator explicit: Commonwealth Labs remains central today even while decentralization is part of the roadmap.

2) Protocol overview

Source: https://docs.common.xyz/commonwealth/protocol/protocol-overview-introduction

Selected excerpts:

Common Protocol is built around the concept of tokenized attention for actions, ideas, and more.

Namespace … is built on ERC1155 tokens that represent community memberships, roles, and permissions.

The Contests system allows communities to run competitions with tokenized rewards.

Launchpad enables communities to launch tokens with built-in liquidity mechanisms.

Notes:

  • This is the key page for understanding that Common is not just forum software.
  • The module split shows where authority can hide: identity / roles, curation contests, referral economics, token launch infrastructure, and hooks.

3) Contests

Source: https://docs.common.xyz/commonwealth/community-overview-1/common-contests

Selected excerpts:

Admins create contests funded by community stake fees or direct ERC20 deposits…

Members submit contest entries as individual threads under contest topics.

The thread with the most upvotes … wins the prize.

Contests utilize modular voting mechanisms.

Notes:

  • Common’s contest primitive is the strongest reason to keep it in the active corpus.
  • It turns forum activity into explicit token-funded competition and contribution curation, which is a different mechanism from simple proposal voting or static forum moderation.

4) Community Coins

Source: https://docs.common.xyz/commonwealth/launch/community-coins

Selected excerpts:

Built on Base, Community Coins turn passive holders into real members.

Bonding Curve Supply: 65%

Treasury Allocation: 15%

Contest Allocation: 7.5%

Voting Mechanism: Weighted

Vote Weight: 100 Tokens = 1 Vote

Quorum: 12.5%

CURVE_MASTER: Can create, update, and manage curves

TRADE_MASTER: Can freeze curves to prevent trading

Notes:

  • This page exposes Common’s most important hidden control surfaces: default tokenomics, baked-in contest loops, and privileged curve-management roles.
  • It shows Common shipping a prefabricated community economy template rather than only a discussion layer.

5) Governance framing

Source: https://docs.common.xyz/commonwealth/community-overview-2/governance/what-is-decentralized-governance

Selected excerpts:

The rules of decentralized organizations are primarily enforced by code, rather than the legal system.

Changes to the governance, require the community to discuss, propose, and vote.

Decentralized governance gives power directly to token holders.

Notes:

  • This page is conceptually simple, but useful because it shows the project’s official idealized governance framing.
  • That framing can then be compared against the more operational control surfaces revealed elsewhere in the docs.

6) Decentralization blog

Source: https://blog.common.xyz/commonwealths-approach-to-decentralization-2/

Selected excerpts:

Basically, we are solving for two things: an amazing product experience and decentralization.

If we don’t decentralize, we’re cognizant that we’ll fall into the same pattern of being a “walled garden”…

As of now, our backend/data is not yet decentralized.

In the short term, we offer an open API (gated by API keys)… later this year, users should be able to run nodes that can host their data.

Notes:

  • This is the most analytically valuable Common source because it names the tension directly: unified UX versus decentralization.
  • It is rare for a project to say so plainly that core backend/data layers remain centralized while decentralization is still in progress.

Why this entry matters

  • Common is a strong comparison class for governance-forum tooling because it blends discussion, identity, token launch, contests, and reward routing into one stack.
  • The main thing to watch is not only whether it has voting contracts, but where practical authority sits across namespaces, hosted clients, data custody, role systems, curve managers, contest defaults, and self-hosting pathways.

Graph View