Mirrored from filpgf.io — ProPGF Batch 3 (Karma program 1479, application 6a26ee7fe6959d5ed0ef1896, status: pending). Contact details redacted; canonical application lives on filpgf.io. 1.1 Project Name Filecoin Core Infrastructure & Integration Support 1.2 Project Github https://github.com/Zondax/fil-propgf3-infra 1.3 Project Website https://github.com/Zondax/fil-propgf3-infra 1.4 Team Lead/Point of Contact Juan Leni, CEO, (slack or telegram) 1.5 Category [ "Core Infrastructure" ] 1.6 Open Source Status Fully Open Source 2.1 Project Summary This project sustains the parts of Filecoin that connect it to the outside world. The most widely used is the Ledger stack for FIL, the device app, the Rust/JS/Go libraries, and the Ledger Live integration which is how FIL holders custody and move funds from a hardware wallet. Next is the Rosetta Filecoin implementation Coinbase uses to integrate Filecoin. Both run on the public node and archival infrastructure we operate, which a range of other teams also build on, from independent developers to our own Beryx explorer and API. We run it all as one platform, so a single Lotus upgrade can ripple through custody, exchange integrations, and chain data at once, which is why we support exchanges and providers across each upgrade, and our archival nodes, which hold complete history since genesis, have let exchanges backfill data they couldn't reconstruct alone. Running it as one shared fleet rather than separate stacks keeps the layer affordable, so a single grant covers infrastructure that would otherwise take several to fund. The grant sustains that operation, keeping the Ledger app and Ledger Live integration, the Rosetta suite, the nodes and public RPC, and network-upgrade support current through every protocol and SDK change. The gap it fills is operational continuity: the 2026 demand-side strategy assumes the network stays reachable and transactable, and nothing the KPIs measure works when an upgrade quietly breaks that layer. 2.2 Who does this work support? [ "Onramps", "Storage Providers", "Application Builders", "Application Users", "Network Infrastructure" ] 2.3 Total Funding Requested (USD) 288000 2.4 Milestones & Budget [ { "title": "Ops Window 1", "description": "Grant term: 1 October 2026 to 31 March 2027.\nThis first window covers 1 October to 30 November 2026. \n\n- Maintain the open-source Ledger stack (Filecoin device app + Rust/JS/Go libraries) and the Ledger Live integration against each Ledger SDK/firmware cycle and the supported device matrix (Nano S Plus, X, Flex, Gen5, Stax), so FIL holders can custody and transact.\n- Keep the Rosetta Filecoin suite (lib, proxy, indexing proxy) compatible with each Lotus release for Coinbase integration.\n- Operate the node and archival infrastructure and public RPC (mainnet and calibration) that the above run on and that other teams query directly.\n- Support exchanges and providers across any Filecoin network upgrade that falls in the window.\n- Proactive bug fixing, security patches, and regression prevention to keep the stack production-grade.", "dueDate": "2026-11-30", "fundingRequested": "96000 USD", "completionCriteria": "- Ledger app and Ledger Live compatible with the current Ledger SDK and functional across the supported device matrix (Nano S Plus, X, Flex, Gen5, Stax)\n- Rosetta suite compatible with the current Lotus release\n- Node and archival infrastructure operating with high availability and complete chain history since genesis\n- Any in-window network upgrade supported" }, { "title": "Ops Window 2", "description": "This window covers 1 December 2026 to 31 January 2027.\n\n- Maintain the open-source Ledger stack (Filecoin device app + Rust/JS/Go libraries) and the Ledger Live integration against each Ledger SDK/firmware cycle and the supported device matrix (Nano S Plus, X, Flex, Gen5, Stax), so FIL holders can custody and transact.\n- Keep the Rosetta Filecoin suite (lib, proxy, indexing proxy) compatible with each Lotus release for Coinbase integration.\n- Operate the node and archival infrastructure and public RPC (mainnet and calibration) that the above run on and that other teams query directly.\n- Support exchanges and providers across any Filecoin network upgrade that falls in the window.\n- Proactive bug fixing, security patches, and regression prevention to keep the stack production-grade.", "dueDate": "2027-01-31", "fundingRequested": "96000 USD", "completionCriteria": "- Ledger app and Ledger Live compatible with the current Ledger SDK and functional across the supported device matrix (Nano S Plus, X, Flex, Gen5, Stax)\n- Rosetta suite compatible with the current Lotus release\n- Node and archival infrastructure operating with high availability and complete chain history since genesis\n- Any in-window network upgrade supported" }, { "title": "Milestone 3", "description": "This window covers 1 February 2027 to 31 March 2027 and closes out the grant term.\n\n- Maintain the open-source Ledger stack (Filecoin device app + Rust/JS/Go libraries …[truncated] 3.1 Impact pathway **Primary objective:** Objective 3, Scale Paid Onchain Flagship Client Adoption (Objectives 1 and 2 secondary, indirect). Our work is the precondition for the integrators and clients this objective counts. **Output:** we keep the pieces that carry most of Filecoin's flow to and from the outside world running and current. First is the Ledger stack: the Filecoin device app, the Rust/JS/Go libraries, and the Ledger Live integration, which is how FIL holders custody and move funds from a hardware wallet. That integration runs on our nodes and stops working without them. Second is the Rosetta Filecoin implementation that Coinbase uses to read and integrate Filecoin. Underneath both sits the public RPC and archival infrastructure other teams query directly, and we support exchanges and providers through each network upgrade so none of it breaks. **Outcome:** exchanges, onramps, builders, storage providers, and flagship clients can reliably submit, track, and settle activity on Filecoin, and FIL holders can custody and move funds securely throughout. A client or exchange can only adopt and stay on Filecoin if it has a working custody path, a current integration layer, and reliable data to operate against, which is exactly what we keep running. **Impact:** the KPI we directly protect is the count and retention of active integrations and onboarded clients. If Ledger Live FIL support lapses, Rosetta falls behind a Lotus release, or the archival/RPC layer degrades, integrations break and clients churn or never onboard, a measurable drop against that KPI. Our contribution is indirect because we don't generate the activity the KPIs count, but these are the rails it moves on, and our metrics table is the external check: Ledger stack currency, Rosetta release currency, and node/archival availability are each a leading indicator of whether the adoption path stays open. Our archival history has already let exchanges backfill data they couldn't reconstruct alone. The downside is concrete: a botched upgrade stalls exchange deposits and withdrawals, suppressing onchain activity and confidence. 3.2 Verification metrics | Metric| Data source | How it's measured | Target (end of grant) | | Ledger device coverage | Ledger app store / GitHub releases | Supported device matrix kept current (Nano S Plus, X, Flex, Gen5, Stax) |Full matrix maintained | | Ledger Live functionality | Ledger Live app (Filecoin account); Zondax/Ledger release notes | FIL send/receive through Ledger Live working on supported devices, current with each Ledger Live and SDK release | Functional and current throughout the term | | Archival completeness | Public RPC queries against historical heights; exchange backfill confirmations | Archival nodes answer queries back to genesis | Complete history maintained | | Network upgrade readiness |Public Filecoin upgrade schedule; GitHub release tags; exchange confirmation | Each mandatory upgrade supported on the node/Rosetta stack within the upgrade window | 100% of in-term windows| | Rosetta release currency | GitHub release tags (rosetta-filecoin-lib/proxy) vs. Lotus releases| Days from a Lotus release to Rosetta compatibility | < 7 days, no missed releases | 3.3 References [redacted] [redacted] [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? Roughly 30%. This is one slice of a multi-protocol company, and the figure is the share of team cost attached to this Filecoin scope, not spare capacity. There's no separate commercial revenue covering it, so without the grant this slice isn't subsidized from elsewhere, the team moves to revenue-bearing work and the Filecoin service winds down (see 4.3). 4.3 If this grant is not awarded, what happens? Active maintenance of the Filecoin stack stops. Zondax is a multi-protocol infrastructure company, and the Filecoin-specific work in this proposal: the node fleet, public RPC, Rosetta suite, and the Ledger device app, libraries, and Ledger Live integration has no payer covering its ongoing cost. The prior commercial engagement that funded comparable work ends 30 September 2026, and without this grant the work does not hold up against revenue-bearing work on other protocols, so the team is redirected accordingly. In practice: the public RPC endpoints are withdrawn, the node fleet is decommissioned, Rosetta and the Ledger open-source stack are no longer maintained. Because the Ledger Live integration depends on this infrastructure, it stops working entirely not just its maintenance, but the service itself cutting off the FIL custody and transaction path for Ledger users. The Beryx explorer and API (separate proposal) also lose the backend they depend on. The consequences fall on specific users. Ledger device users would hit incompatibilities as SDK and firmware cycles move on, and Ledger Live users could lose the ability to manage FIL at all. Coinbase and other Rosetta consumers would have to maintain the integration themselves, which isn't a safe assumption given how much their in-house Filecoin know-how has reduced. Builders and exchanges on our endpoints would have to migrate. This grant keeps the layer maintained inside Zondax rather than sunset for protocols that fund their own support. The fleet runs as one shared operation across public RPC, Rosetta, and the Ledger custody path, which is the main cost efficiency: the same nodes and archival storage serve all of them, rather than standing up a separate stack for each. The largest line is hardware and archival storage, reflecting that this is an infrastructure project rather than a software-development one. 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 most significant external dependency is Ledger. Ledger sets the SDK and firmware requirements and controls the release and approval process for the device app, so changes happen on their schedule and to their criteria, not ours: an SDK or firmware change, a new device, or a revised requirement can force app updates and full re-validation across the device matrix, and Ledger ultimately gates whether and when a release ships. We manage this through an established working relationship with Ledger, but the timeline and approval are not fully in our control. The second external dependency is the Lotus upstream API: Lotus periodically changes its API across releases, which forces re-testing and updates across our Rosetta and node-access tooling, and an unexpected breaking change can compress an upgrade window. On the infrastructure side, archival storage and node capacity scale with reindexing needs and can spike during upgrades, the main cost-variance risk; we manage it by running the fleet as one shared operation rather than separate stacks per workload. Team risk is mitigated by internal cross-training and resource rotation, so no single contributor is a single point of failure on the Ledger or node stack. The principal funding risk is that this work has no commercial revenue behind it and the prior engagement ends 30 September 2026: it depends on grant funding to continue, and without it the work winds down as described in 4.3 rather than degrading gradually. Anything else you want to share that we didn't ask? This application is one of two complementary submissions from Zondax for Batch 3. Beryx is submitted as a separate proposal. The two projects are operationally related but financially and technically distinct: Beryx runs on the infrastructure funded here; this proposal covers the public RPC, upgrade operations, and Ledger client layer that Beryx and other consumers depend on Contributing to Core Infrastructure? Zondax has built and run Filecoin integration infrastructure since 2019, some of the oldest continuously-operated tooling in the ecosystem. The most widely used piece is the Ledger stack for Filecoin: we maintain the Ledger Filecoin device app, the Rust/JS/Go libraries, and the Ledger Live integration which is how FIL holders custody and move funds from a hardware wallet directly inside Ledger Live. That integration runs on our own nodes, without them it has nothing to talk to. We also maintain the Rosetta–Filecoin suite, lib, proxy, and indexing proxy, which is what Coinbase uses to read and integrate Filecoin. Underneath both sits the public archival and light RPC infrastructure on mainnet and calibration (api.zondax.ch) that other teams query directly instead of running their own nodes. And every time the network upgrades, we support exchanges and providers through the transition: tracking the schedule, sending reminders, and answering their questions. So the people who depend on this are every FIL holder using a Ledger device, Coinbase and other integrators reading Filecoin through Rosetta, and the builders, exchanges, and storage providers querying our public nodes. Note: this project is hardware and operations-heavy. A large share of cost is node capacity and storage plus devops hours rather than software development, which is why the ask is larger than a thin software-service proposal of comparable scope. Objective 1 Indirect Objective 2 Indirect Objective 3 Direct