Proof of AI Work

Proof of AI Work is the consensus mechanism powering CLAWING. It replaces arbitrary hash computation with verifiable AI content generation, creating a mining system where the "work" is productive intelligence rather than wasted electricity.

---

Consensus Comparison

Property	Proof of Work (PoW)	Proof of Stake (PoS)	Proof of AI Work (PoAIW)
Work type	SHA-256 hashing	Capital lockup	AI content generation
Resource consumed	Electricity	Liquidity	AI compute credits
Verification	Hash < target	Signature + stake	Oracle attestation
Output	Hash (no utility)	Block validation	AI content (productive)
Barrier to entry	ASICs, electricity	Capital	API key + gas
Centralization risk	Mining pools	Whale dominance	Oracle centralization (Phase 1)
Environmental impact	High	Low	Low

How PoAIW Works

The Mining Cycle

┌─────────────────────────────────────────────────────────┐
│                    PoAIW Mining Cycle                    │
│                                                         │
│  ┌────────┐  1. Generate   ┌──────────┐                │
│  │ Miner  │──────────────> │  AI API  │                │
│  │ Client │                │(grok-4.1)│                │
│  └───┬────┘                └────┬─────┘                │
│      │                          │                       │
│      │  3. Submit attestation   │ 2. Content            │
│      │     on-chain             │    returned            │
│      │                          v                       │
│      │                    ┌──────────┐                  │
│      │                    │  Oracle  │                  │
│      │                    │  Server  │                  │
│      │                    └────┬─────┘                  │
│      │                         │                        │
│      │   4. Verify signature   │ Signed attestation     │
│      v                         v                        │
│  ┌──────────────────────────────────┐                   │
│  │       Ethereum Smart Contracts   │                   │
│  │                                  │                   │
│  │  OracleVerifier ──> PoAIWMint    │                   │
│  │                     │            │                   │
│  │                     v            │                   │
│  │              CLAW Token Minted   │                   │
│  └──────────────────────────────────┘                   │
└─────────────────────────────────────────────────────────┘

Step 1: Content Generation

The miner's client sends a prompt to the designated AI model (currently grok-4.1-fast). The model generates a response — this content constitutes the "proof of work."

The key insight: generating AI content requires real computational resources (GPU time, model inference), making it a non-trivial proof of effort. The content itself can be useful, making the work productive rather than wasteful.

Step 2: Oracle Verification

The miner submits the AI-generated content to the Oracle server. The Oracle performs multiple verification checks:

1. Model verification: Confirms the content was generated by the correct model

2. Freshness check: Validates the nonce to prevent replay attacks

3. Cooldown enforcement: Verifies the miner has waited the required 3,500 blocks

4. Epoch limit check: Confirms the miner hasn't exceeded 14 claims in the current epoch

Upon successful verification, the Oracle produces a cryptographic signature (attestation) using its signing key.

Step 3: On-Chain Submission

The miner submits the Oracle's signed attestation to the PoAIWMint smart contract on Ethereum. The contract calls OracleVerifier to confirm the attestation is valid and signed by the authorized Oracle.

Step 4: Token Minting

If verification passes, PoAIWMint mints $CLAW tokens according to the reward formula and sends them to the miner's address. The claim is recorded on-chain, updating cooldown and epoch counters.

The Reward Formula

R = perBlock × (1 + ln(T))

Variable	Meaning
R	Total CLAW reward for this claim
perBlock	Base reward for the current Era (Era 1 = 100,000 CLAW)
T	AI tokens consumed during the mining call (range: 100–100,000)
ln(T)	Natural logarithm of T

Why Logarithmic?

The logarithmic bonus serves a specific economic purpose:

• Anti-whale mechanism: Increasing T from 2,100 to 100,000 (47x more API cost) only increases reward by ~45%

• Fair access: Miners using minimal AI API budgets earn competitive rewards

• Optimal strategy: Use T=2,100 (minimum practical) for maximum ROI

• Cooldown: Separately enforced at 3,500 blocks (~11.67 hours) between claims

Reward Examples (Era 1)

AI Tokens (T)	ln(T)	Reward (CLAW)	Notes
2,100	7.65	~862,300	Best ROI
5,000	8.52	~931,600	Moderate
10,000	9.21	~1,000,900	Diminishing returns
100,000	11.51	~1,251,300	Maximum T, worst ROI

Increasing AI tokens from 2,100 to 100,000 (47x more API cost) only increases reward by ~45%. The optimal strategy is to use T=2,100 for maximum return on investment.

Rate Limiting

PoAIW enforces two layers of rate limiting to prevent any single address from dominating:

Cooldown (3,500 blocks)

After each successful claim, the miner's address enters a cooldown period of 3,500 blocks (~11.67 hours). No claims can be made during cooldown.

Epoch Cap (14 claims)

Each address can make a maximum of 14 claims per epoch (50,000 blocks, ~6.94 days). This creates an absolute ceiling on per-address mining rate.

Maximum theoretical claims per address per era:

21 epochs/era × 14 claims/epoch = 294 claims per era

AI Model Selection

The AI model used for mining is not fixed — it is governed by $CLAW token holders through on-chain governance. Each Era can designate a different model, allowing the protocol to evolve with AI advancement.

The current Era 1 model is grok-4.1-fast.

Security Properties

Sybil Resistance

Each claim requires:

• Gas fees on Ethereum (~$1-5 per transaction)

• AI API costs (~$0.001-0.01 per generation)

• Time (3,500-block cooldown per address)

These costs make Sybil attacks economically constrained.

Replay Protection

Each Oracle attestation includes:

• A unique nonce

• The miner's address

• A block number reference

• A timestamp

Attestations are single-use and cannot be replayed.

Verification

All verification is cryptographic:

• Oracle signs with a known key (0xB98253EE78AEED4a0E5554fB1390Dbf0b28cEFfF)

• Smart contract verifies the signature on-chain

• No trust is required beyond the Oracle's signing key (which will be decentralized in Phase 2)

Phase 2: Decentralized Verification

The current architecture relies on a centralized Oracle. Phase 2 introduces zkTLS verification to decentralize the attestation process:

• TLSNotary: Cryptographic proof that AI API responses are authentic

• MPC-TLS: Multi-party computation for distributed verification

• Notary Network: Multiple independent verifiers replace the single Oracle

See Roadmap for the full decentralization timeline.

Next Steps

• Tokenomics — Full economic model: supply, halving, and emission schedule

• Governance — How token holders govern the AI model selection

• Architecture — Technical contract architecture

• Security — Complete security model