Bankr: Financial infrastructure for agents, with a launchpad attached

At first glance Bankr looks like a chat-based token launchpad. It is closer to a complete financial stack built so AI agents can fund themselves, and the launchpad is the front door. Bankr originally launched on Clanker's infrastructure; in February 2026 it moved to Doppler, locking in permanent Uniswap V4 rails and a simple, direct creator-fee model: 95% of a 0.7% swap fee, routed to the creator on every trade.

Because a Bankr launch takes one sentence, founders treat it as point-and-click. The platform deliberately restricts configuration to make launching easy, but there is still a gap between deploying and deploying well. The decisions that matter (wallets, fee routing, supply management, community messaging) are front-loaded and irreversible. This low barrier to launching creates interesting complications as well: community members can launch tokens on your behalf, as $SURPLUS recently reminded everyone, and the team then inherits choices it never made.

The platform also ships fast. A default 15% team treasury and Glidepath, a transparent liquidation tool both arrived in the last couple weeks. Launches are Base-only ERC-20s today, while the broader platform already supports agentic swaps and NFTs across ten networks. On July 2, 2026, Bankr announced upcoming support for token launches on Robinhood Chain, a natural step since Doppler already supports the chain and Bankr's own docs now list it for swaps and tokenized stocks. The launch flow itself is not yet documented.

As a token advisory firm, we care as much about the operations of bringing a token to market as we do about the engineering. This guide breaks Bankr down mechanism by mechanism, separating the levers you control from the constants you inherit.

We'll cover:

• Bankr tokenomics overview - supply, fees, and what is fixed at the protocol level.
• How a launch deploys - the four surfaces and what differs between them.
• Supply, vesting, and founder allocation - tokenomics considerations.
• The fee lifecycle - reading, claiming, and transferring creator fees.
• Glidepath - AI-paced liquidations, and why a public commitment can be bullish.
• Token operations - wallet setup and opsec for a one-shot deploy.
• When to use Bankr - considerations in choosing Bankr as a launchpad.
• Robinhood Chain - previewing the next deploy surface.

Bankr tokenomics overview

Every token launched on Bankr has a fixed supply of 100 billion. At launch the supply splits permanently: 85% seeds the pool and trades from the first second, and 15% vests to the the launch-time fee recipient, fully locked for 90 days and then unlocking continuously over the remaining 21 months. Note that launches deployed with an org Partner Key sell the full 100% into the pool and do not include creator vesting.

The vesting recipient is set forever at deploy, so the configuration is incredibly important.

Every trade comes with a hardcoded 0.7% swap fee. As the creator, you keep 95% of that (about 0.665% per trade), while Doppler takes the remaining 5%. While this is slightly lower than what you might get on Clanker (1%) or Flaunch (0.8%), Bankr makes up for it by giving you a built-in 15% vested team allocation—something those competitors don't include by default. (Note: if you launched a token under Bankr's old 1.2% fee structure, you are grandfathered in. Whatever the fee was on your launch day, it stays that way forever.)

Once your token is live, it is totally locked. There are no admin keys, no pause buttons, and you cannot move or withdraw the liquidity pool. You don't own the pool. What you deploy is exactly what you and your community will live with.

To protect the launch, Bankr uses a 10-second anti-sniper shield. In the very first second of trading, the fee is cranked all the way up to 80% to aggressively punish any trading bots trying to snipe the first block. Over the next ten seconds, the fee smoothly drops back down to the normal 0.7%, leaving a fair market.

How a launch deploys

Bankr exposes four token launch methods:

• Natural language. “deploy a token called MyAgent with symbol AGENT,” from the Terminal, the Bankr agent, or social. Tokens default to Base.
• Social (@bankrbot). Tag the bot in a post on X and the token is live before the thread finishes. The deploy is the marketing.
• CLI (bankr launch). An interactive wizard, or headless with --yes, with full control over name, image, associated tweet, website, and fee recipient. The path when metadata and fee routing matter.
• OpenClaw / Token Strategist. For autonomous agents: the Token Strategist skill scores a concept against five market forces, sets up fee distribution, and executes through the CLI.

