Audit a liquidity comparison before relying on its conclusion

Before accepting a liquidity ranking, check whether every number measures the same economic object. A comparison can use accurate figures and still reach an invalid conclusion because their scopes or definitions differ.

Audit a hypothetical claim

Suppose a report says Venue A is deeper because it shows $20 million, while Venue B shows $2 million. On inspection, A's figure is daily volume across several networks, and B's is current TVL in one pool. Neither figure measures matched executable depth, so the ranking is unsupported.

A corrected comparison might quote the same token contracts on the same network for the same $10,000-equivalent input, with fees and timing aligned. The resulting output can then support a size-specific execution comparison.

Check the hidden mismatches

• Volume versus TVL versus depth within a price band.
• Protocol totals versus one accessible pool.
• Current data versus a historical snapshot.
• Average execution limits versus ending marginal-price limits.
• Native token counts versus consistently valued amounts.
• Unique pools versus duplicated aggregator coverage.

Local and execution prices are distinct, so even two measures labeled “1% depth” can require further definition before comparison.

Inspect the conclusion's reach

A better quote at one size does not establish superiority at every size or in the reverse direction. A concentrated pool's local advantage can change when a trade leaves a dense range.

Require the report to state the actual request, observed output, separate costs and comparison boundary. If only aggregate statistics are available, the proper conclusion is that execution capacity has not yet been compared.

This audit does not need a universal scoring formula. Its purpose is to ensure that the chosen evidence answers the stated question. Once units, scope and state match, the remaining differences become economically interpretable rather than artifacts of incompatible dashboards.