Admin guide

Every event in CryptoPOP has three layers:

• The event row — name, description, dates, geofence, and POP rewards.
• The signup page — public RSVP form people use ahead of time. Each signup mints 10 POP as a welcome.
• The QR poster — printed at the venue, scanned during the event to claim the main POP reward. Claims only succeed inside the geofence and inside the time window.

Admin → Events → New event. The important fields:

• Name & description — these show on the RSVP page (read live from the database, so you can edit them any time and the page updates).
• Cover URL — optional hero image for the RSVP page.
• Starts / Ends — the time window claims are accepted in. There's a USA preview underneath each input so you can sanity-check the date.
• Location & geofence — drag the pin to the venue. The radius (meters) sets how far from the pin a phone can be and still claim. 100–300m is typical for a building, 500m+ for a park.
• QR active before start (minutes) — lets early arrivals claim. 60 is common.
• Base POP reward — what each attendee gets for claiming at the event.
• Referral POP reward — bonus POP for inviting someone who signs up through your referral link.

Open the event from Admin → Events and hit QR poster. You get a printable poster with the event QR. A few rules of thumb:

• One poster per event. The QR encodes a signed token tied to the event — don't reuse one event's poster for another.
• Print it big. A4 minimum. Phones need a clean scan from 1–2m away.
• Place it where people congregate: registration desk, food line, near the speakers. Multiple copies is fine; same QR on each.
• QR + geofence + time window all have to match for a claim to succeed. If guests get "out of range" errors, widen the geofence radius in the event settings.
• Standalone codes — the Admin → Codes section is for ad-hoc single-use POP codes (gifts, prizes, raffle wins) that aren't tied to a specific event. Generate one per recipient.

• Admin → Signups — every RSVP across every event. Use this on the day to check in guests.
• Admin → CRM — unified contact view (email, phone, socials, history). Tags drive blast audiences.
• Admin → Wallets — TXC wallets we've spun up for guests who didn't bring their own. You can look up a wallet by email/address; the recovery flow lives at /recover-wallet for the guest themselves.

Every POP we owe — signup bonuses, claims, referrals, manual gifts — sits in Admin → POP awards as a row with a status:

• Pending — recorded in our database, not yet on the TXC chain.
• Sent — the on-chain mint succeeded; the recipient sees it in their wallet.
• Failed — the chain rejected it (bad address, fee issue). Retry from the row or fix the recipient's wallet and re-queue.

The dashboard shows totals for sent and pending so you can keep an eye on whether the mint queue is keeping up.

Admin → Rewards is where you set up activity-based rewards beyond the default signup/claim/referral. E.g. "follow on Instagram → 5 POP". Rules are self-serve — users complete the action in the app and POP is queued automatically.

• Admin → Blast composes and sends a campaign. Pick the audience by event, tag, or "everyone".
• Admin → Blast → History shows past sends, open/click counts, and bounces.
• Admin → Email templates manages the transactional emails (welcome, event confirmation, recovery). Edits go live immediately.
• All email sends use the verified notify.cryptopop.org domain. Replies go to hello@cryptopop.org.

1. 2 weeks out — create event, share RSVP link, print poster draft.
2. Week of — send a reminder blast to confirmed signups.
3. Day of — final poster printed, QR test-scanned, geofence radius double-checked on site.
4. During — keep Admin → Signups open at the door; watch POP awards for stuck mints.
5. After — reconcile pending awards, send a thank-you blast, tag attendees in CRM.