CenturionValidator Program

Centurion Seat Program

Bring your BLS key. Run a funded validator seat.

You operate validator infrastructure and keep validator signing keys. The Foundation validates your pubkey + deposit data, funds the 32 CTN principal, and rewards plus exit proceeds settle through your WithdrawalVault.

See how it works
Apply Now
Console Preview
Illustrative

Validator

Validator Pubkey0x8a3f…c917
WithdrawalVault0x4e1b…a203
Principal32 CTN
Key CustodyOperator

Checks

Withdrawal CredentialsPending
Deposit Data ValidityPending
Allowlist EntryPending
Deposit ConfirmedPending

Lifecycle

Applied

Eligible

Data Submitted

Validated

Allowlisted

Deposited

Seen by CL

Active

Events

Waiting for first event...

32 CTNSeat Principal
Operator-HeldKey Custody
Vault PolicyReward Claims
Vault + 7002Exit Request

Program Operations

Current intake and response targets.

These targets define application triage cadence and incident-response expectations for active external seats.

Intake Mode

Rolling cohort intake

Applications are reviewed continuously and seats are assigned in reliability-scored cohorts.

Initial Review Target

5 business days

Program team target to acknowledge application completeness and eligibility fit.

Technical Follow-up Target

7 business days

Program team target to complete follow-up questions, infra checks, and seat recommendation.

Critical Incident Acknowledgment

15 minutes

Target acknowledgment window for active-seat incidents that may threaten validator continuity.

Incident Update Cadence

60 minutes

Target update frequency during unresolved active-seat incidents until stability is restored.

Planned Upgrade Notice

72 hours

Target notice window for required client upgrades except emergency network-security events.

From Application to Rewards

External operator flow, end to end.

From eligibility review to key generation, data submission, validation, funding, activation, and settlement, each step keeps key custody with the operator.

  1. 1Intake

    Apply

    Submit your operator profile, infrastructure plan, and validator operations experience.

  2. 2Eligibility

    Review & Eligibility

    Centurion reviews reliability, client diversity, and policy fit before assigning a seat.

  3. 3Key Setup

    Generate BLS Keypair

    You generate and keep your validator BLS signing keypair in your own environment. The Foundation does not receive the private key.

  4. 4Submission

    Submit Pubkey + Deposit Data

    You submit the validator public key and deposit data prepared for your seat's vault-bound withdrawal credentials.

  5. 5Validation

    Validate & Allowlist

    The Foundation validates the submitted deposit data against seat assignment, withdrawal credentials, and allowlist policy.

  6. 6Funding

    Foundation Funds Deposit

    After validation, the Foundation submits the 32 CTN deposit transaction for your seat.

  7. 7Active

    Validator Activates

    After deposit inclusion and activation-queue processing, your validator becomes active and begins attesting/proposing under your operational control.

  8. 8Settlement

    Rewards, Claims, and Exit

    Rewards and exit proceeds are governed by your WithdrawalVault. Claims follow vault policy, and the treasury can initiate an exit request through the vault/EIP-7002 path when needed, with final exit timing still governed by consensus-layer rules.

Roadmap

Where the program is going.

Centurion's validator program rolls out in phases. Phase 1 is live, Phase 2 is in active build, and Phase 3 sets the target for program maturity.

Phase 1

Complete
Foundation
  • External BYO-BLS seat model live
  • WithdrawalVault contracts deployed
  • EIP-7002 exit request path active
  • Cohort 1 seats funded and attesting

Phase 2

Active
Expansion
  • Cohort 2 and 3 intake open
  • Operator console with seat status dashboard
  • On-chain explorer for vault inspection
  • Slashing and fault reporting tooling

Phase 3

Planned
Maturity
  • Multi-seat operator management in console
  • Automated upgrade notification system
  • Program rules published on-chain
  • Security audit published

Why Centurion Seats

Capital from the Foundation. Signing authority from you.

The public model removes shared key custody. External operators retain BLS signing control while Foundation systems handle onboarding validation and treasury-side flows handle allowlisting and principal funding.

Foundation-funded principal
The Foundation funds the 32 CTN validator principal for each approved seat. Operators provide infrastructure and execution.
Operator-owned BLS keys
External operators generate and retain validator BLS private material. The Foundation does not generate, store, export, retain, or regenerate those keys.
Vault-bound withdrawal economics
Each seat settles through a dedicated WithdrawalVault with beneficiary claims during normal operation and principal-first accounting during exit settlement.
Exit-request control without shared custody
Treasury-side exit control comes from the vault, treasury controls, and EIP-7002 request path, not from shared signing-key custody. The request can be initiated unilaterally, but consensus-layer eligibility and queue timing still govern completion.

Get Started

Ready to run the external BYO-BLS seat flow?

Use the published application path to start seat intake. Deployments with a dedicated console route this path automatically; otherwise it falls back to direct operator onboarding contact.

Apply Now
Read Seat Model