Liveness Detection Tool

WHAT IT DOES

Liveness Detection Tool gives you complete visibility into the liveness status of validators on any EVM-based blockchain. It reads and displays current validator heartbeat records showing when each validator last responded, last seen timestamps for each validator, validator signature counts tracking how many blocks each validator has signed, block proposal history showing which validators have proposed blocks, block signing history tracking signature participation, validator participation rates calculating the percentage of blocks signed, missed blocks count for each validator, validator uptime percentage over recent windows, recent block production intervals showing network health, validator response times measuring latency, the active validator set currently participating, validator status flags indicating active, jailed, or slashed states, epoch transition records tracking changes between epochs, consensus event logs showing protocol transitions, heartbeat event logs recording validator check-ins, validator reward history showing earnings, validator penalty events for missed duties or misbehavior, validator jail status indicating temporary exclusion, validator activation status for new entrants, validator exit records for validators that have left, consensus round participation tracking round-level activity, block finalization events confirming chain finality, and validator network latency estimates from response patterns. All data is organized in a clean dashboard with validator-level status indicators, uptime percentages, and risk classifications.

HOW TO USE

Connect your wallet to the tool and select the network where your validator liveness tracking contract is deployed. Enter the validator contract address in the input field and click "Detect Liveness". The tool immediately queries the contract using batched multicall to retrieve all liveness state variables in a single consistent snapshot. Results are displayed in organized cards showing the overall system status, current epoch, active validator count, aggregate uptime and participation metrics, and detailed validator-level information including last heartbeat timestamps and missed blocks. The tool refreshes data on demand by clicking the Detect Liveness button again. The tool works with any EVM validator contract that implements standard view functions for heartbeat tracking, uptime, and participation monitoring.

THE MECHANISM

Liveness Detection Tool uses a batched multicall pattern to fetch all liveness state variables in a single RPC request, ensuring that every piece of displayed data comes from the exact same block height. This prevents inconsistencies that would occur if separate calls were made — for example, validator heartbeat timestamps and participation rates might change between calls if a new block is produced mid-query. The tool constructs a single multicall transaction containing all required view functions including getHeartbeat, getUptime, getParticipationRate, getMissedBlocks, and getJailStatus, sends it to the provider, and decodes the aggregated response. If the multicall fails due to provider limits or timeouts, the tool automatically falls back to individual calls, then reconciles results by block number, discarding any data that comes from a different height than the majority. The tool also implements automatic retry with exponential backoff for each call attempt, because public RPC endpoints frequently timeout or reject large batch requests. For heartbeat timestamps, the tool converts Unix timestamps to human-readable dates and computes time since last heartbeat to identify potentially offline validators. Uptime percentages are computed from the ratio of successful duties to total assigned duties, and participation rates are calculated from signature counts against expected signatures. The tool also computes average response time by analyzing the time difference between heartbeat records, providing latency estimates for each validator.

WHAT IT CANNOT SEE

Liveness Detection Tool cannot detect if validators are physically online or just automated scripts, as both would produce the same heartbeat signatures. The tool cannot determine if a validator is running the correct software version or has been compromised, as version information is not recorded on-chain. It cannot detect network partitions that may affect validator connectivity, as partitions are not visible from contract data. The tool cannot verify that heartbeat signatures are generated by the actual validator key and not by a malicious actor, as signature verification requires consensus client validation. It cannot predict future liveness or guarantee that currently active validators will remain responsive, as liveness is inherently unpredictable. The tool also cannot detect if a validator is intentionally not participating or simply experiencing network issues, as the cause of missed blocks is not recorded.

PLEASE NOTE

Liveness Detection Tool supports EVM-compatible chains only. It requires that the validator contract implements standard view functions for the data displayed. Some validator contracts may use custom function names or data structures not covered by the default ABI — users can adapt the tool by modifying the ABI definition in the script. The tool is read-only and does not modify any contract state or initiate transactions. It is free to use and does not store or transmit any data off-device. Always verify validator contract addresses from official sources before use.