RFC-0009 — Operator registration

Owner: Pallet Lead + Security Lead

What it defines

How operators register on chain per RFC-0002 attestation requirements.

Fields

register_operator(
  coldkey,                      // long-lived economic identity
  hotkey,                       // online signing key
  attestation_quote,            // RFC-0002 combined report
  tier,                         // dc-premium | dc-standard | ...
  stake_amount,                 // OROG with USD-pegged ratchet
  geo_region,                   // ISO 3166-1 alpha-2 + subdiv
  ip_24_hash,                   // for diversity enforcement
  sanctions_check_proof,        // (provider_id, screened_at, screener_signature)
  signature
)

Anti-sybil rules

• Same device_cert across coldkeys → both slashed 100% (red-team rule 7).
• IP /24 collision → flag for review; registration blocked if cluster ratio breaches threshold.
• Sanctions screening proof required (RFC §9).

Stake denomination

OROG with USD-pegged ratchet via governance every 30 days.

Re-registration after slash

6mo cooldown + new coldkey + fresh screen. Permanent ban for SanctionsHit and DeviceCertCollision.

Canonical source

chain-tooling-rust/specs/RFC-0009-operator-registration.md