POTLOCK Lists is best modeled as reusable account-registry middleware rather than as a small UI feature inside a grants app. The docs explicitly frame lists as Spotify playlists for any account.
The core control surface is owner/admin policy, not open challenge and arbitration. Owners can add/remove admins, transfer ownership, batch add or remove accounts, tune defaults, and update statuses.
The contract’s default_registration_status and admin_only_registrations settings are analytically important because they determine whether a list behaves like an open application surface, a moderated registry, or a tighter owner-run allowlist.
Registration states matter: Pending, Approved, Rejected, Graylisted, and Blacklisted make list membership more expressive than a flat boolean allowlist.
POTLOCK’s newest quadratic-funding pots can enforce list-based criteria, so list maintenance is not just social discovery; it can directly gate who may apply for funding.
The docs’ note that the official public-goods registry lives on list_id = 1 is worth retaining because it shows how a socially canonical list can emerge inside a permissionless list-creation system.
The listed use cases—membership requirements, donation baskets, airdrop waitlists, RetroPGF signals, and list-based explore pages—show that the primitive generalizes beyond one grants UI.
Specific source signals worth retaining
lists-live.md: best concise statement of the product thesis, role model, use cases, and the fact that lists are enforced in the latest pots.
Contract interface section in lists-live.md: strongest source for the exact policy fields and registration-state design.
contracts-overview.md: useful confirmation that Lists is a first-class PotLock contract rather than a frontend-only affordance.
create-list.md, edit-list.md, and apply-to-list.md: good operator-level evidence for how ownership transfer, manual approval, admin addition, and applicant notes work in practice.
Why this entry belongs in the corpus
It gives the corpus a lower-layer public-goods and registry comparison point beneath broader grant stacks such as POTLOCK and clr.fund.
It helps separate curated-list governance from quadratic-funding math: in practice, capital-allocation systems often depend on who curates the eligible set before any matching formula runs.
The durable insight is that a list can be a real governance primitive when it controls discoverability, application rights, and downstream funding admission.