Every number on this page is a constant in a deployed contract or a rate you can verify on chain. Where something is a judgement call or an open risk, it says so.
One transaction deploys your token, creates a Uniswap V3 pool paired to USDC, mints the entire supply into that pool as single-sided liquidity, and locks the position permanently.
| Supply | 1,000,000,000 | Fixed. No mint function exists. |
|---|---|---|
| Owner | none | The token has no admin after deploy. |
| Transfer tax | 0% | No tax code path exists. |
| Pool | 1% tier | Uniswap V3, paired to native Arc USDC. |
| Opening price | ~$0.0000052 | About $5.2K fully diluted. |
| Address | β¦0000 | Every token address ends in 0000. The salt is ground in your browser before signing. |
| Launch fee | 0.01 USDC | Plus Arc gas, which is paid in USDC. |
For the first 2 blocks, buying from the pool is blocked entirely, and during the restricted window no wallet may end up holding more than 5% of supply.
Every parameter is checked before the token contract is created, so a rejected launch costs you the gas of a cheap revert rather than a full deployment. The page also re-reads the live launch terms and refuses to send if they differ from what it was built against; the contract re-checks the same hash when the transaction executes, so nothing can change between the two.
A trader pays exactly one fee: the 1% Uniswap V3 pool fee, the same on every token here. Nothing is added on top by us at swap time.
Uniswap pays that fee out in both assets of the pair, and each side is treated differently.
Rounding remainders always go to the creator. Integer division leaves at most a couple of micro-USDC per collection; it lands on the creator's side, never ours.
The protocol never holds or sells a token launched here. Its share of the token-denominated fees goes
to 0xβ¦dEaD in full, which means every fee collection also shrinks that token's supply.
Creators are paid in USDC only, deliberately: a payout in your own thin-liquidity token is not really
a payout.
constant in the deployed contract, not settings.
There is no setter. No admin key, including ours, can retune them. Changing them would require
deploying a different contract, which existing pools would not use.
33% of the USDC side of the 1% pool fee, forever, on every trade of the token you launched. In round numbers: $1,000 of volume produces $10 of pool fees, of which about $3.30 is yours.
Fees accrue in the locked position and are paid out when collectFees is called for your
token. Anyone can trigger it; the recipients are fixed on chain, so an open call cannot misdirect
anything. You may also point your share at a different wallet.
The buyback share accumulates as USDC in a vault. On a schedule, a keeper spends it on DOTCOM, the protocol token, and the purchased tokens go straight to the burn address inside the swap itself. They never rest in the vault.
A knockout position is time-boxed exposure: you pick a token, a USDC amount and a duration, pay the duration's price up front, and the token amount is fixed at entry. Survive to expiry and the tokens are delivered to your wallet. Touch the barrier first and the position ends, costing you what you paid. In traditional markets this instrument is called a knockout certificate.
| Duration | You pay (of exposure) | Knocks out if it falls |
|---|---|---|
| 1 hour | 75% | ~17% |
| 4 hours | 67% | ~26% |
| 12 hours | 60% | ~34% |
| 24 hours | 53% | ~42% |
| 3 days | 45% | ~50% |
| 7 days | 37% | ~59% |
The barrier is exact: a position knocks out when its value falls to 110% of what you paid. While your tokens are worth more than 110% of your payment, you cannot be knocked out. After expiry, no knockout is possible at any price; delivery is a right.
Both directions between Base and Arc, over two independent Circle rails: CCTP and Gateway. You pick the rail; if either is unavailable on the current network, its selector is disabled before any money moves. The service fee is 2% of the amount sent, and 3% on CCTP fast transfers, always shown in the quote before you sign. The rates are compile-time constants in the collectors; no setter exists.
| You send | 1,000.00 USDC |
|---|---|
| Bridge fee (2%) | β20.00 |
| Circle Gateway fee | β0.011 |
| You receive | 979.99 USDC |
The fee is taken on the source chain, and the remainder is deposited into your own Circle
Gateway balance using depositFor. You then sign your own burn intent for your own funds.
Nothing of yours is ever held by us, in either direction.
Share your link. When someone who arrived through it trades, you earn 20% of the protocol's revenue from their activity, paid in USDC.
Worked through: a referred wallet trades $10,000. That produces $100 of pool fees, of which $34 is the protocol's share, of which $6.80 is yours.
These are properties of the code, not promises:
| Liquidity | The locker contract has no function that withdraws, decreases or transfers a position. There is no path to remove launch liquidity, for anyone. |
|---|---|
| Fee split | Compile-time constants. No setter exists. |
| Buyback target | Set once, then permanently rejected. |
| Factory binding | The locker binds to one factory once and refuses to be repointed. |
| Referral claims | Cannot be paused. A pause switch over withdrawals is a rug vector and is deliberately absent. |
| Ownership | renounceOwnership is disabled, so the protocol cannot be
accidentally bricked into an unmanageable state. |
Verify everything above yourself. Nothing here asks for trust that the chain cannot confirm.
This page is updated with the live addresses the moment the contracts are deployed and verified on Blockscout.
Swapping and launching are ordinary transactions and work in any wallet. Bridging is different: it asks you to sign an off-chain message that authorises Circle to move your deposited USDC. Some wallets display that message poorly, and a few refuse to sign typed data from a site they do not recognise.
Rabby is what we test against. It decodes the message and shows you the recipient and amount before you approve, which is exactly what you want to check on a bridge.
Rabby flags this bridge contract as new with a trust score of zero, and points out it was deployed within the last few days. Both are true. It went live on 30 July 2026 and has almost no volume through it yet, so there is nothing for a reputation system to score. Those warnings fade on their own as the contract ages and gets used. Suppressing them would mean defeating a mechanism that exists to protect you.
Signing to bridge triggers a separate warning, because you are signing an off-chain message rather than a transaction. That message authorises Circle to move your deposited USDC, which is exactly the pattern phishing sites abuse, so your wallet is right to interrupt. Read it: the recipient shown must be your own address. Our code checks the same fields and refuses to sign if any of them is wrong, but your wallet is the one you should trust.
No third-party audit. The contracts have a test suite covering the fee split, the burn path, the buyback guards and the anti-snipe rules. A test suite is not an audit. One is worth commissioning before the value at stake exceeds what an audit costs, and that has not happened yet.
Arc's Uniswap V3 is a community deployment. It is verified on chain but it is not an official Uniswap deployment. Every pool here depends on it.
Thin pools move on small trades. A new pool holds a few thousand dollars. The swap page refuses to quote when the spot price has run more than 15% from its one-minute average, because that pattern usually means manipulation, but that is a guard rail and not protection.
Nothing here is advice. This site publishes data and executes transactions you sign. It does not tell you what to buy, and it never will.
Something broke, a number looks wrong, a transaction did not do what the page said it would? Write to support@dotcombubble.fun. Include the wallet address, the transaction hash if there is one, and what you expected to happen. Both inboxes are read by a person.
| Support | support@dotcombubble.fun for bugs, stuck transactions, wrong data and questions about how something works. |
|---|---|
| Security | security@dotcombubble.fun for anything that could lose somebody money: a contract flaw, a way around a guard, a frontend that can be made to sign the wrong thing. Please write here first, before posting it anywhere public, so it can be fixed while nobody is exposed. There is no paid bounty programme yet. |
| X | @dotcombubblefun for announcements. Direct messages there are not a support channel. |