Skip to content
CCPEDIAby Unity Nodes

← 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.

126 total referencesSibling CIPs 1Forum posts 0Mailing messages 95GitHub items 25Blog posts 5YouTube videos 0JSONMCP: get_cip_citations

Sibling CIPs · 1

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

Mailing-list messages · 95 · across 16 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 Proposal: FA and SV locking implementation[cip-discuss] · @Simon Meier · 2d ago

    … abstract explaining its content and motivation: ----- This CIP serves to align the stakeholders of CIP-0105 (SV Locking) and CIP-0116 (FA Locking) on the implementation of on-chain enforcement of SV and FA l …

  • Update SV Reward Weight[supervalidator-announce] · @Amanda Martin · 9d ago

    … ar Super Validators, Taurus and Quantstamp have now fallen below the Tier 1 locking threshold under CIP-0105 (SV Locking) and the governance process outlined in CIP-0111 recommends an SV weight adjustments. P …

  • … 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 · 2mo 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 …

  • 1. Consolidate the four-option voting model[cip-discuss] · @Heslin Kim · 2mo ago

    … tuity, 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 · 3mo 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 · 3mo 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 · 3mo 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 · 3mo 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 · 3mo 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 · 3mo 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 · 4mo 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 · 4mo 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 · 4mo 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 · 4mo 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 · 4mo 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 · 4mo 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 · 4mo 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 · 4mo 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 · 5mo 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 · 5mo 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 · 5mo 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 · 5mo 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 · 5mo ago

    Cumberland DRW votes in favor. Thanks Chris

