Keep the complete technical schemas available without forcing every developer to read them on the landing page.
See technical details
Build • Test • Integrate
Build decentralized AI applications.
BitcoinAI is being designed to give developers primitives for AI job requests, routing, verification, escrow, payments, autonomous agents, smart contracts and multichain messaging—while clearly labeling what is available, under development or planned.
- Sovereign L1
- Cosmos-Derived
- Canonical
- Planned
- EVM-Compatible
- Planned
- Cosmos Connectivity
- IBC-First
- Planned
- Planned
- AI-Native APIs
- Planned
Start here
Understand the primitives before writing code.
BitcoinAI is pre-testnet. There is no public SDK, endpoint or contract runtime yet — this page documents the intended developer surface so you can design ahead.
Step 1
Choose Your Application Type
- Smart contract
- AI agent
- Appchain
- AI provider
- Cross-chain app
Step 2
Choose Your Execution Path
- Native module
- EVM contract
- Appchain
- External-chain adapter
Step 3
Use BitcoinAI Primitives
- AI job
- Escrow
- Receipt
- Settlement
- Cross-chain message
Step 4
Test Before Mainnet
- Local dev
- Testnet
- Integration tests
- Security review
SDK package — planned
There is no install command yet. No @bitcoinai package is published to npm.
How the pieces fit together
Develop at the application layer without losing sight of the protocol underneath.
- L5ApplicationsdAppsEnterprise systemsGamesWallets
- L4Smart Contracts / Appchains / AI AgentsApplication logicSpecialized chainsPermissioned agents
- L3BitcoinAI ModulesAI jobsSettlementCross-chain AIFees
- L2AIPoW + DPoSBitcoin-compatible workValidator finality
- L1Bitcoin / BatteryAGI / MultichainWork anchorAI executionExternal ecosystems
AI-native primitive
AI requests should be first-class application objects.
- 1Create
- 2Quote
- 3Escrow
- 4Route
- 5Execute
- 6Verify
- 7Settle
- 8Callback
type AIJobRequest = {
requester: string;
modelPolicy: string;
inputHash: string;
maxCost: string;
paymentAsset: string;
sourceChain?: string;
callback?: string;
timeout?: number;
};Illustrative — conceptual shape only. Not a published or stable interface; field names and types will change.
modelPolicy- Which models, tiers and providers are acceptable.
inputHash- Commitment to the input; the raw input stays off-chain.
maxCost- Upper bound the requester is willing to escrow.
timeout- Deadline after which the job fails and refunds.
On-chain job states
CanonicalQUOTEDESCROWEDSENT_TO_BATTERYEXECUTINGRESULT_RETURNEDPROOF_VERIFIEDPAYMENT_RELEASEDBATT_SETTLEDCOMPLETE
Programmable applications
Use smart contracts for application logic — not protocol-critical shortcuts.
// Illustrative interface only — not a deployed or stable ABI.
interface IBitcoinAIJob {
function requestAI(bytes calldata request)
external
payable
returns (bytes32 jobId);
}No ABI is stable. Contract interfaces will be published with the runtime specification.
Use cases
- Escrow
- Agents
- NFTs
- DeFi
- Marketplaces
- Tokenized assets
- Solidity compatibility target
- Familiar Solidity contracts and compiler toolchains.
- Wallet / tooling target
- Standard EVM wallets, Hardhat / Foundry-style workflows.
- JSON-RPC target
- Ethereum-style JSON-RPC exposed by the planned EVM runtime.
- Deployment flow
- Compile → test on localnet → deploy to testnet → audit → mainnet.
- 01Compile
- 02Localnet
- 03Testnet
- 04Audit
- 05Mainnet
Developer guides
Open the implementation guide you need.
Build with BitcoinAI
Build applications that connect Bitcoin, AI, and multichain infrastructure.
Design against the primitives now, and be ready when localnet and testnet open.