Mirrored from filpgf.io — ProPGF Batch 3 (Karma program 1479, application 6a31958813ef2aeed7ce0d96, status: pending). Contact details redacted; canonical application lives on filpgf.io. 1.1 Project Name OSCIRIS PROTOCOL 1.2 Project Github https://github.com/oscirisprotocol/core 1.3 Project Website https://oscirislabs.com 1.4 Team Lead/Point of Contact Meshach Ishaya (Founder) - TG is @crypticmesh 1.5 Category [ "RFP 3 - AI infrastructure products on Filecoin" ] 1.6 Open Source Status Partial 2.1 Project Summary OSCIRIS Labs is building a Filecoin-backed evidence and provenance layer for secure AI compute. The project will turn OSCIRIS' existing verifier-backed AI workload protocol into a product that stores signed job receipts, model outputs, inference checkpoints, dataset lineage, benchmark archives, and compliance-ready audit bundles on Filecoin. It will support AI application builders, regulated AI teams, and Filecoin ecosystem infrastructure by making Filecoin the durable storage and retrieval layer for verifiable AI execution records. The Filecoin-related opportunity is that AI teams increasingly need tamper-evident evidence, provenance, and audit retention, while Filecoin needs more paid storage use cases tied to real customer workflows. By the end of the grant, OSCIRIS Labs will deliver a working Evidence Vault with APIs, reference schemas, retrieval/export flows, and pilot-ready secure AI compute evidence bundles stored on Filecoin. 2.2 Who does this work support? [ "Application Builders", "Application Users", "Network Infrastructure" ] 2.3 Total Funding Requested (USD) 120000 2.4 Milestones & Budget [ { "title": "Month 1: Filecoin Evidence Schema and Storage Prototype", "description": "Funded period: 07/15/2026 to 01/15/2027. This is a six-month grant term with three checkpoints: Month 1 schema/prototype and OSS release, Month 3 API/dashboard and paid-deal checkpoint, and Month 6 pilot-ready release and Filecoin impact validation. Existing OSCIRIS protocol work, verifier receipts, evidence ledgers, benchmark artifacts, and secure-compute prototypes are pre-grant baseline only; this milestone funds net-new Filecoin Evidence Vault work.\n\nDefine and implement the first Filecoin-backed evidence model for OSCIRIS secure AI compute. This milestone will map OSCIRIS job receipts, verifier records, model outputs, inference checkpoints, dataset provenance, and benchmark archives into durable Filecoin storage objects with clear metadata, content addressing, and retrieval requirements.\n\nDeliverables include the evidence object schema, Filecoin storage integration prototype, sample stored evidence bundles from existing OSCIRIS workflows, and developer documentation explaining how AI infrastructure teams can produce and retrieve verifiable evidence records.", "dueDate": "2026-08-15", "fundingRequested": "30000", "completionCriteria": "1. Evidence schema published for job receipts, verifier receipts, provenance records, model outputs, and benchmark archives.\n2. At least 3 representative OSCIRIS evidence bundles stored through the Filecoin integration path.\n3. Retrieval by job ID and content identifier demonstrated.\n4. Public documentation created for the open-source Filecoin-facing evidence format and prototype integration.\n5. OSS repo published under oscirisprotocol/dsp or another oscirisprotocol GitHub repo with LICENSE, CONTRIBUTING, schema docs, example bundles, and tagged v0.1 release.\n6. Pass/fail acceptance tests: schema examples validate against the published schema; sample bundles are reproducibly generated from the demo repo; stored objects can be retrieved by content ID and matched against original checksums.\n7. Line-item use of funds: Meshach founder/protocol architecture and schema work ($12,000), Angus backend/Filecoin integration engineering ($10,000), Filecoin storage/retrieval testing support ($3,000), and OSS documentation/demo packaging ($5,000)." }, { "title": "Month 3: Evidence Vault APIs and Operator Dashboard", "description": "Month 3 checkpoint in the 07/15/2026 to 01/15/2027 grant term. Build the core customer-facing Evidence Vault layer as net-new Filecoin grant work: authenticated APIs for uploading, indexing, searching, retrieving, and exporting AI evidence stored on Filecoin, plus an operator dashboard for audit review. This milestone moves the work from a schema/prototype into a usable product surface for AI infrastructure teams and regulated users.\n\nThe API will support evide …[truncated] 3.1 Impact pathway Objective selection: Objective 1 - Drive Paid Onchain Deals is Direct; Objective 2 and Objective 3 are N/A. The primary 2026 Network Objective this project targets is Objective 1: Drive Paid Onchain Deals. In the program's terms, the KPI this proposal moves is net-new paid onchain Filecoin storage activity: paid Filecoin storage deals, FVM/onchain storage-payment transactions, or equivalent Filecoin onchain deal/payment records that can be tied to stored data. Evidence Vault activity qualifies because each counted event begins with an AI evidence bundle, produces content IDs, stores that data through Filecoin, and records the paid onchain deal/payment evidence. The output of this project is a working Filecoin-backed Evidence Vault for secure AI compute: schemas, APIs, dashboard, and reference workflows for storing verifier receipts, provenance records, checkpoints, model outputs, benchmark archives, and audit bundles. The direct KPI pathway is evidence object creation -> paid Filecoin storage deal or paid FVM/onchain storage transaction -> retrievable audit/export record -> repeatable paid storage demand from AI workflows. Auditable paid-deal rule: a counted paid action must have an Evidence Vault content ID linked to either a Filecoin storage deal ID or an FVM transaction hash/payment record, plus storage provider/miner ID where applicable, bytes stored, timestamp, and nonzero FIL/payment confirmation. The Evidence Vault index and final report will publish this mapping as content ID -> dealID/txHash -> provider/miner ID -> bytes -> timestamp -> payment confirmation. We will exclude unrelated OSCIRIS storage, manually uploaded artifacts outside the Evidence Vault workflow, unpaid test-only records, free provider pilots, local development records, and any offchain-only payment or retrieval activity that cannot be tied to an onchain deal/transaction identifier. Deal execution plan: OSCIRIS Labs will package evidence bundles, create content IDs, and execute paid storage through direct storage provider deals, Filecoin-compatible deal tooling, or FVM/onchain storage payment flows. Counted pilot deals may be paid from the OSCIRIS grant pilot budget or by design-partner/customer wallets, but they must produce the auditable onchain/provider evidence above. The project does not depend on a single named provider commitment: the vendor/provider support budget covers public Filecoin storage provider onboarding, deal ops, payment verification, retrieval checks, and fallback to fewer larger paid deals if small deal execution is slower than expected. Meshach and Angus own the integration path and Filecoin storage/deal testing budget. Design-partner path: the first pilots will come from OSCIRIS secure-compute workflows plus 2-3 prospective AI infrastructure/evaluation users, including a regulated AI services workflow, an AI benchmarking/eval …[truncated] 3.2 Verification metrics <h2>3.2 Verification Metrics</h2> <table> <thead> <tr> <th>Metric</th> <th>Data source</th> <th>How it is measured</th> <th>Target at end of grant</th> </tr> </thead> <tbody> <tr> <td>Paid Filecoin storage deals or paid storage transactions created</td> <td>Filecoin storage/deal records, storage provider records, payment records where applicable, Evidence Vault deal/transaction index, and final report</td> <td>Count only paid deals/transactions generated through Evidence Vault workflows and linked to evidence bundle content IDs; exclude unrelated OSCIRIS storage and unpaid test records</td> <td>6+ paid deals/transactions, with 2+ completed by Milestone 2</td> </tr> <tr> <td>Filecoin-backed AI evidence objects stored</td> <td>Evidence Vault index and Filecoin storage records</td> <td>Count unique stored receipts, provenance records, inference checkpoints, model outputs, benchmark artifacts, and audit objects linked to content IDs</td> <td>10,000+ evidence objects</td> </tr> <tr> <td>Filecoin storage volume generated by OSCIRIS workflows</td> <td>Storage provider/deal records and Evidence Vault storage logs</td> <td>Sum bytes stored from AI evidence bundles, benchmark archives, provenance records, checkpoints, and audit exports</td> <td>1TB+ pilot evidence data</td> </tr> <tr> <td>Retrievable evidence records</td> <td>Evidence Vault API logs and retrieval tests</td> <td>Count evidence records retrievable by job ID, model, provenance reference, verifier status, tenant, or content ID</td> <td>10,000+ retrievable records</td> </tr> <tr> <td>Verified AI workload runs producing Filecoin evidence</td> <td>OSCIRIS job ledger, verifier receipts, and Evidence Vault index</td> <td>Count secure AI training, inference, RAG, evaluation, and fine-tuning runs that produce signed evidence and store outputs on Filecoin</td> <td>500+ AI workload runs</td> </tr> <tr> <td>Application-builder integration readiness</td> <td>Public docs, reference tooling repository, and integration tests</td> <td>Presence of schema docs, API docs, SDK/reference tooling, sample bundles, and successful integration tests</td> <td>Public docs + reference tooling + 3 integration examples published</td> </tr> <tr> <td>Pilot or design-partner usage</td> <td>Pilot records, usage logs, and final report summary</td> <td>Count teams or internal customer workflows using the Evidence Vault in production-like tests</td> <td>3-5 pilot/design-partner workflows</td> </tr> </tbody> </table> <h2>Paid Deal Evidence Table</h2> <p> Final acceptance evidence should include this reviewer-auditable mapping for every counted …[truncated] 3.3 References Emmanuel Akanji [redacted] Pldg contributor on Akave and Storacha 4.1 Monthly Operating Burn [ "$10-$100K (small team)" ] 4.2 What % of total team monthly burn depends on this grant? 70 4.3 If this grant is not awarded, what happens? OSCIRIS Labs will continue the core secure compute protocol work, but the Filecoin specific Evidence Vault will move slower and remain limited to internal prototypes. The grant accelerates the customer facing storage, retrieval, and audit product needed to turn OSCIRIS evidence artifacts into measurable Filecoin network usage. Budget reconciliation: the form requires a burn range, so we selected USD 10,000 to USD 100,000. The focused project burn is USD 28,500 per month, which sits inside that range. The grant funded period runs from July 15, 2026 to January 15, 2027 as a six month grant term. Total project effort is about USD 28,500 per month for 6 months, or USD 171,000. Grant covered scope is about USD 20,000 per month for 6 months, or USD 120,000. OSCIRIS co funding and in kind support is about USD 8,500 per month for 6 months, or USD 51,000. This covers founder time not billed to the grant, existing infrastructure, advisory support, and unfunded operating overhead. Consolidated grant budget by milestone and contributor: Meshach receives USD 36,000 total, made up of USD 12,000 in Milestone 1, USD 5,000 in Milestone 2, and USD 19,000 in Milestone 3. Angus receives USD 30,000 total, made up of USD 10,000 in Milestone 1, USD 15,000 in Milestone 2, and USD 5,000 in Milestone 3. Ojoma receives USD 18,000 total, made up of USD 10,000 in Milestone 2 and USD 8,000 in Milestone 3. Documentation, demo, and integration test contractor support receives USD 18,000 total, made up of USD 5,000 in Milestone 1, USD 5,000 in Milestone 2, and USD 8,000 in Milestone 3. Filecoin storage and deal testing vendor or provider support receives USD 18,000 total, made up of USD 3,000 in Milestone 1, USD 5,000 in Milestone 2, and USD 10,000 in Milestone 3. These allocations sum to Milestone 1 at USD 30,000, Milestone 2 at USD 40,000, Milestone 3 at USD 50,000, and a total grant request of USD 120,000. Paid deal operations are explicitly resourced. Angus owns the technical deal and transaction metadata capture. Meshach owns provider coordination, design partner coordination, and final verification. The Filecoin storage and deal testing vendor or provider support line covers provider coordination, paid deal execution, retrieval checks, and the payment confirmation table promised in the milestones. Budget to output justification: Meshach and Angus cover the paid deal execution path, metadata capture, and validation table. Ojoma covers dashboard and API reliability needed for retrieval and export. Documentation and demo contractor support covers reproducible acceptance tests and integration materials. Filecoin storage and deal testing vendor or provider support covers provider coordination, paid deal execution, retrieval checks, and payment confirmation evidence. This is why the USD 120,000 request maps directly to the Object …[truncated] 4.4 Core Team Meshach Otonte Ishaya is the founder and technical lead for OSCIRIS Labs. Allocation: 0.45 FTE for 6 months; grant-covered cost $36,000 plus about $24,000 in-kind/co-funded founder time. He leads protocol design, backend implementation, evidence packaging, infrastructure workflows, design-partner onboarding, and final reporting. LinkedIn: https://www.linkedin.com/in/meshach-ishaya-4b986815a/ Angus Ndirpaya Jr. supports backend and Filecoin integration engineering. Allocation: 0.35 FTE for 5 months; grant-covered cost $30,000. He owns Evidence Vault backend, Filecoin integration path, upload/retrieve/export APIs, deal/transaction metadata capture, and integration tests. LinkedIn: https://www.linkedin.com/in/angus-ndirpaya-jr/ Ojoma Onoja is a full-stack systems, API, dashboard, and protocol-adjacent collaborator/advisor. Allocation: 0.25 FTE for 4 months; grant-covered cost $18,000. He owns operator dashboard review, API/frontend/backend integration review, and release hardening support. LinkedIn: https://www.linkedin.com/in/ojoma-onoja/ OSCIRIS Labs will also use clearly scoped contractor/vendor support: docs/demo/integration-test contractor support ($18,000) and Filecoin storage/deal testing vendor or provider support ($18,000). Core protocol and evidence architecture remain under direct founder oversight. 4.5 Has your team received a ProPGF grant or funding from PLFIF before? [ "No" ] 5.1 Key risks & dependencies The main delivery risks are Filecoin integration complexity, retrieval performance, evidence schema design, and the need to keep privacy/security claims within the evidence actually proven by OSCIRIS. There is also a product risk that AI teams may need clearer compliance packaging before they treat evidence storage as a budgeted workflow. OSCIRIS Labs will reduce these risks by keeping the first release narrow: store and retrieve concrete AI evidence bundles, publish the open evidence schema, validate retrieval by job ID/content ID, document claim boundaries, and use pilot workflows before making broader commercial claims. The team will also keep customer-hosted and sensitive deployment components separate from the open Filecoin-facing schemas and tools. Any feedback you have on the application process? The RFP framing is clear, and the milestone-based structure is useful for teams building focused products around Filecoin's 2026 priorities. Anything else you want to share that we didn't ask? OSCIRIS Labs is not applying as a generic AI project. The proposal is specifically to make Filecoin the durable evidence, provenance, checkpoint, and audit layer for secure AI compute workflows. The existing OSCIRIS work already produces the kind of signed receipts, verifier records, model outputs, and benchmark artifacts that Filecoin can store and make retrievable; this grant turns that technical base into a product aligned with Batch 3's AI infrastructure goals. Clarifications for review: grant-funded work is scoped from 07/15/2026 to 01/15/2027 as a six-month grant term. Existing OSCIRIS protocol artifacts are pre-grant baseline; this request funds net-new Filecoin Evidence Vault work. The concrete project burn is $28,500/month, with about $20,000/month requested from this grant and about $8,500/month contributed by OSCIRIS. The milestone schedule is Month 1 schema/prototype, Month 3 API/dashboard with 150GB and 2 paid-deal checkpoint, and Month 6 pilot-ready release with 1TB and 6 paid-deal target. Objective clarification: the form only provides radio buttons for Objectives 1-3, so Objective 1 is selected as Direct. The exact objective title is Objective 1: Drive Paid Onchain Deals, and the KPI this proposal targets is net-new paid onchain Filecoin storage activity verified through paid Filecoin deal IDs or FVM/onchain payment transaction hashes linked to Evidence Vault content IDs. Contributing to Core Infrastructure? Not Applicable Objective 1 Direct Objective 2 N/A Objective 3 N/A Open Source Context OSCIRIS Labs will keep commercially sensitive deployment, customer data, tenant configuration, hosted-service operations, and private customer integrations closed. The grant-funded Filecoin-facing public-good components will be open source and independently usable by third parties. Open-source repos/modules, intended Apache-2.0: https://github.com/oscirisprotocol/core or another repo under the oscirisprotocol GitHub organization if renamed before release. The OSS scope includes Filecoin evidence schemas, receipt/provenance object formats, reference upload/retrieve/export tooling, SDK/client examples, a minimal reference API/server for the Evidence Vault workflow, retrieval/export interfaces, integration tests, sample verifier receipt bundles, demo repository, acceptance-test fixtures, and developer documentation. A third party should be able to generate sample evidence bundles, store/retrieve/export them against Filecoin-compatible storage paths, and reproduce the published acceptance tests without using OSCIRIS Labs' hosted service. Milestone OSS commitments: tagged v0.1 release by Milestone 1 with schemas, example bundles, LICENSE, CONTRIBUTING, and docs; tagged v0.2 release by Milestone 2 with reference upload/retrieve/export tooling, SDK/client examples, and integration tests; tagged v1.0 pilot release by Milestone 3 with demo repo, retrieval/export tests, and content ID -> dealID/txHash mapping examples. Closed scope: hosted multi-tenant deployment, customer UI/tenant management, customer data, proprietary deployment automation, commercial support operations, and private customer integrations. This boundary lets the Filecoin ecosystem reuse the evidence formats and integration layer while allowing OSCIRIS Labs to operate a supported commercial product. Current state and net new grant scope: OSCIRIS has an early public developer MVP available at https://github.com/oscirisprotocol/core. The current public repo is a Rust workspace for the OSCIRIS node CLI, offchain protocol runtime, verifier path, and testnet chain client. The README states that contributors can install osciris-node, generate identities, run the local settlement demo, and follow the multi host testnet join guide. Current public pointers reviewers can inspect: 1. Public repo: https://github.com/oscirisprotocol/core 2. Current progress and protocol boundary: https://github.com/oscirisprotocol/core#current-progress 3. Local settlement demo and quick start commands: https://github.com/oscirisprotocol/core#quick-start 4. Multi host testnet join guide: https://github.com/oscirisprotocol/core/blob/main/docs/multi_host_testnet_join_guide.md Current state checklist before this grant: The existing OSCIRIS work includes an early developer MVP, node CLI, identity generation flow, local settlement demo, multi host testnet join guide, signed claims, enterprise assign …[truncated]