GitHub items · 25

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

  • CIP-0105 Initial implementation for Top Ups using Liquid CCcanton-network/splice-sv-fa-locking#9 · pr · open · @dbzguy56 · 9d ago

    … .com/obsidiansystems/splice/pull/14). Initial DAML implementation for Top Ups using Liquid CC under CIP-0105. ### Pull Request Checklist #### Cluster Testing - [ ] If a cluster test is required, comment `/clu …

  • Cip 0105 with custom templates POCcanton-network/splice#6894 · pr · closed · @jonored · 16d ago

    Implement governance locks with separate templates and _not_ on top of V2 allocations (but _do_ provide the V2 allocation interface for the separate lock templates). Next steps are to do a proper happ

  • [Amendment] CIP-105 Extensioncanton-foundation/canton-dev-fund#644 · pr · closed · @ali-abrar · 16d ago

    … iansystems/canton-dev-fund/blob/e296ea9514e4ba5ac6d28495eb8b31fd7fe71f4e/proposals/2026-04-Obsidian-CIP-0105.md --- ## Summary Obsidian Systems requests a time extension to continue work on CIP-105 design. We …

  • Add voting delegation foundation (VoteDelegation + optional governance party)canton-network/splice#6871 · pr · closed · @ericmann · 17d ago

    … ght/reward changes. - Hard Daml-level enforcement of who-can-vote (UI-level enforcement for now). - CIP-0105 SV locking; non-node-operator voting-entity changes. ## Trust model UI-level enforcement is accepta …

  • Cip 0105 basic sv lockscanton-network/splice#6815 · pr · closed · @dbzguy56 · 19d ago

    WIP, the plan is to have commits be squashed. ### Pull Request Checklist #### Cluster Testing - [ ] If a cluster test is required, comment `/cluster_test` on this PR to request it, and ping someone wi

  • WIP: cip 0105 externally implemented governance lockscanton-network/splice#6427 · pr · open · @jonored · 1mo ago

    WIP code for possible direction for CIP-0105 locking implementation using the existing AmuletAllocationV2 unmodified, for reference only. Do not …

  • Add voting delegation foundation (VoteDelegation + optional governance party)canton-network/splice-sv-voting-dapp#12 · pr · open · @ericmann · 2mo ago

    … ght/reward changes. - Hard Daml-level enforcement of who-can-vote (UI-level enforcement for now). - CIP-0105 SV locking; non-node-operator voting-entity changes. ## Trust model UI-level enforcement is accepta …

  • Fix inaccuracies identified in documentation review passcanton-network/cf-docs#835 · pr · closed · @8bitpal · 2mo ago

    … with the canonical `canton-foundation/cips`. Added CIP-0107, CIP-0112, CIP-0117 (Standards Track); CIP-0105, CIP-0114, CIP-0116, CIP-0119 (Tokenomics); CIP-0111 (Process). Corrected CIP-0082 and CIP-0100 sta …

  • Proposal: CIP-0105 Implementation Phasecanton-foundation/canton-dev-fund#480 · pr · open · @obsidian-golem · 2mo ago

    ## Development Fund Proposal Submission **Proposal file:** Proposal file: [CIP-0105 Implementation Phase.md](https://github.com/obsidiansystems/canton-dev-fund/blob/cip-0105-impl/prop …

  • Proposal: CIP-0105 & CIP-0116 Implementationcanton-foundation/canton-dev-fund#377 · pr · closed · @obsidian-golem · 3mo ago

    ## Development Fund Proposal Submission **Proposal file:** [CIP-0105 Implementation Phase.md](https://github.com/obsidiansystems/canton-dev-fund/blob/cip-0105-impl/prop …

  • Proposal: CIP-0105 & CIP-0116 Implementationcanton-foundation/canton-dev-fund#376 · pr · closed · @obsidian-golem · 3mo ago

    ## Development Fund Proposal Submission **Proposal file:** [CIP-0105 Implementation Phase.md](https://github.com/obsidiansystems/canton-dev-fund/blob/cip-0105-impl/prop …

  • Proposal: Payment Dispute & Refund Authorization Primitive [Avro Digital]canton-foundation/canton-dev-fund#293 · pr · closed · @samsondav · 4mo ago

    … ables Apache 2.0, public Avro Digital repository. ## Prior work SV Governance dApp grant (PR #223), CIP-0105 SV-locking, xCC, Avro Pay.

  • Proposal: Atomic Multi-Leg Settlement Primitive (W15)canton-foundation/canton-dev-fund#291 · pr · closed · @samsondav · 4mo ago

    … versal Primitive (filed in parallel) - Avro Digital prior work: SV Governance dApp grant (PR #223), CIP-0105 SV-locking proposal, DFBA, xCC, Avro Pay

  • Proposal: Payment Dispute & Reversal Primitive (W14)canton-foundation/canton-dev-fund#290 · pr · closed · @samsondav · 4mo ago

    … lement Primitive (filed in parallel) - Avro Digital prior work: SV Governance dApp grant (PR #223), CIP-0105 SV-locking proposal, xCC, Avro Pay

  • Proposal: On-Chain Enforcement of Super Validator Locking and Long-Term Commitmentcanton-foundation/canton-dev-fund#269 · pr · closed · @cardenaso11 · 4mo ago

    … l file:** Link to the proposal added in this PR (e.g., /proposals/your-proposal-name.md) /proposals/CIP-0105.md Permalink: https://github.com/obsidiansystems/canton-dev-fund/blob/1f9706eb379d7327c7f5755763e3b …

  • cip-105: Update wording for more claritycanton-foundation/cips#194 · pr · closed · @stas-sbi · 4mo ago
  • cip-105: Clarify mandatory vestingcanton-foundation/cips#191 · pr · closed · @stas-sbi · 4mo ago
  • feat: CIP-0105 Phase 2 — lock-derived SV weight evaluation (Capability #3)canton-network/splice#4898 · pr · closed · @ericmann · 5mo ago

    … pability #3** from Wayne Collier's Phase 2 locking requirements: calculating locked balance against CIP-0105 threshold levels and assigning the resulting SV weight. This is the mechanism that gives CIP-0105 l …

  • feat: CIP-0105 Phase 2 — Locking Declarations and Delegated Locking (Capabilities #1 + #4)canton-network/splice#4848 · pr · closed · @vaziliaz · 5mo ago

    ## Summary Implements two of the six Phase 2 capabilities from Wayne Collier's [locking requirements](https://github.com/hyperledger-labs/splice/issues/4842): **Capability #1 — Locking Declarations:**

  • Proposal: Phase 2 Capability — Non-SV Balance Locking for SV (CIP-0105)canton-network/splice#4842 · issue · closed · @vaziliaz · 5mo ago

    # Proposal: Phase 2 Capability — Non-SV Balance Locking for SV (CIP-0105) ## Summary Implement capability #4 from the Phase 2 locking requirements: **allow a non-SV party t …

  • CIP-0105 Phase 2: SV locking foundation and weight evaluationcanton-network/splice#4841 · issue · closed · @ericmann · 5mo ago

    ## Summary Tracker for the upstream implementation of CIP-0105 Phase 2 SV locking in Splice. Enumerates the capabilities needed for a complete on-chain Phase 2 fo …

  • Proposal: CIP-0105 Phase 2 On-Chain SV Locking Enforcementcanton-foundation/canton-dev-fund#150 · pr · closed · @ericmann · 5mo ago

    … ntation.md) --- ## Summary This proposal requests funding to design, implement, and devnet-validate CIP-0105 Phase 2 — on-chain Super Validator locking enforcement — as a contribution to the `hyperledger-labs …

  • Proposal: CIP-0105 Compliance Computation Modulecanton-network/splice#4660 · issue · open · @vaziliaz · 5mo ago

    ## Summary CIP-0105 Phase 1 enforcement begins April 1, 2026. Every SV must maintain a minimum locked percentage of lif …

  • CIP-105 Approval canton-foundation/cips#164 · pr · closed · @pedrodneves · 6mo ago
  • cip-0105canton-foundation/cips#161 · pr · closed · @pedrodneves · 6mo ago

Blog posts · 5

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 Returns a 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.