CLRTY Infrastructure Fellowship (CIF) empowers active developers and core contributors in the CLRTY-1 ecosystem to become long-term infrastructure operators securing the network.

CIF is not a simple delegation handout. It is a structured progression system: contributor → operator → core infrastructure participant.

Ownership challenge for applications: XD1DSR.

<aside> ⚠️

CLI honesty: clrtynet ≡ clrty ≡ clarity. Surfaces marked Live are shipped today. Surfaces marked Roadmap are designed but not published as Live binaries/adapters yet. Do not treat invent hosts (api.devnet.clrty.org, etc.) as Live.

</aside>

Program objectives (four pillars)

  1. Optimize Network Integrity — Maximize decentralization, reliability, and performance.
  2. Diversify Stake Sources — Expand operators supported by independent, community-driven stake.
  3. Sustain Network Resilience — Maintain a robust, representative Moniversive testnet/devnet environment.
  4. Formalize Builder Progression — Transparent pathway from contributor → operator → core infrastructure.

Program architecture (summary)

Layer What it does Status
Tier I–III Sandbox → Active → Core eligibility Documented; ops DBs live in Notion
Builder Reputation Score (BRS) Primary routing key for allocation Design + Notion ledger
Vote cost coverage (taper) 100% → 25% over year 1 Program design
Dynamic stake matching Base match × performance multipliers Adapter-pending
Residual delegation Baseline stake for qualifying Fellows Adapter-pending
Delegation routing engine Inputs → matching / residual / tier moves Design
Builder Credits (non-token) Boost match / unlock tiers Notion Credits Ledger
Soft penalties + community signal Accountability + delegator influence Design

Tiered fellowship structure

Tier I — Sandbox Fellows

Tier II — Active Fellows