Skip to content

[Feat]: Short-run governance track and operator management for reservations #205

Closed

Description

@sphamjoli

Component

Other

Priority

P0

Summary

Approvals of pre-launch claims run on a short governance track with a decision period under a day, since a full-length referendum per name does not fit a one-day vetting window. Operators handle day-to-day approve and revoke; OpenGov appoints and removes them and can override. Part of #202.

Proposal

  • Define the short-run track: its origin, decision period, and who may decide. Standing this track up is a governance action, separate from the per-claim approvals that run on it.
  • Operator role: keep multiple holders (today WHITELIST_OPERATOR_ROLE). Their remit changes from minting to approving and revoking reservations in the new contract. OpenGov grants and revokes the role and can revoke any reservation directly.
  • Document how a claim moves from submitted to approved or revoked, and who signs each step.

Acceptance criteria

  • The short-run track is specified: origin, decision period, deciding body.
  • Multiple operators can approve and revoke; OpenGov can appoint, remove and override.
  • The end-to-end approval flow is documented.
  • The split between the operator fast path and OpenGov authority is written down.

Activity

  1. re-gius commented on Aug 12, 2026

    @re-gius
    Collaborator

    Downgraded to P2 and removed because we won't be able to do the necessary runtime changes for this milestone

  2. added
    P1Secondary Priority
    P2Tetiary Priority
    and removed
    P0Highest Priority
    P1Secondary Priority
    on Aug 12, 2026
  3. removed this from the 5 - Release to MainNet milestone on Aug 14, 2026
  4. added
    P0Highest Priority
    and removed
    P2Tetiary Priority
    on Aug 21, 2026
  5. re-gius commented on Aug 21, 2026

    @re-gius
    Collaborator

    Changed again to P0 - we need to do this

  6. re-gius commented on Oct 13, 2026

    @re-gius
    Collaborator

    Closing in favour of #238. The operator role is gone (#272): every whitelist call is now Root-only, so the remaining question is the short governance track. That's tracked in #238 and polkadot-fellows/runtimes#1326, which now notes that the track also needs to handle routine whitelist decisions (accept, reject, grantNames).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions