Mirrored from filpgf.io — ProPGF Batch 3 (Karma program 1479, application 6a318c5513ef2aeed7ce0d94, status: pending). Contact details redacted; canonical application lives on filpgf.io. 1.1 Project Name RWA Compliance Vault on Filecoin 1.4 Team Lead/Point of Contact Cristian Malfesi, Field CTO, Telegram @cristianmalfesi 1.5 Category [ "RFP 1 - Customer-facing products built on Filecoin" ] 1.6 Open Source Status Partial 2.1 Project Summary The RWA Compliance Vault is a compliance-grade evidence and vault-operations product for tokenized real-world-asset (RWA) issuers and regulated asset managers, sold as a supported SaaS offering with Filecoin as the verifiable storage backbone. It closes the gap that blocks institutional capital at the risk-committee stage: today there is no way for an LP, auditor, or regulator to independently verify that a fund's NAV records, asset documentation, and audit trails are unaltered and remain retrievable for the 7-10 years regulators require. Filecoin uniquely solves this, warm Storage PDP makes document availability continuously verifiable on-chain, and because the commitment registry and trigger logic run on FEVM (the same chain as the storage proofs), the absence or failure of a document's proof is itself a natively readable condition, with no trusted oracle. The product supports RWA issuers and asset managers (application users), the storage providers who gain paid, never-churning SLA storage demand billed in USDFC, and application builders who can build on the open evidence protocol. It is deliberately a paid-deal and FEVM-activity play (high-value compliance documents, not high-volume raw data) and open-sourcing the evidence protocol makes it public infrastructure for any compliance-grade use case on Filecoin (legal, healthcare archives, supply chain). 2.2 Who does this work support? [ "Storage Providers", "Application Builders", "Application Users" ] 2.3 Total Funding Requested (USD) $235,000 2.4 Milestones & Budget [ { "title": "Foundation + Public Proof", "description": "Architecture document (data model, contract + API spec, trigger taxonomy, user flows); document store API on calibration testnet via Synapse SDK (upload, retrieve, provenance proof, PDP status); FEVM commitment registry + third-party signer registry on testnet; golden dataset v1 (12-month synthetic fund documentary lifecycle incl. failure scenarios); public self-serve verification sandbox.", "dueDate": "2026-08-31", "fundingRequested": "$45,000", "completionCriteria": "A document round-trips with a verifiable on-chain commitment and PDP status end-to-end on testnet; the public sandbox is usable by reviewers (upload a document, receive CID + on-chain receipt, verify independently)." }, { "title": "Compliance, Ingestion & Indexing", "description": "Ingestion gateway v1 (SFTP/structured-email intake, sender validation, parsing, witness signing); ERC-3643-compatible permissioned share classes + on-chain identity registry wired to KYC provider (testnet); in-house FEVM indexing service (document commits, vault events, compliance events).", "dueDate": "2026-09-30", "fundingRequested": "$45,000", "completionCriteria": "A real-format third-party document is ingested end-to-end via the gateway, anchored and indexed; a non-KYC transfer reverts at the contract level." }, { "title": "Beta / MVP — Full Stack on Testnet", "description": "Vault Observer mode against the design partner's existing setup + Full-vault greenfield template; protection trigger engine across the three trigger tiers + tranche pools exercised with simulated capital; issuer & LP dashboards; auditor view; end-to-end Beta complete on testnet across all four layers.", "dueDate": "2026-10-31", "fundingRequested": "$55,000", "completionCriteria": "The design partner can use the Beta end-to-end on testnet: a document arrives → is anchored → indexed → a missed-payment scenario fires the trigger and a simulated payout → vault operations are governed and anchored → the auditor view verifies it independently." }, { "title": "Adjustments, Hardening & Code Freeze", "description": "Refinement from design-partner feedback; QA hardening on the golden-dataset suite; performance and UX fixes; internal security review complete; registry + vault contracts frozen; external audit engaged and scheduled for Month 5.", "dueDate": "2026-11-30", "fundingRequested": "$40,000", "completionCriteria": "A hardened release candidate the design partner signs off on; internal review complete; code frozen and the external audit booked." }, { "title": "Audit, Production Deployment & First Paying Customer", "description": "External audit complete on the frozen registry + vault contracts (funded within the grant; runs in parallel with production prep), findings addressed; mainnet deployment (docu …[truncated] 3.1 Impact pathway Output: an open evidence protocol on Filecoin (commitment registry, signer registry, verification SDK) plus a commercial service that anchors a fund's documentary lifecycle to Warm Storage and runs governed vault operations on FEVM. Outcome: RWA issuers and their auditors can independently verify that compliance records are unaltered and continuously retrievable, removing the risk-committee blocker that currently gates institutional allocation; each issuer generates paid, SLA-backed storage deals billed in USDFC and recurring FEVM transactions (every document a commitment, every vault operation and trigger a transaction). Impact: Filecoin gains paid, never-churning storage demand under 7-10-year regulatory retention and real on-chain economic activity, and establishes the first regulated financial-data vertical, “a regulator independently verified a fund's audit trail on Filecoin”, which compounds as the customer base and verifiable AUM grow. This moves the 2026 objectives by converting storage capacity into paid on-chain deals (Obj 1) and on-chain value transacted plus gas (Obj 2), with flagship paying-client adoption following as issuers scale (Obj 3). 3.2 Verification metrics | Metric |Data Source |How it's measured |Target (end of grant)| | Paid SLA storage deals (count & value) | Filecoin Pay / on-chain records | USDFC payments tied to Warm Storage SLA deals | ≥1 paying issuer with an active SLA storage deal | |USDFC flow via Filecoin Pay |On-chain (Filecoin Pay) |USDFC transferred for storage billing | Recurring billing flowing from the first issuer| |FEVM transactions (registry + vault) |FEVM block explorer / indexing |Tx count from registry and vault contracts |Live mainnet contracts; recurring document-commit and vault-operation tx | |Verifiable AUM anchored |Issuer disclosure + on-chain commitments |AUM whose compliance documents are anchored on Filecoin |First issuer's AUM anchored on mainnet | |Public sandbox usage |App analytics + on-chain commitments |Documents verified through the public sandbox |Sandbox live from M1 with external usage | 3.3 References Protofire has been a Filecoin infrastructure partner since 2021. Our most directly relevant reference is the Filecoin Node Infrastructure engagement with Protocol Labs, where we optimized node operations, developed Glif Nodes RPC API services, and deployed advanced monitoring - achieving 99.95%+ uptime, sub-800ms data retrieval, and a 240% increase in developer usage (30,000+ developers/month). Full case study: https://protofire.io/projects/filecoin-node-infrastructure/ Beyond Filecoin, Protofire has delivered 200+ projects for ecosystem-defining clients across DeFi and Web3 infrastructure. Public references include: Chainlink — Developer tools suite (SDKs, subgraphs, testing frameworks) that drove 3× more integrations and improved oracle reliability by 75%. https://protofire.io/projects/chainlink-dev-tools/ Balancer — ve8020 Launchpad that cut integration time by 82% and grew governance-aligned TVL from $120M to $730M across 41 protocols. https://protofire.io/projects/balancer/ Safe (Gnosis Safe) — Cross-chain multisig wallet development, now securing $100B+ in assets. https://protofire.io/projects/gnosis-safe-wallet/ The Graph — Subgraph and node management that slashed query times by 92% and indexing costs by 65%, making Protofire the #2 indexer in the ecosystem. https://protofire.io/projects/the-graph-subgraphs/ Full project portfolio: https://protofire.io/projects/ 4.1 Monthly Operating Burn [ "$10-$100K (small team)" ] 4.2 What % of total team monthly burn depends on this grant? ~15–20%. This grant funds a dedicated workstream (smart contract engineers, tokenomics, front-end/subgraph, audit coordination) on top of Protofire's existing project portfolio. It is not survival funding, it is a focused public-good contribution. 4.3 If this grant is not awarded, what happens? Protofire would continue as a Filecoin infrastructure partner, but the Filecoin-specific, open-sourced evidence protocol and the product's Filecoin integration would be deprioritized and slowed. The commercial product could proceed on other storage rails, but without Filecoin's continuously verifiable storage proofs it would not deliver the regulatory-grade verifiability that is the product's core differentiator, and the open public-good protocol for the ecosystem would not ship on this timeline. 4.4 Core Team Protofire is a Filecoin infrastructure partner since 2021, operating services at ~12M daily requests and 99.58% uptime, with 200+ delivered projects for ecosystem-defining clients (public references: Chainlink, Balancer, Safe, among others). The grant team: three full-stack engineers covering smart contracts / Solidity, backend (document store API, Synapse SDK, ingestion gateway), frontend, and FEVM indexing; a QA engineer (golden-dataset end-to-end coverage and hardening); a Product Owner (delivery coordination, design-partner onboarding, customer success); and a part-time compliance specialist with external counsel (KYC/KYB, trigger-logic regulatory review, staged protection path). Relevant delivery references: the VaultOS governed-vault architecture (network-level vault infrastructure delivered for an EVM ecosystem client in under 3 months); RWArmor parametric protection (in active institutional BD); and a KYC-gated P2P OTC layer (dOTC) live in production on three EVM chains. 4.5 Has your team received a ProPGF grant or funding from PLFIF before? [ "No" ] 5.1 Key risks & dependencies External dependency - Filecoin Onchain Cloud: the product depends on Warm Storage, PDP, and Filecoin Pay remaining available on mainnet at current service levels; FEVM contract patterns are validated on calibration testnet before mainnet commitment. Critical path - external audit: the audit must complete within the Month 5 window. Mitigated by booking the slot in Month 1, running an internal pre-audit in Months 2-3, freezing the code in Month 4, and deploying to mainnet in Observer mode only (no funds move) to keep the audited surface small. Customer - design partner: the first paying-customer slot depends on the design partner's timeline; mitigated by a qualified backfill pipeline (fund administrators / tokenization platforms). Regulatory - protection layer: pooled parametric protection is, by substance, insurance or a derivative in most jurisdictions; the grant scope is deliberately testnet-only for this layer, with a staged productization path under legal opinion (counsel review is a funded deliverable). No claim depends on LP capital or insurance licensing within the grant window. Technical - integrations: KYC provider (Sumsub/Persona) integration and third-party document formats from fund administrators. GDPR by design: documents encrypted client-side before storage, erasure via key destruction, no personal data on-chain. Anything else you want to share that we didn't ask? This proposal is deliberately honest about what Filecoin gains: paid, recurring storage demand and FEVM economic activity from a high-value, low-volume regulated vertical, not a TVL or raw-data-onboarding play. Every milestone is externally verifiable (public sandbox at M1, end-to-end testnet at M2-M3, a real paying issuer in production at M5), and the open-sourced evidence protocol is reusable public infrastructure for any compliance-grade use case on Filecoin. Objective 1 Direct Objective 2 Direct Objective 3 Indirect Open Source Context The protocol layer is open-sourced under a permissive license: the FEVM commitment registry contracts, the evidence specification (document schema, signer registry, verification rules), the verification SDK and CLI, indexing schemas, and a reference auditor-view client. The commercial layer (ingestion gateway and parsing pipelines, issuer/LP dashboards, managed onboarding, SLA and support, billing) remains proprietary so that operating revenue funds continued maintenance without further grants. This aligns with the network's objectives: any Filecoin ecosystem team can adopt the evidence protocol without Protofire, and every additional implementer increases the value of the network's storage proofs for regulated use cases.