📖 protocol documentation

How FletchPad works, in full.

The whole protocol in plain terms: how a launch works, where the fees go, the Guild Pool, and exactly what is guaranteed by immutable code versus what is treasury policy. Every claim links to the chain — read the code, not the marketing.

overview

What is FletchPad

FletchPad is a fair-launch token launchpad on Robinhood Chain. One transaction turns a name and a symbol into a live, tradable token — a vanilla OpenZeppelin ERC-20, a Uniswap V3 pool, and a liquidity position locked forever. The single economic twist: the creator keeps 50% of the ETH trading fees, for as long as the token trades.

There is no bonding curve, no migration, and no graduation step. Tokens are born straight on the DEX with liquidity locked from block one. Nothing custom runs at swap time — the trading path is 100% vanilla Uniswap V3. And because every contract is open-source and verified on Blockscout, you never have to take our word for any of it: every claim on this page links to the chain.

🏹 Fair launch · no team allocation🔒 LP locked forever1% fee tierCreator keeps 50% of the ETH feesFees paid in ETH
how a launch works

One transaction: token → pool → Locker

1Deploy the token

One transaction to the LaunchFactory fletch(name, symbol, salt) — deploys a fixed-supply OpenZeppelin ERC-20 via CREATE2. The salt is keyed to your address, so nobody can pre-create your pool. The whole supply (1,000,000,000) is minted once, in the constructor, and never again. No owner, no mint, no tax, no blacklist, no hooks — the runtime bytecode is identical for every launch.

2Create the Uniswap pool

The same transaction creates and initializes the canonical Uniswap V3 pool at the 1% fee tier, paired with WETH, and mints a single-sided position (the range sits just above spot) holding the entire supply. Trading is 100% vanilla Uniswap — nothing custom executes at swap time, so fees accrue natively in the pool.

3Lock the LP

The position NFT is sent directly to the Locker, which can never decreaseLiquidity or move the NFT — for anyone. Liquidity is locked forever. Fees keep accruing in the pool; how they get split is covered next.

For integrators: the position sits just above spot, so until the first swap the pool's in-range liquidity() reads 0 by design — the liquidity lives in the position, above spot. Don't read that as "no liquidity".
fees & revenue

Where the trading fees go

Trading happens in a standard Uniswap V3 1% pool; fees accrue natively in the pool, in both tokens. Turning those accrued fees into payouts is the job of collect(token) on the Locker — a permissionless call anyone can trigger.

  • The WETH side is split exactly 50/50 — 50% credited to the creator, 50% to the protocol treasury. This split is a code constant with no storage to change and no admin path; it cannot change post-deploy. (The odd wei goes to the protocol.)
  • Creators claim with a pull: claimCreator(token) pays the registered creator exactly their accrued balance. Balances are isolated per token.
  • The token side of the fees goes to the treasury as inventory. It is not burned by default and is never sold by the contract — any sale would be treasury policy, done off-chain.
  • No launch fee, no token tax, no bonding-curve surcharge — the swap path is untouched.

On top of the immutable 50% to creators, FletchPad commits 10% of protocol revenue to the Guild Pool for $FLETCH stakers. That 10% is treasury policy, not a contract rule: the treasury calls the pool's fund() with the slice it chooses. The Guild Pool is covered below.

the guild pool

Stake $FLETCH, share the protocol's revenue

The Guild Pool lets $FLETCH stakers share the protocol's revenue, pro-rata by time staked, paid in WETH. It is a zero-admin contract: no owner, no pause, no upgrade — only two immutables (the stake token, $FLETCH, and the reward token, WETH). Nobody — not even us — can touch your funds or the payout math.

Time-weighted epochs

An epoch is the interval between two fund() calls. Your points in an epoch are your staked balance × time. Each fund() closes the current epoch and opens the next. More staked, for more of the epoch, means a bigger share of that fund. No multiplier, no lock.

No lock — but forfeit on early exit

Unstake anytime; your tokens always come back in full. The catch: unstaking before an epoch's share forfeits your points in the open epoch (the forfeited time redistributes to whoever stays). Closed epochs and already-claimable rewards are never touched.

Anti-snipe is emergent

A staker who deposits one second before a fund() earns ~one second of points against everyone else's days — rounding dust, not a slice. The time-weighting defeats last-minute timing without needing any lock.

Permissionless funding

fund() is open — anyone can feed the pool. The 10% of revenue is treasury policy (off-chain), and funding on irregular dates is itself an extra anti-snipe measure: you cannot time a stake to a fund you cannot predict.

The pool distributes whatever the treasury sends, if it sends, split by time staked. It is not a yield product — there is no APY, no promised return, and nothing is implied as recurring. The math is on-chain; read it for yourself.
trust & verify

Built to be checked, not trusted

