growthepie is best understood as ecosystem-measurement infrastructure, not just an analytics website. The official docs explicitly define a public API, canonical identifiers, coverage rules, and freshness guidance.
The strongest mechanism is the master.json / metadata-driven approach: chain coverage, metric coverage, supported entities, units, and exclusions are meant to be checked programmatically rather than inferred from charts.
The docs make methodology legible in a way many analytics products do not. Trust signals include last_updated_utc, verified public endpoints, consistent canonical terms, and alignment between docs and backend source-of-truth artifacts.
Coverage policy matters. The docs say coverage is both metric-specific and chain-specific, and they tell users to ignore chains marked DEV or ARCHIVED for production analysis.
The project is not just a frontend. The GitHub org and repo READMEs show separate public surfaces for metadata/config (gtp-dna), backend ingestion and curation (gtp-backend), frontend, and wiki/docs.
gtp-dna is especially important because it contains chain definitions, DA mappings, economics mappings, and label-confidence data. That means the project’s judgment about names, mappings, and entity verification materially shapes the public analytics layer.
gtp-backend shows a mixed-source ingestion model using RPC nodes and third-party data sources such as Dune, CoinGecko, L2Beat, DeFiLlama, BigQuery, and bespoke indexers before normalization into PostgreSQL and API payloads.
Specific source signals worth retaining
docs.growthepie.com/readme.md: best concise statement of coverage scope, canonical terms, source-of-truth posture, API limits, and data-tier split.
data-quality-and-trust-signals.md: best source for how growthepie thinks about reliability, freshness, and machine-readable trust signals.
coverage-and-exclusions.md: best source for the important idea that coverage is chain-specific and metric-specific, and that consumers should prefer live metadata over hardcoded assumptions.
gtp-dna README: best evidence that metadata, economics mappings, DA mappings, and trusted-entity lists are first-class maintained artifacts.
gtp-backend README: best evidence that growthepie is a real ingestion-and-normalization stack, not just a visualization layer.
Why this entry belongs in the corpus
It adds a useful public-goods analytics and legibility layer between raw data services and higher-level ecosystem narratives.
It is a strong comparison point for projects like L2BEAT and Open Source Observer because its real power lies in coverage policy, metadata curation, naming, exclusions, freshness signals, and source reconciliation.
The durable insight is that analytics influence often comes less from chart design than from defining what counts as a covered chain, app, metric, or trustworthy update.