← CIP-0044 · votes
VOTES / CIP-0044
Add Elliptic as a Tier4 SV · current status: Final · type: Governance
Vote record for CIP-0044, sourced from the Canton cip-vote mailing list (recent CIPs) and vote-tally PDFs attached to the CIP repo (older CIPs).
13 votes recorded● for 12● against 0● abstain 0● unclear 1range 2025-02-07 → 2025-02-13MCP: get_cip_votes
On-chain outcome · 6
Super Validators executed 6 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-02-25 · Update SV reward weight (Global-Synchronizer-Foundation) · Rejected 1 for / 9 against
Tally
in favor · 12 against · 0 abstain · 0 unclear · 1
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 · 13
- in favor
- in favor
- in favor
- in favor
- in favor
- in favor
- in favor
- in favor
- in favor
- in favor
- position unclear
- in favor
- in favor
For AI agents
Same data through MCP:
get_cip_votes({cip_id: "0044"})— 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/0044/mentions— aggregated backlinks (includes mailing-thread references).