Aragon Protocol

Appearance

Plugins ​

The plugins: ready-made functionality a DAO installs. They are governance plugins, they make decisions (propose → vote → execute). Each is its own repo and package built on the common building blocks and installed through the plugin framework, so they share the same proposal shape, membership model, and install lifecycle. Read one closely and the rest read faster.

Token Voting Plugin ​

Token-weighted "one token, one vote" governance:

  • Token Voting Plugin — the plugin overview, proposal lifecycle, and permissions. Start here.
  • Voting power — the token, the snapshot, delegation, and who may propose.
  • Governance tokens — mint a new token, reuse an IVotes token, or wrap an existing ERC-20.

The shared voting model (the Token Voting Plugin builds on it; other voting plugins can reuse it):

  • Majority voting — the support / participation / approval thresholds and pass-fail math.
  • Voting modes — Standard vs Early Execution vs Vote Replacement.

Multisig Plugin ​

Approval by a fixed member set, a proposal passes once minApprovals members approve:

  • Multisig Plugin — the approval model, proposal lifecycle, and permissions. Start here.
  • Membership & eligibility — managing members, the minApprovals invariant, and the two-speed eligibility model.

Admin Plugin ​

Direct execution by a single trusted address, no vote, no window, for bootstrapping and fully-controlled DAOs:

  • Admin Plugin — the zero-width proposal lifecycle, the centralization trade-off, and migrating away.

Staged Proposal Processor (SPP) ​

Meta-governance: orchestrate other plugins into a multi-stage pipeline (e.g. multisig → token vote → admin):

Lock to Vote Plugin ​

Token-weighted voting where power comes from tokens you lock into escrow (custody), not from a balance snapshot:

Where to start ​

New to the framework? Read what a plugin is and how installation works first, then any plugin here.