guardiand v2.5.1

No backwards incompatible changes (unless you're using Infura, which nobody should do anyway).

New features:

• Batched governance message submission.
  A governance prototxt file can now include multiple messages. This significantly improves the workflow when multiple governance votes are submitted at the same time.

• The guardiand template command has been revamped to support generating full governance VAAs. This makes it easier and less error-prone to produce governance proposals.

• Complain about Infura on mainnet.
  As it turns out, Infura has a bug where it would sometimes incorrectly round block timestamps, which causes consensus issues - the timestamp is part of the VAA and nodes using Infura would sometimes derive an incorrect VAA, accidentally attacking the network by signing a conflicting VAA.

  Node operators do not usually rely on Infura in the first place - doing so is less secure than using your own nodes, since nodes blindly trust the connected nodes to verify on-chain message proofs. Node operators sometimes used Infura as a workaround during migrations where their primary node was offline, causing the aforementioned consensus oddities which were eventually found to be Infura-related. This is generally to the detriment of network security and a judgement call made by individual operators. In the case of Infura, we know it's actively dangerous so we add a warning to make sure that future operators know about the issue before considering to use Infura.

Bugfixes:

• The /readyz endpoint on the status server now correctly reports a failure of BSC or Polygon.