Flayer Labs · Flaunch · NFTX · FLAY

Flayer Volume Audit

Where the volume and fee numbers for Flaunch on Base and Robinhood Chain, NFTX V2 and V4, and the FLAY token actually come from, how fresh each source is, and what the live data says.

Data fetched Collected every 6 hours by a Cloudflare Worker · model.json · ledger.csv · sources.json
Freshness verdict

The site is refreshing; its data source is not

Flaunch · live from the backend API

Flaunch today, both chains

These figures come from the same endpoint that powers flaunch.gg (/v1/stats/protocol), so they are current to the minute. Total fees are gross pool fees in USD at the time they accrued (creator share + buybacks + everything else).

Flaunch · history from Flayer's own indexer · both chains

Volume and fees, day by day

Rebuilt by this Worker from the team's Envio indexer instead of Dune: daily volume is the sum of every coin's one-day candle, fees are every PoolFeesDistributed event, each per chain. Backfilled from each chain's first day and refreshed on every run.

Range

All time, straight from the indexer

Fees here are what the contracts distributed (no double count). Volume is the ETH side of every swap, priced in USD at the time.

Independent check · public RPC scans

Fees are still flowing on both chains

Every PoolFeesDistributed event from the Flaunch PositionManagers, read straight from public RPC nodes. The five slots are the event's five amounts; on Base the protocol slot is zero by design and Robinhood takes a protocol cut.

NFTX · V4 live, V2 legacy

NFTX volume

NFTX V4 (rebuilt on Uniswap V4) runs on Ethereum and Robinhood Chain, with Arbitrum and Ink deployed but empty. "Pool volume" is the ETH side of swaps on the collection pools, the figure the nftx.io homepage sums; "trade volume" also counts NFT deposits and redeems at floor value.

Per chain

NFTX V2 and V3 (legacy)

FLAY · token

Does anything accrue to FLAY?

The case for FLAY rests on fee flows reaching the token. This checks each documented route against what is on-chain today.

Value-accrual checklist

Ledger · recorded by this Worker

Both chains, day by day

The backend only reports current totals, so this Worker records them into D1 every six hours (the last reading of each UTC day is kept). These series start on the first day of collection and grow from there.

Catalogue

Every data source, with its freshness

Recommendations

How to make the numbers trustworthy