CIP proposal: DRep Groups, an on-chain register of DRep councils, parties and collectives

Participation10
Last activity1d ago
ADAtainmentDRep1d agoPost #1

Hello everybody,

Many DReps already work together: councils that publish joint reviews, parties with a shared platform, collectives that split the reading of governance actions. Today that membership lives on websites, in Telegram groups and in spreadsheets. A delegator cannot easily check who belongs to which group, and every tool keeps its own list.

I submitted a CIP that records DRep groups on chain: https://github.com/cardano-foundation/CIPs/pull/1318

How it works

  • A group is created with a transaction under metadata label 8416 (registered in CIP-0010, https://github.com/cardano-foundation/CIPs/pull/1317).
  • Its admins are a native script policy, for example 2 of 3 DRep keys. Changes to the group need that policy.
  • A group is either open, so any registered DRep can join, or permissioned, so the admins approve each request.
  • Every member signs their own join and can leave at any time with their own signature only, also from a permissioned group.
  • The group has a profile with name, description, image, charter and an optional website proof.
  • Every rule is defined on chain data alone, so any indexer reaches the same groups and the same verdicts. Test vectors are part of the CIP.
  • Guide, from founding a group to leaving one: https://dreptalk.com/help/drep-groups/

What a group does not do

A group holds no voting power and casts no votes. Members may agree to vote together, and each of them still votes with their own DRep and writes their own rationale. Delegations stay with individual DReps.

Try it

I kept the library separate from DRepTalk on purpose, so wallets, explorers and other governance tools can adopt the format without depending on DRepTalk.

Feedback is very welcome, especially from DReps who already run a council or party and from tool builders. The PR is the best place for comments on the specification, for anything else just reply here.

Cite