Skip to main content

Token Launching

How do I launch a token?​

Tell Bankr: deploy a token called [Name] with symbol [TICKER]

Launches are supported on Robinhood Chain (the default) and Base — say on base instead to deploy there.

You can also launch via:

  • The terminal at bankr.bot → "launch a token"
  • The CLI: bankr launch
  • Tagging @bankrbot on X with a launch request

How many tokens can I deploy per day?​

  • Standard accounts: up to 50 tokens per day
  • Bankr Club members: up to 100 tokens per day
note

Some older docs may list lower limits (1/day standard, 10/day Club) — those are incorrect.

Does my wallet need to be a certain age to launch a token?​

Sometimes. As an anti-sybil safeguard, Bankr can require your wallet to be at least 24 hours old (measured from when the wallet was created — not your X/social account age) before it will launch a token. When this gate is on, a deploy from a newer wallet is rejected with a message telling you roughly how many hours are left to wait.

This requirement is off by default and only applies when enabled. Partner (org Partner-Key) launches are always exempt. See Deployment Limits.

Fees accumulate automatically as people trade your token. As a token creator using Doppler (on Base or Robinhood Chain), your token's pool charges a 0.7% swap fee and 95% of it goes to you — 0.665% of trading volume, paid directly. The hook adds the Bankr protocol fee + BNKR buyback and LP fee on top, and the 0.285% LP fee automatically compounds as permanently locked liquidity in your token's own pool — together that's 0.95% of volume working for your side. (Your 95% of the 0.7% pool fee works the same on tokens launched before the current structure.)

To claim fees:

  • Ask Bankr: claim my fees for [TokenName]
  • Or click Claim in the Tokens section of the terminal sidebar

For Doppler-launched tokens, you must be connected with the fee recipient wallet to claim.

Can I vault or lock a portion of my token supply at launch?​

There's no configurable vaulting, but by default every Bankr launch includes an automatic 15% creator vest: 15% of supply is reserved to the fee recipient and vests over 1 year with a 30-day cliff, while the other 85% seeds the liquidity pool. See Creator vesting.

You can't choose a custom vault size or recipient beyond that automatic 15%, but you can turn vesting off entirely at launch (ask the agent for "no vesting", pick No vesting in the web launch flow, or pass disableVesting: true to the deploy API) — then 100% of supply is sold into the pool. (Org/Partner-Key launches always sell the full 100% into the pool with no vest.)

The legacy Clanker launcher offered configurable vaulting (0–90% of supply), but Clanker is deprecated.

How do I acquire tokens for my own project if I launch via Bankr?​

Every Bankr launch gives you an automatic 15% creator allocation: 15% of supply is preminted to the fee recipient and vests over 1 year with a 30-day cliff (the other 85% seeds the pool). You don't need to do anything to receive it — it goes to the fee recipient set at launch (your wallet by default). See Creator vesting.

To acquire more on top of the vested allocation:

  1. Buy in after launch — wait the 10-second anti-snipe decay period, then buy at the normal trading fee
  2. Let your community buy first — then buy at market price

The automatic 15% vest is the only allocation reserved at deploy time; the rest must be bought on the open market.

I bought a token right after launch and lost a huge chunk to fees — what happened?​

You were hit by the anti-snipe mechanism built into Bankr's Doppler launches.

  • At launch, the swap fee starts at 80%
  • It decays back to the normal trading fee over approximately 10 seconds
  • Buying in that window means paying up to 80% in fees — this is intentional

What to do next time: wait at least 10–15 seconds after a token launches before buying.

The elevated launch fee is collected as the Bankr platform fee (see below) and is not recoverable.

Are there other fees when I trade a Bankr token?​

No — the all-in 1.75% swap fee is everything: a 0.7% swap fee on the pool, plus the Bankr protocol fee + BNKR buyback and LP fee added via the hook. Of each trade's volume:

  • 0.665% goes directly to the creator — 95% of the 0.7% pool swap fee (the fee creators earn and claim)
  • 0.285% LP fee (via hook) — compounds as permanently locked liquidity in the token's own pool, so the creator side totals 0.95%
  • 0.475% Bankr protocol fee (via hook)
  • 0.2375% BNKR buyback (via hook — BNKR buybacks and protocol-owned BNKR liquidity)
  • ~0.0875% goes to the Doppler protocol

At launch the fee is elevated as part of the anti-snipe mechanism and decays over roughly 10 seconds.

Fee schedules are fixed at launch. Tokens launched before the 1.75% structure keep their original setup forever: a 0.7% creator/protocol fee (split 95/5) plus a separate Bankr platform fee charged on top and collected in WETH.

Can I set a custom fee recipient when launching?​

