Mirrored from filpgf.io — ProPGF Batch 3 (Karma program 1479, application 6a318a1413ef2aeed7ce0d92, status: under_review). Contact details redacted; canonical application lives on filpgf.io. 1.1 Project Name Filecoin Data Portal 1.2 Project Github https://github.com/davidgasquez/filecoin-data-portal 1.3 Project Website https://filecoindataportal.xyz 1.4 Team Lead/Point of Contact David Gasquez - @davidgasquez 1.5 Category [ "Core Infrastructure" ] 1.6 Open Source Status Fully Open Source 2.1 Project Summary The [Filecoin Data Portal ](https://filecoindataportal.xyz/)will keep Filecoin's public data layer reliable, open, reproducible, through December 2026. It will maintain the core datasets, models, dashboards, metric docs, public files, and agent-ready resources used by PLFIF, FF, OSO, FilOz, FIDL, Filecoin Plus, Karma, VCs, SP operators, and other ecosystem teams. The work will support FF OKRs, network OKRs, WBR and QBR reporting, PMF, onboarding, paid activity, FEVM and FOC analysis, Filecoin Pay metrics, and ecosystem health tracking. This grant will fund the public data work needed to keep Filecoin teams using one shared source for network metrics through 2026. The main outcomes are clearer KPI definitions, fresher public data, fewer dashboards, better reporting for FEVM activity like Filecoin Pay and FOC, faster answers to recurring ecosystem questions, and easier self serve access for people and agents. This should reduce duplicated private data work, lower vendor spend, and help teams make decisions from the same public evidence. 2.2 Who does this work support? [ "Pods", "Onramps", "Storage Providers", "Network Infrastructure", "Network Governance", "Other" ] 2.3 Total Funding Requested (USD) 160000 2.4 Milestones & Budget [ { "title": "Improve Shared Understanding", "description": "Maintain shared definitions for the main Filecoin KPIs that the Filecoin Data Portal supports. Work on improvements like clarifying Filecoin Pay gross payment volume, Filecoin Pay network fee ARR, protocol revenue, PGF deployments, block rewards, and revenue coverage ratio. Support KPI iteration with PLFIF, FF, FIDL, OSO, FilOz, and other data consumers. Document decisions when metric definitions change.", "dueDate": "2026-08-31", "fundingRequested": "25000", "completionCriteria": "Published metric documentation exists for the main KPI fields. Public issues or PRs show metric definition decisions. At least 3 stakeholder confirmations show that FDP data was used for OKR, WBR, QBR, PGF, or ecosystem reporting. The revenue coverage ratio and Filecoin Pay metrics have documented formulas and source data." }, { "title": "Core data reliability and maintenance", "description": "Keep the existing public datasets and dashboards fresh through the milestone date. Add or improve freshness checks, schema checks, and data quality checks for core public datasets. Fix upstream drift from Lily, Filecoin Pay, FOC, Blockscout, Datacap Stats, CoinCodex, and Filecoin RPC sources. Improve local tooling so errors are caught earlier with fdp check, fdp test, and pipeline status. This includes about $2,000 per month in infrastructure costs while keeping the stack lean enough for others to replicate.", "dueDate": "2026-09-30", "fundingRequested": "40000", "completionCriteria": "GitHub Actions shows successful scheduled runs. Public datasets remain available at data.filecoindataportal.xyz. fdp check, fdp status, and fdp test pass for the supported assets. At least 5 concrete data quality or drift fixes are visible in issues or PRs. Core datasets do not publish current day partial data." }, { "title": "Iterate FEVM metric foundations", "description": "Harden FEVM log ingestion and decoding. Improve Filecoin Pay rail, operator, and payment metrics. Maintain stablecoin tagging and token decimal handling for Filecoin Pay. Improve the model layer for FOC objects such as warm storage datasets, PDP service providers, and payment rails. Add regression tests for known FEVM events where practical.", "dueDate": "2026-10-31", "fundingRequested": "35000", "completionCriteria": "Public datasets include Filecoin Pay rails, Filecoin Pay operator metrics, warm storage datasets, PDP service providers, and daily network metrics. Filecoin Pay gross payment volume run rate and Filecoin Pay network fee ARR remain separate fields. Known token metadata such as USDFC and USDC.axl is documented in the models. Public issues or PRs close material risks around FEVM log ingestion, ABI drift, token units, or public contract tests." }, { "title": "New public datasets/models and reusab …[truncated] 3.1 Impact pathway *You cannot optimize what you cannot see*. The Filecoin Data Portal helps the network see itself so humans can focus on making informed decisions. The output of this projects can be seen as a set of maintained public datasets, metric docs, dashboards, agent resources, and data quality checks. This results on Filecoin teams using one shared source of truth instead of duplicated and private pipelines. **The final impact and goal is better reporting, faster decision making, lower duplicated cost, and clearer measurement of what is going on in the network**. 3.2 Verification metrics These are open metrics that related with the Filecoin Data Portal repository or platform. 1. Dataset freshness. The public run history and freshness checks show whether each supported dataset is current. 2. Number of public datasets with tests and column docs. 3. Number of reusable data requests shipped. 4. Dataset reads per week. 5. Portal and dashboard visits. 6. Number of stakeholder confirmations. 7. Number of downstream reports or tools using resources produced by the Filecoin Data Portal. 3.3 References In the last few months, these are some of the folks that have benefited from my work. - Irene Giacomelli, FilOz: built tooling like SP cost calculators and an L1 health dashboard from Portal datasets and the agent skill. - Tim, FilOz: used several Portal datasets to improve [Filecoin Pay explorer](https://pay.filecoin.cloud/mainnet). - Filecoin Foundation: uses Filecoin in Numbers and open datasets for OKR and ecosystem reporting. - Ian, Filecoin Foundation: used Portal datasets for internal FF reporting and ecosystem analysis. - Carl, OSO: consumes Portal data to enrich and produce detailed reports on impact metrics. - Josh, PLFIF: can vouch for strategic value, critical infra status, and historical ProPGF cost savings. - Diogo, Haven / VC user: consumes public sheets and Portal data for investment analysis. - Juan: Relies on many charts in Numbers for many talks and slides. - FIP 100 committee: used Portal public datasets for committee analysis and governance work. - Karma: displays Filecoin Data Portal metrics and KPIs and data for the projects that apply. - Messari/Nansen: uses Filecoin in Numbers for quarterly Filecoin reporting. - Paul, Filecoin Foundation: said the paid deal dashboard was useful for FF and investors because charts are easy to share. - Nicola, Filecoin ecosystem: requested sector and network metrics, including sectors that were never snapped. - Riba, Filecoin data ecosystem: partner on open data, provider tradeoffs, and shared data foundations. - Eva, Filecoin ecosystem, can vouch for Dune integrations and work done there to provide a much cheaper alternative. - Other teams have used the portal for debugging specific issues. 4.1 Monthly Operating Burn [ "< $10K (basic solo operation or part-time team)" ] 4.2 What % of total team monthly burn depends on this grant? 10-20% 4.3 If this grant is not awarded, what happens? If this grant is not awarded, the Filecoin Data Portal loses its only maintainer. Core datasets, dashboards, public sheets, and reporting pipelines will degrade or go stale. Reporting will become stale and not useful. Teams will fall back to ad hoc analysis, duplicating work (indexing, ...), private platforms (BigQuery, ...), duplicated pipelines, or paid vendors. This increases cost, fragments metric definitions, and reduces trust in shared ecosystem numbers. The portal will silently decay as the public data layer that many teams already depend on increasing costs on all the teams. 4.4 Core Team [David Gasquez](https://davidgasquez.com/). A strong data engineer for the last 10 years, 5 of those around Filecoin ecosystem. He worked on PL data platform, and many other data-adjacent projects in the ecosystem during these years. Since 2024, he maintains the Filecoin Data Portal. He writes about technical adjaccent topics ([data practices, permisisonless systems](https://davidgasquez.com/), and is passionate about open data. 4.5 Has your team received a ProPGF grant or funding from PLFIF before? [ "No" ] 5.1 Key risks & dependencies - Upstream data changes. Starboard, Zondax, Goldsky, Lily, JSON RPC, FEVM, FOC, and Filecoin Pay changes can break pipelines or change metric meaning. - Data quality issues. Some Filecoin data has no clean second source, so errors can be hard to detect without monitoring and stakeholder review. - Scope pressure. Reporting requests, data fixes, and new metrics can grow quickly. I will prioritize reusable public artifacts over one off analysis. - Partner dependencies. Shared schemas and integrations depend on coordination with other teams that might slow things down. Contributing to Core Infrastructure? I maintain the Filecoin Data Portal and derived work. The Filecoin Data Portal is the public, open data layer for the ecosystem decision making. It consists of curated open datasets, dashboards (Filecoin in Numbers, Dune), public sheets, and agent skills/MCPs. It is the shared, reproducible KPI and reporting substrate with no vendor lock-in. Who depends on it: PLFIF, the Filecoin Foundation, OSO, FilOz, Karma, investors, SP operators, committees like FIP-100, downstream AI agents, and external analysts (Messari, Nansen) for their quarterly Filecoin reports. If this work is not funded, core datasets and dashboards will go stale, FF OKR, network OKR, WBR, QBR, PMF, onboarding, paid activity, FEVM, FOC, and Filecoin Pay reporting will degrade, and teams will fall back to duplicated private pipelines or paid vendor data. Today this is a lean public infrastructure layer that serves about 600 portal visits per day, 300 Filecoin in Numbers visits per day, almost all stakeholders in the ecosystem, about 10,000 public dataset reads per week, and the most starred Filecoin dashboard on Dune. It also helped avoid about $500,000 in equivalent vendor spend in ProPGF Batch 2. Overall, it gives teams a shared source for network metrics instead of forcing each one to maintain private pipelines or pay vendors to get them. Objective 1 Indirect Objective 2 Direct Objective 3 Indirect Open Source Context The Filecoin Data Portal is fully open source and reproducible. All code, datasets, dashboards, documentation, and agent skills are public under an open license, with no closed or proprietary components. Datasets are served as plain files with no API gating or rate limits, and the stack is reproducible end-to-end while relying on open and free tools. On top of that and besides the open and transparent repository activity, most of the work is done in the open while I document the [roadblocks and decisions](https://github.com/davidgasquez/filecoin-data-portal/issues/233). You can follow along on [issues](https://github.com/davidgasquez/filecoin-data-portal/issues) and PRs!