{"ok":true,"version":"2026.07.15.12","data":{"id":"case-study-event-badges","title":"Case study: event badge rollout","type":"Case Study","level":"Intermediate","readTime":7,"summary":"How a community program shipped verifiable badges without financial claims.","tags":["case-study","badges","community"],"outcomes":["See a safe launch timeline","Learn what copy avoided","Measure engagement lifts"],"outline":["Goal and scope","Implementation notes","Outcome metrics"],"cta":"Review the case study","path":"/library/case-study-event-badges","hasFullBody":true,"body":{"sections":[{"heading":"Goal and scope","paragraphs":["A community workshop wanted proof-of-attendance for 120 builders. They rejected any marketplace, price, or “early investor” framing. Success metric: 70%+ of attendees claimed a badge within 48 hours and zero support tickets about wallets losing funds."]},{"heading":"Implementation notes","paragraphs":["They ran the full flow on testnet first using this hub’s sandbox payload pattern. Metadata used hashed emails, event slug, and a public disclaimer URL. Issuance required checking a checkbox: “I understand this is not money or an investment.”","Copy review removed “mint,” “drop,” and “floor price.” They used “issue attendance record” instead."]},{"heading":"Outcome metrics","paragraphs":["Claim rate: 78%. Support tickets about keys: 0. Legal review time: half a day because the design was non-transferable and non-financial. Lesson: clear scope beats flashy chain features."]}]}}}