Support

Contact and response expectations for active seat operators.

Use the program contact channel for onboarding questions, incident escalation, and upgrade coordination. Review self-service steps before reaching out.

Contact

One channel for all program communication.

Program contact
validator-program@centurion.network

Use this address for:

Seat applications and eligibility questions

Onboarding support and deposit data submission

Seat status and assignment notifications

Upgrade coordination and technical follow-up

Active-seat incident escalation

Response Targets

Operational expectations before and after seat assignment.

These targets define how applications are triaged and how active-seat incidents are handled.

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.

Incident Reporting

For active-seat incidents, format your report clearly.

How to report an incident

Email validator-program@centurion.network with the subject line:

INCIDENT: [your validator pubkey — first 12 characters]

Include in the body:

What you are observing (missed attestations, client crash, sync issue, etc.)

When it started — UTC timestamp if possible

What you have already tried

Your hosting provider and client software versions

The program team targets 15-minute acknowledgment for active-seat incidents. Response may be slower outside business hours.

Before You Reach Out

Self-service steps to try first.

1

Check your validator client logs first — most connectivity and signing issues surface there.

2

Confirm your execution and consensus clients are fully synced and not stuck.

3

Check the Announcements page for any known network issues or active incidents.

4

Review the FAQ for common questions on keys, onboarding, and exit behavior.

5

Review the Docs runbook for monitoring and upgrade procedures.

Never send over email

Validator BLS private keys or keystore JSON files

Validator mnemonic phrase or seed words

EVM wallet seed phrase or private key

The program team will never ask for any of the above. If you receive a request for private key material from anyone claiming to represent Centurion, do not comply and report it immediately.

Ready to Run a Seat

Apply for an external validator seat.

No token purchase required. You provide infrastructure and key custody. The Foundation funds the 32 CTN principal after approval.