HotStuff Consensus Monitor

WHAT IT DOES

HotStuff Consensus Monitor gives you complete visibility into the live consensus state of any EVM-based HotStuff consensus contract. It reads and displays the current consensus contract state including the complete validator set with weights, current view and round numbers, the current leader or primary validator, pending blocks awaiting consensus, detailed vote tallies per block showing which validators have voted, commit certificates confirming finality, prepare certificates demonstrating quorum readiness, generic certificates for generic consensus messages, finalization status of the current height, block height tracking the blockchain level, chain configuration parameters, timeout values that trigger view changes, pacemaker state managing view progression, sync status for catching up, individual validator weights used for voting power calculations, quorum threshold parameters determining supermajority requirements, lock status indicating what the contract has committed, execution status showing block execution progress, safety rules state for consistency enforcement, quorum certificate data showing threshold crossing, view change messages tracking leadership transitions, consensus metrics including latency and success rates, and network parameters controlling protocol behavior. All data is organized in a clean dashboard with real-time updates, giving developers and protocol researchers deep insight into HotStuff consensus execution and certificate-chain management.

HOW TO USE

Connect your wallet to the tool and select the network where your HotStuff consensus contract is deployed. Enter the consensus contract address in the input field and click "Monitor Consensus". The tool immediately queries the contract using batched multicall to retrieve all consensus state variables in a single consistent snapshot. Results are displayed in organized cards showing the overall system state, validator roster, current view details, certificate chain information, and finalization status. The tool refreshes data on demand by clicking the Monitor Consensus button again. The tool works with any EVM HotStuff contract that implements standard view functions for validators, views, certificates, and quorum tracking.

THE MECHANISM

HotStuff Consensus Monitor uses a batched multicall pattern to fetch all consensus 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 weights and certificate counts might change between calls if a new proposal is committed mid-query. The tool constructs a single multicall transaction containing all required view functions including getValidators, currentView, pendingBlocks, prepareCertificates, commitCertificates, and quorumCertificate, 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. All certificate counts and quorum thresholds are computed with BigNumber precision to accurately reflect the supermajority requirements of HotStuff, and validator weights are summed and compared to thresholds using integer arithmetic to avoid precision errors. The tool also tracks the certificate chain by fetching prepare, commit, and generic certificate counts in sequence, providing a complete picture of the protocol's progress through its three phases.

WHAT IT CANNOT SEE

HotStuff Consensus Monitor cannot simulate actual network conditions or message propagation delays, as those require real network simulations. The tool cannot predict when consensus will finalize in real network conditions, as finalization depends on network timing and validator responsiveness. It cannot detect if validators are actually following the protocol or if they are equivocating (sending conflicting messages), as that requires cross-validator message comparison. The tool cannot verify the cryptographic signatures of messages without validator public keys, which are not stored in the consensus contract. It cannot prove that the consensus state is accurate without running a full consensus client and validating each message individually. The tool also cannot detect Byzantine faults or identify which validators are misbehaving, as that requires analyzing message patterns across multiple views and rounds.

PLEASE NOTE

HotStuff Consensus Monitor supports EVM-compatible chains only. It requires that the consensus contract implements standard view functions for the data displayed. Some HotStuff 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 consensus contract addresses from official sources before use.