Trading
Every token launched on degen.zone trades in-app, on every venue. On Robinhood Chain, BSC, Base, Ethereum and Arc a token opens straight into a hooked concentrated-liquidity pool and your trade is a swap in that pool through degen.zone's own router - no order book, no counterparty search, a market from block one. This page covers where a trade executes, the mechanics that protect it, and the limits that apply.
The basics
The trade panel on every token page has two tabs. Buy spends the chain's native coin (ETH on Robinhood Chain and Base, USDC on Arc, BNB on BSC, SOL on Solana) - or the pair asset on a custom-pair token - and receives tokens; Sell does the reverse. Quick-amount chips (0.01 / 0.05 / 0.1 / 0.5 of the native coin on buys, 25/50/75/100% of balance on sells) cover the common cases; both sides accept custom amounts. Prices display in USD or native terms - a global toggle, since the truth underneath is always the native amount.
Every trade pays the token's swap fee - the one its creator fixed at launch, between 0.5% and 5%, shown on the token page - plus the platform and referral add-on of 0.35% that rides on top. The pool's own LP fee is zero: the hook takes the whole fee inside the swap, on buys from the coin you send and on sells from the coin you receive. Where it goes: Fees & earnings.
Where your trade executes
The panel picks the execution path from the token's venue; you never choose a router. On the board every row wears a venue chip (V4, Infinity, PONS) so you can see it before opening the page.
| Token | Executes through | Settles in |
|---|---|---|
| Direct launch on Robinhood, Base, Ethereum or Arc | degen.zone’s Uniswap V4 swap router | The canonical Uniswap V4 PoolManager |
Direct launch on BSC, chip Infinity | degen.zone’s PancakeSwap Infinity swap router | PancakeSwap Infinity’s Vault |
Direct launch on BSC, chip V4 | degen.zone’s Uniswap V4 swap router (BSC address set) | The canonical Uniswap V4 PoolManager on BSC |
| Graduated PONS token on Robinhood | DegenPonsSwapRouter - permissionless, no owner | The token’s PONS Meme-hook pool on Uniswap V4 |
| PONS token still on its curve | The PONS launchpad curve directly | PONS’s own contract |
| Solana custom pair (Raydium CLMM) or graduated DBC token | Jupiter routing | Raydium CLMM / Meteora DAMM v2 |
| Solana native-SOL launch on its curve | Meteora DBC directly | The DBC pool |
| pump.fun bundle-mode token | pump.fun’s curve | pump.fun |
The two BSC routers are the same ABI compiled against two different singletons: the Infinity router settles token and BNB balances through PancakeSwap's Vault lock, the V4 router through the PoolManager's unlock. A BSC token lives in exactly one of them, fixed at launch, and the app resolves which from the launcher that emitted it. Every router is a thin pass-through: it holds nothing between transactions and every swap is bounded by your own minimum-received amount.
A PONS-venue token that has graduated into its Uniswap V4 Meme-hook pool on Robinhood trades from the same panel as any other. You can buy with native ETH or with the pair's quote asset, and sell back. The quote you see is the fill you get: it already includes PONS's 1% base fee and the creator tax, so nothing is discovered at signing time.
Quotes & slippage
The quote you see while typing is read live from the pool through the router's quoter (or from Jupiter on Solana). The quote that protects you is a different one: at the moment you submit, the app takes a fresh quote and derives a minimum-received bound from your slippage tolerance (presets 0.5% / 1% / 3%, or custom). If the price moves past that bound before your transaction lands, the trade reverts - you keep your funds instead of filling at a worse price. Every swap also carries a deadline, so a transaction stuck in a wallet for minutes cannot fill against a stale price later.
On a busy pool a few tenths of a percent of movement between submit and inclusion is normal; too tight a tolerance means honest reverts, too loose invites worse fills. The default of 1% is a reasonable middle for most pools.
Buying
- One transaction; no approval needed when you are spending the native coin. Buying a custom-pair token with its ERC-20 quote (USDG, USDC, a tokenized stock) needs a one-time approval of that quote to the router first.
- The router refunds any unspent native coin in the same transaction, so an exact-out buy never overpays.
- On a token with active holder rewards, the buy is what earns you a share of the fee stream from that block on - there is no staking step.
- On a curve venue (see below) the curve's own rules apply: a minimum buy of
0.0001of the native coin, and the completing buy is charged only what fills the curve, with the excess refunded.
Selling
- The first sell of a token needs a one-time approval transaction (a standard ERC-20 allowance to degen.zone's router for that venue); after that, selling is a single transaction. On Solana there is no approval step at all.
- Your minimum-received bound works exactly like on buys - a stale price reverts rather than fills.
- The pool is the counterparty. A direct-launch pool was seeded with the full supply below spot and its LP position burned, so there is always a bid; the depth at any price is whatever the market has bought up to that point.
Limits the contracts enforce
| Limit | Value | Scope |
|---|---|---|
| Swap fee | 0.5% - 3% | Fixed per token at launch by the creator; shown on its page |
| Platform + referral add-on | 0.35% | On top of the creator’s fee, every direct-launch trade |
| Pool LP fee | 0 | Direct-launch pools; the hook takes the whole fee |
| Dev-buy cap | 20% of supply | The creator’s atomic launch buy on a direct launch (the wizard aims at 19% for margin) |
| Bundle wallets | 50 | Recipients per opening bundle, on-chain cap |
| Minimum buy | 0.0001 native | Curve venues only |
| Max wallet | 2% of supply | Curve venues only, while bonding, on tokens with anti-sniper on |
A direct-launch pool has no wallet cap and no anti-sniper window: the whole supply is on the book from the first block, priced below spot, and the fee hook is the only thing between a trader and the pool.
How live is “live”
The home page's feed and the token page update over a realtime socket. Launches and trades are pushed with a target of under a second from the chain event - the feed animates a new token in the moment it exists. Behind the instant feed sits a durable indexer that is the source of truth; if the two ever disagree for a moment, the indexer wins, which is why a card can very occasionally adjust a value a second after appearing. Charts are built server-side from every indexed trade, at intervals from 1m to 1d. On BSC the indexer reads both singletons, so an Infinity pool and a V4 pool chart the same way.
Curve venues and graduation
Robinhood, BSC, Base, Ethereum and Arc direct launches have no curve and no graduation: the pool you trade on day one is the pool forever. A bonding curve with a graduation step still describes three places: the PONS venue on Robinhood (graduates into a Uniswap V4 Meme-hook pool, then trades in-app as above), a Solana native-SOL launch on Meteora DBC (graduates into a Meteora DAMM v2 pool), and the coming-soon chains Ronin (would graduate to Katana V3) and HyperEVM. While a token bonds, every trade is a direct exchange with the curve contract at the curve's price. See Graduation.
Charts are drawn from degen.zone’s own indexer. On EVM chains - and on Solana custom-pair (Raydium CLMM) tokens - the chart keeps flowing. But a native-SOL curve token that migrates to a Meteora DAMM v2 pool outruns the indexer today: those post-migration swaps aren’t indexed yet, so the chart and volume stop at graduation. Trading continues in-app through Jupiter; only the candles pause until that coverage ships.
