Verify Discord Voice Attendance Records

AttendiBot signs every completed voice session with Ed25519. Verification proves the record matches what the server signed — it was not edited after the fact.

Online verification (fastest)

Use the public verifier on attendibot.com/#verifier:

1. Copy a session UUID from Discord log embeds or the dashboard
2. Paste it into the verifier
3. Confirm Signature valid and review duration, channel, and timestamps

No login required. This is the easiest way for members to settle disputes.

Verify inside Discord

Admins with Manage Server can run:

• /admin verify_session — check a single session signature
• /admin verify_period — check an archived period snapshot

See Commands for parameters.

Offline verification (Pro exports)

Pro servers can download signed period export bundles from the dashboard. Each bundle includes:

• Period payload JSON
• Ed25519 signature
• Offline receipt material for independent verification

Follow Independent verification for CLI and tooling steps.

Transparency log proofs

Pro tier also supports transparency log inclusion proofs for advanced audit workflows. See Signing & verification and Independent verification.

What verification does not prove

Verification confirms integrity (the record was not tampered with). It does not prove:

• The member was actively studying (use fairness rules and community norms)
• Audio content (AttendiBot never records voice — metadata only)

Configure fairness and tracking to match your server's expectations.

Troubleshooting invalid signatures

If verification fails after a deployment or key rotation:

1. Check signing status in the dashboard
2. Run Repair period snapshots (dry run first) for archived periods
3. See Troubleshooting

Support is available via the link in the site footer once your support Discord is configured.