Activation is earner-based

Clarity Sanity is a system-level protocol for infrastructure operators, not a public claim/airdrop. You activate by verifying, not by signing up. There is no "claim" button — there is "sync and verify".

The loop

Deploy Sanity Node → Sync to kernel → Submit Proof-of-Sanity → Accrue BRS
  → Cross activation threshold (5 sane epochs) → Eligible for delegation / ZETA / RELAY payout

1. Deploy the Sanity Node

Run a node client that re-executes committed blocks and recomputes each state root. The deterministic check is exactly sanity::proof_of_sanity::reverify:

SHA3-256(block_bytes) compared to the canonical root
→ Sane | Irrational | Pending

Source: CLRTY_SUBSTRATE/sanity/proof_of_sanity.rs

2. Sync to the kernel

Connect the node to the CLRTY-1 subnet and reach the "Sane-State" verification threshold. Confirm the node is streaming verdicts.

3. Submit Proof-of-Sanity

Each epoch, submit your verdict. SanityEngine::submit_proof records it and refreshes your BRS.

• After SANE_STATE_THRESHOLD (5) sane epochs the program is activated for you
• BRS begins to accrue toward delegation / ZETA eligibility
• Missing/failing epochs decay your reputation (decay_factor 0.85 after 3 missed)

4. Passive monetization (RELAY)

No manual claiming. As your verified work is used:

1. sanity_pool fee bucket (10% / 1000 bps) funds the RELAY pool
2. Pool distributes weighted by BRS × ln(1+usage) × longevity × reliability
3. Residue recycles back into the pool