Skip to content

← CIP-0105 · citation graph

CITATIONS / CIP-0105

Super Validator (SV) Locking & Long-Term Commitment Framework · status: Active

Every place across CCPEDIA's corpus that references CIP-0105 — sibling CIPs, forum threads, the cip-* / grants-* mailing lists, GitHub issues + PRs across all indexed Canton repos, third-party blog coverage, and YouTube transcripts. Each section samples the most recent N; counts above the sample are the totals.

117 total referencesSibling CIPs 2Forum posts 0Mailing messages 93GitHub items 20Blog posts 2YouTube videos 0JSONMCP: get_cip_citations

Sibling CIPs · 2

CIPs that declare a requires: dependency on CIP-0105, or reference it in their content.

Mailing-list messages · 93 · across 5 threads

Messages on cip-vote, cip-discuss, grants-discuss, and other validator-announce lists. Items with cip_id_match badge come from CCPEDIA-parsed mailing_messages.cip_id — only-here join.

  • CIP-TBD: Add Halborn as a Weight 4 Super Validator[cip-discuss] · @Edgar Cepin · 12d ago

    … roups relevant to its contribution areas, including the Tokenomics Working Group Participate in the CIP-0105 locking framework at the highest tier practical for a Weight 4 SV within 3 months of onboarding Bea …

  • CIP-0105 and CIP-0116: Add automated onchain votes[cip-discuss] · cip_id match · @Wayne Collier · 14d ago

    … mated, and how automated enforcement would work. I'd like to propose the following text be added to CIP-0105 and CIP-0116 to describe automated enforcement: CIP-0105: Automated Onchain Weight Reduction Super …

  • SV Governance CIPs[cip-discuss] · @Heslin Kim · 19d ago

    … uity , rather than from accumulating a large fixed token amount. Under the framework established in CIP-0105, SVs already receive rewards structured such that a significant portion (typically 70%) is locked t …

  • … erm commitment to the Canton ecosystem. CC+ acknowledges and accepts the locking requirements under CIP-0105. Total Addressable Market and Regulatory Context The Corporate Commercial Paper market exceeds $14 …

  • Rewards Locking Module[cip-discuss] · @Luke Farrell · 1mo ago

    … at the Global Synchronizer must provide in order to satisfy the Phase 2 enforcement requirements of CIP-0105 (Super Validator Locking and Long-Term Commitment Framework) and CIP-0116 (Featured App Locking), t …

  • Update SV Reward Weight[supervalidator-announce] · @Amanda Martin · 2mo ago

    May 23 at 12:00 UTC marks 30 days since SV Locking enforcement began under CIP-0105. Elliptic has now provided a locking PartyID showing that it is funded above the 70% threshold requ …

  • Update SV Reward Weight[supervalidator-announce] · @Amanda Martin · 2mo ago

    May 23 at 12:00 UTC marks 30 days since SV Locking enforcement began under CIP-0105. Ledger has now provided a locking PartyID showing that it is funded above the 70% threshold requir …

  • Update SV Reward Weight[supervalidator-announce] · @Amanda Martin · 2mo ago

    May 23 at 12:00 UTC marks 30 days since SV Locking enforcement began under CIP-0105. Tradeweb has now provided a locking PartyID showing that it is funded above the 70% threshold requ …

  • CIP-0105: Super Validator (SV) Staking[cip-discuss] · cip_id match · @James Lang · 2mo ago

    In addition, the ability to transfer locked tokens among custodians, exchanges, and self-custody solutions should be formalized. Locking Canton via a 3rd party vendor should not result in that vendor

  • CIP-0105: Super Validator (SV) Staking[cip-discuss] · cip_id match · @Luke Farrell · 2mo ago

    As a update: the working group for scoping phase2 Splice requirements has included supplier substitution on both actively locked CC + vesting locked CC I want to request if there is any feedback on th

  • CIP-0105: Super Validator (SV) Staking[cip-discuss] · cip_id match · @Luke Farrell · 2mo ago

    Building on Andrew's definitions above, attached (and below) is a document with proposed detailed Supplier Substitution workflows during manual Phase1, for discussion on May 6th (tomorrow) Tokenomics

  • Update SV Reward Weight[supervalidator-announce] · @Amanda Martin · 2mo ago

    Dear Super Validators, Following review under CIP-0105 (SV Locking) and the governance process outlined in CIP-0111, Tokenomics recommends the following S …

  • Tokenomics Outcomes - April 22nd 2026[tokenomics-announce] · @Amanda Martin · 3mo ago

    … : https://ccview.io/sv-locking/ https://lighthouse.cantonloop.com/sv-locking Official Documentation CIP-0105 SV Locking Operational Guidelines CIP Milestone Guidance The Super Validator Accountability Framewo …

  • CIP‑01XX: Process for Reducing Super Validator Weight[cip-discuss] · @Eric Saraniecki · 3mo ago

    … ock the requisite CC to maintain its current weight and thus has its weight reduced as set forth by CIP-0105 (SV Locking). To avoid any doubt, any scenario in which an SV has its weight reduced (partially or …

  • CIP‑01XX: Process for Reducing Super Validator Weight[cip-discuss] · @Kinga Bosse · 3mo ago

    … ock the requisite CC to maintain its current weight and thus has its weight reduced as set forth by CIP-0105 (SV Locking). To avoid any doubt, any scenario in which an SV has its weight reduced (partially or …

  • CIP‑01XX: Process for Reducing Super Validator Weight[cip-discuss] · @Alex Chen · 3mo ago

    … ock the requisite CC to maintain its current weight and thus has its weight reduced as set forth by CIP-0105 (SV Locking). To avoid any doubt, any scenario in which an SV has its weight reduced (partially or …

  • CIP-TBD: Infrasingularity max weight 5 SV - Vitesh Malhotra[cip-discuss] · @Eric Saraniecki · 3mo ago

    … ---------|--------------------------|---------------| | 1. Compliant SV Node Operation & CIP-0045 / CIP-0105 Compliance | As the official Canton NaaS provider, deploy and maintain our own dedicated SV node fr …

  • CIP-0105: Super Validator (SV) Staking[cip-discuss] · cip_id match · @Chris Matturri · 3mo ago

    Thanks Andrew- I think this minor adjustment of a 24 hour window to unlock/ relock CC makes sense. This should help SVs looking at lending facilities to source CC needed to lock- which would be awesom

  • [Updated] CIP 0105: Super Validator (SV) Locking & Long-Term Commitment Framework[cip-vote] · cip_id match · @Amanda Martin · 3mo ago

    We have reached 2/3 approval for this updated timeline. Thanks for your participation.

  • [Updated] CIP 0105: Super Validator (SV) Locking & Long-Term Commitment Framework[cip-vote] · cip_id match · @Veronica Augustsson · 3mo ago

    7RIDGE/C7 votes in favour Veronica V E R O N I C A A U G U S T S S O N / P A R T N E R ​​​​ ​ 7RIDGE IS A PRIVATE MARKETS ASSET MANAGER INVESTED IN TRANSFORMATIVE TECHNOLOGY FOR FINANCIAL SERVICES TO

  • CIP-0105: Super Validator (SV) Staking[cip-discuss] · cip_id match · @Andrew Bryan · 3mo ago

    Hi All, I'd like to make one slight adjustment to my above formal definition of the "lock substitution" mechanism that would allow for immediate unlock of CC. In the above, I incorrectly stated that t

  • CIP-0105: Super Validator (SV) Staking[cip-discuss] · cip_id match · @Wayne Collier · 3mo ago

    Hi, James. During phase 1, if the SV reports both the source wallet and the target wallet are listed as locking wallets, the SV's locked balance wouldn't change when they moved funds from one custodia

  • [Updated] CIP 0105: Super Validator (SV) Locking & Long-Term Commitment Framework[cip-vote] · cip_id match · @Chris Zuehlke · 3mo ago

    Cumberland DRW votes in favor. Thanks Chris toggle quoted message Show quoted text

  • MPCH is in favor Get Outlook for iOS toggle quoted message Show quoted text

  • [Updated] CIP 0105: Super Validator (SV) Locking & Long-Term Commitment Framework[cip-vote] · cip_id match · @Luca Toscani · 3mo ago

    Orb 1 votes in favor Luca Toscani (650) 283-3681 toggle quoted message Show quoted text

GitHub items · 20

Issues, PRs, and dev-fund proposals across all indexed Canton repositories that mention CIP-0105.

Blog posts · 2

Third-party coverage and ecosystem blog posts. Each links to the original publisher; CCPEDIA only indexes, doesn't republish.

For AI agents

Same citation graph through programmatic surfaces:

  • get_cip_citations — MCP tool. Input: {cip_id}. Output: counts plus sample items per source. Use when an agent needs "everything that references CIP-X across CCPEDIA's corpus" in one round-trip.
  • GET /api/v1/cips/0105/citations — JSON shape mirroring this page.
  • The legacy /api/v1/cips/0105/mentions stays for backward compat — it returns topic / thread counts; this new endpoint returns per-post / per-message granularity plus GitHub and YouTube coverage.