Validator considers itself synced before sentry is fully caught up #4721
Description
Validator considers itself synced before sentry is fully caught up
Description
When running a validator behind a sentry node in a private network :
- The validator quickly reaches the highest block height known by the sentry.
- It then switches to consensus mode and considers itself fully synced.
- However, the sentry is still catching up on blocks.
- The validator stops progressing and must be restarted to continue syncing.
Your environment
- OS and CPU architecture (example: debian 12)
*Docker Compose using the image: ghcr.io/gnolang/gno/gnoland:chain-test7 - Private network setup on Scaleway:
- Sentry node configured with both public and private IPs
- Validator node configured with only a private IP
Steps to reproduce
- Start a sentry node from scratch in a private network. .
- Start a validator node connected to this sentry.
- Observe the validator reaches the sentry’s current block height quickly.
- Validator switches to consensus while the sentry is still syncing.
Expected behaviour
The validator should continue syncing until the sentry is fully caught up, instead of assuming it is synced prematurely.
Logs
2025-09-03T13:35:16.887Z INFO Executed block {"module": "state", "height": 58003, "validTxs": 0, "invalidTxs": 0}
2025-09-03T13:35:16.887Z INFO Committed state {"module": "state", "height": 58003, "txs": 0, "appHash": "9C260DDAFE018AD17B823A9C1AC12CE87887D49132E9851A1A5A171B4EDE57D7"}
2025-09-03T13:35:17.364Z INFO Time to switch to consensus reactor! {"module": "blockchain", "height": 58004}
2025-09-03T13:35:17.364Z INFO Stopping BlockPool {"module": "blockchain", "impl": "BlockPool"}
2025-09-03T13:35:17.364Z INFO SwitchToConsensus {"module": "consensus"}