Summary: Kleros Curate is best understood not as a generic list builder or moderation frontend, but as a reusable challengeable-registry mechanism. Its core move is to let a list creator define an acceptance policy (Primary Document), deposit schedule, challenge window, and arbitration venue, then let open participants submit, challenge, and defend entries under those rules. If no one challenges, an item passes by default; if challenged, the dispute is escalated to Kleros jurors. That makes Kleros Curate analytically useful because it separates several layers that community curation rhetoric often flattens together: authorship of the criteria, parameterization of challenger incentives, court selection, juror-count calibration, and even meta-registry discoverability through Curate’s own List of Lists browser.
What it does:
Lets anyone deploy an open curated registry with its own title, description, acceptance criteria, item schema, and optional badge system
Uses a challenge period for submissions so unchallenged items are accepted by default while contested items move into arbitration
Supports both challenges to new submissions and challenges to removal requests, turning list maintenance into a continuing dispute process rather than a one-time allowlist
Lets list creators tune core registry economics such as submission deposits, removal deposits, challenge deposits, challenge-period duration, initial juror count, and selected Kleros court
Routes disputes to different Kleros courts, so the practical decision-maker depends partly on the creator’s choice of venue and fee calibration
Maintains a browser-level List of Lists registry where lists themselves can be submitted and challenged, making discoverability another governed layer rather than a neutral directory
Key claims:
The official product docs describe Kleros Curate as a decentralized app for creating open curated registries of just about anything using financial incentives plus Kleros dispute resolution, which is the clearest reason to catalog it as reusable registry middleware rather than as one niche list product.
The tutorial makes the Primary Document explicit as the central policy object: it is the acceptance-criteria document jurors use to decide whether an item belongs. That means practical authority begins with whoever authors and updates the criteria, not with the UI alone.
The parameter guide is especially important because it treats registry design as a balance between false positives and false negatives. That is a stronger analytical framing than a generic community moderation pitch: Curate is effectively a human-powered classifier whose precision and recall are shaped by deposits, challenge bounties, court choice, and challenge windows.
Court selection is a real governance surface, not a cosmetic setting. Kleros’s own parameter guide says different courts are calibrated for different skills, effort levels, and arbitration fees, so list designers partly choose who their likely jurors will be.
Challenger incentives are not incidental. The official parameter note explains that deposits should compensate not only jurors but also challengers who spend effort scanning pending entries, and it explicitly discusses the Challenger’s Dilemma where successful filtering changes the economics of future monitoring.
The tutorial’s List of Lists flow shows that registry discoverability is itself challengeable and curated. A list can exist onchain without being surfaced in the main browser until it is separately submitted and accepted there.
Curate belongs in the active corpus because it gives a clean comparison point for recipient registries in public-goods funding, token or creator allowlists, challengeable identity or content registries, and other systems where the real question is who defines admissibility and who is paid to defend it.
Whitepaper: No standalone Kleros Curate whitepaper or litepaper surfaced in this pass. The strongest primary materials were Kleros’s official Curate docs, tutorial, and parameter-design note, with the broader Kleros whitepaper remaining useful background for the underlying arbitration layer; see ../whitepapers/kleros-curate-primary-sources-2026-05-12.md.