Deployment is gas-sponsored within limits: 50 tokens per day on a standard account, 100 for Bankr Club. Bot-like deploy patterns trip spam protection and can restrict an account, so programmatic deployers should clear their use case with support before scaling.

The social launch is a real edge for narrative and agent launches, where speed and proof-of-life matter more than configuration. For anything with a cap table or a fee-routing plan, deploy from the CLI so the metadata and the beneficiary are correct at block one.

Supply, vesting, and founder allocation

Bankr’s default 15% allocation locks into a visible schedule, ending the era where founders had to secretly buy up their own token supply at launch just to secure funding. As those tokens unlock, teams can easily apply further custom vesting using tools like Sablier.

The biggest advantage is flexibility. This 15% is a single, unified bucket that teams can use however they want - whether for founder pay, an operational treasury, or both. By putting this baseline allocation on a predictable schedule, Bankr builds immediate community trust and drastically reduces the need to hoard extra tokens off the open market.

However, if your project requires a massive treasury beyond this 15%, you may still need to acquire extra supply. If you do, the golden rule applies: be completely transparent with your community and publish a clear plan for how and when you will liquidate those funds.

If your project needs a more complex setup or extra funding beyond the default, you have a few options:

• Custom Smart Contracts (DERC20): You can work directly with the Bankr team before you launch to hardcode a custom split. For example, LienFi used this to mathematically lock their ecosystem fund all the way until 2030.
• Live Off the Fees: Because your trading fees pay out in a mix of WETH and your native token, you can actually leave your 15% token stash completely untouched and fund your daily operations strictly using that ongoing revenue. Just keep in mind that the WETH-to-Token ratio fluctuates based on market activity, so don't build your budget assuming a perfect 50/50 split.
• The Treasury Snipe: Just wait out the 10-second anti-bot penalty, then buy your extra treasury tokens directly from the open market. Be warned that if you do this, you should be transparent with the community on how many tokens were purchased

The fee lifecycle

Once your token is live, trading fees become your main financial tool. Everything is public - anyone can see exactly how much you are earning on-chain or through Bankr's open API. When you claim those fees, they pay out as a mix of WETH and your native token. Bankr will cover the gas fees for up to 10 claims a day if you're using one of their managed wallets, but if you're claiming to a standard cold wallet, you'll need to pay the ETH for gas yourself.

By default, the massive 95% creator fee goes straight to the wallet that launched the token. You can permanently transfer this revenue stream to a new wallet at any time, but there is a catch: any unclaimed fees already sitting in the pool will go to the new wallet the moment you make the switch. Always claim your existing balance before handing over the keys.

Founders usually transfer the fee stream for three reasons:

• Upgrading the Treasury: Moving funds from a single developer's wallet to a more secure corporate multisig.
• Project Handoffs: Passing ownership of the project to a new team or a DAO.
• Emergency Security: Quickly pointing the money stream to a fresh wallet if a private key gets compromised.

If you do transfer the project to a new team, there is one massive trap you need to avoid: transferring the fee stream does not move your 15% vested token allocation. That vesting address is permanently locked into the smart contract the second you launch. If you hand the project over, you have to create a separate agreement to settle those vested tokens, because the protocol simply cannot reroute them for you.

Glidepath: AI powered treasury management

Glidepath is a treasury management tool built by Bankr that allows for scheduled liquidation of your team’s unlocked tokens.

Interestingly, scheduling your sales publicly can actually be bullish because certainty kills investor fear. When buyers see your exact caps and timelines, the panic disappears. It’s the most credible way to take profit without destroying your own chart.

However, two catches remain: selling is still selling - sometimes holding to grow the project is the smarter move - and the system currently runs on Bankr's private servers, not an unbreakable smart contract. Because a founder can cancel the plan at any time, you should view Glidepath as a strong show of good faith rather than an ironclad guarantee.

How it works:

