Skip to content

LimitBreak Registry Governance Specification

Organisational Structure & Context

Vision & Mission

To provide an open, decentralized, and secure governance structure for managing creator token registries (whitelists and blacklists) using the Powers protocol. This ensures that creators and collectors (Members) have a voice in maintaining the integrity of the ecosystem while empowering elected Executives to manage day-to-day operations efficiently.

Treasury Management

The organization may control a treasury, but its primary asset is the control over the LimitBreak CreatorTokenTransferValidator lists.

Roles

Role IdRole nameSelection criteria
0AdminInitial deployer. Restricted powers.
1MemberHolders of the ERC-721C token collection.
2ExecutiveElected by Members through a formal election cycle.
PublicEveryone.

On-chain Mandates

Membership Mandates

RoleName & DescriptionBase contractUser InputExecutable OutputConditions
PublicJoin Membership
Assigns Member role if caller holds ERC-721C token.
ERC721_GatedAccessNonePowers.assignRole(MEMBER)Balance check > 0.

Electoral Mandates (assigning Executive role)

RoleName & DescriptionBase contractUser InputExecutable OutputConditions
MemberNominate Self
Add self to candidate list.
ElectionList_Nominatebool nominateCall to ElectionList.nominateNone.
MemberStart Election
Initiates an election cycle.
ElectionList_CreateVoteMandateTitle, Start, EndPowers.adoptMandate(VoteMandate)None (or rate limited).
MemberCast Vote
Vote for candidates.
ElectionList_Vote (Temporary)bool[] choicesCall to ElectionList.voteDuring election period only.
PublicTally Votes
Count votes and assign roles.
ElectionList_TallyTitle, Start, EndPowers.assignRole(EXECUTIVE)Election period ended.
PublicCleanup Election
Remove temporary vote mandate.
ElectionList_CleanUpVoteMandateTitle, Start, EndPowers.revokeMandate(VoteMandate)Tally completed.

Executive Mandates (Registry Management)

Note: The following pattern repeats for Remove Blacklist, Add Whitelist, and Remove Whitelist.

RoleName & DescriptionBase contractUser InputExecutable OutputConditions
ExecutivePropose Add Blacklist
Initiates a proposal to blacklist an account.
StatementOfIntentaddress[] accountsNone (Signal)Voting Period: 5 days.
Quorum: 1 (Executive).
MemberVeto Add Blacklist
Vetoes an active proposal.
StatementOfIntentaddress[] accountsNone (Signal)Voting Period: 3 days.
Quorum: 10%.
ExecutiveExecute Add Blacklist
Executes the blacklist addition if not vetoed.
BespokeAction_Simpleaddress[] accountsCall to Registry.addAccountsToBlacklistNeed Fulfilled: Proposal.
Need Not Fulfilled: Veto.

Constitutional Mandates (Reform)

RoleName & DescriptionBase contractUser InputExecutable OutputConditions
MemberConstitutional Reform
Adopt new mandates.
Mandates_AdoptMandateInitDataPowers.adoptMandateVoting Period: 14 days.
Quorum: 20%.
Succeed At: 66%.

Description of Governance

The governance system uses an Optimistic Execution with Veto model for daily operations, and a Direct Democracy model for elections and constitutional changes.

  1. Optimistic Execution: Executives can propose changes to the registry. These proposals have a delay (e.g., 5 days). If Members do not explicitly veto the proposal within a shorter window (e.g., 3 days), the Executive can execute the change. This balances efficiency with safety.
  2. Veto Power: Members hold the ultimate check on power. A successful veto (requiring 10% quorum) blocks the Executive's action.
  3. Elections: Executives serve at the pleasure of the Members and are elected through a transparent on-chain process.
  4. Reform: The constitution (set of mandates) can only be changed by a supermajority of Members.