THE BACKGROUND WAS EMPTY.
LET'S
PUT CUPPY
ON THE MAP.
Draw Cuppy somewhere you're allowed to. Take a photo. Drop the city. The map starts with one mark.
01 FIRST
DRAW ANYWHERE
Draw Cuppy on paper, legal chalk walls, or any surface you have permission to use. Take a photo. Send it in.
- A one-page drawing guide
- Photo, city, and handle submission
- Human review before a sighting goes live
- A share card made for the timeline
WHAT CHANGESThe first public file of Cuppy sightings.
02 NEXT
THE PUBLIC MAP
Every approved sighting gets a pin. Open a city and see who left Cuppy there first.
- Sightings grouped by city
- A permanent file number for each approved post
- A weekly field note from the map
- Report tools and location privacy controls
WHAT CHANGESDrawings become a map the community can point to.
03 DESIGN / NOT LIVE
BURN A MARK
When the contract and public ledger are ready, a holder can burn $CUPPY to seal an approved sighting in the archive. Until then, this stays a design—not a promise.
- Verified burn transactions only
- Permanent archive marks for completed burns
- A public burn ledger with transaction links
- No burn button before the full path can be checked
WHAT CHANGESOne approved image, one burn transaction, one receipt anyone can open.
04 AFTER THE FIRST CITY
THE TABLE GOES OUTSIDE
A drawing day becomes the working model: a table, a field zine, approved walls, and an archive drop. The next city earns its turn by organizing.
- A first-city pilot with a published recap
- City plates and printed field notes
- A reusable host kit for the next city
- The next city chosen from real submissions
WHAT CHANGESA repeatable city kit—not a list of vague partnerships.
THE LOOP EARNS TRUST ONE RECEIPT AT A TIME.
NO RECEIPT.
NO BURN CLAIM.
- ROUTEWhich product revenue enters the loop.
- WALLETWhich wallet buys and which address burns.
- RECEIPTEvery buyback and burn linked onchain.
- CADENCEA clear schedule before the first cycle.