Consensus Participation

What are Consensus Participation alerts?

• According to the Algorand Pure Proof-of-Stake protocol, addresses that are online and hold a stake in the network are expected to participate in the consensus mechanism. Participation takes the form of block proposals and votes. Oftentimes, issues such as a misconfigured node, expired key, or network problems can cause an address to fail to cast the expected number of votes determined by its stake in the network. To inform account owners about such issues, we provide two types of alerts:

  1. Address that usually votes is not casting any votes

  2. Address that usually votes is not casting the expected number of votes

How are voting alerts triggered?

• Consensus Participation alerts get triggered on an hourly basis. Once our algorithm determines that an address that usually votes is not voting or is not voting at the expected level for the past hour, an alert will be triggered.

What notifications will I receive?

• You will receive a single email notification per address you are subscribed to informing you when any voting issue has started. If the issue persists every hour, you will not receive any additional notifications, but its status will remain “Firing” in the Metrika platform.

• Once the issue is resolved, you will receive a single email notification informing you about the resolution of the voting issue.

How do I resolve it?

• There may be various root causes causing this alert. Here are some recommended checks on your account’s health to identify the potential issue:

  1. If you’re not casting any votes, check that the participation key has not expired.

  2. Check that the server works.

  3. Check that the node is on the correct network, and whether the node is fully synced or catching up.

  4. Check that the software is the latest version. Get the algod version of your node with the command algod -v.