Skip to content

Ecosystem

Multichain and interoperability

How AI jobs and applications can move across networks while preserving security and status transparency.

Multichain by design

BitcoinAI is designed to coordinate activity across multiple ecosystems.

BitcoinAI as a routing and verification hub connected to 11 ecosystems; none of the routes is live.Bitcoin-connectedCosmos / IBCEthereumBaseArbitrumOptimismBNB ChainPolygonSolanaAppchainsFuture chainsBitcoinAIroute · verify · settle
  • Bitcoin-connected applicationsResearch target
  • Cosmos / IBCPlanned
  • EthereumPlanned
  • BasePlanned
  • ArbitrumPlanned
  • OptimismPlanned
  • BNB ChainPlanned
  • PolygonPlanned
  • SolanaResearch target
  • AppchainsPlanned
  • Future chainsResearch target

No external-chain integration is live. Each route is listed with its own status.

  1. L3AI protocolJob, receipt, verification and settlement semantics
  2. L2Message formatTransport-agnostic cross-chain AI request
  3. L1TransportIBC, bridge adapters, messaging networks — per route
The AI transaction model should remain independent from the transport layer. IBC, bridge adapters, messaging networks, and future interoperability systems carry messages; they do not define the BitcoinAI AI protocol itself.

AI that crosses chains

An AI request can begin on one chain and return somewhere else.

Cross-chain AI jobs are asynchronous state machines with explicit request, acknowledgment, timeout, verification, and settlement states.

Engineering
  1. 01Source Chain
  2. 02Cross-Chain Request
  3. 03BitcoinAI
  4. 04BatteryAGI
  5. 05Proof-of-AI
  6. 06BitcoinAI Verification
  7. 07Settlement / Callback
  8. 08Destination Chain

Explicit job states

  1. 01REQUESTEDRequest emitted on the source chain
  2. 02RECEIVEDBitcoinAI acknowledges the packet
  3. 03ESCROWEDPayment locked against the job
  4. 04EXECUTINGBatteryAGI routes and runs the job
  5. 05VERIFIEDProof-of-AI receipt checked on BitcoinAI
  6. 06CALLBACK_PENDINGResult relayed to the destination
  7. 07CALLBACK_COMPLETEDestination acknowledged; settled
  8. FAILED / TIMEOUTFailure state: Deadline passed or proof invalid → refund path
Cross-chain jobs are asynchronous, not pretend atomic transactions across unrelated consensus systems.

Every route has a security model

Cross-chain connectivity must be evaluated route by route.

Engineering
Cross-chain risks and the controls that address them
Bridge compromiseControl: Route-specific policy, value limits, circuit breakers
Message replayControl: Sequence numbers and nonces bound to chain IDs
Stale stateControl: Timeouts and acknowledgments
Destination-chain reorgControl: Finality thresholds per destination
Validator mismatchControl: Light clients where available
Oracle failureControl: Multiple sources, bounds and fallbacks
Callback failureControl: Retry windows and refund paths

Controls toolkit

  • Sequence numbers
  • Nonces
  • Timeouts
  • Acknowledgments
  • Finality thresholds
  • Light clients
  • Route-specific policy
  • Circuit breakers

What is ready vs. what is planned

Application capabilities should be transparent before mainnet.

  • CanonicalPart of the current canonical protocol design. Not yet live; may change before mainnet through the published specification process.
  • PlannedPart of the current design and roadmap. Not yet launched.
  • Research targetAn engineering or research goal. Not a demonstrated production benchmark; subject to independent validation.
  • EngineeringBeing specified and engineered. Exact parameters and rules are not final.
  • Testnet TBDNot yet set. The value will be defined in the testnet specification and published before it applies.
Ecosystem capabilities and their status
Sovereign L1CanonicalCosmos SDK / CometBFT sovereign Layer 1
Smart contractsPlannedApplication-layer programmable state
EVM compatibilityPlannedEVM-compatible smart-contract execution
CosmWasm / WASMPlannedWebAssembly smart contracts (CosmWasm)
IBCPlannedIBC channels to Cosmos-ecosystem chains
EVM adaptersPlannedAdapters for Ethereum and EVM L2 ecosystems
Solana adaptersResearch targetAdapters for Solana-connected applications
Appchain SDKPlannedTooling to connect appchains to BitcoinAI
Cross-chain AI requestEngineeringAsynchronous request / acknowledgement / timeout / callback
BTC payment adapterResearch targetEscrow adapter, channel, bridge or L2 — not selected
Tokenized asset toolkitPlannedReference contracts and workflows for tokenized assets
NFT toolkitPlannedReference NFT / digital-asset contracts
AI marketplacePlannedComposable AI services
Enterprise private-AI integrationPlannedPrivate execution with public commitments
Financial-market modulesResearch targetSettlement, collateral and audit-trail primitives for licensed operators
Agent permission frameworkPlannedApplication-layer policy engine
Appchain templatesPlannedStarter appchain configurations
Developer SDKPlanned@bitcoinai/* TypeScript packages — not published
ExplorerPlannedBlock and AI-job explorer
FaucetPlannedTest-token faucet
Public testnetTestnet TBDLaunch date and parameters not yet set

Nothing on this page is live on mainnet. Statuses update here as each capability ships.

Keep exploring

BitcoinAI is designed for an intelligent economy that operates across borders, industries and communities.Photo by Max van den Oetelaar · Unsplash