Data policy
Methodology and Data Sources
This page defines the minimum quality rules 0pools should apply before publishing live pool, route, liquidity, fee, volume or comparison data as indexable public content.
Current data status
The current public 0pools website does not publish live pool metrics, individual pool-detail pages, protocol rankings, risk scores, APY tables or route-comparison datasets. Existing infrastructure pages are product and concept pages.
Minimum requirements for future pool pages
- Protocol, chain, token pair and pool or contract identifier.
- Liquidity, trading volume, fee tier and route assumptions where available.
- Source URL or source system for each displayed metric.
- Timestamp showing when data was last fetched or calculated.
- Clear explanation of delays, caching, missing data and calculation limits.
- Risk notes that avoid calling a pool safe, best or guaranteed.
Indexability policy
A programmatic pool page should be indexable only when it has meaningful, current and unique information. Empty pages, duplicate token-pair routes, unsupported chains, filter URLs, sorting URLs, tracking-parameter URLs and pages with missing primary data should be excluded from the sitemap or marked noindex.
Methodology limits
Any 0pools score, comparison, route estimate or projected settlement window should explain the inputs used, what the number does not measure and when it was last updated. A score is not a guarantee of outcome, availability, safety, liquidity or regulatory status.