Transparent by design.

Reserve funding

Daily USD value of LINK transfers from the Payment Abstraction contract to the Chainlink Reserve, as indexed by DefiLlama. The source calls this series “dailyHoldersRevenue”; we use the narrower label “reserve funding.” It does not represent dividends paid to holders.

The cumulative chart sums funding within the selected period. It is not the reserve's token balance: it does not subtract withdrawals or include transfers from other senders. Historic USD values come from the provider; we do not divide them by today's LINK price to invent token quantities.

Reserve contract: 0x9A709B7B69EA42D5eeb1ceBC48674C69E1569eC6.

Request fees and aggregator receipts

Oracle request fees are the USD-valued LINK payments indexed from OracleRequest events on Ethereum, BNB Chain, Polygon, OP Mainnet, Arbitrum, and Avalanche. The adapter's descriptive text mentions several services, but its code specifically scans this event. We therefore do not present the series as complete CCIP, Data Feeds, or total platform revenue.

Fee aggregator receipts are tokens received by the fee aggregator contract, valued in USD. Receipts may reflect payment batching and may not occur on the same day as service usage.

These series are displayed separately. We do not add parent totals to their components or add reserve funding to the upstream fees that may have funded it. Neither series measures all private enterprise revenue or token-holder profit.

Circulating supply

We read Chainlink's official circulating-supply endpoint. Raw token amounts are stored as decimal strings in the source archive; display values are converted from 18-decimal base units. The maximum supply is one billion LINK.

The endpoint does not publish an observation timestamp or historical supply series. We label its retrieval time and collect daily snapshots from launch. These snapshots are observations at collection time, not finalized end-of-day balances. We do not backfill an estimated release curve or equate supply changes with exchange selling.

Staking and reserve holdings may be included in published circulating supply. We do not subtract them to create an unsupported “liquid supply” estimate.

Funding pace and related receipts

Reserve funding arrives in batches: the initial 90-day sample contained 13 positive payment days with a median seven-day interval. This is an observation of that sample, not a guaranteed schedule. Five-biggest-day concentration was removed because it mostly reflected batching rather than underlying adoption.

Weekly charts aggregate complete Monday–Sunday UTC weeks entirely inside the selected period. Incomplete boundary weeks are excluded. Any missing daily observation makes that week's amount unavailable. The trailing four-week average requires four consecutive complete weekly values; it is not a forecast.

Fee aggregator receipts and reserve funding are separate observations along a related payment path. The first sums tokens received by the aggregator; the second measures LINK sent from Payment Abstraction to the reserve. Do not sum them or infer a conversion rate from their ratio. Conversion valuation, routing, timing, and other transfers can affect differences; aggregate series do not establish transaction-level reconciliation.

Dates, gaps, and refreshes

Charts use UTC days and exclude the current partial day. Percentage changes compare equal-length complete periods. A missing day makes a period total unavailable; zero is used only when the source explicitly reports zero. “All” starts at the later first observation shared by the request-fee and reserve-funding series. Provider zeros are not independently verified evidence of no activity.

Opening the dashboard checks sources when the previous check is more than six hours old. “Check sources” requests an update, with a shared ten-minute cooldown. Each source is refreshed independently and keeps its last good data after failures. There is no always-on scheduler configured in this release. Raw runtime responses are archived and source snapshots persist in the database.

The API observation date and retrieval date are distinct. Flow charts label the source's latest coverage date; source responses can contain today's incomplete observation, which is excluded from charts. Data older than 48 hours since collection is marked stale; price is marked stale after one hour from its source timestamp. A source failure also marks the retained data stale.

Reserve token balance and historical transfers could not be independently retrieved during setup. Staking principal, CCIP aggregates, and historical supply releases are not yet included. Their absence is a coverage gap, not a zero balance or zero usage.

DefiLlama's endpoints were publicly accessible during setup. Provider terms, rate limits, and API availability can change. Public community distribution should include a review of provider redistribution terms and access requirements.

Why these metrics?

Reserve funding measures one observable route from payments to LINK accumulation. Fees measure a limited slice of paid usage. Supply provides the counterweight: how many tokens are circulating. Together they explain more than price or integration announcements alone, while leaving room for what public data cannot establish.

LINK price is secondary context from DefiLlama's coin-price endpoint. No valuation multiple or price forecast is inferred from these datasets.