Flipside Label Coverage Estimator

We are estimating coverage for some label types where it makes sense to do so: these addresses reflect patterns consistent with the type of address we are labeling (e.g. a contract that is engaging in an event akin to a swap, but for which we do not know the protocol or operator responsible for its deployment). However, coverage estimates for many label types are not feasible because they reflect only truths that are reported via project documentation, or have small N. Examples of these include L2 addresses, dapps (that don't fit into a standard defi bucket), centralized exchanges, operators, and known garbage or spam addresses that we label as flotsam.Use the parameter below to toggle between chains. Parameter only applies to EVM chains.

We obtain DeFi labels for protocols from a variety of sources including public repositories like etherscan, thegraph, and protocol documentation, as well as from known factory contracts for major dexes like Uniswap and Sushi.
In this coverage methodology we compare our labeled contracts to any contract that may be part of a DeFi protocol based on the events it emits (swap, borrow, deposit, etc).

Please note: we also provide fully curated dex details in our ez_dex_swaps views, which we include based on the highest volume protocols on DeFi Llama (e.g. https://defillama.com/dexs/chains/avalanche -- you should see coverage in our swaps table for any major dex in that list)
However, not every chain has an ez_dex_swaps table. It is on our upcoming roadmap.

flipside

flipside

Flipside Label Coverage Estimator