We checked the sources for this chapter on 17 Sept 2026. Use the linked sources for current availability, terms and network details. See subsequent updates
| Metric | Available evidence | Interpretation |
|---|---|---|
| Mainnet age | Public launch September 16, 2026 | One day old at the research snapshot |
| Launch applications | Circle says more than 100 | Issuer-reported; not independently reconciled contract-by-contract |
| Named launch ecosystem builders | Circle says more than 100 | Includes different relationship types |
| Testnet transactions | More than 700 million reported | Test activity, not mainnet economic settlement volume |
| Projects built | More than 1,200 reported | Includes experiments; not necessarily maintained companies |
| Arc House and Architects | More than 75,000 active members and 10,000 ambassadors reported | Publisher-defined community metrics, not unique paying users |
| This research inventory | 228 records | Organizations, products and prototypes, not live-app count |
| Mainnet TVL, recurring users and fee revenue | Not reliably established in the reviewed extraction | No invented values or extrapolation from testnet |
| Active voting validators | Not independently counted | Announced cohort is not a live power-distribution snapshot |
Published launch/community figures: S002 S068. Explorer and service-monitoring entry points: S024 S025 S023.
The mainnet explorer is dynamically rendered; this research did not obtain a trustworthy reproducible full metrics extraction. A blank or zero value in a text-only extraction is not evidence of zero onchain activity. The status page displayed operational services in the inspected snapshot, but that does not establish a long mainnet uptime record. S024 S023
A better measurement framework
For genuine adoption, track active fee-paying entities after filtering obvious incentive loops; repeat usage; external inflows versus internally recycled stablecoins; lending utilization and borrower concentration; DEX depth at realistic trade sizes; realized fees; protocol losses; and customer dependence on subsidies. For institutions, distinguish announced involvement, technical integration, pilot transactions and recurring commercial volumes.
For developer health, track maintained repositories and deployed contracts rather than counting forks or stars. For token economics, track implemented revenue routing and actual reward distributions rather than assuming whitepaper diagrams are executable policy. For grants, measure maintained products after the award, not application counts.
Sources & references
Documents cited in this chapter.