Developers
Appchains and modules
The architecture and checklist for application-specific chains and deeper protocol integration.
Native protocol modules
Security-critical functions belong in native modules.
x/aipowEngineeringAccept and weight merge-mined work within the epoch budget
- Inputs
- AuxPoW claims, Bitcoin headers, optional Proof-of-AI
- Outputs
- Accepted work, epoch reward instructions
x/bitcoinEngineeringTrack Bitcoin headers, chainwork and reorgs
- Inputs
- Relayed Bitcoin block headers
- Outputs
- Canonical tip, confirmation depth
x/aiCanonicalAI job lifecycle, escrow and receipt verification
- Inputs
- AI job requests, provider receipts
- Outputs
- Job state, verification result
x/settlementPlannedBATT settlement instructions and fee split
- Inputs
- Verified jobs, escrowed value
- Outputs
- Provider and validator settlement
x/crosschainaiEngineeringCross-chain AI request routing, timeouts and callbacks
- Inputs
- IBC packets, adapter messages
- Outputs
- Acknowledgements, callbacks, refunds
x/stakingCanonicalDelegated Proof of Stake with effective-stake cap
- Inputs
- Bonds, delegations, evidence
- Outputs
- Validator set, voting power
x/governanceCanonicalParameter changes and upgrades
- Inputs
- Proposals, votes
- Outputs
- Approved parameter / software changes
x/feesCanonicalFee collection and distribution
- Inputs
- Transaction and AI service fees
- Outputs
- Distribution to validators, delegators, providers
These names describe responsibilities, not code that exists today. No public protocol repository has been published yet.
Code meets infrastructure
AI-native applications need both software primitives and reliable compute.
Developers can design application logic around requests, receipts, contracts and settlement while compute providers and validators handle different parts of the underlying execution path.
Temporary Unsplash placeholder · Photo by Vitaly Gariev
Build a specialized chain
Appchains can consume BitcoinAI AI, proof, and settlement primitives.
- Step 1: Choose chain security modelYour own validators, shared security or another model — it is not inherited automatically.
- Step 2: Configure interoperabilityIBC channel or adapter, with a documented trust model.
- Step 3: Define AI request pathWhich jobs are sent to BitcoinAI and who pays.
- Step 4: Define settlement assetWhat escrows and settles each job.
- Step 5: Define callback rulesWhere results land and how they are applied.
- Step 6: Define timeoutDeadlines and the refund path on expiry.
- Step 7: Define trust assumptionsWrite down what each party must trust.
- Step 8: Test failure handlingTimeouts, invalid proofs, relayer outages, reorgs.
Future developer assets
- Appchain templatePlanned
- IBC configPlanned
- Reference adapterPlanned
- Sample AI callback contractPlanned