Badge issuance playbook

Intermediate · 12 min read

Step-by-step workflow to issue proof-of-attendance badges with verifiable metadata.

Badge definition

Define the badge as proof of a completed action: attendance, course module, volunteer hours, or workshop participation. Name the issuer, the event, and the date range.

Write a one-sentence purpose with no financial claim. Example: “Confirms the holder completed the 2026 Community Builder workshop.”

Metadata checklist

Minimum fields: badge_id, event_name, issuer_name, issued_at, recipient_ref (hashed email or public handle — not secrets), network (testnet first), transferability (prefer non-transferable), disclaimer_url.

Optional: skill tags, score band (pass/fail only unless needed), verification endpoint, schema_version.

Issuance flow

1) Collect consent to issue a public or semi-public record. 2) Confirm eligibility (attendance list). 3) Generate a mock payload in sandbox. 4) Review compliance preflight. 5) Only then consider any real tooling — still non-custodial, still no trading UI.

Keep humans in the loop for first launches. Agents can draft metadata; they should not silently mint or move value.

Verification guide

Publish a verify page that shows issuer identity, event name, issue time, and the disclaimer. Do not surface wallet keys or private recipient data.

Document how a third party checks authenticity without trusting a single screenshot. Prefer signed metadata schemas and public issuer keys over “trust this PNG.”

Checklist