T0 LOCAL Reward enforcement works in the local simnet. Public GPU testnet is in development. View delivery status →
Documentation · DRAFT v0.1
DRAFT v0.1

Abakos Whitepaper

The detailed Abakos protocol, economics, marketplace, and risk design.

All documentation

Abakos: A Proof-of-Useful-Work L1 with Enforced Usefulness

Whitepaper v0.1 — draft. Public-facing. Figures and parameters are illustrative starting assumptions, not final.

Compute that pays for itself.

Abstract

Abakos is a Layer-1 blockchain — a fork of Bitcoin's btcd — that replaces SHA-256 hashing with a Proof-of-Useful-Work (PoUW) function based on matrix multiplication (GEMM), the core operation of AI. Unlike prior PoUW attempts, Abakos makes usefulness an enforced economic property: a miner earns the full block reward only for work bound to a paid compute job settled through an on-chain marketplace with stablecoin escrow. Empty/random mining is permitted (for liveness/security) but earns only a floor fraction of the reward. A consumer application, Abakos Chat, channels mainstream demand directly into this loop. The result is GPU compute priced below centralized and decentralized alternatives, because the same watt-hour earns a mining subsidy and produces paid AI output (2-for-1).

1. Background & motivation

AI progress is bottlenecked by GPU compute, which is expensive and concentrated in a few hyperscalers. Simultaneously, Proof-of-Work blockchains expend large amounts of energy to produce only network security. PoUW has long promised to merge the two — to make the energy that secures a chain also produce something valuable.

The leading deployed attempt, Pearl (PRL), runs a matmul-based PoUW. But its protocol verifies only that a matrix multiplication was performed correctly — not that it served any real AI workload. Empirically (arXiv 2606.04819), Pearl's network represents on the order of 320,000 GPU-equivalents and ~112 MW, yet produces essentially zero useful AI: miners grind random matrices because that is cheaper than serving real inference. Statistical "is-this-a-real-model" checks are trivially defeated by adversarial sampling.

The core tension (verifiability vs. usefulness): tasks that are easy to verify tend not to be useful, and useful tasks are hard to verify cheaply.

2. Design principle: enforce usefulness economically

Abakos does not try to cryptographically detect "real" AI matrices (a losing game). Instead it makes useful work the dominant economic strategy:

reward_block = base_subsidy * (FLOOR + (1 - FLOOR) * useful_ratio)
FLOOR = 0.25
useful_ratio ∈ [0,1] = fraction of the block's matmul work bound to PAID escrow jobs
  • Random/empty mining → useful_ratio = 0 → 25% of the reward.
  • Fully paid, verified work → useful_ratio = 1 → 100%.
  • The unrewarded remainder (up to 75%) is burned.

A miner serving paid jobs therefore earns the stablecoin payment and the full block reward on the same compute; a miner grinding randomness forfeits 75% of the subsidy. Usefulness becomes the profit-maximizing choice.

3. Architecture

3.1 Consensus & PoUW

  • Base layer: Nakamoto consensus (longest chain), forked from btcd (ISC).
  • Work function: tiled, noised matrix multiplication (NoisyGEMM) on GPU, with a

    • Blake3 jackpot under the difficulty target and a Plonky2 zero-knowledge proof for cheap on-chain verification (building on the open cuPOW construction, eprint 2025/685).

  • Precision: INT8 first; FP8/BF16 next (standard-compatible, vLLM/SGLang

    • drop-in) — multi-vendor (NVIDIA + AMD) from day one.

3.2 Model registry

On-chain registry binding a model_id to a weights_hash, precision, and min_vram. PoUW proofs bind their input matrices to a registered weights hash, and jobs are routed to providers with sufficient VRAM.

3.3 Compute marketplace + escrow (the differentiator)

  • Buyer orders compute (batch inference, embeddings, fine-tuning, or a chat

    • session) and locks stablecoin (USDC/USDT) in escrow. Abakos does not issue its own stablecoin — it accepts existing ones.

  • Job lifecycle: CREATED → FUNDED → ASSIGNED → PROVEN → SETTLED / REFUNDED.
  • A miner runs the job, produces output + PoUW/ZK proof; nodes verify proof and

    • escrow; settlement pays the miner in stablecoin and grants the block reward share — atomically.

  • Disputes/timeouts refund the buyer; reputation and optional stake/slashing

    • protect against non-delivery and Sybil supply.

  • Fee: 2% per settlement (1% treasury / 1% burn).

