Skip to content

AIPoW

Security, roles and energy

The security boundaries and real-world operating context around AIPoW participation.

Verify every claim

The same work or AI receipt must not be reusable across invalid contexts.

Engineering
Conceptual work bindingHash( … )
Fields bound into the conceptual commitment and why each one matters
FieldPurpose
Hash( chain_idPrevents cross-chain reuse
|| epochPrevents temporal replay
|| miner_addressBinds the payout
|| auxpow_work_idBinds the mining proof
|| model_hashBinds the AI evidence
|| input_hashBinds the AI evidence
|| output_hashBinds the AI evidence
|| job_nonce )Prevents duplicate reuse

■ work binding■ AI evidence binding

Additional controls

  • Duplicate claim tracking
  • Bitcoin chainwork checks
  • Canonical header policy
  • Stale claim handling
  • Receipt signature verification
  • Provider policy
  • Merkle inclusion proof
  • Optional TEE / zk verification

Exact consensus rules are implementation-defined.

Work granularity

BitcoinAI can distinguish frequent mining work from high-assurance Bitcoin blocks.

Mining shares

Testnet TBD

Frequent · lower individual assurance

Potential use

  • More frequent reward accounting
  • Pool participation evidence
  • Work measurement

Canonical Bitcoin blocks

Engineering

Rare · highest assurance

Potential use

  • High-assurance anchoring
  • Strong Bitcoin-chain reference
  • Checkpointing

Final policy for accepted share difficulty, pool attestations, or canonical Bitcoin block requirements remains an implementation parameter.

One operator, multiple options

Mine, validate, provide AI — or combine them.

  • Miner only

    Receives

    • Work-provider AIPoW reward (BTCAI)

    Does not receive

    • PoS security pool
    • Validator AIPoW share
    • Validator BATT share

    …unless they also stake or delegate.

  • Miner + Delegator

    Receives

    • Work-provider reward (BTCAI)
    • Delegator-side validator economics
  • Miner + Validator

    Receives

    • Work-provider reward (BTCAI)
    • Validator economics
  • Miner + AI Provider

    Potentially receives

    • Work-provider reward (BTCAI)
    • BATT provider revenue
    • 1.05 qualification pathway, if valid
  • Miner + Validator + AI Provider

    Potentially receives

    • All applicable revenue streams — each in its own asset

BTCAI and BATT are always separate assets. They are never added together.

Validator role comparison

Earn BTCAI. Optionally bond BTCAI.

Mining can become a path into long-term network security.

AIPoW work earns BTCAI. The miner either keeps it liquid or delegates it; delegated BTCAI becomes bonded stake that participates in validator and delegator economics.
AIPoW work
Earn BTCAI
Keep liquidDelegate
Stays in your wallet
Bonded stake
Validator / delegator economics

Staking remains optional for miners.

Auto-delegate part of mined BTCAI

Planned
  • 0%
  • 25%
  • 50%
  • 75%
  • 100%

Planned wallet / mining-dashboard concept. Not a live feature.

Shared work

Reuse existing work instead of creating a separate hash race.

  • Merge mining can reduce incremental computation relative to an independent proof-of-work network.
  • AIPoW seeks to increase revenue potential from work miners already perform.
  • No new independent BitcoinAI ASIC race is required under the intended merge-mining design.

Additional rewards may still influence total mining economics and energy incentives. BitcoinAI therefore describes AIPoW as energy-conscious shared work, not zero-energy Proof of Work.

BitcoinAI does not claim

  • Not claimed: Zero energy
  • Not claimed: Carbon neutrality
  • Not claimed: No environmental impact
  • Not claimed: No effect on mining economics
Mining and AI infrastructure ultimately connect protocol design to real energy systems and engineering operations.Photo by Sikwe Scarter · Unsplash