Fees paid by users (30d)
Total protocol-level charges paid for the service. Base-chain gas is excluded unless the protocol captures it.
Make the uncertainty
part of the data.
Atlas normalizes the questions, not the protocols. Native terms and caveats stay visible wherever standardization would mislead.
A normalized economic statement
Fees paid by users=Supply-side income+Gross protocol income+Direct external costs+Unclassified flow
Gross protocol income (30d)
The portion controlled by the protocol, treasury, contributors, or a protocol-directed value mechanism before observable direct costs.
Net protocol revenue (30d)
Gross protocol income after observable direct costs required to deliver the service.
Token-holder value (30d)
Operational value sent to holders through direct distributions, buybacks, or burns. The mechanism must be shown because these are not equivalent.
Liquidity-provider income (30d)
Fee or reward income allocated to liquidity providers, before inventory losses and capital costs.
Validator / node income (30d)
Fee and reward income allocated to validators or node operators. Fee-funded and issuance-funded amounts are separated where possible.
Incentives and emissions (30d)
New issuance or treasury spend used to fund security, liquidity, or usage. A missing value never becomes zero.
Treasury income (30d)
Operational flow sent to a governance, community, or protocol treasury.
Accounting-style profit (30d)
Net protocol revenue after operating expenses and incentives. Usually unavailable because off-chain expenses are not public.
DEX volume (30d)
USD value of swaps in the reporting window, included only as demand context.
Liquidity / TVL
Current value committed to the protocol. It is context, not revenue.
What the badge promises
Published by a direct or inspectable data source for this period.
Calculated from sourced values with the formula retained.
Depends on an explicit assumption that can change the answer.
A documented rule or classification reviewed by a human.
The source does not expose enough evidence. It is not zero.
Two credible sources or fields cannot be reconciled yet.
Rules and amounts need different proof
- 01
Direct on-chain state or events with a documented calculation
- 02
Official protocol API derived from chain data
- 03
Official documentation or ratified governance for rules
- 04
Open-source adapter with inspectable methodology
- 05
Reputable secondary analytics source
- 06
Manual estimate with a visible formula
A primary-source rule does not prove a live amount. An observed transfer does not, by itself, prove its accounting classification. Atlas keeps both pieces.
Every $100 must land somewhere
- Every percentage names its basis: user fees, network fee, system income, or issuance.
- Flow shares must total 100% or expose a residual.
- Fee-funded and issuance-funded participant income stay separate.
- Buyback, burn, direct distribution, and treasury accrual are different mechanisms.
- Accounting profit stays unavailable when operating costs are missing.
What this MVP cannot prove
The snapshots do not predict token price, future volume, or the behavioral response to a governance change. Off-chain expenses are often unavailable. Open adapters can have incomplete coverage. Static $100 maps explain the rule, not every period's realized outcome.
Correction policy: preserve the prior claim in version history, update the source ledger, explain the classification change, and never silently rewrite an uncertain number.