← CIP-0009 · citation graph

CITATIONS / CIP-0009

Add Broadridge as a T1 (weight 10) Super Validator · status: Final

Every place across CCPEDIA's corpus that references CIP-0009 — sibling CIPs, forum threads, the cip-* / grants-* mailing lists, GitHub issues + PRs across all indexed Canton repos, third-party blog coverage, and YouTube transcripts. Each section samples the most recent N; counts above the sample are the totals.

4 total referencesSibling CIPs 2Forum posts 0Mailing messages 1GitHub items 1Blog posts 0YouTube videos 0JSONMCP: get_cip_citations

Sibling CIPs · 2

CIPs that declare a requires: dependency on CIP-0009, or reference it in their content.

CIP-0010Final
LCV have met all their requirements to be a T1 Super Validator
mentions →
CIP-0011Final
IEU have decided to forgo SV minting rights
mentions →

Mailing-list messages · 1

Messages on cip-vote, cip-discuss, grants-discuss, and other validator-announce lists. Items with cip_id_match badge come from CCPEDIA-parsed mailing_messages.cip_id — only-here join.

  • CIP TBD: Traffic-Based App Rewards[cip-discuss] · @Yiannis Varelas · 5mo ago

    Simon, thanks for submitting this. This is extremely well thought out and I’ll limit my feedback to the wallet/operator perspective, because this CIP is a massive time saver. As operators of Loop and

GitHub items · 1

Issues, PRs, and dev-fund proposals across all indexed Canton repositories that mention CIP-0009.

For AI agents

Same citation graph through programmatic surfaces:

  • get_cip_citations — MCP tool. Input: {cip_id}. Output: counts plus sample items per source. Use when an agent needs "everything that references CIP-X across CCPEDIA's corpus" in one round-trip.
  • GET /api/v1/cips/0009/citations — JSON shape mirroring this page.
  • The legacy /api/v1/cips/0009/mentions stays for backward compat — it returns topic / thread counts; this new endpoint returns per-post / per-message granularity plus GitHub and YouTube coverage.