verified launches.

both are allowed. one is verified. the other isn't.

how to ship a verified launch

1. at mint time, oauth with the identity you're crediting.
2. successful oauth proves you control it right now.
3. token mints with verified = true baked into on chain metadata.
4. wherever the token shows up (our ui, dexes, trackers), it carries a small verified ✓ next to the identity.

skip the oauth and the token still launches. fees still route correctly. the identity is still public. it just doesn't get the flag.

what verified means

• the named identity ran the launch at mint time.
• fees route to that same identity's wallet (or escrow until they connect one).

what verified does not mean

• the token is a good investment. nothing makes that true.
• the team is doxxed.
• anyone is endorsing anything beyond “yes, this one is mine.”

can i verify retroactively

no. if someone credited your handle without your knowledge, you can still claim the fees (see claimable escrow). but the token stays unverified. the flag is bound to launch time oauth, full stop. otherwise it'd be trivial to fake.