3.4 PoUW ↔ job binding

The block header commits to the served job_ids, their input Merkle roots, and escrow references; the verifier checks the escrows are funded and that the PoW inputs match the committed job inputs. The hardest open problem is binding "this jackpot came from these paid inputs" cryptographically; if a perfect binding is too costly, security falls back to the economic binding (a funded escrow must exist for useful_ratio > 0), which already inverts the economics against empty mining.

3.5 Model sizes & provider tiers (open-weights only)

Closed frontier models (Claude Opus, GPT, Gemini) have secret weights and cannot be run by any decentralized network; Abakos serves strong open-weight models (Llama, Qwen, DeepSeek, Mistral, Gemma). Models that fit on one GPU are served independently (data-parallel) — ideal for a decentralized network. Models too large for one GPU (e.g. 400B+) are hosted by datacenter/neocloud providers with local multi-GPU boxes; model splitting happens inside one provider, never across the public internet.

4. Abakos Chat

A simple, crypto-invisible "ChatGPT for everyone": email login, pay by card or ABK (cheaper). Every message is served by the Abakos network → mainstream, paying demand flows straight into the marketplace, raising the network's useful_ratio. Early phase is hybrid (reliable partner GPUs for low latency), moving decentralized as latency stabilizes.

5. Economics & token (ABK)

  • Max supply: 2,100,000,000 ABK.
  • Allocation: 70% mining, 10% treasury, 8% team, 7% liquidity & listing,

    • 5% ecosystem (transparent on-chain vesting).

  • Emission: Bitcoin-style halving (every ~4 years), fit so cumulative

    • mining emission converges to the 70% allocation (~183.8M ABK in year 1).

  • Value accrual: 1% of the 2% fee is burned, plus the empty-mining penalty

    • burn → deflationary with real volume.

  • Two separate flows: subsidy (token, volatile) vs. revenue (stablecoin,

    • price-independent) — kept strictly separate, technically and legally.

  • Utility: compute/chat payments, mining rewards, optional staking for job

    • priority, later governance.

6. Security & trust

  • The base layer inherits Bitcoin/btcd's battle-tested consensus; the novel

    • parts (PoUW kernel, reward-split, escrow, ZK verification) are the risk surface and must be audited before mainnet.

  • Launch strategy is mainnet-first but gated: a short incentivized testnet

    • (also a marketing vehicle) → security audit → mainnet + token.

  • Transparency as policy: open-source node at testnet, an honest public

    • "% useful compute" metric, and clear disclaimers (not financial advice).

7. Go-to-market (summary)

Supply first (neoclouds with idle GPUs + solo miners via a 1-click installer), then point demand at it: latency-tolerant batch jobs for fastest revenue, then Abakos Chat for mainstream scale, plus academic grants for credibility. See docs/06-go-to-market.md.

8. Roadmap

  • P0–1: btcd fork, PoUW kernel, reward-split + model-hash commitment,

    • public incentivized testnet + explorer.

  • P2: marketplace MVP (batch), buyer SDK, Abakos Chat MVP.
  • Audit (mandatory).
  • P3: mainnet + token, DEX/CEX listing, FP8/BF16 + real-time chat,

    • neocloud partners.

  • P4: vLLM/SGLang plugin, managed API, AMD/non-AI GEMM, Chat mobile + ABK

    • pay.

9. Risks

Verifiability gap (mitigated economically, not statistically); supply/demand bootstrap (supply first + ecosystem incentives + Abakos Chat); token-price dependence of the subsidy (mitigated by stablecoin revenue); decentralized inference latency (hybrid first); competition (Pearl, Gonka, io.net, Akash — differentiated by enforced usefulness + consumer app + price). Legal/MiCA: the token is subject to legal review; stablecoin compute sales are kept separate from token speculation. See docs/10-risks-and-legal.md.

10. References

  • Pearl whitepaper — https://pearlresearch.ai/
  • cuPOW: Proofs of Useful Work from Arbitrary Matrix Multiplication — https://eprint.iacr.org/2025/685
  • The Usefulness Gap in PoUW (empirical study of Pearl) — https://arxiv.org/html/2606.04819v2
  • Gonka (Proof of Compute) — https://gonka.ai/

This document is for information only and is not financial advice or an offer of securities. The ABK token structure is subject to legal review.