← CIP-0069 · votes
VOTES / CIP-0069
Add Ledger as an SV of Weight 5 · current status: Final · type: Governance
Vote record for CIP-0069, sourced from the Canton cip-vote mailing list (recent CIPs) and vote-tally PDFs attached to the CIP repo (older CIPs).
6 votes recorded● for 6● against 0● abstain 0range 2025-07-15 → 2025-07-18MCP: get_cip_votes
On-chain outcome · 7
Super Validators executed 7 DSO vote requests whose stated reasoning cites this CIP. This is the ledger record, so it says what was carried out rather than what was discussed.
- 2026-05-30 · Update SV reward weight (Global-Synchronizer-Foundation) · Accepted 13 for / 0 against
- 2026-05-01 · Update SV reward weight (Global-Synchronizer-Foundation) · Accepted 12 for / 1 against
- 2026-04-30 · Update SV reward weight (Global-Synchronizer-Foundation) · Rejected 4 for / 9 against
- 2026-04-30 · Update SV reward weight (Global-Synchronizer-Foundation) · Rejected 0 for / 9 against
- 2026-04-29 · Update SV reward weight (Global-Synchronizer-Foundation) · Rejected 2 for / 9 against
- 2025-12-16 · Create unclaimed activity record (ledger-ledgerops-2) · Accepted 12 for / 0 against
- 2025-10-01 · Update SV reward weight (Global-Synchronizer-Foundation) · Accepted 9 for / 0 against
Tally
in favor · 6 against · 0 abstain · 0
Positions are parsed from each message's body text (most are one-line statements like "Five North in favor"). If parsing was uncertain, the row appears as position unclear below — please flag if you spot a misread.
Individual votes · 6
- in favor
- in favor
- in favor
- in favor
- in favor
- in favor
For AI agents
Same data through MCP:
get_cip_votes({cip_id: "0069"})— formatted markdown of each vote message in chronological order.get_cip_citations— full citation graph (includes the same vote messages plus everything else that references this CIP).get_cip_history— status transitions over time (/governance/timeline).GET /api/v1/cips/0069/mentions— aggregated backlinks (includes mailing-thread references).