Governance timeline

How many distinct CIPs have ever passed through each status. A CIP can appear in multiple rows here over its lifetime (e.g. Draft → In Review → Final = 3 statuses).

• Approved79
• Final70
• Proposed28
• Draft28
• Active10
• In Review7
• Withdrawn4
• Replaced4
• Rejected2
• Proposed Amendment1
• Obsolete1

Events where a commit changed a status that was already set, so both sides are known. The rest are a CIP's first appearance in the repository, which has no previous status and so no from_status.

Derived live from cip_status_history on every request. The table is rebuilt every 6 hours by walking the upstream repository's commit history: for each CIP file, the status is read at every commit that touched it, and a row is written wherever it changed. 253 rows cover 140 proposals. Because every date is a commit date, a rebuild reproduces the same rows rather than adding to them. Open pull requests have no history on the main branch, so a draft is dated from when its PR was opened.

Read individual histories via GET /api/v1/cips/:id/history or via the get_cip_history MCP tool. For the citation graph (who else references this CIP), see per-CIP citations.

This page tracks how proposals moved through their statuses. Below is what the Super Validators actually executed on chain, with per-SV votes and effective dates.

665 vote requests spanning 2024-06-29 to 2026-11-20, carrying 7743 individual votes from 15 Super Validators. 604 accepted, 45 rejected, 10 expired, 6 still open. 80 distinct CIPs are cited in the reasoning.

Read from the DSO vote-results endpoint of the public Scan API and stored with the complete original payload per request. This is the execution half of Canton governance; the timeline above is the deliberation half, and the two are joined wherever a vote reason names a CIP.

Super Validators usually link to a mailing-list post when they explain a vote. 603 of 612 of those links resolve to a thread or message held here, so the trail from a decision to its stated reasoning to the primary document stays inside CCPEDIA. The 9 that do not are mostly tokenomics and supervalidator-announce, either posts predating the archive crawl or lists CCPEDIA does not index.

AI tools can query the same record through MCP with list_governance_votes, get_governance_vote, list_votes_by_sv and get_cip_vote_outcome.