Day 0 checklist
All items are pending unless supported by recorded evidence. Preparing this document does not authorize a live token transaction or public announcement.
Owners
| Role | Owner | Evidence / contact |
|---|---|---|
| Launcher | @nobudgetw | X |
| Independent verifier | Unassigned (community verification) | How to verify |
| Publisher | @nobudgetw | X |
| Security watch | @nobudgetw | X |
| Comms lead | @nobudgetw | X |
This is a one-person project, so no one independent of the launcher holds the verifier role. Wherever a step calls for Verifier sign-off, the launcher performs it as a self-check: run npm run token:verify, compare the address in an explorer, and record the UTC time and the evidence. Every such record is labeled self-checked, not independent. Anyone can repeat the same checks with the public verification guide. Please report any mismatch through the official channels.
Before launch
- Read current official sources using source verification.
- Confirm jurisdiction review, fees and separately authorized launch scope.
- Record role owners and incident channel.
- Configure and verify domain, official social channels, 2FA and access recovery.
- Review metadata, image, name/ticker and risk copy.
- Verify 0% founder/team allocation, no presale, VC or private round in the chosen flow.
- Rehearse publication, wrong-address recovery and scam-alert deployment. Review the announcement drafts with
npm run content:announce -- --preview. - Run website checks and production build.
At an authorized launch
- Launcher records outcome and public transaction evidence.
- Verifier compares exact mint address independently with explorer and platform.
- Record supply, decimals, token program and observed authority states.
- Add verified address, links and creator public wallet to central config.
- Review the config diff with a second person and run all checks.
- Publisher deploys the approved config and verifies copy/explorer behavior.
- Render announcements from the deployed config with
npm run content:announce -- --out artifacts/content/day-0-announcements.md(refused unless status isliveand X is inverifiedChannels). Never type or paste the address by hand. - Approved X and community announcements match the exact same address.
Follow-through
- Check impersonation and incorrect metadata.
- Record a first transparency log with sources; leave unavailable metrics unknown.
- Check remaining questions, disclosure corrections and incident reports.
- Confirm only verified listings or pools are described publicly.