1. Infrastructure
Bare-Metal, Not Shared Cloud
Validator workloads run on dedicated servers in professional colocation
facilities. The goal is to reduce shared-failure risk, keep performance
predictable, and maintain direct control over the hardware path.
2. Redundancy
Primary and Standby Design
Low Fee Validation maintains a primary validator and a standby validator.
This architecture supports controlled failover and maintenance operations
without relying on a single machine or a single maintenance window.
3. Monitoring
Health Checks and Alerts
Operations are monitored through validator health, sync status, RPC health,
slot lag, and external networking checks. Network transport used for
validator performance is also verified after upgrades and incident recovery.
4. Change Management
Updates Are Applied in Stages
Software changes are first prepared on the standby path. Synchronization and
validator health are verified before controlled migration. The peer node is
only updated after the new active side is confirmed healthy.
5. Operations
Consensus Safety Comes First
Operational procedures prioritize avoiding double signing, validating health
before and after migration, and keeping rollback paths ready. When there is
uncertainty, changes are paused until the validator state is clearly safe.
6. Incident Response
Recover, Verify, Then Proceed
If a transport, software, or sync issue is detected, the response flow is to
restore healthy validator communication, confirm service health, and only then
continue with maintenance. This reduces the chance of compounding faults during
live operations.