Pay
Buyers fund base bundles and add-ons (GPU, persistent storage, IP lease) from an ABA wallet.
Protocol · Public sandbox live
SANDBOX LIVE
PoS rails. Full utilization. ABA settlement.
Abakos forks the open Akash marketplace stack onto its own PoS chain so ABA can capture value. The Provider Agent keeps hardware busy: rent CPU, RAM, GPU and storage via the Console, or idle-mine GPU and CPU into ABA. Buyers pay with ABA wallets at the start. Earlier PoUW research is archived.
Simple version, before the technical detail
"Consensus" means every validator agrees on what happened and in what order. Abakos uses Proof of Stake for that. Separately, the Provider Agent maximizes income: rent resources through the Console when buyers exist; mine the most profitable coin on idle GPU and CPU and auto-convert it into ABA when they do not. Storage and RAM earn on rental only. Chain security inflation pays validators, not compute hosts. MVP payments are wallet ABA only.
Architecture path
From utilization to settlement.
01
Hold ABA
Buyers fund rentals and jobs from an ABA wallet. Fiat to ABA onramp is post-launch, not MVP.
02
Console demand
ABA is locked in escrow against a base bundle (CPU+RAM+disk[+GPU]) and any add-ons (persistent storage, IP lease).
03
Agent fills the hour
Serve the rental or job; if GPU/CPU would sit idle, mine the most profitable coin and auto-convert to ABA instead.
04
Settlement
ABA pays the host for compute and add-ons; protocol fee and burn rules apply on settlement.
Own chain, not a tenant app
Why fork instead of deploying on live Akash.
Running as an app on someone else's chain would not give ABA native fee capture, genesis allocation, or validator economics. Abakos forks the open Akash stack (Cosmos SDK + CometBFT, Apache-2.0) onto its own network so ABA is the settlement and staking asset.
IN DESIGN
Current honesty
The public sandbox (chain, EVM, wallet, explorer, ABA/USDC DEX, Provider Agent buyback + dashboard, zero-fee) is live. Not yet live: external validators (decentralization), on-chain escrow modules, and the Console. Litepaper and whitepaper on this site match the PoS / Agent thesis; older numbered research notes in the repo are historical.
How the products fit together
One backend. Products in, Agent out, one window.
There is one underlying system: the PoS chain plus job, escrow and ABA wallet rails. The Console, Developer API, Abakos Chat and Enterprise offtake create demand that fills hardware. The Provider Agent Dashboard keeps supply utilized (rent or mine). Explorer is the public window.
| Surface | Money flow | Needs the real-time path | Phase |
|---|---|---|---|
| Console (templates + bundles + add-ons) | In, ABA wallet | Only for live sessions | Phase 2 |
| Console, batch jobs | In, ABA wallet | No | Phase 2 |
| Enterprise offtake | In, ABA wallet | No | Phase 2, same rails |
| Developer API, batch | In, ABA wallet | No | Phase 3 |
| Developer API, streaming | In, ABA wallet | Yes | Phase 4, with Chat |
| Abakos Chat | In, ABA (+ product markup) | Yes | Phase 4 |
| Provider Agent Dashboard | Out, ABA to hosts (job or buyback) | N/A | Phase 1 |
| Explorer | None, public proof only | N/A | Public at Phase 1 |
| Fiat to ABA onramp | Card → market-buy ABA → escrow | N/A | Post-launch, not MVP |
This is the one table to check for "what can I expect, and from when." Every other page's status badges roll up to this.
Token utility
What ABA is for.
Receive
Hosts earn ABA from rentals, add-ons, or idle GPU/CPU mining converted into ABA.
Stake
Validators stake ABA to secure the PoS chain.
Fiat onramp
Card purchase market-buys ABA for escrow. Not in the MVP.
Why batch API and Enterprise come before Chat, not after
Developer API batch endpoints and Enterprise offtake reuse the same batch/escrow infrastructure the Console already needs for Phase 2. Chat and streaming need a low-latency real-time job path, which is why they land together at Phase 4.