$B2B Protocol Whitepaper

Version 1.1. Base. Launch day.

1. What this is

$B2B is a swarm of eight AI bots on Telegram that work on chain for you.

You open a private chat. They join. You ask them to look at a token, watch a wallet, or plan a trade. They split the work between them, each one does its part, and they report back in plain language. Every check they run reads live data from the chain. They do not call out to other paid APIs for the things that matter.

That is the product. A team of specialist agents in your pocket, working on Base, on demand.

2. Why a swarm

Most "AI agents" are one bot wrapping ChatGPT. That is fine for chatting. It is not fine for on chain work, because one model has to pretend it is also a node, also a security researcher, also a holder analyst, also a market data feed. It does all of them badly.

We split the job across eight bots. Each one has a small, clear role. They run at the same time. The Coordinator stitches their answers into one report.

The eight agents:

  • Coordinator. Reads what you wrote, picks a plan, sends work out, collects the answers.
  • Intel. Pulls live data for any address, token, or contract on Base.
  • Auditor. Runs the contract through twenty five plus security checks against the raw bytecode.
  • Whales. Maps the top holders, deployer, and LP wallets. Falls back to RPC log scanning when explorers fail.
  • Markets. Pulls live price, liquidity depth, and trade volume.
  • Risk. Takes everything above and produces one risk score with a short verdict.
  • Exec. Builds trade plans through Uniswap v2 and v3 on Base with risk gates in front.
  • Watcher. Runs long jobs in the background. Wallet alerts, price triggers, scheduled actions.

You always talk to the Coordinator. The Coordinator decides who does what.

3. How a request flows

You type "deep dive 0xabc...". Here is what happens in your group.

1. Coordinator parses the request, picks "deep audit" as the plan. 2. Coordinator dispatches Intel, Auditor, Whales, and Markets at the same time. 3. The four specialists run in parallel. Each one returns a short structured block. 4. Coordinator passes the four results to Risk. 5. Risk writes the final score and short verdict. 6. Coordinator posts the summary and offers buttons for the next action.

Total time, under sixty seconds for almost every token.

4. The token

$B2B is the protocol's token on Base.

Total supply is one billion. Fixed. There is no mint function. Once the contract is deployed, the supply is the supply forever.

At launch, the allocation is simple:

  • 95% (950,000,000 tokens) into liquidity. Paired with ETH on Uniswap V2 (Base). The LP tokens are locked.
  • 5% (50,000,000 tokens) held by the team wallet. Used for exchanges, partnerships, and operating costs.

No private sale. No public sale. No allocations. No farm rewards. No airdrops at launch. No tax on any trade, ever.

Anti sniper limits

For the first hour of trading the contract enforces two limits that grow on their own. After the limits reach total supply, they have no effect.

  • Max wallet starts at 2% of supply (20,000,000 tokens) the second trading is enabled.
  • Max transaction starts at 1% of supply (10,000,000 tokens) the second trading is enabled.
  • Both limits grow by 0.03% of total supply per second. That is 300,000 tokens of headroom added every second to each limit.
  • Max wallet reaches total supply at 3,267 seconds after trading start. That is about 54 minutes 27 seconds.
  • Max transaction reaches total supply at 3,300 seconds after trading start. That is 55 minutes.

After both limits hit total supply the contract behaves like a plain ERC20. There is also a one way removeLimits() switch the owner can pull earlier if the chart is already healthy.

What the owner cannot do, ever

  • Mint new tokens. There is no mint function.
  • Blacklist a wallet. There is no blacklist function.
  • Pause trading once it is enabled. The enable switch is one way.
  • Add a tax. There is no tax code path in the contract.
  • Slow the limit growth, change the growth rate, or reset the timer. The growth schedule is a hard coded constant.

What the owner can do

  • Enable trading once.
  • Flag the LP pair address.
  • Exclude a wallet from the limits (used for CEX listings, market makers, the team wallet itself).
  • Remove the limits early as a one way switch.
  • Renounce ownership. After renounce, none of the above is possible by anyone.

5. The product roadmap

We ship the swarm on launch day. That is what is live right now.

Next, in order:

  • Phase A. Audited Escrow and Registry on Base. Bots stake $B2B to be eligible for work. Failed work gets slashed.
  • Phase B. Real trade execution by Exec, gated by Risk. Buys and sells on Uniswap v2 and v3, from your Telegram, with risk checks in front of every order.
  • Phase C. Monitor worker. The Watcher gets a persistent polling worker so alerts fire from the cloud, not your phone.
  • Phase D. Multi chain. Ethereum mainnet, then BNB, then Arbitrum.

We do not promise dates. We promise the order.

6. The hard problems

We are honest about what is hard.

  • Trade execution needs a hot wallet. Any bot that buys and sells for you must hold keys. We mitigate this with per action caps, risk gates in front of every order, and a user set max exposure. Real execution waits for a clean audit.
  • MEV bots are faster than us. We do not promise to be first. We promise to be safe first. Every trade goes through Risk before Exec.
  • AI is fallible. The bots can be wrong. Always cross check. Start with small amounts.

7. Risks and disclaimers

$B2B is a utility token, not a security. Holding it grants no claim on revenue, equity, or assets. The contract is open source. The total supply is fixed. You should read the contract before buying.

Autonomous on chain action carries real risk. Smart contracts can have bugs. Networks can congest. AI bots can hallucinate. Use small amounts until you trust the agents.

This is not financial advice.

8. Where to find everything

  • Contract source: /contracts/src/B2BLaunchToken.sol in the repo.
  • Deployed address: see /contracts/deployments/launch-base.json after launch.
  • BaseScan: the verified source code page goes live at deploy time and links from the website.
  • Telegram: the Coordinator bot is linked from the website.