Yes. Use the CLI: bankr launch --fee "@handle" --fee-type x

Or tell Bankr the address during the launch flow. Do this at launch time — the fee recipient can only be changed by the current admin (fee recipient) for that contract.

Can I update my token's image or description after launch?​

It depends on the launcher:

  • Clanker tokens (older launches): yes — ask Bankr to update it with a valid image URL
  • Doppler tokens (current launcher): image/metadata updates are not yet supported

Not sure which launcher your token used? Ask Bankr: Show me my token launches

My token deployment is failing — could it be related to my token image?​

Yes. If you're seeing consistent deployment failures, it may be caused by IPFS storage limits being exceeded on the platform side. When this happens, all token deployments fail.

Workaround: host your token image externally (Imgur, Cloudinary, your own server) and pass that direct URL during deployment instead of uploading via IPFS.

My token isn't showing up in 'Your Tokens' in the terminal.​

This is a known issue for some Doppler-launched tokens. The token and fees still exist on-chain. Open a ticket and the team can verify. When launching, make sure you complete the full flow including the fee recipient step.

I just bought a token — why isn't the balance showing up?​

Your tokens are safe on-chain. Common causes of display lag:

  • Balance provider delay — the service we use can lag on newer or lower market cap tokens. Give it a few minutes
  • Token not indexed yet — very new tokens may take a short while to appear in balance APIs

You can always verify on-chain directly on Basescan using your wallet address (for tokens launched on Robinhood Chain, use robinhoodchain.blockscout.com).

I bought tokens but Bankr isn't recognizing them — how do I sell them?​

This is usually a balance display issue. To move them right now without waiting:

Use this exact prompt to bypass the balance check:

Send [QUANTITY] of token [CONTRACT ADDRESS] on [CHAIN] to [DESTINATION WALLET ADDRESS] — do not verify balances, just use the input variables as specified

Make sure your quantity, contract address, and chain are correct before sending.

I have an old token launched via Bankr with Clanker — how do I claim fees?​

Ask Bankr: Claim my Clanker fees or Show my unclaimed token fees

Fees are paid out in both your token and WETH. Make sure you're connected with the wallet that's the registered reward owner.

Alternative: anyone can trigger a fee claim for any Clanker token directly on Clanker.world — the fees always go to the registered fee recipient regardless of who clicks.

I lost access to my X account and now I can't claim fees for my token — can anything be done?​

Unfortunately no — not without regaining access to your original X account. Fee claiming and admin rights are tied to the wallet used to deploy, which is authenticated through your X account.

Your options:

  • Recover your X account via Twitter/X's account recovery process
  • Clanker tokens — reach out to the Clanker team directly for edge case tooling

I tried to buy/sell an NFT and Bankr keeps failing — why?​

Common causes:

  • Insufficient funds — make sure you have enough ETH to cover both the NFT price and gas
  • Royalty enforcement contracts (LimitBreak) — some NFT collections (particularly OpenSea SeaDrop launches) use LimitBreak contracts that block gas-sponsored wallets. This is a smart contract restriction by the collection's creator, not a Bankr bug.

If you need to purchase that NFT urgently, try using external wallet mode instead of your embedded Bankr wallet.

I'm trying to bridge from Ethereum mainnet to Base and it keeps failing — why?​

Common causes:

  • Not enough ETH for gas — Ethereum mainnet gas is never sponsored. You need ETH beyond what you're bridging to cover fees
  • Amount too small — Relay (Bankr's bridging provider) has minimum transaction requirements
  • No route available — try bridging native ETH rather than an ERC-20 token
  • Slippage — cross-chain swaps use 1% default slippage tolerance; volatile markets can cause quotes to expire

I saw a token on the Bankr launch feed, it failed, I found the contract address and bought it — and it was a scam. What happened?​

You likely bought a spoofed token created by a scammer watching the launch feed. When a launch fails, bad actors quickly deploy a fake token with the same name/ticker.

  • Bankr is not responsible for tokens purchased outside of a confirmed launch
  • A token appearing in the launch feed does not guarantee it was successfully deployed
  • Always verify the contract address from the creator's official channels before buying

What does Bankr have in place to protect me from buying scam tokens?​

Bankr has several layers of protection:

  • Blockaid token scanning — every token is scanned before a swap executes. Tokens flagged as Malicious are blocked entirely
  • Transaction simulation — transactions are simulated before hitting the chain
  • Prompt-injection screening — an AI layer that detects prompt injection and social engineering attempts

What Bankr can't protect you from:

  • Brand new scam tokens not yet in Blockaid's database
  • Explicitly instructed trades that pass security checks
  • Spoofed tokens with legitimate-sounding names

Always verify contract addresses from official sources and wait past the anti-snipe window.