$ZERO Launch Guide — fast launch on Jupiter Studio, credibility track after

Version: 1.0 — 9 September 2026 Strategy: Launch quickly and cleanly on Jupiter Studio (permissionless, no-code), then apply to ecosystem programs for funding and support once the token is live and there's something to show.

0. How to read this guide

Every step is tagged with who does it:

• YOU — needs your wallet, your money, or your identity. Only you can do these.
• CLAUDE — I produce it; you review and approve.
• TOGETHER — I draft, you decide.

Total time on your side, spread over roughly two weeks: about 6–8 hours, most of it in Phase 1 (prep). Launch day itself is under an hour.

Important: Jupiter Studio's exact screens, limits, and options change. Everything below reflects what's documented as of September 2026. Before launch day, we re-check the current Studio interface together and adjust.

1. The stack (why these sites)

What Studio gives you for free that we'd otherwise have to build: fixed 1B supply (no mint authority to abuse), creator vesting with cliff enforced on-chain, 50% of LP locked for a year at graduation, anti-sniper fee (99% decaying to 0% over a random 15–60 seconds), token page with your updates shown to traders on jup.ag, and instant tradability through the Jupiter aggregator.

2. Tokenomics adjusted to Studio's constraints

Studio fixes some things. The white paper needs to match them exactly or it reads as a broken promise.

