Mirrored from filpgf.io — ProPGF Batch 3 (Karma program 1479, application 6a2702f5e6959d5ed0ef1898, status: pending). Contact details redacted; canonical application lives on filpgf.io. 1.1 Project Name Beryx: Filecoin Explorer, Public API and Traces 1.2 Project Github https://github.com/Zondax/fil-propgf3-beryx 1.3 Project Website https://beryx.io 1.4 Team Lead/Point of Contact Juan Leni, CEO 1.5 Category [ "Core Infrastructure" ] 1.6 Open Source Status Fully Open Source 2.1 Project Summary Beryx is the public, genesis-complete chain-data layer for Filecoin: a free API exposing the full history of the chain, an open-source explorer built on it, and a traces service that lets developers see exactly how transactions and smart contracts executed. This project keeps those three services running, correct, and current as Filecoin and the FVM evolve, for the developers who build and debug on Filecoin, the storage providers and analysts who watch the network, and anyone who needs to look up or verify something on chain. Its indexed coverage of chain and built-in-actor data (miner and sector lifecycle, multisig, datacap, deals, verified registry, internal messages, drand, chain economics, plus FEVM/ERC-20 and decoded contract state) now approaches the depth of Lily, the Filecoin project's reference chain-state indexer, but exposed as a live public API rather than a node each team has to run and a database they have to host. The 2026 strategy names chain data as a high-value area, and Beryx is the open, public version of it, the same data the ecosystem already uses to see what is happening on the network. The gap it fills is comprehensive, free, verifiable observability: without it, builders fall back to running their own indexers or to less complete sources, which raises cost and lowers trust across everything built on top. Beryx runs on the node and archival infrastructure in Zondax's companion proposal; this proposal funds the data and interface layer on top of it. 2.2 Who does this work support? [ "Application Builders", "Application Users", "Network Infrastructure", "Network Governance", "Storage Providers" ] 2.3 Total Funding Requested (USD) 144000 2.4 Milestones & Budget [ { "title": "Milestone 1 - Open-source release + Ops Window 1", "description": "Covers 1 October to 30 November 2026. \n\nPublish the full Beryx stack as open source, including the indexing backend that was previously operated privately, under a permissive license with documentation sufficient for a third party to run it independently. In parallel, operate the explorer, public API, and Traces service to the standing targets, keep indexing current with the chain, and absorb any Filecoin or FVM change in the window. This milestone is weighted higher because it covers the one-time engineering to clean, document, and release the indexing backend and supporting services, on top of normal operation.", "dueDate": "2026-11-30", "fundingRequested": "120000", "completionCriteria": "Beryx explorer, API, and indexing backend published in public repositories under an open-source license, with setup documentation; explorer, API, and traces available to target for the period; API free under the fair-use policy; data correct and current with the chain through any in-window upgrade. Verified by the public repositories plus a period report covering availability, API usage, and data currency" }, { "title": "Milestone 2 - Ops Window 2", "description": "Covers 1 December 2026 to 31 January 2027. \nDescription: Operate the now-open-source Beryx explorer, public API, and Traces service. Keep the indexing current with the chain, absorb any Filecoin or FVM change in the window so API responses, traces, and the explorer stay correct, and maintain the free public API under the fair-use policy. Triage and address issues raised against the public repositories.", "dueDate": "2027-01-31", "fundingRequested": "12000", "completionCriteria": "Explorer, API, and traces available to target for the period; API free and reachable under the fair-use policy; data correct and current with the chain, including through any in-window upgrade; public repositories maintained and issues triaged. Verified by a published period report covering availability, API usage, and data currency." }, { "title": "Milestone 3 - Ops Window 3", "description": "Covers 1 February 2027 to 31 March 2027 and closes out the grant term.\n\nDescription: Continue operating the open-source Beryx explorer, public API, and Traces service through the end of the term. Keep indexing current, absorb any upstream Filecoin or FVM change, maintain the free public API, and continue triaging issues against the public repositories.", "dueDate": "2027-03-31", "fundingRequested": "12000", "completionCriteria": "Explorer, API, and traces available to target for the period; API free and reachable under the fair-use policy; data correct and current with the chain; public repositories maintained and issues triaged. Verified by a published period report plus an end-of-grant conti …[truncated] 3.1 Impact pathway **Primary objective:** Objective 2, Strengthen Network Profitability & Cryptoeconomics direct contribution to its transparency and measurement dimension; indirect to deal volume and revenue. Objectives 1 and 3 secondary, indirect. **Output**: we keep the Beryx explorer, public API, and traces available, correct, and current with the chain. **Outcome**: developers can build and debug against reliable data and execution traces, and the ecosystem, including the Foundation and reviewers, can measure and verify network activity from a free, public source. **Impact**: the 2026 strategy calls explicitly for transparent impact measurement and data-driven public-goods funding, and Beryx is the open substrate that makes that possible, the same complete chain index used to see what is actually happening on Filecoin. Our direct contribution is to that measurement and transparency goal: Beryx's outputs (a genesis-complete public API, traces, and explorer) are what activity is measured through, externally verifiable via the metrics in our table. Our contribution to the headline cryptoeconomic KPIs is indirect, since we don't generate deal volume ourselves, but the link is close, because the data we publish is what those metrics are computed and trusted from. For developers (Objectives 1 and 3), the API and traces are what a builder needs to ship and debug a contract and what a flagship client needs to audit its own activity; without reliable public data, they fall back to running their own indexers or to opaque sources, raising cost and lowering trust. 3.2 Verification metrics | Metric | Data Source | How it's measured | Target | | Service availability| Zondax status page | Monthly uptime % across explorer, API, traces | At target for the period | | API usage | Beryx API telemetry; GitHub-token registrations | Requests served per month; active access tokens | Sustained or growing vs. baseline | | Traces usage | Traces service telemetry | Traces queries served per month |Sustained or growing vs. baseline | 3.3 References [redacted] [redacted] [redacted] [redacted] [redacted] [redacted] [redacted] [redacted] 4.1 Monthly Operating Burn [ "$10-$100K (small team)" ] 4.2 What % of total team monthly burn depends on this grant? 15% 4.3 If this grant is not awarded, what happens? The prior commercial engagement that funded comparable work ends 30 September 2026. If this work is not funded the public Beryx services stop being maintained. The explorer, public API, and traces have no payer covering their ongoing cost, and Zondax, as a multi-protocol company, can't sustain them against revenue-bearing work on other protocols. In practice the services would be frozen and then taken down: the free public API would go offline or behind limits, the explorer would stop tracking protocol changes and drift out of correctness, and the traces service would be retired. The ecosystem would lose its genesis-complete, free public Filecoin chain index and the open explorer built on it, and developers would fall back to running their own indexers or to less complete sources. Beryx also depends on the node and archival infrastructure in the companion proposal; if that isn't funded, Beryx has no data to serve regardless. 4.4 Core Team **Juan Leni**: CEO and founder, Zondax. Overall responsibility for the company and the maximum engineering authority on this work. Long-standing lead of Zondax's Filecoin engagement, including the Ledger Filecoin application and the team's protocol and integration work across multiple L1 ecosystems. **Ainhoa Aldave**: Operations and delivery. Project management, partnerships, and coordination, including communication with exchanges and providers and the day-to-day running of the grant. **Emmanuel Murano:** Engineering Manager. Architecture and engineering oversight across the node infrastructure, Rosetta suite, and Ledger stack; responsible for the operational delivery of the maintained components. 4.5 Has your team received a ProPGF grant or funding from PLFIF before? [ "No" ] 5.1 Key risks & dependencies The main dependency is the companion infrastructure proposal: Beryx runs on the node and archival infrastructure funded there, so if that isn't funded, Beryx has no data to serve regardless of this grant. The two are scoped and measured separately at the funder's request but are technically linked. The main external dependency is the Filecoin and FVM upstream: protocol and FVM changes can alter data formats and execution semantics, which means the indexer, API, and traces need updating so results stay correct through each upgrade, and an unexpected change can briefly affect data currency. This is also a maintenance-level scope: at this budget the project keeps the services running and correct rather than building major new features, which would need separate funding. And the work has no commercial revenue behind it, so a funding gap stops it rather than degrading it gradually. Anything else you want to share that we didn't ask? This is one of two complementary Batch 3 submissions from Zondax. Beryx is submitted separately so its public-good impact can be measured on its own. This proposal covers the data and interface layer (explorer, API, traces); the companion proposal funds the node and archival infrastructure Beryx and other consumers run on. Contributing to Core Infrastructure? Beryx is Filecoin's public chain-data layer, built and operated by Zondax. The Beryx API indexes the whole chain since genesis and exposes it through a free public API, a complete, queryable history of every account, transaction, internal message, and fee, available to anyone with a token. The Beryx Explorer is the human-facing interface on top of that API, and it's one of the explorers listed in Filecoin's own documentation. The Traces service exposes detailed transaction execution data, which is what developers use to debug and verify how their smart contracts actually behaved on chain. Beryx API and Explorer both won Filecoin RetroPGF in Rounds 1 and 2, so the network has already recognized the work as a public good. Who depends on it: FVM and smart-contract developers building and debugging against the API and traces, storage providers and analysts watching network activity and fees, and anyone who needs to look something up on Filecoin through the explorer. Objective 1 Indirect Objective 2 Direct Objective 3 Indirect Open Source Context Beryx is open source. The explorer is already published publicly, and the Beryx API is free and open under a fair-use policy with tokens available to anyone with a GitHub account. Part of this grant (Milestone 1) is to bring the full stack to current, actively maintained open source: refreshing the public explorer repository to match what runs in production, and publishing the indexing backend that produces the data, which was previously operated privately. Once released, the whole stack can be audited, forked, and run independently, so no single provider is a dependency, anyone can stand up the same index. This directly supports the 2026 strategy's emphasis on open, verifiable infrastructure.