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
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
Target: ~5 business days
Program team target to acknowledge application completeness and eligibility fit. Not a guaranteed turnaround.
Technical follow-up target
Target: ~7 business days
Program team target to complete follow-up questions, infra checks, and seat recommendation. Not a guaranteed turnaround.
Critical incident acknowledgment
Target: ~15 minutes
Target acknowledgment window for active-seat incidents that may threaten validator continuity. Best-effort; not a contractual SLA.
Incident update cadence
Target: ~60 minutes
Target update frequency during unresolved active-seat incidents until stability is restored. Best-effort; not a contractual SLA.
Planned upgrade notice
Target: ~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]
What you are observing.
When it started - UTC timestamp if possible.
What you have already tried.
Your hosting provider and client software versions.
Before you reach out
Self-service steps to try first.
Check your validator client logs first.
Confirm execution and consensus clients are fully synced.
Check announcements for known network issues.
Review FAQ for common questions on keys, onboarding, and exit behavior.
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 private key material. Report suspicious requests immediately.
Ready to run a seat