V4-from-Launch: We Shipped Native Uniswap V4 Pools
5 min read
Since we launched the first version of THRYX, every token went through the same lifecycle: start on a bonding curve, trade until 250M THRYX raised, then graduate to Uniswap V4. That worked. Six tokens graduated. Hundreds of thousands of THRYX in fees distributed to creators. But bonding curves have a ceiling: during the curve phase, the token is invisible to DexScreener, 1inch, CoW Protocol, and every other aggregator on Base. DEX-visible liquidity only arrived at graduation.
We are changing that. New tokens on THRYX now skip the curve and launch directly onto a Uniswap V4 pool. From the moment the pool is created, every aggregator on Base can route trades through it.
What is the anti-sniper hook?
V4 hooks are smart contracts that intercept swaps before and after they execute. The THRYX anti-sniper hook — validated end-to-end on Base Sepolia with 17 of 17 tests passing — intercepts every buy in the first 60 seconds after a token launches and charges a parabolic-decay fee.
At second one, the fee is 80%. At second thirty, it is around 40%. By second sixty it has fully decayed to zero and normal 1% trading resumes. A bot that tries to front-run the creator in the first few seconds loses most of the trade value to the fee instead of keeping it as profit. That fee is split 50/50 between the token creator and the THRYX protocol.
The hook fires on every swap through the V4 PoolManager. It cannot be bypassed by routing through a different path — the hook address is registered in the pool key itself, so any trade that skips the hook is rejected by the PoolManager.
What are limit orders and stop-loss orders?
The LimitOrderManager is a standalone contract that holds user orders and executes them when the market reaches the target price. Place a limit buy at $0.002 and it buys automatically when the price hits that level. Place a stop-loss sell at $0.001 and it sells automatically if the price drops there — even if you are offline.
Orders are executed by a permissionless keeper network. Anyone can call executeOrder when the trigger is met and collect a 0.3% bounty from the order size. This means orders fill quickly with no centralized dependency — no server needs to be running, no cron job needs to be awake.
Limit orders work on any V4 pool on THRYX: new V4-native tokens, the 6 already-graduated legacy tokens, and the THRYX/WETH pool on your Dashboard.
What happens to legacy tokens?
Nothing. All 642 tokens that launched on the bonding curve before this upgrade keep trading on their curve. Graduated tokens keep trading through the Diamond on their existing V4 pools. The upgrade adds new code paths for V4-native launches but does not touch any existing token state. The Diamond contract uses append-only storage, so no existing field moves or changes value.
If you hold tokens from before the upgrade, your holdings are untouched. If you are a creator collecting fees on a legacy token, you keep collecting. If your token is approaching graduation, it still graduates at 250M THRYX raised, exactly as before.
What does the upgrade look like technically?
| Component | Change |
|---|---|
| LaunchV4Facet | New Diamond facet — launches tokens directly into V4 pool (additive, no old selectors replaced) |
| ThryxAntiSniperHook | New hook contract — intercepts swaps during 60s anti-sniper window |
| LimitOrderManager | New standalone contract — holds and executes limit/stop-loss orders |
| LpLocker | New contract — locks LP NFT for 1 year to prevent creator rug |
| SwapFacet | Updated — routes V4-native tokens through V4 path; legacy curve path unchanged |
| ViewsFacet | Updated — estimate function handles V4-native price queries |
| PaymasterFacet | Updated — sweeps hook fees back to Diamond paymaster reserves |
| LaunchFacet, GraduationFacet, ClaimFacet | Unchanged — all 642 legacy tokens unaffected |
Is the upgrade live on mainnet?
The anti-sniper hook and LimitOrderManager are validated on Base Sepolia (17/17 tests passed). The mainnet Diamond upgrade (diamondCut) is in the security-audit stage before deployment. We run a Cyrus security audit on every changed contract before the mainnet write. Once the audit clears and the treasury is funded for gas, the diamondCut goes live. All content, FAQ, and help documentation is updated now so users understand the new model before the contracts land.
What stays the same?
Everything about the existing user experience remains unchanged. Gasless trading for all users. 70% creator fee split. THRYX rewards per trade and per launch. Daily streak bonuses. The MCP server for AI agents. Email notifications. The AutoTrader. The bonding-curve math on legacy tokens. The graduation flow for tokens approaching 250M THRYX. None of that changes.
When can I launch a V4-native token?
The mainnet diamondCut is expected within two weeks, pending Cyrus audit completion and treasury top-up for gas. The launch form will default to V4-native automatically once the upgrade is live — no setting to toggle, no extra steps. Create your account now if you have not already — when the upgrade lands, your next token launch will go straight to V4.
Frequently asked
- Do V4-native tokens still pay 70% creator fees?
- Yes. The fee split is unchanged — 70% to the token creator, 30% to the protocol. Anti-sniper fees during the 60-second window are split 50/50 creator and protocol, so creators actually earn more during the launch window than on a normal trade.
- Can I still use the bonding-curve model?
- The bonding-curve launch path remains available in the Diamond contract. The UI will default to V4-native after the upgrade, but legacy curve launches can still be triggered via the API for anyone who prefers the gradual-price-discovery model.
- What is the keeper bounty for limit orders?
- 0.3% of the order size, paid in the output token of the swap. If your 0.1 ETH limit buy executes, the keeper earns 0.0003 ETH from the order. This comes out of the order amount, not from a separate fee on top.
- Can bots bypass the anti-sniper hook?
- No. The hook address is encoded into the V4 pool key. Any swap that does not route through the registered hook fails at the PoolManager level. There is no alternative routing path to the same pool.
- Are LP tokens locked?
- Yes. The LpLocker contract locks the LP NFT for 1 year at launch. The creator cannot remove liquidity during that period, which prevents a rug immediately after launch.
- What happens to my existing positions?
- Nothing. Holdings, balances, pending rewards, streak counters, and fee accruals are all unchanged by the Diamond upgrade. The new code paths only activate for tokens launched via launchV4() after the diamondCut.