On-chain Votes

The record

570 vote requests spanning 2024-06-29 to 2026-07-28, carrying 6574 individual votes from 15 Super Validators. 515 accepted, 40 rejected, 10 expired, 5 still open. 72 distinct CIPs are cited in the reasoning.

Recent decisions

A revoke action targets the contract id of the right being withdrawn rather than a readable name, so that column is blank for those rows. The full payload is stored per request and reachable through the MCP tool get_governance_vote.

How each Super Validator votes

Abstentions are recorded on the request rather than as a cast vote, so they are counted separately and are not part of the for and against totals. Super Validators that joined recently, or were offboarded, show a shorter active span and a smaller total.

Where this comes from

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 deliberation half lives in the CIPs themselves and on the cip-discuss list, and the two are joined here wherever a vote reason names a CIP.

Super Validators usually link to a mailing-list post when they explain a vote. 512 of 520 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 8 that do not are mostly tokenomics and supervalidator-announce, either posts predating the archive crawl or lists CCPEDIA does not index.

For how proposals moved through their statuses see the CIP governance timeline. 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.

Answered from this data