• Commit. You lock a chosen amount of your own tokens to a vesting wallet. Your LP is never touched.
• 48-hour heads-up. Selling starts after a roughly 48-hour public window, from the current market cap, not the higher caps shown in the preview.
• AI-paced slices. Each sale is sized to live liquidity and volume, capped to a fraction of real depth, with timing fuzzed so it is harder to front-run.
• Live transparency. The token page shows how much is committed and how much remains, in real time.
• Configuration. Your real choices are the amount committed, the source wallet, whether to cancel, and how you communicate it. Bankr controls execution after commit: pacing, slice sizing, and timing. The LP is never touched, and Glidepath does not reroute vesting or fee rights.
• Cancellation. Within ~30 minutes of committing it is an instant undo. After selling begins, cancellation stops sales immediately; unsold tokens return after a public 7-day cooldown, and realized proceeds stay with you.

How you use it is a treasury decision, and sophisticated holders will read it closely. Three funding approaches cover most teams, ordered from least to most likely:

Use a Glidepath when:

• Your wallet is outgrowing pool depth. This happens fast on Bankr: fees accrue in native tokens and the 15% starts unlocking at day 90.
• You need operating cash beyond the WETH stream. A transparent schedule beats a discovered dump every time.
• You are handing the project over. Glide out before transferring ownership.
• The overhang itself is the problem. When the community is obsessing over your wallet size, naming your number is the fastest way to un-freeze the bid.

Skip it when:

• The pool is too thin. Even capped slices will dominate volume and crush price.
• WETH fees already cover costs. Unsold native supply is dry powder, not an obligation.
• You are disguising a full exit. Commit 100% of your holdings and the market reads the abandonment instantly and reprices, no matter how slow the schedule.

We’d love to see some enhancements to Glidepath:

• Irrevocable mode. Let founders lock the schedule so it cannot be canceled. A commitment that cannot be walked back should earn a credibility premium over a soft promise.
• Verifiable caps. Publish the per-slice sell limits and make them checkable on-chain, so holders verify the math instead of trusting the AI.
• Execution receipts and an API. An open feed of what has sold, what remains, the executed price, and when the next window opens.
• A circuit-breaker. An optional price floor that pauses selling in a crash, so the schedule never liquidates a treasury for pennies.
• Auto-commit. Route newly claimed fees and fresh unlocks straight into the Glidepath so they never pile up in a personal wallet.

Token operations

Permissionless launchpads give you one shot, and Bankr's deployer configuration and vault recipient are hardcoded. Speed at the deploy box should never replace opsec. We recommend a small set of multisig wallets, 2-of-3 signers at minimum, separated by function.

A few practices belong on the launch checklist:

• Treat the deploy as one-shot. Triple-check the beneficiary, the vault recipient, and the metadata before signing, with a second pair of eyes.
• Sweep on a schedule. Claim and move proceeds to treasury on a cadence rather than letting balances sit in an operational wallet.
• Mind the ten-claims-per-day gas ceiling. Pre-fund external signers, or route claims through a Bankr-managed wallet.
• Label your wallets publicly. Tag the deployer, vault, and treasury on Basescan so the community can tell vesting movement apart from sell pressure.
• Pre-announce unlocks. Communicate the 15% vesting schedule, and any DERC20 schedule, before tokens move, so a scheduled unlock never reads as a surprise dump.

When to use Bankr

Bankr is the right call when the launch matches what the platform optimizes for.

• Agent self-funding tokens. The defaults are purpose-built: zero configuration, instant deploy, a simple direct creator-fee stream, sponsored gas, and an LLM Gateway that routes fee revenue straight to compute. DRB, an agent token that did over $70M in volume, is the archetype: the fee flow is the product.
• Narrative and social launches. Deploying from a post creates instant social proof. CLAWD peaked near a $40M market cap days after its January 2026 deployment and used the stack's immutability, with admin set to the burn address, as a credibility feature.
• Structured launches, if you use the vesting surface. LienFi proved a real cap table is possible through DERC20. The default path is intentionally narrow, so know which primitives are available and lock the configuration before deploy.

The usual permissionless tradeoffs (locked LP, no admin keys, no pause) apply to Bankr as they do to every launchpad in the category, and we covered them in the tokenomics section. Two distinctions are specific to Bankr within the Base ecosystem:

• Fee economics are constants, not choices. The 0.7% fee and the 95/5 split are hardcoded on standard launches. If your model needs creator-set fee levels, a different split, or revenue routed into buybacks, Clanker and Flaunch offer more flexibility, and higher default creator takes of roughly 1% and 0.8% of volume.
• No auction phase. Bankr launches go live instantly at a fixed range. If price discovery before open trading is the thesis, deploy through Doppler directly, which supports Dutch-auction mechanics on the same underlying stack.

