Centurion Validator Program
You operate validator infrastructure and keep your signing key. After seat approval and enrollment-token issuance, the Foundation validates your pubkey and deposit data, funds the 32 CTN principal, and routes settlement through a dedicated WithdrawalVault.
Control boundary
Who controls what - at a glance.
Four control planes, each held by exactly one party. No shared custody, no hidden paths.
Operator
Signing stays with operators.
Validator BLS private keys, keystores, and mnemonics stay in the operator environment.Foundation
Funding stays with the Foundation.
Principal is validated, allowlisted, and funded by the Foundation after seat approval and onboarding-data validation.Vault
Settlement stays in vault policy.
Rewards and exit proceeds follow the deployed vault version's delay, rate-limit, and principal-first accounting rules.Lifecycle
From application to active validator.
A simple process with clear handoffs between you, the Foundation, and the network.
- Phase 1
Apply
- Phase 2
Set up
- Phase 3
Validate & fund
- Phase 4
Activation
Why this model
Capital from the Foundation. Authority from you.
Key custody
What the Foundation never receives.
Validator BLS private keys, keystores, and mnemonics are generated and stored entirely in your environment. Onboarding only moves the public key and deposit data.Fault domains
What happens if you go offline.
Downtime is in the operator fault domain. The treasury/vault/CIP-7002 path can initiate an exit without custody of your signing key.Settlement
How settlement protects principal.
Rewards and exit proceeds flow through your WithdrawalVault under principal-first accounting: the Foundation recovers up to 32 CTN, and excess is allocated to the beneficiary wallet.Ready to run a seat