Every FletchPad contract is open-source and verified on Blockscout, and every launched token is a vanilla ERC-20 with the same runtime bytecode. The "is it a honeypot?" question is settled on-chain — real sells exist in the pools' trade history. There is no privileged code to hide behind.

The full breakdown — the complete contract list, the scanner false-positive explainer, and the token-is-vanilla checklist — lives on the Trust page. This page links each mechanic to the exact contract; the Trust page is where you go to audit them all at once.

security

What the code guarantees vs. what depends on the treasury

We split this honestly. Some properties are guaranteed by immutable code — no admin can ever change them. Others depend on the treasury/admin, which today is a single address, not a multisig or timelock. We do not claim FletchPad is "fully decentralized." Here is the exact line.

Immutable — no admin path exists
  • The LP is locked forever. No function can decreaseLiquidity or move the position NFT, for any caller.
  • The 50/50 WETH fee split is a code constant — no storage, no setter, no admin path.
  • Every token is a vanilla ERC-20 — no owner, no mint after construction, no blacklist, no tax, no hooks, no proxy or upgrade.
  • The Guild Pool has no admin, owner, pause, or upgrade — stake, unstake, claim, and fund are all open.
Discretionary — treasury / admin policy
  • Treasury address is singular today. The protocol's WETH share and token inventory sit in one treasury address — not yet a multisig or timelock.
  • Token-side burn is opt-in and off. The Locker's one admin-tunable parameter is tokenBurnBps — it is capped and currently 0, so nothing is burned and the whole token side goes to treasury inventory. It cannot touch the WETH split, the creator's 50%, or the LP lock.
  • New launches can be paused. The LaunchFactory admin can setPaused — this blocks only new launches, never existing pools, the Locker, or your fees. Admin handover is two-step.
  • Revenue use is policy. What the treasury does with its WETH share and token inventory — including the 10% to the Guild Pool — is policy, not code.
chain & gas

Robinhood Chain, official Uniswap, gas-free window

  • FletchPad runs on Robinhood Chain (chain id 4663). Tokens pair against the chain's canonical WETH.
  • The Uniswap V3 deployment — factory, position manager, router, quoter — is the official one on 4663, proven byte-for-byte against Arbitrum One. It is not a custom fork.
  • A limited-time gas-free window is live now — launching and trading cost you no gas. It won't last forever.
Network nameRobinhood Chain
Chain ID4663 (0x1237)
Currency symbolETH
RPC URLhttps://rpc.mainnet.chain.robinhood.com
Block explorerhttps://robinhoodchain.blockscout.com
or add the network by hand with the values above
Explorer: robinhoodchain.blockscout.com. Always confirm you are on fletchpad.fun — we will never DM you or ask for your seed phrase.
chain id 4663official Uniswap V3gas-free window live now
faq

Questions, answered

Why no airdrop or points?

Because they are the thing FletchPad is built against. Creators keep 50% of the ETH fees, and the Guild Pool shares a portion of protocol revenue — real WETH — with $FLETCH stakers, pro-rata by time staked. No points, no IOUs, no "token coming soon."

What is “fletching”?

Launching a token on FletchPad. A fletcher makes arrows; you fletch a token — deploy it, pair it on Uniswap, and lock the LP, all in one transaction.

What is an epoch, and what does “forfeit” mean?

An epoch is the interval between two fund() calls to the Guild Pool. Your points in it are your staked balance × time. If you unstake before the epoch's share is paid, you forfeit your points in that still-open epoch — your tokens still return in full, and any closed-epoch rewards you've earned are untouched.

Is there an APY?

No — there is no APY, no fixed rate, and no promised yield; nothing here compounds on a schedule. The Guild Pool shares real protocol revenue, paid in WETH, with $FLETCH stakers, split pro-rata by time staked. Funding is discretionary — the treasury sends what it sends, when it sends it, and nothing is implied as recurring. There is no lock: unstake anytime (you only forfeit points in the still-open epoch), and since we are at genesis, nothing has been distributed yet.

Can the team pull the liquidity or change the fee split?

No. The LP lock and the 50/50 WETH split have no admin path anywhere in the code — verify it on the Locker. See the Security section for the full immutable-vs-discretionary line.

What does “no migration” mean?

Many launchpads start a token on a bonding curve and later "migrate" it to a DEX — a step that has been exploited elsewhere. FletchPad tokens are born on Uniswap V3 with the LP locked from block one. There is no migration step, ever.

Do I need $FLETCH to launch a token?

No. Anyone can fletch a token. $FLETCH is the genesis token; staking it in the Guild Pool is how you share in protocol revenue — it is not required to create a launch.

Where do I verify all of this?

On-chain. Every contract is verified on Blockscout, $FLETCH's pool is on GeckoTerminal, and the Trust page ties each claim to the code.