Feature Activation Pipeline
Core Protocol · Abyss
The multi-step process by which a protocol change transitions from SIMD proposal to live mainnet behavior. A feature is assigned a unique keypair; once merged into the client, it remains inactive until a validator with sufficient stake creates the feature account via `solana feature activate`. Activation takes effect at the start of the next epoch after the feature account is created. The pipeline allows coordinated rollout: features first activate on testnet/devnet, then mainnet, and validators running older clients that lack the feature code will halt at the activation slot boundary rather than diverge.