THRYX vs Zora vs Clanker: A Factual Base Launchpad Comparison (2026)
10 min read
Three Base-native token launch surfaces have emerged with serious traction by mid-2026, and they target three different launch shapes. THRYX is a gasless launchpad with a built-in trading AI; Zora puts a coin behind every creator post; Clanker turns a Farcaster cast into a deploy. The right call depends on what your launch actually is — a community token, a piece of viral content, or a quick experiment from a Farcaster handle. This post lays out what each does, how the economics line up, and where each platform structurally fits. Anything I am not confident about is omitted rather than guessed.
What all three have in common
All three platforms deploy ERC-20 tokens on Base (Coinbase's Ethereum L2, chain id 8453). Base block times are around two seconds, gas is fractions of a cent, and Uniswap V4 is the canonical AMM substrate. WETH at 0x4200000000000000000000000000000000000006 is the L2-native wrapped ETH on every Base venue, and graduated or instantly-LP'd tokens from any of the three end up routable through DEX aggregators (1inch, CoW, ParaSwap, Matcha) once liquidity hits a V4 pool. So the chain plumbing under all three is identical. What differs is the launch surface — what the user actually does to get a token live, and what the platform does to economize the rest.
The fundamental design difference
THRYX is a launchpad: a website where you fill in a name, ticker, optional image, and click a button. Until 2026-05-04 every new token started on a bonding curve and graduated to Uniswap V4 once realThryx crossed 250M; from that date onward every new launch is V4-native from t=0 with an anti-sniper hook. Zora is a creator app where the act of posting is the act of minting — every post can become a coin, and trading the post means trading the coin. Clanker is a Farcaster bot where mentioning the agent with a name and symbol triggers an on-chain deploy and an LP seed. THRYX optimizes for "I want a token I can hand to a community"; Zora optimizes for "this piece of content should be tradable"; Clanker optimizes for "deploy this token in one cast, right now, where I already am."
Quick comparison
| Dimension | THRYX | Zora | Clanker |
|---|---|---|---|
| Chain | Base | Base | Base |
| Launch surface | Web app (thryx.fun) + REST + MCP | Zora app (post = coin) | Farcaster cast tagging the bot |
| Wallet to start | None — email + password (custodial) | Wallet via Privy / connected | Farcaster account + connected wallet |
| Gas to launch / trade | $0 — sponsored by paymaster | Standard Base gas | Standard Base gas |
| Liquidity model | Bonding curve (legacy) → V4; V4-from-launch (new) | Pool seeded per coin | Single-sided LP at deploy |
| Fee per trade leg | 1% (50 bps grandfathered on ~600 legacy tokens) | Public protocol fee | Pool LP fee |
| Creator share | 70% of swap fee | Creator / referrer split per Zora rules | Pool fees to creator wallet |
| Native AI tools | Per-user LLM autotrader + MCP server (15 tools) | None first-party | The bot itself is an agent |
| Anti-sniper | Hook decays 80% → 1% over 60s on new launches | Per-coin design choice | None at the deploy primitive |
| Built for | Communities + AI agents | Creators + content economy | Farcaster-native one-shot deploys |
A few of the Zora and Clanker rows say "per ... rules" instead of a hard number. That is deliberate. Both have shipped fee schedules and product changes during 2026, and citing a number I cannot verify on the day of writing would be worse than naming the structural shape. Confirm live rates on each platform before committing capital.
THRYX in one paragraph
THRYX (thryx.fun) is a gasless meme-coin launchpad on Base. The Diamond proxy at 0x2F77b40c124645d25782CfBdfB1f54C1d76f2cCe holds about ten active facets — LaunchV4Facet for new V4-native launches, SwapFacet for trades, GraduationFacet for legacy curve→V4 migration, ClaimFacet for creator fees, AdminFacet for parameters, ViewsFacet for reads, and a PaymasterFacet that closes the gas loop by skimming a small slice of every swap into the on-chain ETH balance that pays the relay back. Users sign up with email and password; a server-managed Base wallet is provisioned for them, exportable any time. Every action — launch, buy, sell, claim — is an EIP-712 typed-data signature submitted by a Cloudflare Worker relay. From the user's perspective: zero ETH ever leaves their wallet for gas. By 2026-05-09 the platform has 129 users, 648+ tokens launched, 6 graduated to V4 under the legacy model, and shipped V4-from-launch as the default for all new tokens five days ago.
The two pieces that differentiate THRYX from a generic launchpad are the per-user LLM autotrader and the MCP server. The autotrader (at thryx.fun/autotrader) gives every user a Llama 3.3 70B agent — Groq inference is sponsored by the platform — with an editable system prompt, a per-user position-size cap, and a daily-loss guideline. It ticks every minute, picks the most-overdue enabled agent in a 4-way concurrent batch, and trades through the same /api/trade/buy and /api/trade/sell routes a human user hits. The MCP server (@thryx/mcp-server on npm, also on the Anthropic MCP Registry) exposes 15 tools to any MCP-compatible client (Claude Desktop, Claude Code, Cursor) — discovery, risk scoring, protocol params, and gated write tools for launching and trading. Read tools work without auth; write tools require a per-agent API key.
Zora in one paragraph
Zora's 2026 thesis is that every social post is also an asset. When a creator posts on Zora, the post becomes an ERC-20 coin on Base, and the act of "supporting" the post is buying the coin. Every coin gets its own pool; trades route through Uniswap. The model is creator-economy first — the token is downstream of the content, not upstream. Earnings flow to the creator and to referrers based on Zora's rules at the time of the trade. Onboarding pulls heavily on the Zora app and embedded wallets. The pitch to creators is fundamentally different from THRYX: instead of "launch a community token," it is "the things you make are tradable." If you are a creator with a body of work and want each piece to have its own price discovery, Zora is structured around that.
Clanker in one paragraph
Clanker is a Farcaster-resident agent that deploys an ERC-20 on Base when you cast at it with a token name and symbol. The agent sees the cast, deploys the token, seeds an LP, and replies with the contract address — the loop is one cast in, one token out. Liquidity is single-sided at deploy, and creator fees flow to the casting wallet. Clanker fits a specific shape: you are already on Farcaster, you have a moment that wants a ticker, and you want the deploy to happen inside the same channel where the conversation is happening. There is no separate website to log into and no curve to bond before liquidity exists; the trade-off is fewer launch-time levers (no anti-sniper hook, no curve discovery, no platform-side custody) compared to a full launchpad surface.
Fees, splits, and the round-trip cost on each
Round-trip cost — buy then immediately sell — is the cleanest single number for comparing trade economics, because it bakes in both legs of the fee plus any spread. THRYX charges 1% per leg on new V4-native launches, so the round-trip is 4.5% (1% buy + 1% sell + the V4 anti-sniper hook only kicks in inside the 60-second window post-launch). Around 600 legacy tokens were grandfathered at 50 bps per leg, which puts their round-trip at 3.5%. Those numbers are protocol-level — verifiable on-chain via the ViewsFacet — and the 70/30 creator/protocol split applies on every leg. For Zora and Clanker, the round-trip math depends on the per-pool fee tier they configure at launch (V4 supports 5 bps, 30 bps, 100 bps, and others) plus any platform-side rake. Treat the comparison below as a structural map, not a price quote:
| Cost surface | THRYX (new V4-native) | THRYX (legacy curve grandfathered) | Zora / Clanker (general shape) |
|---|---|---|---|
| Per-leg swap fee | 1.0% | 0.5% | Pool fee tier (varies; commonly 30 bps or higher) |
| Round-trip floor | 4.5% (incl. anti-sniper outside 60s window) | 3.5% | 2x pool fee + any platform rake |
| Anti-sniper window | 80% → 1% parabolic decay over 60s | N/A (curve) | Not part of the deploy primitive |
| Creator share | 70% of swap fee, every trade, lifetime | 70% of swap fee, every trade, lifetime | Per-platform rules; commonly LP fees + referral splits |
| Gas to user | $0 | $0 | Standard Base gas per trade |
Rewards beyond fees — only one of the three has them
THRYX layers a THRYX-token reward schedule on top of fee economics. The numbers below are live as of 2026-05-02 — they were rebalanced down from the v2.15 schedule because the prior pool burn outpaced revenue. Confirm via thryx_protocol_params before relying on them in code:
| Action | THRYX reward | Daily cap |
|---|---|---|
| Launch a token | 250,000 THRYX | 5 / day |
| Trade >= 0.0001 ETH (base) | 10,000 THRYX | 15 / day |
| Trade >= 0.0002 ETH (tier 1) | 40,000 THRYX | (within 15/day) |
| Trade >= 0.001 ETH (tier 2) | 100,000 THRYX | (within 15/day) |
| Trade >= 0.005 ETH (tier 3) | 400,000 THRYX | (within 15/day) |
| Trade >= 0.02 ETH (tier 4) | 1,000,000 THRYX | (within 15/day) |
| 2-day trading streak | +25,000 THRYX/day | |
| 7-day streak | +100,000 THRYX/day | |
| 30+ day streak | +500,000 THRYX/day |
Neither Zora nor Clanker ships an equivalent platform-token reward schedule. That is a real difference for traders running long horizons: a daily-active user who stays in tier-3 trade sizes plus a 30-day streak collects meaningful THRYX inflow on top of P&L. It is also a real cost to the protocol — the rewards pool is a finite buffer drawn from protocol THRYX reserves, which is why the schedule has been rebalanced once already and may move again.
Where each platform structurally fits
THRYX is the strongest fit when the launch is community-oriented — there is a Discord or a Telegram or a movement, and you want a token that anyone (including non-crypto users) can buy with no wallet setup, that pays you 70% of fees from trade #1, and that exposes itself to AI trading agents through MCP and the on-platform autotrader. The gasless paymaster removes the single biggest onboarding wall (an exchange + a wallet + ETH for gas). Zora is the strongest fit when the launch is content-anchored — every post becomes its own market, the creator has a back catalog or a posting cadence, and the audience overlap is with the Zora app itself. Clanker is the strongest fit when the launch is Farcaster-native — the creator and the audience already live on Farcaster, the moment is fleeting, and the deploy needs to happen in-channel without leaving the app.
These are not contradictions. The same person can run a community token on THRYX, drop content coins on Zora, and ping Clanker for ad-hoc moments. The chain underneath is the same; the launch surface is the choice.
Choosing between them — a quick decision tree
- Does your audience live primarily on Farcaster, and is the launch a one-shot moment? -> Clanker.
- Is the token downstream of a piece of content (a post, a track, a video, an artwork), and do you want the content + the asset to be the same primitive? -> Zora.
- Do you want $0 onboarding for non-crypto buyers, a 70% creator share, AI agent infrastructure (MCP + per-user LLM trader), and Uniswap V4 from t=0 with anti-sniper protection? -> THRYX.
- Want all three? Use them in parallel — they do not exclude each other and the chain economics are identical underneath.
Frequently asked questions
Frequently asked
- Are THRYX, Zora, and Clanker on the same chain?
- Yes. All three deploy ERC-20 tokens on Base (chain id 8453). DEX aggregators that index Base — 1inch, ParaSwap, CoW Protocol, Matcha — pick up tokens from all three once they have a Uniswap V4 (or V3) pool with non-trivial liquidity. Cross-platform routing therefore works the same way once a token is live.
- Why does THRYX trade gas-free when Zora and Clanker do not?
- THRYX runs an on-chain paymaster (PaymasterFacet on the Diamond) that holds an ETH balance funded by skimming a slice of every swap fee. The Cloudflare Worker relay submits user-signed EIP-712 transactions to the Diamond, and the paymaster reimburses the relay's gas spend in the same transaction. Result: the user never holds ETH for gas, and the relay does not bleed funds. Zora and Clanker use standard Base gas, which is already cheap (fractions of a cent) but is not zero and requires the user's wallet to be funded.
- Can I trade tokens from Zora or Clanker through THRYX?
- Not directly through THRYX's in-app swap UI — THRYX's SwapFacet routes only tokens registered in its own state (legacy curve tokens, V4-native THRYX-paired tokens, and graduated THRYX-paired tokens). For tokens deployed elsewhere, route through any standard Base aggregator (1inch, ParaSwap, Matcha) once their Uniswap pool is live. The chain is the same; the routing UI differs.
- Is there a competitor disparagement angle here?
- No, and there should not be. The three platforms target different launch shapes — community vs content vs Farcaster-channel. Stating which design fits which use case is factual; ranking them as winners or losers is not, because the ranking depends entirely on what you are launching.
- Does THRYX support content-coin or Farcaster-cast launches as well?
- THRYX has a /launch flow keyed on token name + symbol + image; it does not couple a launch to a Farcaster cast or a Zora post. If your launch is content-anchored or Farcaster-native, the platform that sits closest to that surface (Zora or Clanker respectively) is the structural fit. THRYX's sweet spot is community + agent-driven launches with $0 onboarding for non-crypto users.
- How do I verify the THRYX numbers in this post?
- Read the live values from the Diamond at 0x2F77b40c124645d25782CfBdfB1f54C1d76f2cCe via any Base RPC. ViewsFacet exposes feeBps, creatorFeeSplit, virtualThryxInit, virtualTokensInit, graduationThreshold, paymasterEthBalance, and the reward params. The MCP tool thryx_protocol_params returns the same values as a JSON blob if you prefer that interface. Reward schedule changes are recorded on-chain — the post-2026-05-02 setRewardParamsV2 transaction is in the project archive at contracts/deployments-mainnet.json.
Related Posts
- THRYX vs pump.fun — Cross-chain comparison against the Solana incumbent.
- The Best Free Alternative to pump.fun on Base — Deeper THRYX feature breakdown.
- Gasless Meme-Coin Launchpad on Base — How the paymaster covers every trade.
- V4-from-Launch — The upgrade that put new tokens directly on Uniswap V4.
- MCP Server for Crypto Trading — How AI agents plug into THRYX.