← CIP-PR-0127 · citation graph
Citations / CIP-PR-0127
On-Chain Enforcement of FA and SV Locking (Implementation of CIP-0116 and CIP-0105) · status: Draft
Every place across CCPEDIA's corpus that references CIP-PR-0127: 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.
Mailing-list messages · 17 · across 2 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.
I completed revising the delivery plan and the compatibility mode specification, which resulted in the following changes: Adjust the delivery plan to deliver transfers and substitutions as part of Inc
These are great comments. See my answers inline below. On Thu, Oct 8, 2026 at 8:48 PM Andrew Bryan via lists.sync.global wrote: Thank you for posting the updated CIP draft. We have a couple smaller co
Thank you for posting the updated CIP draft. We have a couple smaller comments: I think it's potentially operationally dangerous to have on-chain locking go live substantially before substitution and
Hi Simon, Thanks, this is helpful. To answer your question directly: 30 days. I would place that window slightly differently though, so that it needs no on-chain change at all, not even to the underlo
Thanks Andrew for discovering this missing workflow step. I have updated the CIP proposal with a separate section specifying the ability to transfer locks: you can read the new section here: https://g
Fair points Simon. Regardless of any change to rules, I agree with aligning to one variable of underlock grace period. In our view, 7 days should be more than sufficient given the availability of capi
Hi Abdulkadir, I can't speak to whether the SV rights owners are willing to lower the requirements for getting a featured app right. I'm wondering whether there's an option to modify your proposal, so
Hi all, Thanks to Simon and Jonathan for the detailed work. I have one suggestion on the provisional FA lock flow, since this CIP is where the automation promised in CIP-0116 §2.2 lands. It follows th
I believe this is a much-needed addition that will help our work at the SVAC. Currently we are looking at SVs that move locked CC from one wallet to another and the frequent response we get is "intern
I agree with Wayne on the differences in use cases in scope. Our goal with the proposed addition is to allow a SV or FA to transfer between their own wallets when needed for operational purposes such
I've found it helpful to think of two use cases for substitution: 1. Locked funds are controlled by the same entity, but they want to change the wallet where the locked funds are recorded. In this cas
Yes that makes sense. Given there is inherent protection to the FA or SV - the beneficiary of the lock stays same - a natural extension of that is the beneficiary is a party. Similar to assignment of
this look more likely to be used when an existing locked wallet owner wants to migrate to a new partyID they also control without needing double the capital for example, migrating from one host (custo
Hi Andrew This is essentially liquid staking from my initial read? One thing to consider is the case where an FA has borrowed CC from a locked party on direct commercials. So if the lock is an FA supp
Hi All, Cumberland would like to propose an adjustment to the current proposal to enable transfer of locks between wallets and similar use cases where existing locks are used instead of pre-funding. T
Hi all, the design including the full Daml implementation of the CIP proposal from this discussion thread is progressing well. You can see the progress on this preview PR: https://github.com/canton-ne
Hi all, We are happy to share a proposal for how to implement on-chain SV and FA locks and their enforcement. You can find the full proposal in this PR: https://github.com/canton-foundation/cips/pull/
GitHub items · 4
Issues, PRs, and dev-fund proposals across all indexed Canton repositories that mention CIP-PR-0127.
**Vesting lock transfer request parsing**. Add `GLR_TransferVestingLock`. Parse `cip-127/memo` reason key as `GLR_TransferVestingLock` if `lock-status=vesting`: - vesting requires `lock-vesting-durati
Fixes #99 This implements memo tag parsing and encoding, and more generally introduces the concept of a `GovernanceLockRequest` which is the definitive set of operations that can be performed using ei
Per discussion in our meeting on 2026-10-06, we'd like to rework how we handle locks and unlocks in compatibility mode (TSv1). The new approach is described [here](https://docs.google.com/document/d/1
See abstract for the content and motivation.
Blog posts · 3
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.
SoFi added Canton Coin, Marex and LSEG took up their Super Validator weight, Broadridge processed $7.5 trillion in repo on Canton, and a new proposal would make all of MainNet burn CC. Here is everything that moved on Canton from October 5 to October 11, one update at a time.
An update to CIP-0127 proposes a way to change the owner of locked Canton Coin while keeping the lock in place. It would let participants move to a new custodian without first unlocking or replacing the funds.
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/PR-0127/citationsReturns a JSON shape mirroring this page.- The legacy
/api/v1/cips/PR-0127/mentionsstays for backward compat. It returns topic / thread counts; this new endpoint returns per-post / per-message granularity plus GitHub and YouTube coverage.