Recommended split of the 25% creator allocation (all of it vests together — Studio doesn't split it, so the split is a published commitment you enforce via Squads/Streamflow after unlock):

The airdrop timing problem — a decision for you (TOGETHER): The creator allocation is locked for the 6-month cliff. So the airdrop pool can't be distributed from it until month 7. Two options:

• Option A — Airdrops start month 7. Simple, fully consistent with vesting. Subscriber sign-ups before then earn a claim that pays out once tokens unlock. Streamflow can schedule this.
• Option B — Seed an early airdrop from a public-curve buy. On launch day, the treasury wallet buys a small amount on the bonding curve (say 0.5–1% of supply) at the same public price as everyone else, and that becomes the first airdrop round. Fully transparent because the buy transaction is public, and it lets you drive website traffic in week one.

I recommend B for a small first round plus A for the main pool. Either way the white paper states it plainly.

Why 25% and not higher: anything much above 30% starts to look like an insider-heavy launch even with vesting. 25% is defensible: three-quarters of supply goes to the public at one price.

3. Phase 1 — Prep (Days 1–7)

3.1 Wallets and treasury — YOU

1. Create a dedicated deployer wallet. Phantom or Backpack, brand new, not your everyday wallet. Whichever wallet launches on Studio is the one that claims creator fees forever and receives the vested allocation, so this wallet is permanent infrastructure. Write the seed phrase on paper, two copies, two locations. A hardware wallet (Ledger) is worth it here.
2. Fund it with 3–5 SOL. Covers Studio launch, Squads setup, Streamflow fees, an optional launch-day treasury buy, and transaction fees with margin.
3. Create a Squads multisig at squads.so. If you're solo right now, set it up as 1-of-1 but structured so you can add signers later; if you have a collaborator you trust, 2-of-2 or 2-of-3 from day one. This is the treasury wallet you publish.
4. Send me the public addresses (never the seed phrase) of the deployer wallet and the Squads vault. I'll put them in the white paper and site.

3.2 Token identity — TOGETHER

Decide and lock:

• Name: ZeroState (or "ZeroState Token")
• Symbol: $ZERO — check on jup.ag search that nothing prominent already uses it; if taken, fallback options: $ZST, $ZSP, $ZSTATE
• Token image: 512×512 PNG, works at 32px
• Header banner for the Studio token page
• One-paragraph description and social links (site, X, GitHub)

I'll draft the description and produce image specs; you approve or supply your own artwork.

3.3 Documents — CLAUDE

I produce, you review:

1. White paper v2 — updated to match Studio's fixed supply, 25/75 split, 12-month/6-month-cliff vesting, airdrop option chosen above, 1% fee, LP lock. Published as PDF + web page.
2. Tokenomics one-pager — the table above, wallet addresses filled in.
3. Website token page — mint address (added after launch), links to: Studio page, Solscan, LP lock tx, Squads treasury, white paper, airdrop claim form, GitHub access instructions.
4. Subscriber airdrop form — collects email + Solana wallet address, exports CSV in Streamflow's format. (This is the one small piece of code still needed.)
5. Launch announcement copy — X thread, newsletter email, site banner.
6. First treasury report template — so the "public treasury reporting" promise starts in week one.

3.4 Launch-week milestone — YOU

Line up one visible thing that isn't a promise. Any of:

• A 60–90 second demo video of Companion's software core running offline
• A photo/video of the Hearth prototype in a real nursery
• The Hoplings repo (or a sanitised subset) live and gated behind $ZERO on GitHub

This is what makes the launch read as a builder funding a real project rather than a token looking for a story.

3.5 Legal check — YOU

Fifteen minutes with a lawyer who knows UAE virtual-asset rules (VARA covers Dubai; ADGM/FSRA covers Abu Dhabi; Fujairah falls under federal SCA rules). The questions to ask: does a utility/access token launched permissionlessly on a DEX, with no presale and no promise of returns, trigger a licensing requirement for me personally? I'm not a lawyer and this is the one step I can't substitute for.

4. Phase 2 — Launch day (Day 8; under one hour)

Do this on a desktop browser with the deployer wallet, not on mobile.

4.1 Studio launch — YOU (I'll be on a call or in chat with you step by step)

1. Go to studio.jup.ag and connect the deployer wallet.
2. Choose Custom mode (not Meme — Meme is preconfigured and won't give you vesting control).
3. Enter token info: name, symbol, image. Don't use the "Magic Gen" auto-generator.
4. Configure:
   • Quote token: SOL
   • Creator vested allocation: 25%
   • Vesting: 12 months, daily unlock
   • Cliff: 6 months
   • Market-cap / graduation target: we'll pick this together the day before based on what's realistic; a lower graduation threshold means liquidity moves to the real pool sooner.
5. Upload the header banner, paste the description, add social links.
6. Review screen — stop here. Screenshot it and send it to me. I check every number against the white paper. Vesting cannot be changed after this point.
7. Confirm and launch. Token is live on the bonding curve immediately.
8. Copy the mint address and the launch transaction signature. Send both to me.

4.2 Optional treasury buy — YOU (only if Option B chosen)

Within the first few minutes — but after the anti-sniper window (wait at least 60–90 seconds so you're not paying the 99% fee yourself) — buy the agreed small amount on the curve from the Squads treasury wallet, not the deployer. Send me the transaction signature; it goes on the site as the first airdrop reserve.

4.3 Go public — CLAUDE drafts, YOU posts

Within the hour of launch:

• Post the launch update inside Studio (it shows on the token's jup.ag page) — mint address, vesting summary, link to white paper.
• X thread, newsletter, site banner — all pre-written, you paste and send.
• Update the website token page with mint address and links (I'll have it staged; you flip it live, or give me deploy access and I do it).

5. Phase 3 — First week after launch (Days 8–15)

5.1 Verification and listings — CLAUDE prepares, YOU submits

These are free, all wallet- or form-based, and are what buyers check:

5.2 GitHub gating — YOU sets up, CLAUDE writes the rules

1. Create a free account at guild.xyz, sign in with the deployer wallet.
2. Create a guild "ZeroState", connect the GitHub platform and authorise your GitHub org.
3. Add a requirement: Solana token balance ≥ X $ZERO (mint address). I'll recommend the threshold — low enough that a normal subscriber can qualify, high enough to mean something.
4. Map that requirement to repo access for the gated repos.
5. Link the Guild join page from the website.

5.3 Airdrop pipeline — CLAUDE builds, YOU runs

1. Subscriber form is live (built in Phase 1).
2. For each airdrop round: I export the verified wallet list as CSV → you upload it to Streamflow Airdrops from the treasury wallet → Streamflow creates a claim page → subscribers claim from your site. Traffic loop achieved.
3. Option B round runs in week one; Option A rounds start month 7.

5.4 First treasury report — CLAUDE drafts, YOU publishes

A one-page report, day 14: launch tx, mint, vesting schedule with unlock dates, treasury balance, fee revenue so far, airdrop round 1 details, what's being spent on what. Recurring monthly. This is the single most persuasive anti-pump-and-dump artefact you'll have, because it's boring and verifiable.

6. Phase 4 — Credibility and funding track (Weeks 3+)

All of these are compatible with an already-launched token. Sequence by effort and fit:

Not worth pursuing after launch: Xcombinator, CoinList, Solanium, StarLaunch — they are launch venues, and the launch has already happened.

7. Workflow summary — who does what

8. Budget

Fiat costs outside crypto: lawyer consult; audit later (typically low four figures USD for a small scope).

9. Launch-week checklist

Before pressing launch

• ☐ Deployer wallet backed up, funded
• ☐ Squads vault created, address published
• ☐ Symbol confirmed available
• ☐ Artwork + banner final
• ☐ White paper v2 published, matches Studio settings exactly
• ☐ Site token page staged (mint address blank)
• ☐ Airdrop form live
• ☐ Milestone asset ready (demo video / pilot / repo)
• ☐ Announcement copy approved
• ☐ Legal check done
• ☐ Studio review screen screenshot sent to me and checked

Launch hour

• ☐ Launch on Studio (Custom, 25%, 12m, 6m cliff, SOL)
• ☐ Mint address + tx to me
• ☐ Treasury buy after anti-sniper window (if Option B)
• ☐ Studio update posted
• ☐ X / newsletter / site live

Days 1–14

• ☐ Metadata verified, DexScreener, CoinGecko, CMC submitted
• ☐ Guild live, gated repo tested with a real wallet
• ☐ Airdrop round 1 (if Option B)
• ☐ First treasury report published
• ☐ LP lock tx linked once graduation happens

Weeks 3+

• ☐ Superteam UAE application
• ☐ Colosseum registration
• ☐ Foundation grant draft
• ☐ Audit scoped

10. Things that would damage credibility (avoid)

• Changing any published number after launch — Studio won't let you change vesting, but don't change the stated split either.
• Selling from the deployer or treasury wallet in the first months. Every wallet is public; people watch.
• Promising price or "returns" anywhere — site, X, Discord. Utility and access only.
• Paying for a small staking-tier launchpad badge after the fact. A clean permissionless launch with on-chain vesting reads better than a weak logo.
• Going quiet. Monthly treasury report, even when there's little to report.

Working document. Re-verify Studio's current settings on launch day; adjust this guide and the white paper together if anything has changed.