Today, any ClawBank OS company can launch a token on Base: a 1 billion supply, the entire supply locked in a Uniswap v4 pool quoted in CLAWBANK, from the operator's own wallet, with the gas sponsored.
When we shipped ClawBank OS in August, a company could import a token it already had. Launching one was still on the list for later. It ships inside ClawBank OS now, from HQ, from a text to Manfred, from any MCP client, or from the API.
ClawBank OS: The Self-Optimizing Crypto Company (Alpha) August 28
Today we're releasing ClawBank OS in alpha.
ClawBank is a set of tools you add to an agent stack you already run. Manfred is one client, and an agent you operate yourself over MCP is another. That agent can form the legal entity, move money through the bank account, and sign the company's contracts.
ClawBank OS is where the same company gets a public face: a site the builder deploys, a domain paid in USDC, a business email on that domain, and an X account attached to the company.
Built on OpenLaunch
The launch infra is built on OpenLaunch from @kevincodex (Also founder of Twigpine). We've both been building agent-centric tools over the last year, and this is finally where our stacks have a chance to meet.
One transaction on OpenLaunch's canonical factory launches it. ClawBank builds that transaction, sponsors the gas, and asks you to confirm. Your wallet is the launcher, and OpenLaunch's locker holds the liquidity. Collecting fees calls the locker on-chain, so the token and the pool keep trading even if openlaunch.lol is down. Their site is the public page for the description, image, banner, and links, and it also lets you trade the pool directly. Factory addresses, locker addresses, and the rules around both are in OpenLaunch's rules.
Launch Structure
Your own self-custody wallet sends the transaction, so make sure you interact with the ClawBank Money capabilities at least once before you try. If that wallet does not exist yet, the launch refuses and tells you to open Money and retry.
The token is a plain ERC-20 with a fixed supply of 1,000,000,000 and 18 decimals. That is the supply the contract will ever have. The contract has no further minting, and it has no owner, pause, or blacklist.
The pool is Uniswap v4, and every launch we do is quoted in CLAWBANK. The entire supply goes into one liquidity position, owned by OpenLaunch's locker. The locker has no withdraw, decrease, or burn path, so the liquidity stays where this transaction put it. The same transaction writes the fee recipients, and those recipients are fixed.
You choose the name (1 to 40 characters) and the ticker (1 to 10 characters, letters and digits). You can add a description, website, image, banner, and X handle now, or leave them blank and set them later. The website defaults to the company's live domain. If the company has no domain yet, it defaults to the deployed site.
The opening price is a dollar FDV between $1,000 and $1,000,000. Leave it blank, and the pool opens at $10,000. ClawBank reads the live CLAWBANK/USD mark, converts your FDV into a Uniswap start tick, and snaps to the nearest valid tick. Ticks come in multiples of 200, which is why the preview can disagree slightly with the number you typed, in dollars and in CLAWBANK. The preview is the price that goes on-chain. If two price sources diverge by more than 5%, the launch stops. A guessed mark would be a different product from the one on the preview.
When the transaction mines, the company is recorded as having launched a token, and the contract shows up in your wallet as a token you can trade. Share the address from the on-chain Launched event. You will also get a trade page at https://openlaunch.lol/t/base/<token> and a contract page on Basescan. A failed launch deploys nothing, and you can try again. One token per company.
Import is still there for a Base token the company already had. That path stores the address on the company. A launch creates a CLAWBANK pool and a fee split, and an imported token already uses the company's one token slot.
Fee Splits
ClawBank OS token launches charge a pool fee is 3%. The percentages are split as follows: half to the company wallet, 30% burned, and 20% to the ClawBank treasury. On $1,000,000 of volume, the fee is $30,000: $15,000 to the company wallet, $9,000 burned, and $6,000 to the ClawBank treasury.
The company wallet is the same wallet that launched. The burn share goes to the dead address and is destroyed when fees are collected. The ClawBank share pays the ClawBank treasury, and that address is written into the launch in the open.
Uniswap takes the fee from the incoming token, so the two directions burn different assets. A buy brings CLAWBANK in and the company token out, and the burn share of that fee destroys CLAWBANK. A sell brings the company token in, and the burn share destroys it.
Fees sit in the pool until somebody collects them. Collect is permissionless. It takes nothing from your wallet; the gas is sponsored, and every recipient is paid in the same transaction, so nothing is left to claim afterward. The web UI has a Collect fees button. A text or an agent can collect without a second YES, because nothing leaves the wallet. The number on the Token card is what has already been collected, counted in CLAWBANK.
Launch Process
Start with a preview. A preview moves nothing, and the screen has to be right: the opening FDV in dollars and in CLAWBANK, the pool fee, and each recipient with a percentage and an address. It should also say that the whole supply goes into the locked pool, that this launch has no allocation and no vest, that the fee routing cannot be changed, and that the gas is sponsored.
Once the preview looks right, the launch is four steps.
- Open Money once, so the wallet exists.
- Preview a name, a ticker, and an opening FDV.
- Read the actual FDV and the recipient list on the preview.
- Confirm. HQ has a confirm screen. A text pauses for YES, and that prompt names the ticker, the company, the opening FDV, and the 3% split, and it tells you the routing cannot be changed. An API caller with a send-scoped token checks the ticker and the FDV before calling launch.
Quote and launch take the same arguments everywhere: name, symbol, opening_fdv_usd, and optionally a description, website, image, banner, and X handle. If the account has one company, you can omit company_id. The company name works as the id.
An agent previews with quote_os_token_launch and launches with launch_os_token. Quote needs a read scope. Launch needs send. Over HTTP those are POST /api/v1/os/companies/:id/token/launch/quote and POST /api/v1/os/companies/:id/token/launch. The quote comes back with gas_sponsored: true. The launch returns launch.token_address only after the chain event, and that field is the address to give people. The rest of the fields, scopes, and errors are in the ClawBank OS docs.
The public page can still change after launch. Description is plain text, up to 280 characters. Image URL, banner URL, website, and X handle can change with it. A blank field keeps the current value, and only HTTPS URLs are accepted. The wallet that launched is the wallet that signs the edit. The edit costs no gas and moves no funds. In a text, you confirm the company and the fields you are changing, and the prompt tells you the name, the ticker, and the fees stay as they are. HQ can also generate a wide banner and publish it with the company site, so the token page has an image to fetch.
Token Distribution
The new token is tradable in your wallet as soon as the launch lands. The Token card links to a spot buy, a DCA, and a buy-the-dip. Trade quotes the buy in USDC and routes it through the CLAWBANK pool. The first quote on a new pool can take about a minute. An empty quote on that first try means the route is still waking up, so wait and quote again.
Once the token has a price, the same wallet can run momentum, mean reversion, grid, and rebalancing. A strategy spends your money. That money is separate from the locked launch liquidity, and the strategy is separate from Trade to Earn. HQ deep-links those three from the card. The rest of the strategy set is there once you ask for it.
ClawBank Deals already accepts any Base ERC-20 you hold, and a token you just launched is one of them. You escrow some of it. You get a claim code, shown once, and a preview link that shows the terms. Redeeming takes the code, so the preview link is safe to post. Whoever redeems the code first gets the deal. If the code goes unclaimed, the tokens come back when the window ends. The window is 7 days unless you choose another.
You buy the token before you can deal it. Every token from the launch sits in the pool, so you get yours the same way any buyer does: by paying the pool. The buy moves the price. The deal spends what that buy left in your wallet.
Deals on this token come in the same three shapes as deals on any other token.
- Liquid. The recipient gets tokens they can hold or sell.
- Vested. Claiming mints a non-transferable Sablier stream to their wallet, and the tokens vest along a straight line over anywhere from 1 to 730 days. What has vested is theirs. The stream stays in their wallet, which keeps the unvested position from being sold.
- KPI. The tokens release only if a market cap holds at or above a threshold for a sustained window, 24 hours by default, before a deadline you set. The check runs every 15 minutes, and the level has to hold, so a wick through the number leaves the tokens where they are. The watched token defaults to the token in the deal, and you can point the condition at a different token. Miss the deadline and the tokens return to you. After the deal is accepted, the condition and the deadline are what end it.
Liquid deals are free. Vested and KPI deals carry a small creation fee, and that fee buys back CLAWBANK. A vested deal also has a cancel choice, set when you create it and shown before the recipient accepts. Canceling returns whatever has not vested yet, and tokens already vested stay with them.
A KOL deal you can cut the same day: buy a slice, escrow 1 million of your tokens, and release it only if the market cap holds $5 million for 24 hours within 90 days. You hand over the code yourself, by text, email, DM, or out loud across a table. Sending it is your job. They claim by opening the link, by typing the code into the console, by texting Manfred CLAIM and the code, or by having an agent redeem it. If they have no account, claiming creates the wallet, and the claim costs them nothing. We sponsor that gas. If the market cap never holds, the tokens come back to you.
The company keeps its bank rail on that same account. After the bank KYC, fiat moves between the rail and the self-custody wallet, so dollars can come in and go out beside the pool. The agent that launched can run the buy and the deal, then move dollars on the bank rail when you tell it to.
Locked Parameters
A handful of terms freeze when the transaction mines. A later edit of the public page leaves every one of these in place.
- The name and the ticker.
- The supply of 1 billion, with no further minting.
- The pair, which is CLAWBANK.
- The pool fee, 3%, and who receives it: 50% to the company wallet, 30% burned, 20% to the ClawBank treasury.
- The lock on the liquidity.
Description, image, banner, website, and X handle stay editable. The launcher wallet signs that edit; it costs no gas, and a blank field keeps the current value.
Price discovery belongs to the pool. Whoever wants the token buys it, including you. Vesting and KPIs happen after, in a deal, and the deal spends tokens you bought. The pool opens at the FDV on the preview. The first buyers get that price, and a bot that lands in the opening block is one of those buyers.
Formation gave agents a body. Records gave them a memory. Contracts let them make promises. Deals let them bind a token to an outcome. ClawBank OS gave the company a public face. A launch gives that company a market, quoted in CLAWBANK.
Originally published on X.