Consensus Protocol Tester
Free to download on every platform. Comes pre-installed on BotFone, BotPad and BotFlip — with extra free apps included.
About this app
WHAT IT DOES
Consensus Protocol Tester gives you direct visibility into the live consensus state of any EVM-compatible blockchain that exposes consensus-related contract data. It retrieves and displays the current validator set, active committee assignments, ongoing epoch and round information, finalized block numbers, proposal data from the current and recent rounds, vote counts per proposal, and all consensus parameters such as block gas limits, minimum validator stake, slashing conditions, and chain configuration values. You can inspect the current leader or proposer for any given round, see which validators are online and participating, and track how votes are distributed across proposals in real time. The tool also surfaces historical finalized blocks and lets you compare committee assignments across epochs to detect rotation patterns or anomalies.
HOW TO USE
Connect the tool to any supported EVM chain by providing an RPC endpoint and the address of the consensus contract you wish to inspect. Once connected, the interface displays a dashboard with tabs for each major data category: Validator Set, Epoch/Round, Finalized Blocks, Proposals, Votes, and Parameters. You can click on any validator address to see its voting history and participation rate. Use the timeline controls to step through past epochs and rounds to review historical consensus data. Export any view as JSON for offline analysis or integration with other monitoring tools. The tool refreshes data automatically every few seconds but also provides a manual refresh button for on-demand checks.
THE MECHANISM
Consensus Protocol Tester works by aggregating on-chain data from multiple contract views and events in a single coordinated query pipeline. Instead of making separate RPC calls for each piece of data — which would quickly hit rate limits and produce inconsistent snapshots due to state changes between calls — the tool batches all required view functions into a single multicall transaction. This guarantees that every piece of data in a given dashboard view comes from the exact same block height, ensuring consistency across validator sets, proposal states, and vote counts. The tool also implements automatic retry with exponential backoff for each multicall attempt, because public RPC endpoints frequently timeout or reject large batch requests. If a batch call fails, the tool falls back to individual calls for each data item, then reconciles the results by block number, discarding any items that come from a different height than the majority. This hybrid approach makes the tool reliable even on congested or unreliable RPC endpoints, and it works without requiring archive node access or special API keys.
WHAT IT CANNOT SEE
Consensus Protocol Tester cannot verify the correctness of consensus decisions without running a full node — it only reports what the contract states, not whether those states are valid according to the underlying consensus rules. It cannot detect if validators are colluding or voting maliciously, because collusion and intent are off-chain activities that do not appear in contract storage. It cannot prove the validity of proposed blocks without executing them, which is outside the tool's scope. It cannot detect network partitions or liveness issues, because those conditions are visible only from the perspective of a node participating in the network's gossip layer. It cannot verify the cryptographic signatures of votes without validator public keys, which are not stored in the consensus contract itself. It also cannot predict future committee assignments or propose any changes to the consensus configuration — it is a read-only inspection tool.
PLEASE NOTE
Consensus Protocol Tester supports EVM-compatible chains only. It requires that the target chain exposes consensus contract data via standard Solidity view functions and events. Some chains may use custom contract layouts or non-standard interfaces; those are not supported unless the user provides an ABI mapping. The tool is free to use and does not store or transmit any data off-device.