Validators
NO-ACK Checkpoint Troubleshooting
Use a structured process to investigate NO-ACK checkpoint outcomes without restarting unrelated services.
In this guide
Practical outcomes
- Collect state evidence
- Check acknowledgement path
- Apply scoped recovery
How this works in practice
Use a structured process to investigate NO-ACK checkpoint outcomes without restarting unrelated services.
Validator operations rely on separate but connected layers: Bor must execute and produce blocks, Heimdall must coordinate validator state and spans, and the checkpoint path must submit and acknowledge commitments on schedule.
Implementation sequence
Turn the topic into a controlled implementation rather than a one-off transaction. Each step below should leave evidence a teammate, user or auditor can independently review.
- 01. Collect state evidence. Define the expected result, capture the relevant onchain or operational evidence, and stop for review if the result differs from the plan.
- 02. Check acknowledgement path. Define the expected result, capture the relevant onchain or operational evidence, and stop for review if the result differs from the plan.
- 03. Apply scoped recovery. Define the expected result, capture the relevant onchain or operational evidence, and stop for review if the result differs from the plan.
Evidence to retain
When investigating an incident, capture block height, sync state, peers, relevant process logs, checkpoint age, transaction hashes and the exact time window before restarting anything.
Control point
Use scoped recovery. A delayed checkpoint does not automatically justify restarting unrelated services. Classify the fault first, protect keys and state, then make the smallest change that restores the affected path.
Related guides
Ramestta Validator Requirements
Review the operational, infrastructure and security expectations before participating in the Ramestta validator network.
Validator Hardware and Capacity Planning
Plan reliable node resources, storage, networking and redundancy for validator and supporting infrastructure.
Validator Monitoring Guide
Monitor validator health across node processes, disk, peers, RPC, block production, signatures and checkpoints.