CIP-0116: Featured App Locking

Summary

This proposal introduces per-party CC locking requirements for Featured App (FA) designation.

The objective is to:

• Shift FA governance towards a market-based process
• Prioritize applications that demonstrate committed capital

Motivation

Featured App designation currently relies heavily on Foundation governance.

This proposal introduces objective, on-chain criteria to:

• Reduce reliance on Foundation prioritization
• Allow all CC holders to participate in FA designation process

Specification

1. Featured App Requirements

To qualify for and maintain Featured App status, an application must:

1. Maintain good standing with the Foundation
2. Satisfy the applicable minimum CC locking requirement per PartyId

Failure to meet either condition results in loss of Featured App status.

Locking is required per PartyId.

2. Locking Requirements

2.1 CC Requirements

Non-Issuer Featured App Parties

• Locked: 5,000,000 CC per PartyId

• Follows similar process as SV Locking:

  Hold funds in a segregated, identifiable PartyId

  • Inform Foundation
  • Only actively locked CC counts toward FA eligibility
  • 60-day unlock period - vests 1/60 per day Asset Issuer Featured App Parties

• Locked: 25,000,000 CC per PartyId

• Follows similar process as SV Locking:

  Hold funds in a segregated, identifiable PartyId

  • Inform Foundation
  • Only actively locked CC counts toward FA eligibility

• 60-day unlock period - vests 1/60 per day

2.2 New Featured Apps

• Prior to voting:
  • FA Applicant identifies PartyID and CC that will be locked
  • If it meets the threshold, Foundation will order reviews based on the time at which assets were pre-positioned
  • Automating this process will be presented in a future CIP
• If FA Applicant is approved, they must lock ahead of a vote to feature their party ID
  • Onchain vote will be gated on FA proving they have locked sufficient token
• If an application is not approved, CC may be moved immediately

2.3 Existing Featured Apps

• Existing Featured Apps have 30 days from CIP approval to meet their locking requirements
• Failure to meet this requirement results in loss of Featured App status
• FA status may be regained through a new application process

2.4 FA Guideline Enforcement

• The Foundation will enforce proper PartyId separation as required under FA Guidelines
• FA Status can be revoked if the locked amount falls below required thresholds or if a Featured App does not meet the required lock after introducing activity necessitating a move into a higher locking amount.

3. Enforcement

• Locking requirements must be satisfied continuously
• If locking falls below required thresholds, Featured App status is immediately removed

Super Validator operators are required to implement and maintain a rapid-response unfeaturing process.

This process must:

• Allow any Super Validator to initiate an unfeature action via a standard proposal mechanism following official notice from the Foundation
• Require SV Operators to respond within 30 minutes or less from initiation of an unfeature vote proposal

4. Governance

The Tokenomics Working Group and Super Validators may propose updates to:

• Locking thresholds
• Lock durations

All updates must:

• Be publicly communicated
• Include an effective date
• Provide reasonable notice prior to enforcement
• Go through full governance process and SV vote

Copyright

This CIP is licensed under CC0-1.0: Creative Commons CC0 1.0 Universal.

Changelog

• 2026-05-20: Approved
• 2026-05-15: Updated
• 2026-05-06: Proposed