What Arc's highest-volume addresses actually are — derived from public chain data alone: bytecode, contract calls and block authorship. No label set is copied from another provider, and no attempt is made to attach a natural person to an address. ← Terminal
Classifications are derived automatically and are not verified. A type tells you what an address
behaves like on-chain — it is not a claim about who operates it. Expect gaps: an address doing nothing
recognisable is simply shown as contract.
The method and thresholds may change while this is being tested. Don't build anything on these results yet — the stable API is the one to rely on.
Volume on Arc is concentrated enough that deriving the head of the distribution covers almost all flow. Curated means we assert the name; derived means the chain does — the “why” column is the evidence.
| # | Address | Type | Why | Interfaces | Funded by | Transfers | Volume |
|---|---|---|---|---|---|---|---|
| Deriving… | |||||||
Addresses sharing a bytecode fingerprint are the same contract deployed more than once. Identifying one identifies the whole family — this is what makes labelling scale.