About the Swan 1.0 archive

Everything in this section describes Swan 1.0 — the network before the Inference Cloud. It is kept for existing operators and for the historical record, and is no longer maintained: external links may be dead, programs have ended, UBI has stopped, and the economics described here (UBI, ECP/FCP roles, task auctions) have been replaced. For anything current, start at Welcome.

What changed

Swan 1.0	Swan 2.0 (current)	Where to read about it
Two provider roles, ECP (ZK proofs) and FCP (Kubernetes tasks)	One Computing Provider that serves AI inference over a WebSocket connection — no public IP, domain or TLS needed	Become a Provider
Providers paid mainly from UBI — a daily SWAN allocation sampled across registered hardware	Providers paid per token at a published payout price for every request they serve	How the Marketplace Works
Consumers bought compute through task auctions (Orchestrator, Lagrange, Swan Console)	Consumers call an OpenAI-compatible API and pay per token from a prepaid credit balance	For Developers
Collateral sized by Computing Units (CU × 3,533 SWAN)	Collateral deposited per provider account, see the current rules	Earnings and Collateral

Still running a legacy CP?

The ECP/FCP pages below remain the reference for withdrawing collateral and exiting the legacy network. The recommended path for the hardware itself is to install the current computing-provider and join the inference network — the provider guide takes about fifteen minutes.

In this section

• UBI Allocation Curve — the Swan 1.0 reward model

• Swan 1.0 Computing Protocol — task workflow, CP Protocol and CPAccount contract, Layer3 job submission, AVS reputation, dynamic pricing, payment channels

• Swan 1.0 Collateral and Rewards — Computing Units, per-card collateral, DePIN Oracle, Treasure DAO

• Swan CP UBI — the UBI program as it applied to ECP/FCP operators

• Legacy Computing Provider (ECP/FCP) — setup, funding and exit procedures

• Market Provider, Storage Provider — the auction-era marketplaces

• App Deployment and Storage, Developer Tools — Lagrange/LDL deployments, Swan SDK, Swan Console, IPFS storage

• Mission 3.0 and Past Campaigns — completed community programs and testnets