Financial parameters, staking structures, and software requirements for CIF. How operators qualify for and maintain Foundation-pool delegation when adapters are live. Until then, treat matching/residual as program design.

Enrollment still requires ownership challenge XD1DSR — Ownership page (02).

1. Supply cap & micro-denomination

Parameter Value
Hard supply cap 16,000,000 CLRTY
Fine units Protocol fee/reward sub-units (see genesis / mint manifests for exact decimals)
Example vote buffer 0.0355 CLRTY illustrative operational balance

2. Allocation & eligibility (two tracks)

            [ Approved Fellowship Applicant ]
                            |
          +-----------------+-----------------+
          |                                   |
[ Residual Delegation ]             [ Matching Delegation ]
- Baseline stake                    - Matches external stake
- Baseline + residual criteria      - Stricter performance ceilings

Delegation delay: stake activation/removal may lag 1–2 epochs (~4 days design assumption).

3. Mainnet criteria (design benchmarks)

Performance

Metric Requirement
Vote credit production ≥ 97% of cluster average (prior epoch)
Client binaries Track CLRTY client release notes (Roadmap Agave/Firedancer tables are placeholders — do not treat as Live required binaries today)
Security / restart response Patch / act within 24 hours

Financial & concentration

Rule Cap
Validator commission ≤ 5%
MEV / tip commission (if applicable) ≤ 10%
ASN concentration ISP ≤ 25% of network stake
Data center concentration Facility ≤ 15% of network stake
Total existing stake ceiling ≤ 1,000,000 CLRTY

Matching boost

Eligible for performance-adjusted matching if residual requirements pass and:

Formula (design):

Matched Stake = Base Match × Performance Multiplier