Skip to content

← CIP-0011 · citation graph

CITATIONS / CIP-0011

IEU have decided to forgo SV minting rights · status: Final

Every place across CCPEDIA's corpus that references CIP-0011 — 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.

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

Sibling CIPs · 7

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

Forum posts · 1

Individual posts on forum.canton.network that mention CIP-0011. Showing 1 most recent of 1.

  • Hi, is this the right place to ask a CIP-112 v2 design/semantics question? If there is a better venue, happy to move it there. I’m looking for clarification on committed allocations. My current unders

Mailing-list messages · 2

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.

GitHub items · 10

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

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/0011/citations — JSON shape mirroring this page.
  • The legacy /api/v1/cips/0011/mentions stays for backward compat — it returns topic / thread counts; this new endpoint returns per-post / per-message granularity plus GitHub and YouTube coverage.