Developers
SDK, API and local development
The practical tools and environments for building against BitcoinAI as engineering work becomes available.
One developer experience
Expose the protocol through small, composable SDKs.
@bitcoinai/sdkCore client: accounts, signing, transactions, queries
@bitcoinai/aiAI job requests, quotes, receiptsdepends on @bitcoinai/sdk@bitcoinai/aipowAIPoW claim parsing and verification helpersdepends on @bitcoinai/sdk@bitcoinai/crosschainCross-chain AI request encoding and trackingdepends on @bitcoinai/sdk, @bitcoinai/ai@bitcoinai/contractsTyped bindings for the planned EVM runtimedepends on @bitcoinai/sdk@bitcoinai/appchainAppchain integration helpers and fixturesdepends on @bitcoinai/sdk, @bitcoinai/crosschain
- Dependency rules
- Packages depend only on @bitcoinai/sdk or lower layers — no cycles, no wallet or UI framework dependencies.
- Semver plan
- 0.x during testnet (breaking changes allowed with notes); 1.0 only after mainnet interfaces settle.
- Browser / Node compatibility
- ESM-first, tree-shakeable, no Node-only APIs in browser entry points.
Connect to the network
Keep APIs explicit, versioned, and easy to inspect.
- Cosmos RPCPlannedCometBFT RPCendpoint: not yet published
- REST APIPlannedCosmos REST / gRPC-gatewayendpoint: not yet published
- gRPCPlannedCosmos SDK gRPC servicesendpoint: not yet published
- EVM JSON-RPCPlannedEthereum-style JSON-RPC for the planned EVM runtimeendpoint: not yet published
- WebSocketPlannedEvent subscriptionsendpoint: not yet published
- AI Job APIPlannedCreate, quote, escrow and track AI jobsendpoint: not yet published
- AIPoW relay APIEngineeringMerge-mining work submission relayendpoint: not yet published
- Cross-chain APIPlannedCross-chain AI request trackingendpoint: not yet published
- Provider APIPlannedProvider-facing job and settlement APIsendpoint: not yet published
Develop locally
Build against local infrastructure before testnet.
bitcoinai-nodeBitcoinAI nodevalidators ×4Local validator setevm-runtimeLocal EVM runtimemock-batteryagiMock BatteryAGI providermock-battMock BATT settlementbtc-fixturesTest Bitcoin headers / fixturesibc-appchainLocal IBC / appchain fixture
# Illustrative future layout — this file does not exist yet.
services:
bitcoinai-node: { ports: ["26657", "1317", "9090"] }
validator: { deploy: { replicas: 4 } }
evm-runtime: { ports: ["8545"] }
mock-batteryagi: { depends_on: [bitcoinai-node] }
mock-batt: { depends_on: [bitcoinai-node] }
btc-fixtures: { volumes: ["./fixtures/headers:/data"] }
ibc-appchain: { depends_on: [bitcoinai-node] }Test before mainnet
Every integration should survive a hostile testnet.
- FaucetComing with testnet
- ExplorerComing with testnet
- RPCComing with testnet
- DocsComing with testnet
- Validator guideComing with testnet
- AIPoW test relayComing with testnet
- AI provider sandboxComing with testnet
- Smart-contract deploymentComing with testnet
- Cross-chain demoComing with testnet
A hostile testnet should include
- Invalid and replayed receipts
- Provider timeouts and outages
- Relayer delays and dropped packets
- Reorgs on connected chains
- Adversarial agents hitting spending limits
No testnet endpoint, faucet or explorer exists yet. Links will appear here when they do.
Built by people
The next AI economy will be created by builders.
Developers, entrepreneurs and operators turn protocols into useful products. BitcoinAI is designed to give them open infrastructure for intelligent applications.
Temporary Unsplash placeholder · Photo by litoon dev