Skip to content
A monetary-system scene: a gold-rimmed coin with an abstract ledger mark above a chain of ledger blocks and a descending staircase of halving bars, over a blue network grid

Optimism community · Planned EVM adapter

Connect Optimism applications to verifiable AI.

A planned EVM adapter could let Optimism applications request AI through BitcoinAI, receive verified result commitments and retain their users, assets, consensus and canonical state on Optimism.

08

Modular EVM superchain

Keep Optimism. Add an AI coordination layer.

Superchain applications can explore consistent AI request semantics while each route preserves its own finality assumptions.

PlannedPlanned EVM adapter

What Optimism already does well

OP Stack modularity, shared standards and a growing network of EVM chains.

  • OP Stack modularity, shared standards and a growing network of EVM chains.
  • Solidity-compatible developer workflows
  • Programmable application state
  • Established wallet and contract patterns

What BitcoinAI can add

Planned AI-request contracts, BatteryAGI execution, Proof-of-AI receipts and asynchronous callbacks.

  • Planned EVM transport adapter
  • BatteryAGI execution
  • Proof-of-AI receipts
  • AI-agent infrastructure
  • Asynchronous callbacks and settlement

Asynchronous cross-chain architecture

How a Optimism AI request could work.

Messaging is transport. BitcoinAI defines the AI transaction semantics, BatteryAGI coordinates heavy execution, and the source environment remains authoritative for its own state.

  1. 01

    Optimism application creates an AI request

  2. 02

    Planned EVM adapter transports the request

  3. 03

    BitcoinAI finalizes job and payment state

  4. 04

    BatteryAGI executes the workload

  5. 05

    Proof-of-AI receipt is verified

  6. 06

    Result callback returns to Optimism

The route is an asynchronous state machine. Acknowledgement is not finality, and every transport keeps its own validator, bridge, custody and reorganization assumptions.

Application opportunities

What Optimism builders could create.

These are design opportunities, not claims of live integrations or guaranteed adoption.

01

Cross-chain agents

Use cross-chain agents with explicit job, verification, timeout and callback states.

02

Public-goods analysis

Use public-goods analysis with explicit job, verification, timeout and callback states.

03

Governance tooling

Use governance tooling with explicit job, verification, timeout and callback states.

04

Application automation

Use application automation with explicit job, verification, timeout and callback states.

05

Creator services

Use creator services with explicit job, verification, timeout and callback states.

06

Shared AI markets

Use shared ai markets with explicit job, verification, timeout and callback states.

Builder surface

Build the adapter, the application or the proof layer.

The integration surface spans contracts, message encoding, provider selection, receipts, callbacks, observability and failure handling.

Request contracts

Typed Optimism contracts for job creation, budgets, timeouts and callbacks.

Agent applications

Bounded automation with owner permissions, spend limits and auditable results.

Verification tools

Receipt explorers, provider reputation and portable proof interfaces.

Settlement UX

Clear pending, verified, failed, timed-out and refunded application states.

Security and trust boundaries

Connection does not erase sovereignty.

Optimism keeps its users, assets, application state, consensus and governance. BitcoinAI verifies its own AI job and settlement state.

  • Optimism integration is planned and is not live.
  • Optimism retains its own consensus, application state and governance.
  • The route is asynchronous; applications must handle timeouts, replay protection and failed verification.
  • Every bridge, relayer and liquidity route retains its own security and custody assumptions.

Planned EVM adapter

Build the Optimism AI route.

Developers can help specify the Optimism route, test failure states and build applications that use AI without asking the community to abandon its own chain.