ACME
Back to Homepage
Canton Network Approves CIP-0116, Introducing CC Locking Requirements for Featured App Status
TECHNOLOGY

Canton Network Approves CIP-0116, Introducing CC Locking Requirements for Featured App Status

Canton Network has approved CIP-0116, requiring Featured App applicants to lock between 5 million and 25 million CC per PartyId to qualify for and maintain Featured App designation, replacing a Foundation-led process with on-chain, market-based criteria.

May 22, 2026 at 6:20 PM3 min read
CantonNews
CantonNews
Editorial Team

Canton Network has approved CIP-0116, a governance proposal that introduces on-chain Canton Coin locking requirements for applications seeking Featured App designation. The change shifts the process away from Foundation-led prioritisation toward a more objective, market-based framework.

Under the new rules, applications must meet minimum CC locking thresholds per PartyId to qualify for and maintain Featured App status. Non-issuer Featured App parties are required to lock 5 million CC per PartyId, while asset issuer parties face a higher threshold of 25 million CC per PartyId. Locked funds must be held in a segregated, identifiable PartyId and are subject to a 60-day unlock period, vesting at a rate of 1/60 per day.

Existing Featured Apps have 30 days from the proposal's approval to meet the new requirements. Failure to do so results in loss of Featured App status, which can only be regained through a new application process.

For new applicants, the process requires identifying and pre-positioning the required CC before a vote is initiated. The Foundation will order reviews based on the time at which assets are pre-positioned. An on-chain vote is gated on the applicant proving sufficient locked token ahead of any approval.

Enforcement is continuous. If a Featured App's locked amount falls below the required threshold at any point, Featured App status is immediately removed. Super Validator operators are required to maintain a rapid-response unfeaturing process, with a mandatory response time of 30 minutes or less from the initiation of an unfeature vote proposal.

Future updates to locking thresholds and lock durations may be proposed by the Tokenomics Working Group and Super Validators, subject to full governance process, public communication, and a Super Validator vote.

Source: github.com
Explore Further
Developer ResourcesExplore Daml, CIP-56 & Zenith →