Trust

• Bonding-curve parameters, supply, fees, and the graduation threshold are fixed at deploy — no setter, ever.
• At graduation, the seeded liquidity is permanently locked: a full-range Uniswap V4 position minted straight to 0x…dEaD, with no withdraw path Fletch or anyone else could take. It is not held in a contract we could later drain — verify it yourself with a single ownerOf read on the position. (Tokens launched earlier graduated to Uniswap V2, where the LP token was burned to the same dead address — same guarantee, older venue.)
• The token is a minimal ERC-20: no owner, no mint, no pause, no tax, no blacklist. Supply is minted once.

Tokens launched today graduate to an official Uniswap V4 pool (paired against native ETH). This is the current model — every generic surface on the site describes it. Legacy tokens on the older Uniswap V2 venue are covered below; per-token pages always show the venue that token actually graduated to, never generic copy.

• Liquidity is permanently locked, not burned. There is no LP token to burn on V4 — instead graduation mints a full-range pool position owned by 0x…dEaD with no withdraw path. Verify it yourself: ownerOf on the position resolves to the dead address, and the safety strip reads that locked position's depth directly (never pool-wide liquidity a third party could pull).
• Reserves are untouchable. A v3 pool charges a disclosed 1.00% fee (immutable, capped at 3%) on each post-graduation swap, split 80% creator / 20% treasury. This is a fee v2 tokens did not have. It is charged on trade volume and never reduces the locked reserves.
• The pool's built-in Uniswap LP fee is 0% — all disclosed revenue is the Fletch hook fee (a nonzero LP fee on locked liquidity would fund nobody).
• Fees accrue in ETH on sells and in the token on buys; creator and treasury sell the token share, which is normal market activity that moves price. The fee is on volume, but that does not mean zero price impact on holders — we state it rather than implying otherwise.

The exact rate and split shown on every v3 trade surface are read from the immutable on-chain hook, so what is advertised is what is deployed.

Tokens that launched before the v3 cutover graduated to Uniswap V2, not V4. Their pages keep the original copy and it stays true for them: the graduation LP was burned to 0x…dEaD, and there is no Fletch post-graduation fee — Uniswap's own 0.30% trade fee went to the burned LP, i.e. to nobody. We never retrofit the v3 1% hook fee onto a v2 token, and we never tell a v3 token its LP was "burned."

One honest wrinkle unique to the V2 tokens: a Uniswap V2 pair sits at a CREATE2-precomputable address, so anyone could add liquidity to it before a token graduated and keep a withdrawable position of their own. That seeded liquidity never touched the curve reserves or the LP Fletch burned, but it means such a pool can be only partially burned. We disclose it per-token in the safety strip (the lp cell) with two on-chain reads, not one: the pool's real LP burn ratio flags a seeded pool as "partial" while the pre-minter still holds their LP, and — because their profit step is to burn that LP and withdraw, which restores the burn ratio — the pool's live reserves flag a "shallow" pool whose liquidity sits far below what graduation seeded. That second read persists after the withdrawal, so a materially drained pool is flagged rather than reading as cleanly burned. One honest limit: a partial drain that leaves the pool within the depth of a normally heavily-sold coin isn't distinguishable from ordinary selling, so treat the flags as a floor on disclosure, not a guarantee — always read the live liquidity number for yourself. The v3 Uniswap V4 venue mints its locked position straight to the dead address and the safety strip reads that position's depth directly, so this pre-mint wrinkle does not apply there.

No key — ours or anyone's — can pause trading, mint tokens, touch a curve's reserves, or move a user's funds. The privileged surface is fee routing on the launchpad only, held by the deployer at launch and handed to a multisig thereafter: set treasury, set the creation fee (≤0.01 ETH), and set the referral share (a cut of the protocol's own fee, never the creator's). The post-graduation hook fee is not on that surface: its rate (1%, capped 3%) and its 80% creator / 20% treasury split are immutable in the deployed hook — no key can raise it, retarget it, or turn it off, and it never touches the locked reserves. Legacy v2 tokens carry no Fletch post-grad fee at all. That is the whole of it.

v3 tokens graduate into Uniswap V4 — the singleton PoolManager, the PositionManager that holds the dead-owned locked position, and the shared fee hook, all shown in the contracts list below. Legacy tokens depend instead on Uniswap V2, paired against the WETH its router uses on Robinhood Chain (a value read from the router at deploy, not one Fletch picks). Uniswap V4, Uniswap V2, and the chain itself are dependencies outside Fletch's control. The chain is a young Arbitrum-based L2 with a single sequencer; its infrastructure carries its own risks. We name these because pretending a dependency doesn't exist is how trust gets broken.

The contracts have had rigorous internal, multi-agent adversarial review and a full test suite. They are not yet covered by a completed independent audit — an audit is in progress. Until a report is published and linked here, treat the contracts as unaudited. We will not describe Fletch as "audited" anywhere until that report exists. The contracts are immutable, so an undiscovered bug cannot be patched — this is a real, disclosed risk. See Terms & Risk.

If you find a bug in the contracts, report it privately first. Because the contracts are immutable, we cannot patch, pause, or upgrade deployed code — but a coordinated report still lets us warn users, stop this front-end from serving the affected token or pool, and guide the next deployment. There is no paid bug bounty today, and we won't pretend otherwise. Our disclosure contact and policy live in /.well-known/security.txt.

Read the source on Blockscout — don't take our word; the contract tab shows verification status directly.