verify package is intentionally minimal: it has zero non-stdlib dependencies.
Any auditor can run it without installing CometBFT, cloud KMS SDKs, or ZK libraries. It is the
independent verification artifact — the thing you hand to a third-party auditor.
BuildSigningPayload
state.executePollClose — it produces an identical
payload that can be verified against the stored tally signature.
VerifyECDSA
crypto/x509.ParsePKIXPublicKey — no external dependencies.
End-to-end verification
What verification proves
A valid tally signature proves:- The counts, total votes, and Merkle roots were not modified after poll close
- The signing key was the managed signer registered for this deployment (public key on record)
- The Merkle roots commit to the exact set of ballot IDs (List 1) and identity hashes (List 2) at the time of close
ConfirmedCount metric provides.