Hatch User Guide

For token creators on Four.meme, for hatchers who discover and endorse launches, and for traders who want to read an attestation before buying.

Audience: non-engineers. If you want to integrate, go to DEV-GUIDE.md and API.md.

Table of contents

1. Check a token score in 10 seconds (no wallet)
2. For creators — score, enroll, launch
3. For hatchers — discover, signal, earn
4. For traders — read the attestation
5. Understanding the score
6. Privacy, fees, safety
7. Get help

Check a token score in 10 seconds (no wallet)

1. Open gohatch.fun.
2. Paste any Four.meme token contract address in the input.
3. Hit Check score.

If the token has been scored before, you land on /score/:id with the full breakdown. If not, you land on /launch?address=… pre-filled to score it yourself.

No wallet. No signup. No email. Score lookups are free.

For creators

You built a token. You want a Hatch Score on it before launch so buyers can see the signals, and you want to enroll it into Hatch's launch flow so you get verified-human early buyers + seed liquidity + the Crack.

Step 1 — Score your token

1. Go to /launch.
2. Fill in: token name, ticker, one-paragraph pitch, image URL (optional), X handle (optional), creator wallet (optional — but enrollment needs it).
3. Submit. Scoring takes ~15–30 seconds; six signals run in parallel.
4. Land on /score/:id. That URL is your public share link — OG image renders in X, Telegram, Discord unfurls automatically.

See Scoring guide for what each signal measures and how the aggregate is weighted.

Step 2 — Decide based on the band

• 🟢 Green (≥70) — strong signal. Ready to enroll + launch.
• 🟡 Amber (45–69) — mixed signal. Fix the lowest signal first (image, name, social). Re-score after iterating.
• 🔴 Red (<45) — weak signal. We recommend iterating before launch.

Preliminary badge — if you see "Preliminary" on the score, two signals are currently stubbed (creator wallet history via Bitquery, contract risk via GoPlus) while keys are provisioned. The aggregate is re-weighted over live signals only — no fake scores. When keys land, you can re-score for a full reading without changing the original URL.

Step 3 — Enroll

On /score/:id, click Enroll for launch:

1. Connect your wallet (MetaMask or any EVM browser wallet).
2. Sign a canonical EIP-191 message — no gas, no transaction.
3. Optionally schedule a launch time. You'll get T-60min, T-10min, and T+0 notification slots automatically.
4. Land on /score/:id/launch — a share-ready countdown page.

See Creator flow guide for deeper detail, including editing the pre-launch page, scheduling, and attendance stats.

Step 4 — Launch on Four.meme

Hatch does not replace Four.meme. You still launch via Four.meme's bonding curve. Hatch sits alongside and injects verified-human buyers + seed LP. The integration docs for the Hatching window land with Sprint E.1.

Dashboard

/dashboard — connect your wallet to see every launch you enrolled, band, scheduled dispatches, attendance, and share URLs. Client-driven (no server session needed).

For hatchers

A hatcher is a verified-human early buyer. You get first access to launches during the hatching window, signal conviction that weighs the feed, and eventually earn a pro-rated slice of the 0.5% protocol fee on launches you helped graduate.

Today (pre-D.2)

• Browse /hatchers/feed — every Hatch-scored launch, newest first. Public read, no wallet.
• Browse /leaderboards/today — best + worst of the last 24h (preliminary rows excluded).
• Browse /creator/:address — public creator launch history.

Once D.2 ships (Hatcher NFA mint)

• Verify with World ID (sybil resistance).
• Mint your soulbound Hatcher NFA (BAP-578, non-transferable).
• Get personalized feed filtering + push notifications.
• Join Crews — small groups that discover, signal, and earn together.

See Hatcher flow guide for the full lifecycle.

For traders

Before you buy a Four.meme token, check if it has an on-chain attestation.

Reading an attestation

1. Paste the token address on gohatch.fun.
2. On /score/:id, scroll to the Publish panel. If the attestation block shows a tx hash, the score is on-chain via HatchAttest on BNB Chain. The digest is the keccak256 of the canonicalized score — you can independently verify on BscScan.
3. No attestation = either the score is preliminary (two signals stubbed), the creator hasn't published yet, or the score is too new.

What an attestation guarantees

• Every signal was live (no stubbed data).
• The score was computed from a prompt+model version that's recorded.
• The digest is deterministic — same inputs produce the same 32-byte hash.
• Publishing refuses hasStubs: true rows. No fake green.

See Attestations guide for schema, verification, and what to do if an attestation appears to misrepresent the token.

Understanding the score

The six signals

Weights: meme 25% · creator 20% · image 15% · name 10% · social 15% · risk 15%. Re-weighted over live signals only when stubs are present.

Bands

• 🟢 Green (≥70) — strong: multiple signals green, no red flags.
• 🟡 Amber (45–69) — mixed: iterate on the weakest signal.
• 🔴 Red (<45) — weak: likely to stall or rug without intervention.

Why preliminary scores get re-weighted

A 50%-real number shared at 100% confidence is worse than no number. If two signals are stubbed, the aggregate is re-weighted over the four live signals. The score card, OG image, and share copy all carry a "Preliminary" badge. Attestations refuse preliminary rows by design.

Percentile

/score/:id shows where you rank against other non-preliminary scores in the last 7 days. "Top 15%" means 85% of recent scores were below yours. Hidden when sample size is <10.

Re-score

Hit Re-score on any score page. It replays the stored submission with fresh LLM calls and returns a new UUID. The original URL still works — your old share links don't break.

Privacy, fees, safety

What Hatch stores

• Your submission (name, ticker, pitch, image URL, X handle).
• The LLM raw response (for audit + replay).
• Your enrollment signature (creator address, timestamp).
• Admin-level: API key hashes, webhook endpoints.

What Hatch does NOT store

• Your private keys (ever — Hatch never sees them).
• Credit cards or payment methods (we don't bill creators).
• Email unless you send one to support@.

Fees

• Score lookup — free.
• Scoring a token — free. Anthropic API cost is absorbed.
• Enrollment — free. One signed message, zero gas.
• Protocol fee — 0.5% of post-graduation LP fees, collected only after the token crosses the Crack. Nothing before graduation.

Safety rails

• HatchNest treasury has per-token and daily caps + time-locked withdrawals (judge-panel audit item #1).
• Attestation publisher refuses stubbed signals.
• Admin panel is read-only. Mutations go through per-domain admin tokens (launch dispatcher, webhook dispatcher).
• .well-known/security.txt (RFC 9116) for coordinated disclosure.

Get help

• FAQ: gohatch.fun/support
• Email: support@gohatch.fun (24h weekday SLA)
• Security: security@gohatch.fun (4h business-hours SLA)
• Telegram: @gohatch — fastest
• Status: gohatch.fun/transparency — changelog + incident log

If Hatch broke and you need to reach a human right now, Telegram is fastest. If it's a security vulnerability, use email (not public channels).