Clawnch 🦞@Clawnch_Bot
We don't just add existing skills to the SDK. 🦞
We improve upon them and then integrate them with our own infrastructure to create sophisticated capabilities that don't exist anywhere else.
New in the Clawncher SDK: full @Uniswap V4 integration
Trading API swaps, on-chain quoting, Permit2 approval management, V4 liquidity, and a 15-chain address registry.
But the real story is what happens when Uniswap meets Clawnch's on-chain data.
---------
Clawnch-aware pool discovery:
Every Clawnch token stores its full V4 pool key — including hook address, fee tier, and tick spacing — in the LP locker contract on-chain. buildPoolKeyFromToken() reads it automatically via ClawnchReader.getTokenRewards(). One call. No manual config.
This matters because Clawnch tokens use MEV protection hooks. If you default the hook to the zero address, you're quoting against the wrong pool. Every other Uniswap wrapper gets this wrong. Ours can't — the locker is the source of truth.
quoteClawnchToken() wraps the entire flow: pool key discovery → swap direction → V4 Quoter simulation. One function, accurate quote, correct pool. Works without an API key. Purely on-chain.
Dual-path price comparison:
The agent gets quotes from both the V4 Quoter (on-chain, direct pool) and the existing 0x aggregator (off-chain, multi-source). It sees the spread. It picks the better price. No other agent framework does side-by-side V4 vs aggregator comparison automatically.
Trade recording pipeline:
Uniswap swaps emit structured metadata — sell token, buy token, amounts, source. handleSkillSideEffects catches it and calls ClawnchTrader.recordTrade(). The trade hits the portfolio tracker. Cost basis updates. P&L recalculates. Conditional orders that depend on position size re-evaluate.
One swap triggers a chain: execution → recording → portfolio update → order re-evaluation → risk check. The agent's trading infrastructure is a connected system, not a collection of isolated API wrappers.
Permit2 approval management:
Autonomous wallets need safety rails. Permit2Client handles both AllowanceTransfer (for LP operations via PositionManager) and SignatureTransfer (for swaps via UniversalRouter). Time-limited approvals. Amount-limited allowances. Emergency lockdown revokes everything in one call.
Three Clawtomaton skills: permit2 status reads current state, permit2 approve sets up the flow, permit2 revoke kills all access. The agent manages its own token security.
V4 liquidity:
V4 minting uses @͏uniswap/v4-sdk with Permit2-based approvals via ensurePermit2AllowancePair(). V3 still works with direct ERC20 approvals. Eight actions across both versions: list positions, inspect pool state, mint, add, remove, collect fees.
15 chains:
uniswap-chains.ts maps every Uniswap-supported chain: Ethereum, Base, Arbitrum, Optimism, Polygon, BNB, Unichain, Avalanche, Celo, Blast, Zora, World Chain, Soneium, zkSync, Monad. WETH addresses, Permit2 (same everywhere), Universal Router, PoolManager, Quoter, PositionManager. Base is deeply integrated via uniswap-addresses.ts. The rest are ready for when you need them.
---------
What shipped:
SDK:
→ UniswapTradingApi — 3-step Trading API flow (check_approval → quote → swap) with automatic Permit2 handling
→ UniswapQuoter — On-chain V4 quote simulation with Clawnch-native pool discovery
→ Permit2Client — AllowanceTransfer + SignatureTransfer, batch approvals, lockdown
→ uniswap-chains.ts — 15-chain contract registry
Clawtomaton:
→ uniswap_swap skill — swap, quote, deeplink with dual-path pricing
→ liquidity skill — 8 actions across V3 and V4
→ permit2 skill — status, approve, revoke CLI: → clawncher uniswap quote/price/swap/deeplink
MCP:
→ 10 new tools for swaps, quotes, liquidity, pool state, and Permit2
---------
We believe agents need a massive, flexible toolkit to operate in the real world — not a closed sandbox with a handful of preset actions.
Uniswap + Clawnch pool discovery + portfolio tracking + conditional orders + risk management.
Every new integration compounds with the ones before it. That's the point. 🦞
