Partnership · BOT Chain

A partnership packet for BOT Chain

BOLT is the operating layer that turns BOT Chain into a complete DeFi + AI ecosystem. This page is a one-screen pitch for the BOT Chain core team.

176 / 176 testsDeployed on Bohr (chain 968)Mainnet activation pending

What it does

  • Native AMM + router. Phase 1 shipped — pairs, fees, treasury accrual.
  • Launch infrastructure. Phase 2 shipped — registry, locker, vesting.
  • Grant accountability. Sprint 4 shipped — registry + Merkle payouts.
  • AI-agent registry. Phase 2 shipped — base layer for AgentFi.
  • Vaults + router aggregation + adapters. Phase 3 shipped; BDEX / Bridge adapters gated until BOT Chain publishes their ABIs.
  • Compute-asset registry. Phase 3 — future BOT Chain compute liquidity.
  • BOLT Spark. Phase 4 — permissionless bonding-curve launch layer with auto-migration into BOLT pools at graduation.

Why BOT Chain needs it

BOT Chain currently relies on B DEX as the only liquidity primitive. That's a single-point dependency for an entire ecosystem. BOLT is the second liquidity primitive — open-source, audit-ready, BOT-aligned, and independent of B DEX. It ships with the missing infrastructure (launches, locks, vesting, grants, registries) that B DEX does not provide.

Strategic role: BOLT is to BOT Chain what Raydium / Meteora are to Solana — except BOLT also ships the launchpad, the grant program, and the AI-agent registry as native primitives, not third-party add-ons.

Readiness evidence

  • 18 Solidity contracts deployed on Bohr; 176 / 176 Foundry tests passing.
  • All four phases (Core AMM, Launch, Grants, Liquidity infra) deployed to BOT Chain testnet (Bohr · chainId 968). Addresses public on /contracts/.
  • B DEX (Uniswap V3 fork) router/factory/quoter consistency read-only validated against mainnet.
  • BOT Chain RPC https://rpc.botchain.ai verified live (chainId 0x2a5).
  • Audit packet at audit/ — 6 documents covering scope, threat model, contracts, test catalog, known limitations.
  • Deployment scripts refuse to run unless chainId matches the target network and deployer balance > 0.

Once mainnet deployment completes

  • Day 0 — BOT Chain provides: funded deployer EOA, explorer API key, testnet RPC + chainId, finality estimate.
  • Day +3 — Phase 1 deployed; all contracts verified on scan.botchain.ai.
  • Day +5 — Phase 2 deployed; pnpm smoke:botchain clean.
  • Day +7 — Indexer running against mainnet; app.boltterminal.xyz on live data.
  • Day +14 — First weekly grant epoch published via BoltGrantPayouts; claim UI shipped.
  • Day +21 — Milestone 1 — Phase 1 + Phase 2 + Grants live; first 2 epochs distributed; dashboards public.
  • Day +30 — Audit engagement; audit/ packet handed off.
  • Day +45 — Milestone 2 — audit report delivered; high/critical findings remediated.
  • Day +60 — Phase 3 contracts written, tests passing; awaiting BDEX + Bridge ABIs.
  • Day +90 — Milestone 3 — Phase 3 mainnet deployment (vaults, aggregator, compute registry); cumulative KPIs reported.

Commercial value

  • Swap protocol fee (1/6 of LP fee growth → BOT treasury).
  • Launch setup fee + premium placement.
  • Liquidity lock + vesting setup fees.
  • Grant Engine SaaS.
  • Market Maker Desk subscriptions.
  • Nexus analytics / API access.
  • BO Wallet routing revenue share (post-listing).
  • BOLT Spark launch fee, bonding-curve trade fee, migration fee, featured placement, BOLT Verified upgrades.
  • Future token / governance model (deferred until contracts are stable).

What BOLT needs from BOT Chain

  • Funded deployer EOA (~0.75 BOT for Phase 1 + 2; ~1.5 BOT for early grant epochs).
  • BOTCHAIN_EXPLORER_API_KEY for scan.botchain.ai/api (unblocks contract verification).
  • Testnet RPC + chainId (unblocks CI against a real non-local environment).
  • Finality model (typical reorg depth) — sets indexer cursor + grant epoch cadence.
  • B DEX router + factory ABI (Phase 3 BDEXAdapter activation).
  • BOT Bridge ABI / API (Phase 3 BridgeAdapter activation).
  • BO Wallet listing process (so BOLT appears in the wallet dApp browser).
  • Grant economics target — total weekly BOT allocation + expected eligible user count.
BOLT Spark for BOT Chain. Spark adds a permissionless launch layer to the ecosystem. Strategic upside for BOT Chain: new token launches, new active wallets, additional gas volume, fresh pair candidates for BOLT pools and B DEX, more Scheme A grant candidates, and a launchpad story competitive with leading L1/L2 ecosystems.
Partnership structure. We are open to a grant-funded ecosystem partnership, a strategic investment, or a deeper acquisition structure if BOT Chain wants BOLT to become a primary liquidity terminal. We are happy to ship as an independent ecosystem participant.

Initial milestone funding · $150k – $250k

Funds the work required to move BOLT from Bohr testnet to BOT Chain mainnet and stand up the first ecosystem cohort. Approximate use of funds:

  • Contract verification — submit every Bohr / mainnet deployment to scan.bohr.life and scan.botchain.ai, plus the third-party audit engagement bundle.
  • Mainnet deployment — fund the deployer multisig and operate Phase 1 → Phase 4 mainnet rollout under the existing fail-closed scripts.
  • BDEX routed-swap validation — exercise a routed swap against a Bohr B DEX pool, then activate BDEXAdapter in two-step pattern.
  • BridgeAdapter verification — read the BOT Bridge EIP-1967 implementation, sign off the public surface, then activate.
  • BO Wallet listing — submission, asset packaging, listing follow-through.
  • First ecosystem launches — operator support for the first cohort of Spark + BoltLaunchFactory projects (incubation, locker setup, vesting wiring, BOLT Verified review).
  • Grant Engine alignment with Scheme A — wire the BOT Chain Foundation Scheme A scoring into the BoltGrantPayouts epoch builder so eligible users claim grants without leaving BOLT.

The exact tranche structure is open to BOT Chain Foundation preferences (single grant, milestone-gated tranches, strategic investment).

Request technical walkthroughView proof packReview Bohr deployment