{"cip_id":"PR-0127","title":"On-Chain Enforcement of FA and SV Locking (Implementation of CIP-0116 and CIP-0105)","status":"Draft","counts":{"sibling_cips":0,"forum_posts":0,"forum_topics":0,"mailing_messages":17,"mailing_threads":2,"github_items":4,"blog_posts":3,"youtube_videos":0,"total":24},"sibling_cips":[],"forum_posts":[],"forum_topics":[],"mailing_messages":[{"id":"cip-discuss-883","thread_id":"121068557","thread_title":"CIP-0127: FA and SV locking implementation","group_slug":"cip-discuss","author":"Simon Meier","sent_at":"2026-10-09T08:36:08.000Z","url":"https://lists.sync.global/g/cip-discuss/message/883","subject":"CIP-0127: FA and SV locking implementation","snippet":"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","cip_id_match":true},{"id":"cip-discuss-881","thread_id":"121068557","thread_title":"CIP-0127: FA and SV locking implementation","group_slug":"cip-discuss","author":"Simon Meier","sent_at":"2026-10-09T06:27:31.000Z","url":"https://lists.sync.global/g/cip-discuss/message/881","subject":"CIP-0127: FA and SV locking implementation","snippet":"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","cip_id_match":true},{"id":"cip-discuss-880","thread_id":"121068557","thread_title":"CIP-0127: FA and SV locking implementation","group_slug":"cip-discuss","author":"Andrew Bryan","sent_at":"2026-10-08T18:47:58.000Z","url":"https://lists.sync.global/g/cip-discuss/message/880","subject":"CIP-0127: FA and SV locking implementation","snippet":"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 ","cip_id_match":true},{"id":"cip-discuss-878","thread_id":"121627308","thread_title":"CIP-0127: FA ve SV kilitleme uygulaması","group_slug":"cip-discuss","author":"Abdulkadir CANPOLAT","sent_at":"2026-10-07T13:07:27.000Z","url":"https://lists.sync.global/g/cip-discuss/message/878","subject":"CIP-0127: FA ve SV kilitleme uygulaması","snippet":"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","cip_id_match":true},{"id":"cip-discuss-877","thread_id":"121068557","thread_title":"CIP-0127: FA and SV locking implementation","group_slug":"cip-discuss","author":"Simon Meier","sent_at":"2026-10-07T08:53:12.000Z","url":"https://lists.sync.global/g/cip-discuss/message/877","subject":"CIP-0127: FA and SV locking implementation","snippet":"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","cip_id_match":true},{"id":"cip-discuss-874","thread_id":"121068557","thread_title":"CIP-0127: FA and SV locking implementation","group_slug":"cip-discuss","author":"Luke Farrell","sent_at":"2026-10-06T16:24:13.000Z","url":"https://lists.sync.global/g/cip-discuss/message/874","subject":"CIP-0127: FA and SV locking implementation","snippet":"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","cip_id_match":true},{"id":"cip-discuss-873","thread_id":"121068557","thread_title":"CIP-0127: FA and SV locking implementation","group_slug":"cip-discuss","author":"Simon Meier","sent_at":"2026-10-06T11:11:42.000Z","url":"https://lists.sync.global/g/cip-discuss/message/873","subject":"CIP-0127: FA and SV locking implementation","snippet":"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","cip_id_match":true},{"id":"cip-discuss-872","thread_id":"121068557","thread_title":"CIP-0127: FA and SV locking implementation","group_slug":"cip-discuss","author":"Abdulkadir CANPOLAT","sent_at":"2026-10-06T10:58:47.000Z","url":"https://lists.sync.global/g/cip-discuss/message/872","subject":"CIP-0127: FA and SV locking implementation","snippet":"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","cip_id_match":true},{"id":"cip-discuss-871","thread_id":"121068557","thread_title":"CIP-0127: FA and SV locking implementation","group_slug":"cip-discuss","author":"Yiannis Varelas","sent_at":"2026-10-06T09:33:37.000Z","url":"https://lists.sync.global/g/cip-discuss/message/871","subject":"CIP-0127: FA and SV locking implementation","snippet":"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","cip_id_match":true},{"id":"cip-discuss-869","thread_id":"121068557","thread_title":"CIP-0127: FA and SV locking implementation","group_slug":"cip-discuss","author":"Andrew Bryan","sent_at":"2026-10-05T20:14:50.000Z","url":"https://lists.sync.global/g/cip-discuss/message/869","subject":"CIP-0127: FA and SV locking implementation","snippet":"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 ","cip_id_match":true},{"id":"cip-discuss-868","thread_id":"121068557","thread_title":"CIP-0127: FA and SV locking implementation","group_slug":"cip-discuss","author":"Wayne Collier","sent_at":"2026-10-05T19:37:32.000Z","url":"https://lists.sync.global/g/cip-discuss/message/868","subject":"CIP-0127: FA and SV locking implementation","snippet":"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","cip_id_match":true},{"id":"cip-discuss-867","thread_id":"121068557","thread_title":"CIP-0127: FA and SV locking implementation","group_slug":"cip-discuss","author":"ds","sent_at":"2026-10-05T19:23:17.000Z","url":"https://lists.sync.global/g/cip-discuss/message/867","subject":"CIP-0127: FA and SV locking implementation","snippet":"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 ","cip_id_match":true},{"id":"cip-discuss-866","thread_id":"121068557","thread_title":"CIP-0127: FA and SV locking implementation","group_slug":"cip-discuss","author":"Luke Farrell","sent_at":"2026-10-05T19:10:26.000Z","url":"https://lists.sync.global/g/cip-discuss/message/866","subject":"CIP-0127: FA and SV locking implementation","snippet":"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","cip_id_match":true},{"id":"cip-discuss-864","thread_id":"121068557","thread_title":"CIP-0127: FA and SV locking implementation","group_slug":"cip-discuss","author":"ds","sent_at":"2026-10-05T18:33:09.000Z","url":"https://lists.sync.global/g/cip-discuss/message/864","subject":"CIP-0127: FA and SV locking implementation","snippet":"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","cip_id_match":true},{"id":"cip-discuss-863","thread_id":"121068557","thread_title":"CIP-0127: FA and SV locking implementation","group_slug":"cip-discuss","author":"Andrew Bryan","sent_at":"2026-10-05T18:20:31.000Z","url":"https://lists.sync.global/g/cip-discuss/message/863","subject":"CIP-0127: FA and SV locking implementation","snippet":"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","cip_id_match":true},{"id":"cip-discuss-862","thread_id":"121068557","thread_title":"CIP-0127: FA and SV locking implementation","group_slug":"cip-discuss","author":"Simon Meier","sent_at":"2026-10-01T14:06:52.000Z","url":"https://lists.sync.global/g/cip-discuss/message/862","subject":"CIP-0127: FA and SV locking implementation","snippet":"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","cip_id_match":true},{"id":"cip-discuss-836","thread_id":"121068557","thread_title":"CIP-0127: FA and SV locking implementation","group_slug":"cip-discuss","author":"Simon Meier","sent_at":"2026-09-03T13:28:00.000Z","url":"https://lists.sync.global/g/cip-discuss/message/836","subject":"CIP Proposal: FA and SV locking implementation","snippet":"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/","cip_id_match":true}],"mailing_threads":[{"id":"121068557","title":"CIP-0127: FA and SV locking implementation","group_slug":"cip-discuss","message_count":0,"last_post_at":"2026-10-09T08:36:08.000Z","url":"https://lists.sync.global/g/cip-discuss/topic/cip_0127_fa_and_sv_locking/121068557"},{"id":"121627308","title":"CIP-0127: FA ve SV kilitleme uygulaması","group_slug":"cip-discuss","message_count":0,"last_post_at":null,"url":"https://lists.sync.global/g/cip-discuss/topic/cip_0127_fa_ve_sv_kilitleme/121627308"}],"github_items":[{"id":"canton-network/splice-sv-fa-locking#106","type":"issue","repo":"canton-network/splice-sv-fa-locking","number":106,"title":"Daml: Lock transfer proposal creation via `V1.TransferFactory_Transfer`","state":"closed","author":"tellary","created_at":"2026-10-08T12:42:08.000Z","url":"https://github.com/canton-network/splice-sv-fa-locking/issues/106","snippet":"**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"},{"id":"canton-network/splice-sv-fa-locking#100","type":"pr","repo":"canton-network/splice-sv-fa-locking","number":100,"title":"Memo tag parsing and encoding","state":"closed","author":"mrdziuban","created_at":"2026-10-07T13:54:28.000Z","url":"https://github.com/canton-network/splice-sv-fa-locking/pull/100","snippet":"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"},{"id":"canton-network/splice-sv-fa-locking#99","type":"issue","repo":"canton-network/splice-sv-fa-locking","number":99,"title":"Daml: Memo tag for compatibility mode","state":"closed","author":"mrdziuban","created_at":"2026-10-07T13:21:57.000Z","url":"https://github.com/canton-network/splice-sv-fa-locking/issues/99","snippet":"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"},{"id":"canton-foundation/cips#250","type":"pr","repo":"canton-foundation/cips","number":250,"title":"CIP-0127: SV and FA locking implementation","state":"open","author":"meiersi-da","created_at":"2026-09-03T13:03:34.000Z","url":"https://github.com/canton-foundation/cips/pull/250","snippet":"See abstract for the content and motivation."}],"blog_posts":[{"id":"cantonnews-cashen-passes-500-million-locked-canton-coin-worth-over-60-million","title":"Cashen passes 500 million locked Canton Coin, worth over $60 million","excerpt":"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.","published_at":"2026-10-13T16:42:34.056Z","url":"https://cantonnews.org/cashen-passes-500-million-locked-canton-coin-worth-over-60-million","tags":"third-party,aggregator","source_label":"aggregator"},{"id":"cantonnews-canton-weekly-recap-sofi-lseg-ripple-and-7-5-trillion-in-repo","title":"Canton weekly recap: SoFi, LSEG, Ripple and $7.5 trillion in repo","excerpt":"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.","published_at":"2026-10-12T18:13:26.124Z","url":"https://cantonnews.org/canton-weekly-recap-sofi-lseg-ripple-and-7-5-trillion-in-repo","tags":"third-party,aggregator","source_label":"aggregator"},{"id":"cantonnews-canton-proposal-adds-a-way-to-transfer-locked-cc","title":"Canton proposal adds a way to transfer locked CC","excerpt":"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.","published_at":"2026-10-07T09:58:17.153Z","url":"https://cantonnews.org/canton-proposal-adds-a-way-to-transfer-locked-cc","tags":"third-party,aggregator","source_label":"aggregator"}],"youtube_videos":[],"derivedAt":"2026-10-15T16:39:41.020Z","source":"derived from cips + forum_posts + mailing_messages + github_items + blog_posts + youtube_videos","canonical":"https://ccpedia.xyz/cips/PR-0127/citations"}