Robinhood Chain: the next surface, previewed

On July 1, 2026, Robinhood Chain went live on mainnet: an Arbitrum Orbit L2 with roughly 100-millisecond blocks, built around tokenized stocks, with Uniswap as a day-one partner. Bankr has said token launches there are coming and has published no docs. The preview still writes itself, because Bankr's stack is Doppler underneath and Doppler already supports Robinhood Chain launches through its multicurve create flow, documented in a walkthrough posted July 2.

If Bankr adopts that model, the striking part is how much becomes configurable. The Base flow froze nearly everything. Doppler's Robinhood flow is the opposite:

The open question is which of those knobs Bankr freezes. Everything about the Base surface says it will pick one fee tier and standardize the curves. That is right for the memecoin surface and wrong if the vesting primitives get buried the way DERC20 was buried on Base, where LienFi needed direct coordination to build a cap table. On Robinhood the config surface already exists; hiding it would be a choice.

Whichever contracts ship, the chain changes the launch calculus:

• A new buyer, not a narrower one. Brokerage customers in 120-plus countries (U.S. excluded for stock tokens) on top of crypto-native flow. Memecoins are already emerging on the chain, and launchpad support is the tell: Robinhood wants the full spectrum of tokens, not an enterprise-only catalog. The open question is distribution, since @bankrbot's social-deploy virality has no proven equivalent there yet.
• A natural fit for agents. A 100-millisecond chain with retail flow is a strong surface for Bankr's agentic stack. Agents that deploy, swap, and fund themselves from fee revenue can operate at chain speed, against a buyer base crypto-native launchpads have never reached.
• Partial rails. Uniswap handles pooling from day one, but indexer and analytics coverage will lag, and a fee dashboard that cannot see the chain is a fee stream you cannot verify.
• Faster blocks. At 100-millisecond blocks, the ten-second fee decay spans about a hundred blocks, a stronger anti-snipe window, but only if the decay hook gets ported and tuned. Without it, speed favors bots.

What we hope Bankr designs for:

• Port the anti-snipe decay, rescaled to the new block cadence. A fast chain without it hands the open to bots.
• Keep fee parity and one dashboard. Same 95/5 split, sponsored gas, and open fee reads, with a chain field in the API so Base and Robinhood tokens roll up into a single view.
• Expose the multicurve and vesting surface as first-class CLI options, not a partner-only conversation.
• Ship Glidepath on day one. A young chain with thin liquidity is exactly where an uncapped dev exit does the most damage.
• State any launch standards up front. The chain is clearly open to all token types. If the regulated context ever brings listing rules, publishing them early beats surprising builders later.

Robinhood Chain is the first real test of whether Bankr's stack is portable or merely resident on Base. The decay hook, the fixed split, the fee lifecycle, and the social deploy are each an integration choice on the new chain rather than an inheritance.

Conclusion

Bankr is the fastest way to launch a fee-generating token on Base, but just like with other launchpads, it's also permanent. The anti-bot protections, the locked liquidity pool, the fixed fee splits, and the rigid team vesting schedule aren't restrictions you can work around, they are the core design. They reward founders who understand exactly what they are doing before hitting deploy. And teams should be fully ready to manage the token operations as soon as the token is launched.

Published by Ventari. We advise on tokenomics, launch mechanics, and liquidity design for teams launching on Base. If your next launch needs more than a chat command, let's talk.

Sources

Bankr and Doppler sources

• Bankr getting-started overview
• Bankr token-launch overview
• Bankr token-launch FAQ
• Bankr fee splitting
• Bankr reading fees
• Bankr claiming fees
• Bankr transferring fees
• Bankr Glidepath
• Bankr LLM Gateway
• Bankr supported chains
• Bankr token-launch API
• Doppler documentation
• Doppler SDK

Robinhood Chain and tokenized-stock sources

• Robinhood Chain mainnet announcement
• Arbitrum’s Robinhood Chain announcement
• Robinhood Chain overview
• Robinhood Chain contracts
• Bankr tokenized stocks