AIPoW
Mining infrastructure
The practical pool, claim and infrastructure layer behind the AIPoW design.
Merge-mining economics
BitcoinAI is designed as an incremental reward, not a replacement for Bitcoin mining economics.
Shape only: the auxiliary layer sits on top of existing work. No amounts or ratios are implied.
- 01Bitcoin remains the primary mining economy.
- 02BitcoinAI seeks to add an auxiliary reward on top of existing work.
- 03Merged mining can be compelling even when the auxiliary reward is much smaller than Bitcoin's primary subsidy.
- 04Operational integration cost matters more than matching Bitcoin dollar-for-dollar.
Merge mining has long-standing precedent: auxiliary proof-of-work networks such as Namecoin and Rootstock accept Bitcoin work through AuxPoW-style commitments.
No live price or profitability comparison is shown. Any future market comparison will be dated, sourced and labeled as a historical illustration.
For pool operators
Integrate BitcoinAI without rebuilding your entire mining stack.
- 1ASIC miners(Existing mining stack)
- 2Mining pool / Stratum layer(Existing mining stack)
- 3Bitcoin work construction(Existing mining stack)
- 4BitcoinAI commitment / AuxPoW path(New BitcoinAI integration)
- 5AIPoW relay / submission(New BitcoinAI integration)
- 6BitcoinAI verification(BitcoinAI network)
- 7Pool reward accounting(New BitcoinAI integration)
- 8Miner payouts(Existing mining stack)
Integration components
- BitcoinAI commitment generation
- AuxPoW proof extraction
- Miner identity / payout mapping
- Share accounting
- AIPoW claim relay
- Epoch tracking
- Reward reconciliation
- Optional Proof-of-AI receipt binding
- Operator monitoring
No current pool-software compatibility is claimed.
Miner workflow
Design around existing mining operations where practical.
BitcoinAI should aim to minimize disruption to established pool workflows.
Potential integration layers
- L1Pool-side commitment plugin
- L2Job template extension
- L3AIPoW relay service
- L4Payout mapping service
- L5BitcoinAI node interface
- L6Optional AI receipt service
| Interface | Status |
|---|---|
| Stratum V1 | Testnet TBD |
| Stratum V2 | Testnet TBD |
| Solo-mining RPC | Testnet TBD |
| Pool API | Planned |
| AIPoW relay API | Planned |
| Payout API | Planned |
Final Stratum compatibility and pool adapters will be defined during implementation and testnet integration.
Developer view
AIPoW claims should be explicit, replay-resistant, and auditable.
{
"chainId": "bitcoinai-testnet",
"epoch": 12345,
"minerAddress": "btcai1...",
"auxpowWorkId": "0x...",
"bitcoinHeaderHash": "0x...",
"workCommitment": "0x...",
"workWeight": "1.00",
"proofOfAI": null,
"nonce": "..."
}{
"workWeight": "1.05",
"proofOfAI": {
"jobId": "ai-job-...",
"providerId": "provider-...",
"modelId": "model-...",
"inputHash": "0x...",
"outputHash": "0x...",
"receiptHash": "0x...",
"signature": "..."
}
}Conceptual schema only. Final binary encoding, consensus serialization, proof fields, and validation rules are implementation-defined.
Open participation
AIPoW should remain permissionless.
- Miner
- Bitcoin-compatible work
- AIPoW submission endpoint
- BitcoinAI verification
- Reward accounting
A valid participant should not need
- Special permission
- Validator status
- BTCAI stake
- AI infrastructure for base 1.00 work
Final solo-miner API / RPC design — planned
No submission form or endpoint is live. None is simulated here.
What miners need
Reuse mining infrastructure. Add BitcoinAI integration.

Existing mining infrastructure
Potentially reusable- SHA-256 ASICs
- Pool infrastructure
- Stratum
- Bitcoin node / block templates
- Payout systems
- Monitoring
BitcoinAI-specific integration
May require- AIPoW commitment logic
- AuxPoW proof builder
- BitcoinAI node or relay
- Miner payout address mapping
- AIPoW epoch awareness
- AI receipt integration for the 1.05 path
AIPoW integration cost depends on pool architecture and final implementation. No hardware minimums are published.