CIP-0116 Enforcement
What is CIP-0116 and why do Canton apps get paused because of it?
CIP-0116 is Featured App Locking, and it is not a dormant rule. It is cited by 58 on-chain governance requests, 54 of which were accepted, and 57 of them withdrew an app's Featured App right for failing the locking requirement. Enforcement runs from 2026-06-20 to 2026-07-16.
Derived from CCPEDIA's own sync of primary sources. Last updated 2026-07-21.
How it is used
Of the 58 requests citing this CIP, 57 are revocations. That ratio is the point: CIP-0116 exists as a compliance obligation, and the governance record shows it being applied to remove status from apps that did not meet it, one vote at a time.
Read the proposal itself at CIP-0116.
Most recent enforcement actions
| Date | Action | Outcome | Vote |
|---|---|---|---|
| 2026-07-16 | Revoke Featured App right | Accepted | 9 for / 0 against |
| 2026-07-09 | Revoke Featured App right | Open | 8 for / 5 against |
| 2026-07-05 | Grant Featured App right | Accepted | 13 for / 0 against |
| 2026-06-29 | Revoke Featured App right | Accepted | 10 for / 0 against |
| 2026-06-29 | Revoke Featured App right | Accepted | 10 for / 0 against |
| 2026-06-29 | Revoke Featured App right | Accepted | 10 for / 0 against |
| 2026-06-29 | Revoke Featured App right | Accepted | 10 for / 0 against |
| 2026-06-29 | Revoke Featured App right | Accepted | 10 for / 0 against |
| 2026-06-29 | Revoke Featured App right | Accepted | 10 for / 0 against |
| 2026-06-29 | Revoke Featured App right | Accepted | 10 for / 0 against |
Showing 10 of 58. The rest are on on-chain votes.
How this was counted
A request counts here when its written reasoning names CIP-0116 explicitly. The match requires the identifier itself, not a bare number, so a request mentioning an unrelated 116 is not counted. A request that enforces the same rule without naming it would be missed, which means this figure is a floor rather than a ceiling.
Common questions
- What is CIP-0116 on Canton Network?
- CIP-0116 is "Featured App Locking", currently Active. It sets a locking requirement that a Featured App must meet, and it is enforced by Super Validator vote rather than automatically.
- How many times has CIP-0116 been enforced?
- 58 on-chain governance requests cite CIP-0116, of which 54 were accepted. 57 of them sought to withdraw a Featured App right, so it is overwhelmingly used to remove status rather than grant it.
- Why was my Canton app paused under CIP-0116?
- Because a Super Validator vote found it out of compliance with the locking requirement and withdrew its Featured App right. The request, the stated reason and every individual vote are on the public record.
- Is CIP-0116 enforcement automatic?
- No. Each case is raised as a separate governance request and voted on individually. That is why there is a dated record of every instance rather than a single rule change.
- When did CIP-0116 enforcement start?
- The first request citing it took effect on 2026-06-20, and the most recent on 2026-07-16.
