Skip to content

Technology

Scale, security and status

Research targets, engineering boundaries and the status of the protocol components behind the overview.

Scaling for AI

Scale execution by separating consensus, parallel processing, proof batching, and AI compute.

1 · Transaction lanes

  • Consensus critical
  • AIPoW
  • AI requests
  • AI receipts
  • Settlement
  • Cross-chain
  • General transactions

2 · Parallel execution

  • BlockSTM-style deterministic parallelism
  • Application-aware scheduling
  • Low-contention state design

3 · State partition keys

  • job ID
  • provider ID
  • model ID
  • chain ID
  • settlement ID
  • receipt batch ID

4 · Merkle batching

Compress many AI events into compact commitments.

5 · Off-chain compute

BatteryAGI · Provider network · Horizontal scaling

100,000–500,000

concurrent AI transactions/jobs

Research target

100K+ native TPS is a research/engineering target and must not be presented as achieved until reproducible multi-validator benchmarks exist.

Defense in depth

Separate responsibilities. Contain failures. Verify everything.

No system is absolutely secure. BitcoinAI's design aims to limit the blast radius of any single failure.

Bitcoin Work Layer

Risks

  • Pool concentration
  • Invalid AuxPoW
  • Stale work
  • Chain reorg assumptions

Mitigations

  • Verification
  • Chainwork tracking
  • Confirmations
  • Policy thresholds

PoS Layer

Risks

  • Validator concentration
  • Downtime
  • Equivocation
  • Governance capture

Mitigations

  • Delegation spread
  • Stake cap
  • Slashing
  • Governance thresholds

AI Layer

Risks

  • Fake receipts
  • Replay
  • Provider fraud
  • Unverifiable proprietary models

Mitigations

  • Signed receipts
  • Nonces
  • Commitments
  • Verifier tiers
  • TEE / zk options

Cross-Chain Layer

Risks

  • Bridge failure
  • Adapter compromise
  • Message reordering
  • Destination-chain finality

Mitigations

  • Route-specific security
  • Timeouts
  • Acknowledgements
  • Asynchronous state machines

What is final vs. what is still being engineered

Clear status. No hidden assumptions.

  • CanonicalPart of the current canonical protocol design. Not yet live; may change before mainnet through the published specification process.
  • ProposedA proposed design parameter subject to review, governance and change.
  • PlannedPart of the current design and roadmap. Not yet launched.
  • EngineeringBeing specified and engineered. Exact parameters and rules are not final.
  • Research targetAn engineering or research goal. Not a demonstrated production benchmark; subject to independent validation.
  • Sovereign Cosmos-derived Layer 1Canonical
    Current design
    Cosmos SDK / CometBFT sovereign L1
    Finalization needed:
    Mainnet genesis parameters
  • AIPoWCanonical
    Current design
    AuxPoW-verified work with halving envelope
    Finalization needed:
    Epoch length and envelope parameters
  • Delegated Proof of StakeCanonical
    Current design
    Validator + delegator security, BFT finality
    Finalization needed:
    Active set size, slashing parameters
  • 210,000,000 max supplyCanonical
    Current design
    Fixed ceiling, 105M / 105M split
    Finalization needed:
    Genesis distribution details
  • 1.00 / 1.05 work weightsCanonical
    Current design
    Relative weights within a fixed budget
    Finalization needed:
    Proof-of-AI qualification rules
  • 20% active distributionCanonical
    Current design
    Share of halving envelope actively distributed
    Finalization needed:
    Governance change process
  • 40% / 60% active splitCanonical
    Current design
    Work providers / validators + delegators
    Finalization needed:
    —
  • 10,000,000 validator capCanonical
    Current design
    Linear effective stake up to cap
    Finalization needed:
    Enforcement module specification
  • Bitcoin light clientEngineering
    Current design
    Header tracking, chainwork, canonical tip, reorg handling, confirmation depth
    Finalization needed:
    Confirmation depth and reorg policy
  • AuxPoW implementation detailsEngineering
    Current design
    Merge-mining proof format, share vs. block handling, pool integration
    Finalization needed:
    Final proof format and pool integration
  • Proof-of-AI receipt standardEngineering
    Current design
    Signed receipts, anti-replay binding, verifier tiers, Merkle batching
    Finalization needed:
    Encoding, verifier set, tier policy
  • EVM runtimePlanned
    Current design
    EVM-compatible smart-contract execution
    Finalization needed:
    Runtime selection and audit
  • CosmWasm / WASMPlanned
    Current design
    WebAssembly smart contracts (CosmWasm)
    Finalization needed:
    Scope decision
  • Appchain integrationsPlanned
    Current design
    Appchain connection to proofs, AI services and settlement
    Finalization needed:
    Launch partners and security model
  • IBC routesPlanned
    Current design
    IBC channels to Cosmos-ecosystem chains
    Finalization needed:
    Channel selection
  • EVM adaptersPlanned
    Current design
    Adapters for Ethereum and EVM L2 ecosystems
    Finalization needed:
    Adapter security review
  • Solana adaptersResearch target
    Current design
    Adapters for Solana-connected applications
    Finalization needed:
    Feasibility research
  • Native benchmark configurationEngineering
    Current design
    Reproducible multi-validator throughput benchmarks
    Finalization needed:
    Published, reproducible results
  • Cross-chain security policiesEngineering
    Current design
    Per-route security models, timeouts, acknowledgements
    Finalization needed:
    Per-route policies
  • Oracle / pricing systemEngineering
    Current design
    Price and quote inputs for AI jobs and settlement
    Finalization needed:
    Oracle design and sources
  • BATT settlement reserveEngineering
    Current design
    BATT settlement reserve mechanics
    Finalization needed:
    Reserve mechanics specification