This guide onboards developers, systems architects, and software contributors to the CLRTY Infrastructure Fellowship (CIF).

Focus: deploy and validate the CLRTY software stack you can run today, document MIRRA scheduling constraints as Roadmap design, and prepare for Foundation delegation adapters when they ship — not invent validator binaries as Live.

[ STEP 1: Keys / Identity ] → [ STEP 2: Fellowship Intake ] → [ STEP 3: Core Stack ]
                                                                      │
[ STEP 6: Delegation Queue ] ← [ STEP 5: Consensus / Telemetry ] ← [ STEP 4: MIRRA Config ]
            │
[ STEP 7: Performance Tracking ] → [ STEP 8: Matching & Scale-Up ]

Step 1: Cryptographic identity & voting keys

Establish separate identities for Moniversive Devnet/Testnet vs Mainnet.

Key role Purpose Live today?
Identity / wallet Contributor entity in registry Live: clrtynet wallet status
Vote / telemetry Sign validations & stream metrics Roadmap: dedicated vote keygen + remote signer
Authorized withdrawer Offline authority over vote account Roadmap: create-vote-account flow

Minimum balance (design): keep vote authorization funded with at least 0.0355 CLRTY illustrative buffer so epoch transitions do not starve fees under the 16,000,000 CLRTY hard-cap design.

Live path now:

clrtynet wallet status --json
clrtynet node register --dry-run --json

Roadmap: clrty-keygen new, paper wallets, vanity grind — see Operator Guide (page 03).

Step 2: Fellowship intake & KYC/KYB

Prevent sybil attacks and align with distribution policy.

  1. Complete KYC/KYB and list technical contributions (protocol, client, tooling, docs).
  2. Prove key ownership with challenge XD1DSR — Ownership page (02).
  3. Submit to CIF Applications and email [email protected].
  4. Approved applicants are indexed on the registrar queue (Participants DB).
# Roadmap — not Live yet (clrtynet ≡ clrty ≡ clarity)
clrtynet sign-offchain-message XD1DSR --keypair PATH_TO_KEYPAIR
clrty sign-offchain-message XD1DSR --keypair PATH_TO_KEYPAIR

There is no Foundation form on third-party org sites — CIF Applications + email only.