← 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.
Sibling CIPs · 3
CIPs that declare a requires: dependency on CIP-0105, or reference it in their content.
Forum posts · 1 · across 1 topic
Individual posts on forum.canton.network that mention CIP-0105. Showing 1 most recent of 1.
… . That file explains all of your diffs: (a) ② lists organisations with SV weight. ① is Lighthouse’s CIP-0105 locking dashboard: one row per reward-receiving party, plus org rows, with Tier 1/2/3 from lock com …
Mailing-list messages · 99 · across 18 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.
… a more accurate rationale statement is "Maximize economic alignment between actors as described in CIP-0105 and CIP-0116, while minimizing operational frictions of the locks" Agreed. It also seems to me that …
… a more accurate rationale statement is "Maximize economic alignment between actors as described in CIP-0105 and CIP-0116, while minimizing operational frictions of the locks" Separately from the above, i thi …
… pital strip. Issuance becomes a function of the commitment ratio rather than of elapsed time. Under CIP-0105 and CIP-0116, locked CC already buys eligibility; this proposal makes it buy the resource. If adopt …
… dashboards are: CCView SV Locking Dashboard Lighthouse SV Locking Dashboard Official Documentation CIP-0105: Super Validator Locking and Long-Term Commitment Framework SV Locking Operational Guidelines CIP-0 …
… 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 …
… 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 …
… 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 …
… 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 …
… 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 …
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 …
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 …
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 …
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
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
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
Dear Super Validators, Following review under CIP-0105 (SV Locking) and the governance process outlined in CIP-0111, Tokenomics recommends the following S …
… : 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 …
… 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 …
… 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 …
… 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 …
… ---------|--------------------------|---------------| | 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 …
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
We have reached 2/3 approval for this updated timeline. Thanks for your participation.
GitHub items · 37
Issues, PRs, and dev-fund proposals across all indexed Canton repositories that mention CIP-0105.
### Motivation Explain to SV operators how to create and manage their governance locks using their token standard wallet. ### - Add a new page "Governance Locks" below "Global Synchronizer & Tokenomic
… his updates the TSv1 withdraw operations for `GovernanceLock`s and `VestingLock`s to check for the `cip-0105/unlock-at` and `cip-0105/withdraw-at` metadata keys respectively. The metadata values are expected …
[Announcement](https://lists.sync.global/g/supervalidator-announce/message/597)
… a utility strip (TU) and a capital strip (TC). Issuance follows the commitment ratio. It completes CIP-0105/0116 and deprecates the CIP-0104 reward machinery, the CIP-0098 cap, the CIP-0084 price recommendat …
[Announcement](https://lists.sync.global/g/supervalidator-announce/message/588)
… om/canton-network/splice-sv-fa-locking/pull/58)) on each one to convert it to a real lock. Per the [CIP-0105 design doc](https://docs.google.com/document/d/1VGtgNSNHrHnSLggqxlvhCTFrMPgaeCs2OLEJ8Fq9Ar4/edit?ta …
… mitment Framework](https://github.com/meiersi-da/cips/blob/bf79396b8c5f360b2e6c58dfe7e7d9bbf5226dd6/cip-0105/cip-0105.md ) [CIP: Featured App Locking](https://github.com/meiersi-da/cips/blob/bf79396b8c5f360b2 …
## Why The CIP-0105 design mentions adding global configuration parameters for the vesting durations of both SV and FA …
## Why `ProvisionalFeaturedAppLockConversionTrigger` (CIP-0105, "Compatibility mode for SV locks") runs in the SV app and needs to find `GovernanceLock` contracts …
Per [CIP-0105 implementation design](https://github.com/meiersi-da/cips/blob/83738faa3b826b5d97567790f61c1a583066 …
## Why `ExpireVestingLockTrigger` (CIP-0105, "Compatibility mode for SV locks") runs in the SV app and needs to find `VestingLock` contracts wh …
## Why `ExpireVestingLockTrigger` (CIP-0105, "Compatibility mode for SV locks") runs in the SV app and needs to find `VestingLock` contracts wh …
… .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 …
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
… 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 …
… 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 …
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 code for possible direction for CIP-0105 locking implementation using the existing AmuletAllocationV2 unmodified, for reference only. Do not …
… 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 …
… 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 …
## 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 …
## Development Fund Proposal Submission **Proposal file:** [CIP-0105 Implementation Phase.md](https://github.com/obsidiansystems/canton-dev-fund/blob/cip-0105-impl/prop …
## Development Fund Proposal Submission **Proposal file:** [CIP-0105 Implementation Phase.md](https://github.com/obsidiansystems/canton-dev-fund/blob/cip-0105-impl/prop …
… ables Apache 2.0, public Avro Digital repository. ## Prior work SV Governance dApp grant (PR #223), CIP-0105 SV-locking, xCC, Avro Pay.
… versal Primitive (filed in parallel) - Avro Digital prior work: SV Governance dApp grant (PR #223), CIP-0105 SV-locking proposal, DFBA, xCC, Avro Pay
Blog posts · 6
Third-party coverage and ecosystem blog posts. Each links to the original publisher; CCPEDIA only indexes, doesn't republish.
Cashen, the marketplace where Canton’s Featured Apps and Super Validators source locked Canton Coin, now has more than 500 million CC in live locking deals, worth over $60 million. That is up from 215 million in late June, and the climb is getting steeper. Here is how the market works and why demand keeps growing.
Canton Strategic Holdings reported $1.5 million in second-quarter revenue, including $191,226 from network validation and $1.3 million in other revenue, primarily from locking-as-a-service agreements.
Canton Strategic Holdings' Q2 report says Canton Network averaged 2.28 million daily transactions, Featured Apps increased from 47 to 107, and approximately 200 new Validators launched. This deep dive examines the reported activity, institutional transactions, application growth, governance changes and data qualifications behind those figures.
Canton Strategic Holdings is introducing a locking-as-a-service offering for Canton Network app builders and Super Validators. The service follows CIP-0105 and CIP-0116, helping participants meet Canton Coin commitment requirements while managing capital more efficiently.
Canton Strategic ended the first quarter with 3.68 billion Canton Coin, $41.5 million in cash, Super Validator approval, and a strengthened capital base as it builds its public-market strategy around Canton Network infrastructure.
Canton Network has ended liveness rewards for validators, moving its incentive model away from passive node operation and toward usage, application demand, and long-term alignment.
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/citationsReturns a JSON shape mirroring this page.- The legacy
/api/v1/cips/0105/mentionsstays for backward compat. It returns topic / thread counts; this new endpoint returns per-post / per-message granularity plus GitHub and YouTube coverage.