Mirrored from filpgf.io — ProPGF Batch 3 (Karma program 1479, application 6a2d40a6e0e7d91b6125baac, status: pending). Contact details redacted; canonical application lives on filpgf.io. 1.1 Project Name QAPP by DeployQuantum: Verifiable PQC Compliance Records on Filecoin 1.2 Project Github https://github.com/deployquantum 1.3 Project Website https://deployquantum.com/ 1.4 Team Lead/Point of Contact Nikos Fratzeskos, Head of Partnerships & Ecosystem, DeployQuantum. Telegram: @Ozyman21 1.5 Category [ "RFP 1 - Customer-facing products built on Filecoin" ] 1.6 Open Source Status Fully Open Source 2.1 Project Summary Regulated organisations in the EU and the US now carry legal post-quantum deadlines: DORA covers 22,000+ financial institutions, NIS2 covers roughly 160,000 entities, and CNSA 2.0 starts a supplier attestation wave in 2027. Each of them has to prepare for quantum, show that its vendors are compliant too, prove all of it to a regulator, and report to stakeholders, without exposing the sensitive details of its own systems. DeployQuantum already produces the core evidence these organisations need: cryptographic inventories (CBoMs with per-asset Mosca scores) and regulator-ready exposure assessments. What is missing is a neutral place where that evidence, together with the vendor attestations that accompany it, can live so that a third party can verify it existed, when it existed, and that it has not changed. QAPP anchors hash commitments of compliance evidence to Filecoin as paid, verifiable, tamper-evident storage deals, so a regulator or auditor verifies integrity and timing without ever seeing the underlying systems. This brings a recurring class of paying web2 customers onto Filecoin, in direct response to the Batch 3 call for customer-facing products serving compliance and regulated data. The pipeline, schema, and verifier tool are all published open source so any compliance vendor can adopt Filecoin as its evidence layer. 2.2 Who does this work support? [ "Storage Providers", "Application Builders", "Application Users", "Other" ] 2.3 Total Funding Requested (USD) $86,700 2.4 Milestones & Budget [ { "title": "M1 (Month 2 of 6, $28,700): Evidence schema and architecture", "description": "This milestone defines what we build and proves Filecoin is the right anchor.\n• Open evidence-record specification: what gets hashed, what stays private, and how a vendor\nattestation chains to its parent organisation.\n• Integration architecture on Filecoin Onchain Cloud: Warm Storage and PDP for verifiable persistence,\nFilecoin Pay for stablecoin settlement.\n• Requirements gathered from design-partner organisations already in DeployQuantum's pipeline. Our lead partner is one of the largest banks in Greece, which has already shared its compliance framework and sample data with us; we are also in early discussion with two service-provider organisations in the same regulated space. Partners can be named to reviewers on request.\n• Anchor-chain due-diligence note: Filecoin’s own post-quantum posture and why hash-based anchoring\nstays sound for decade-horizon evidence.\n\nBudget ($28,700): engineering $8,000, product and crypto-domain $16,000, compliance and legal (LOI\nand NDA templates) $4,000, Filecoin and infrastructure $700.", "dueDate": "2026-10-01", "fundingRequested": "$28,700", "completionCriteria": "Done when all four are delivered and the public items are live:\n• Evidence-record specification, published openly.\n• Integration architecture document naming the Warm Storage and PDP path and Filecoin Pay.\n• Requirements summary from at least two design partners, with letters of intent secured.\n• Anchor-chain due-diligence note, published openly." }, { "title": "M2 (Month 4.5 of 6, $33,000): Working pipeline on testnet", "description": "A working, open-source pipeline running end to end on the Calibration testnet.\n• Anchoring pipeline: a DeployQuantum readiness-scan output becomes a timestamped,\nhash-committed Filecoin evidence record.\n• Verifier tool (CLI plus a minimal web view) that confirms a record’s existence, integrity, and timestamp.\n• Public repository with setup documentation, under a permissive licence.\n\nBudget ($33,000): engineering $24,000, product and crypto-domain $6,000, compliance and legal\n$1,000, testnet and infrastructure (CI, hosting) $2,000.", "dueDate": "2026-12-15", "fundingRequested": "$33,000", "completionCriteria": "Done when a reviewer can clone the public repository, run the verifier against a sample record on Calibration, and reproduce the result:\n\n• Pipeline turns a readiness-scan output into a timestamped, hash-committed record, shown end to end\non at least one redacted sample.\n• Verifier confirms a record’s existence, integrity, and timestamp against Calibration.\n• Public repository contains the pipeline, the verifier, and setup docs under a permissive licence." }, { "title": "M3 (Month 6 of 6, $25,000): Mainnet pilot and release.", "description": "A …[truncated] 3.1 Impact pathway **Primary objective**: Drive Paid Onchain Deals (Direct). The work also supports, indirectly, Strengthen Network Profitability and Cryptoeconomics and Scale Paid Onchain Flagship Client Adoption. So in the objective selectors: Objective 1 (Drive Paid Onchain Deals) = Direct, Objective 2 (Strengthen Network Profitability and Cryptoeconomics) = Indirect, Objective 3 (Scale Paid Onchain Flagship Client Adoption) = Indirect. This project contributes directly to Drive Paid Onchain Deals. The KPIs it moves are the number of paid storage deals on Filecoin and the number of distinct paying clients, specifically a class of web2 demand Filecoin does not reach today: regulated organisations paying to anchor compliance evidence. **Output**: an open evidence schema, an anchoring pipeline, a verifier, and a mainnet pilot with regulated design partners. Outcome: those organisations get a regulator-verifiable evidence trail for their post-quantum migration, including the vendor attestations they collect, without exposing internal systems, and they pay for it through Filecoin Pay as recurring storage deals. Mapping to the KPI: the section 3.2 metrics translate straight into it, at least 50 evidence records anchored and at least 4 paid storage deals from one paying organisation during the pilot. **How we measure success**. Primarily by the number of distinct paying organisations onboarded and by recurring deal frequency across audit cycles, not by pilot-stage dollar volume, which is intentionally small because a hash commitment is tiny. The pilot proves a repeatable, recurring paid-deal pattern; deal volume then scales with the number of regulated organisations, each anchoring every audit cycle, which is why the demand compounds. The work also supports Scale Paid Onchain Flagship Client Adoption indirectly, by establishing a beachhead in the regulated mid-market that can grow toward larger institutions. **What counts as a paid onchain dea**l. One Filecoin storage deal created when an organisation anchors a batch of evidence at an audit checkpoint. Records are batched, so the deal is the per-organisation, per-cycle unit, not one deal per record. **Scaling beyond the pilot.** Regulated organisations do not anchor once, they anchor every audit cycle, which is where the recurring demand comes from. Baseline cadence is quarterly, aligned to reporting cycles, with some organisations monthly. A typical organisation anchors roughly 50 records at onboarding (its cryptographic inventory, its exposure assessment, and around 40 vendor attestations), then 10 to 20 incremental records each cycle as attestations refresh, which is one to two paid deals per organisation per quarter. The pilot proves this for one organisation. From DeployQuantum's existing regulated-EU funnel we target three to five paying organisations by month 12 and eight to twelve by mont …[truncated] 3.2 Verification metrics **1. Evidence records anchored on mainnet** Data source: onchain records plus the pilot report How it is measured: count of compliance records hash-anchored via QAPP Target: at least 50, from one pilot organisation (a second is upside) **2. Paid Filecoin storage deals** Data source: chain explorer and deal IDs How it is measured: count of paid deals created, records batched into periodic deals Target: at least 4 over the pilot **3. Pilot organisations anchoring** Data source: pilot write-up plus onchain payer addresses How it is measured: distinct paying organisations Target: 1 design partner (a second is upside) **4. Open artefacts released** Data source: public GitHub repository How it is measured: schema, pipeline, verifier, and documentation under a permissive licence Target: 4 artefacts at v1.0 **5. Anchor-chain due diligence** Data source: the published Milestone 1 note How it is measured: a public post-quantum posture assessment of the Filecoin stack Target: published openly 3.3 References We are new to the Filecoin ecosystem, so we lead with work a reviewer can verify directly rather than self-description. Public and checkable now: our post-quantum methodology and the Filecoin scorecard at layerqu.com/chains/filecoin; our live assessment tooling at deployquantum.com/learn; and our Head of Research's QAOA review, Blekos et al., Physics Reports 1068 (2024), [one of the most cited QAOA reviews in the field](https://www.sciencedirect.com/science/article/abs/pii/S0370157324001078). On design partners, our lead partner is one of the largest banks in Greece, which has already shared its compliance framework and sample data with us and can be named to reviewers on request. We are also in early discussion with two service-provider organisations in the same regulated space. We can share an LOI template and further partner detail on request. 4.1 Monthly Operating Burn [ "$10-$100K (small team)" ] 4.2 What % of total team monthly burn depends on this grant? Roughly 35%. The grant works out to about $14.5K per month over six months against a team burn of roughly $40K per month. It funds the dedicated Filecoin integration time of the two to three people on this workstream; it is material for this project and not existential for the company. 4.3 If this grant is not awarded, what happens? The compliance product continues; it is core to our commercial roadmap. What changes is the evidence layer: without this grant the Filecoin integration is deprioritised behind paid engagements and our raise, evidence anchoring ships on conventional infrastructure first, and the Filecoin path slips nine to twelve months and loses its open-source, any-vendor-can-adopt shape. The grant is what makes Filecoin the default evidence layer rather than a later option. 4.4 Core Team **Antonis Argyros**, CEO: 26+ years venture building, two exits, one merger; founder of Greek Quantum Gate (1,000+ members). linkedin.com/in/antonisargyros **Christos Papalitsas**, Quantum Product: senior quantum lead at a Fortune 100 global pharma; PhD in optimization and quantum computing; 12+ years across telecom, product, and scientific computing. linkedin.com/in/papalitsas **Kostas Blekos**, Head of Research: lead author of Blekos et al., a review on the Quantum Approximate Optimization Algorithm and its variants, Physics Reports 1068 (2024) ([one of the most cited QAOA reviews in the literature](https://www.sciencedirect.com/science/article/abs/pii/S0370157324001078)); head of research at a quantum deep-tech company. **Nikos Fratzeskos**, Head of Partnerships & Ecosystem (point of contact for this application). linkedin.com/in/nfratz 4.5 Has your team received a ProPGF grant or funding from PLFIF before? [ "No" ] 5.1 Key risks & dependencies **Pilot conversion**. The mainnet pilot depends on design partners committing inside the grant window. Mitigation: we recruit from an active commercial funnel of regulated EU mid-market firms with named compliance deadlines, and the pilot asks them to anchor evidence they already produce, not to adopt new internal tooling. **Regulatory acceptance**. Whether a given regulator accepts onchain-anchored evidence varies by jurisdiction. Mitigation: the QAPP supplements rather than replaces filing formats (the record proves integrity and timing of evidence the organisation still submits conventionally), and we already ship jurisdiction-specific addenda in our assessment work. **Technical dependency on Filecoin Onchain Cloud**. The pipeline builds on Warm Storage, PDP, and Filecoin Pay, which are young surfaces. Mitigation: M2 runs entirely on Calibration before any mainnet commitment, and the Synapse SDK is the documented integration path. **Anchor-chain cryptography**. Storing post-quantum compliance evidence on a chain whose own signatures are not yet post-quantum invites an obvious question. We answer it in the design: records are hash commitments, and hash-based integrity is not affected by the signature-breaking attacks that threaten elliptic-curve cryptography; M1 publishes the full anchor-chain assessment so the trade-off is documented rather than hidden. **Team size**. Small team with commercial workload. Mitigation: fixed-scope milestones, and the grant explicitly funds the dedicated integration time. Anything else you want to share that we didn't ask? On the timeline. Just so the dated milestones are read correctly: we have written this as a six-month plan which will start on grant award rather than at submission. On an early-August start the dates land near Month 2, Month 4.5, and Month 6 (roughly early October, mid December, and early February). These are illustrative and would shift with the actual award date. We mention it only to explain how the dates were derived, not to assume an outcome. On scope. We understand this sits in the compliance and regulated data lane of the customer-facing products RFP, which may be adjacent to what you most directly expected. Before applying we checked with the team and took the signal that applications beyond the core focus areas would be explored this round, so we felt encouraged to put it forward. We read that as openness to explore, nothing more. On Filecoin. We have done preliminary work on the network's post-quantum surface rather than claiming deep internal expertise: our LayerQu product keeps a public scorecard of Filecoin's signature and proof stack (layerqu.com/chains/filecoin), which is where the Milestone 1 due diligence starts from. We are approaching this with a broad scope in mind and are ready to adjust the shape, sequencing, or emphasis to whatever is most useful to the network. Karma Profile 0x3238f683c549b9be4b72708782a6ca652843964a06badbb566ff3933a7e6a4d0 Objective 1 Direct Objective 2 Indirect Objective 3 Indirect Open Source Context Everything this grant funds is published openly under a permissive licence: the evidence record schema, the anchoring pipeline that writes compliance evidence to Filecoin, the verifier tool a regulator or auditor uses to check a record, and the documentation. Any compliance vendor, not just DeployQuantum, can adopt the pipeline; that is the point. The verifier and the record format have to be open for the product to work at all: a regulator only trusts evidence it can check without trusting the vendor. DeployQuantum’s commercial assessment services sit upstream and are not part of the grant scope, and any enterprise workflow software we may later build on top of this layer sits outside the grant scope as well; the trust layer itself stays open.