Skip to content

Technology

Proof-of-AI

How useful AI work can be evidenced, verified and connected to on-chain settlement.

Two engines. One network.

Work determines contribution. Stake secures finality.

AIPoW

Purpose

  • Work-based issuance
  • Bitcoin merge mining
  • Useful AI enhancement
  • Permissionless work contribution

DPoS

Purpose

  • Canonical consensus
  • Finality
  • Smart-contract state
  • Governance
  • Settlement

“AIPoW does not replace consensus. DPoS does not replace work. BitcoinAI uses each mechanism for the role it performs best.”

AI receipts

Compact evidence on-chain. Heavy AI data off-chain.

Engineering
ProofOfAIReceiptschema · conceptual
Proof-of-AI receipt fields
FieldTypeDescription
job_idUnique job identifier
requesterAccount that requested the job
provider_idAI provider identity
model_idModel identifier
model_hashModel version or artifact hash
input_hashCommitment to the request input
output_hashCommitment to the result
exec_meta_hashExecution metadata commitment
Developer view: 7 more fields
Additional receipt fields
nonceAnti-replay nonce
verificationVerification method / tier
provider_sigProvider signature
verifier_evidenceIndependent verifier evidence
tee_attestationTEE attestation hash
zk_proofzk proof hash
payment_refSettlement / payment reference

Anti-replay binding

Hash(chain_id || epoch || miner_address || auxpow_work_id || model_hash || input_hash || output_hash || job_nonce)

Conceptual binding structure; final encoding is implementation-defined.

Merkle batching

Merkle root → on-chainreceipts (off-chain data, on-chain inclusion proofs)
1. Many receipts2. One Merkle root3. Compact on-chain commitment4. Individual inclusion proofs

AI off-chain. Trust on-chain.

BitcoinAI coordinates AI without making every validator run the model.

Request on BitcoinAI. Execute on BatteryAGI. Verify on BitcoinAI. Settle in BATT.

  1. 01BitcoinAIRequest created
  2. 02BatteryAGIQuote returned
  3. 03BitcoinAIBTCAI escrowed
  4. 04BatteryAGIJob routed
  5. 05Off-chainBatteryAGI executes
  6. 06Off-chainResult produced
  7. 07BatteryAGI → BitcoinAIProof-of-AI receipt returned
  8. 08BitcoinAIBitcoinAI verifies
  9. 09BitcoinAISettlement released
  10. 10BATTBATT providers paid

Stays off-chain

  • Prompts
  • Model weights
  • Images / video
  • Embeddings
  • Tensors
  • Logs
  • Large model outputs

Recorded on BitcoinAI

  • State
  • Commitments
  • Receipts
  • Settlement
  • Verification
  • Smart-contract consequences

Built for AI-scale activity

The AI runs where computing is efficient. BitcoinAI records what matters.

100K–500K

Designed for 100,000–500,000 concurrent AI transactions/jobs.

Research targetEngineering target; subject to benchmark validation.

Native finalized throughput remains an engineering and benchmarking target until demonstrated under reproducible multi-validator testing.

  1. 01Users, Apps & AI Agents
  2. 02BitcoinAI Transaction Lanes
    • AI request
    • Receipt
    • AIPoW
    • Settlement
    • Cross-chain
  3. 03Parallel Execution
  4. 04Merkle Batching & Proof Layer
  5. 05BatteryAGI + Battery Coin Compute Mesh

Parallel execution

Independent lanes process non-conflicting transactions side by side.

Low-contention state

State is partitioned so hot accounts don't serialize the whole chain.

Compact commitments

Merkle batching anchors many results in small on-chain proofs.

Off-chain AI compute

Models run on BatteryAGI; the chain verifies receipts, not tensors.

Architecture becomes software

The protocol only matters if developers can turn it into useful systems.

BitcoinAI's technical layers are being engineered so builders can work from understandable application primitives down into consensus, proofs and interoperability when deeper control is required.

Temporary Unsplash placeholder · Photo by Vitaly Gariev