Compare Mode

Head-to-head comparison of two Hatch-scored tokens.

The URL

/score/:id/vs/:other

Both segments accept either a UUID or a 0x-address. The page always redirects to the canonical /vs/ URL (UUID on both sides) so share links remain cacheable.

Examples:

• gohatch.fun/score/a1b2c3d4/vs/e5f6g7h8 — UUID vs UUID
• gohatch.fun/score/a1b2c3d4/vs/0x1234... — UUID vs address, redirects
• gohatch.fun/score/0x1234/vs/0x5678 — address vs address, redirects
• /score/a1/vs/a1 — self-compare; bounces to /score/a1

What compare shows

1. Two ScoreCards side-by-side — aggregate, band, preliminary flag.
2. Per-signal win count — "Token A wins 4 of 6 signals."
3. Verdict header — natural language summary:
   • "$YOLK wins — leads by 23 points."
   • "Dead heat — aggregates are tied."
4. Share panel — X + Telegram templates for the comparison.
5. Swap button — flips left/right (and updates the URL).
6. Score another — jump back to /launch.

Custom OG image

/api/og/score/:id/vs/:other renders a 1200×630 PNG for unfurls. Shows both cards stacked with the verdict header on top. Works in X, Telegram, Discord, Slack unfurls out of the box.

Honesty rules

• If either side is preliminary, the verdict carries a "preliminary — aggregates may shift when stubbed signals land" disclaimer.
• Bands are shown on every card; a "green wins" can be visually distinguished from an "amber barely wins."

When to use it

• Creator vs competitor positioning.
• Two of your own tokens — which to push to launch first.
• KOL roast content — "A vs B, you decide."

The band-aware share templates lean into roast copy for red bands, comparison copy for amber, and flex copy for green (see scoring guide for the share copy rules).