CIPs
Canton Improvement Proposals. Lookup, status, votes, citations, dependency chains, governance comparisons, on-chain DSO governance votes.
Canton Improvement Proposals. Lookup, status, votes, citations, dependency chains, governance comparisons, on-chain DSO governance votes.
14 tools in this group.
compare_governance_outcomes
Aggregate governance throughput over a window: CIPs that changed status (approved / rejected / advanced), counts of cip-vote and cip-discuss mailing activity, and dev-fund proposals merged or closed. Canton-specific. Use to summarise "what governance has shipped this quarter?".
curl -X POST https://ccpedia.xyz/mcp \
-H 'content-type: application/json' \
-H 'accept: application/json, text/event-stream' \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"compare_governance_outcomes","arguments":{}}}'detect_cip_dependency_chain
Walk the CIP requires: graph from a starting CIP or PR draft. Returns the full chain of prerequisites that must reach Final before the starting proposal becomes implementable, with each prerequisite's current status. Accepts both approved CIPs ("CIP-0112", "0112") and dev-fund PR drafts ("PR-203"). Canton governance only. Use when planning around a CIP that hasn't shipped yet.
curl -X POST https://ccpedia.xyz/mcp \
-H 'content-type: application/json' \
-H 'accept: application/json, text/event-stream' \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"detect_cip_dependency_chain","arguments":{}}}'get_cip
Fetch the full markdown body of a single Canton Improvement Proposal (CIP) by its ID (e.g. "CIP-0042", "0042", "PR-0117"). Use when you already know which CIP and need its complete text. title, status, author, and full content. For browsing or filtering multiple CIPs use list_cips; for status timeline use get_cip_history. Canton/Daml/Splice ecosystem only. not Cardano or other 'CIP' schemes.
curl -X POST https://ccpedia.xyz/mcp \
-H 'content-type: application/json' \
-H 'accept: application/json, text/event-stream' \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"get_cip","arguments":{}}}'get_cip_attachments
List file/PDF attachments linked to a single Canton Improvement Proposal (CIP). supporting docs and signed-vote-record PDFs, with filenames and URLs. Use to find downloadable artifacts for a CIP. For the parsed who-voted-how breakdown use get_cip_votes; for the proposal text use get_cip. Canton ecosystem only. not Cardano or other 'CIP' schemes.
curl -X POST https://ccpedia.xyz/mcp \
-H 'content-type: application/json' \
-H 'accept: application/json, text/event-stream' \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"get_cip_attachments","arguments":{}}}'get_cip_citations
Comprehensive citation graph for a Canton Improvement Proposal (CIP). every place across CCPEDIA's corpus that references CIP-N. Returns per-source counts AND samples for: sibling CIPs (declared requires: or content-mentions), individual forum posts (not just topic count), individual mailing-list messages (cip-vote / cip-discuss / grants-discuss / validator-announce), GitHub items (issues + PRs + dev-fund proposals across all indexed Canton repos), blog posts (third-party coverage), and YouTube videos (transcript matches). CCPEDIA-unique: joins through our parsed mailing_messages.cip_id column give per-message granularity no other source has. Use when an agent needs 'who is referencing CIP-X and where' / impact analysis. For the proposal's own text use get_cip, for its votes use get_cip_votes, for the legacy aggregated counts use get_cip_mentions. Canton/Daml/Splice ecosystem only.
curl -X POST https://ccpedia.xyz/mcp \
-H 'content-type: application/json' \
-H 'accept: application/json, text/event-stream' \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"get_cip_citations","arguments":{}}}'get_cip_history
Get the status-transition timeline of a single Canton Improvement Proposal (CIP). each dated from->to change (e.g. Draft->Review->Final). Use for 'how/when did CIP-X move through governance' questions. Returns history only, not the proposal body (get_cip) or vote tallies (get_cip_votes). Canton ecosystem only. not Cardano or other 'CIP' schemes.
curl -X POST https://ccpedia.xyz/mcp \
-H 'content-type: application/json' \
-H 'accept: application/json, text/event-stream' \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"get_cip_history","arguments":{}}}'get_cip_implementation_status
For one CIP, report whether code/grants are tracking the proposal: linked dev-fund PRs, related ecosystem projects, status transitions. Canton governance. Use after find_cip_for_feature to gauge readiness.
curl -X POST https://ccpedia.xyz/mcp \
-H 'content-type: application/json' \
-H 'accept: application/json, text/event-stream' \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"get_cip_implementation_status","arguments":{}}}'get_cip_mentions
Find every place that references a given Canton Improvement Proposal (CIP). forum threads, mailing-list posts, blog articles, Dev Fund grant proposals, and sibling CIPs that require/cite it. A reverse-reference (backlink) lookup: use for 'who is discussing CIP-X and where' / impact questions. Not for the proposal's own text (get_cip) or its vote records (get_cip_votes). Canton ecosystem only. not Cardano or other 'CIP' schemes.
curl -X POST https://ccpedia.xyz/mcp \
-H 'content-type: application/json' \
-H 'accept: application/json, text/event-stream' \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"get_cip_mentions","arguments":{}}}'get_cip_vote_outcome
Find out whether a Canton Improvement Proposal (CIP) was actually acted on ON CHAIN, and how. Returns every DSO governance vote request whose text cites this CIP, with outcomes and dates. This answers 'was it decided', which the mailing-list tools cannot: get_cip_votes reads the discussion on the cip-vote list, this reads the ledger. Example: CIP-0116 (Featured App Locking) is cited in dozens of requests that paused apps for non-compliance. Canton ecosystem only, not Cardano or other CIP schemes.
curl -X POST https://ccpedia.xyz/mcp \
-H 'content-type: application/json' \
-H 'accept: application/json, text/event-stream' \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"get_cip_vote_outcome","arguments":{}}}'get_cip_votes
Get the formal vote tally (in-favor / against / abstain, one entry per recorded vote) for a specific Canton Improvement Proposal (CIP), sourced from the Canton cip-vote mailing list. Use for 'who voted how' / approval-trail verification on Governance-type CIPs. Not the attachment PDFs (get_cip_attachments) or status timeline (get_cip_history). Canton ecosystem only. not Cardano or other 'CIP' schemes.
curl -X POST https://ccpedia.xyz/mcp \
-H 'content-type: application/json' \
-H 'accept: application/json, text/event-stream' \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"get_cip_votes","arguments":{}}}'get_governance_vote
Get the full detail of one Canton on-chain DSO governance vote request: the proposed action, the requester's stated reason, every Super Validator's individual vote with their own written reason, who abstained, the outcome and the date it took effect. Use after list_governance_votes when a specific decision matters. Canton ecosystem only.
curl -X POST https://ccpedia.xyz/mcp \
-H 'content-type: application/json' \
-H 'accept: application/json, text/event-stream' \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"get_governance_vote","arguments":{}}}'list_cips
Browse Canton Improvement Proposals (CIPs), optionally filtered by status (Draft/Review/Final/Withdrawn/Rejected/Superseded) and type (e.g. "Standards Track"). Returns a metadata list (id, title, status, type, author). not full text. Use to discover or enumerate CIPs when you don't have a specific ID; use get_cip to read one. Canton/Daml/Splice governance only. not Cardano or other 'CIP' schemes.
curl -X POST https://ccpedia.xyz/mcp \
-H 'content-type: application/json' \
-H 'accept: application/json, text/event-stream' \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"list_cips","arguments":{}}}'list_governance_votes
List Canton Network on-chain DSO governance vote requests and their outcomes, from the ledger itself. Covers Featured App rights being granted or revoked, Super Validator reward-weight changes, SV offboarding, and AmuletRules/DsoRules config changes. CCPEDIA-unique: no other public source exposes this joined to the CIP corpus. Use for 'what has the DSO decided recently', 'which apps got Featured App status', 'what got rejected'. For one CIP's fate use get_cip_vote_outcome; for one Super Validator's record use list_votes_by_sv. Canton ecosystem only.
curl -X POST https://ccpedia.xyz/mcp \
-H 'content-type: application/json' \
-H 'accept: application/json, text/event-stream' \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"list_governance_votes","arguments":{}}}'list_votes_by_sv
Get the on-chain voting record of Canton Super Validators: how many DSO governance votes each has cast, how often they voted for or against, how often they abstained, and the span of their participation. Use for 'how does Tradeweb vote', 'which SVs abstain most', 'who is most active in governance'. CCPEDIA-unique: derived from the full ledger vote history. Canton ecosystem only.
curl -X POST https://ccpedia.xyz/mcp \
-H 'content-type: application/json' \
-H 'accept: application/json, text/event-stream' \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"list_votes_by_sv","arguments":{}}}'