Skip to content

Omnia Protocol: Zero-Knowledge Identity Shards with Filecoin-Backed Proof Storage and Data Availability #2124

Description

@Willow7737

Filecoin Open Grant Proposal

Omnia-Filecoin Provenance Integration

Integrating ZK-verified supply chain provenance with Filecoin's decentralized storage network

Field Details
Category Integrations
Proposer Willow7737
Repositories omnia-protocol, omnia-web
License MIT/Apache-2 dual-license (new code); CC0 (existing codebase)
Total Budget $50,000
Duration 24 weeks (6 months)

Maintenance and Upgrade Plans

The Omnia Protocol is a long-term infrastructure project with an active development roadmap extending through Phase 9 (Universality). The Filecoin integration will be maintained as a core component of the protocol going forward.

Ongoing Maintenance (post-grant): The Filecoin Settlement Adapter will be maintained alongside the existing Ethereum and Celestia adapters as a first-class settlement target. Bug fixes, compatibility updates for Filecoin network upgrades, and performance improvements will be included in the regular Omnia Protocol release cycle (currently biweekly). The existing bug bounty program ($100–$50,000 per finding) covers the Filecoin adapter code once merged.

Upgrade Roadmap:

  1. FVM-native provenance verification using Filecoin's native actor model instead of EVM compatibility, reducing gas costs and improving performance
  2. DataCap allocation for subsidized storage of public-interest provenance data (e.g., pharmaceutical anti-counterfeiting records)
  3. Snap-deal integration for real-time provenance data onboarding without waiting for sector sealing
  4. Cross-settlement verification enabling a provenance claim proven on Filecoin FEVM to be verified on Ethereum or other supported chains

Community Support: The Omnia Protocol maintains active GitHub Discussions and a Discord server for community support. The Filecoin integration will be documented with the same level of detail as existing adapters, and community contributions to the adapter will be welcomed under the project's CC0 license.


Team

Team Members

Willow7737 — Project Lead & Protocol Engineer

Team Website

https://github.com/Willow7737/omnia-protocol

Relevant Experience

The project lead (Willow7737) has single-handedly designed and implemented the entire Omnia Protocol codebase over 18 months — 81,000+ lines of production Rust across 224 source files with 1,382 passing tests. This demonstrates deep expertise in distributed systems, consensus algorithms, zero-knowledge proofs, post-quantum cryptography, and systems programming in Rust. The codebase includes production-grade implementations of:

  • BFT consensus with VRF leader selection
  • Groth16 zero-knowledge proofs on BN254
  • ML-KEM-768 post-quantum cryptography
  • Feldman VSS distributed key generation
  • A complete slashing engine

All built from scratch with zero production unwrap() calls and #![forbid(unsafe_code)] enforced across all crates.

Critically, this project requires extending Omnia's existing settlement-agnostic architecture with a new Filecoin adapter. The team has already successfully implemented two settlement adapters (Ethereum via Alloy with live RPC integration, and Celestia with real HTTP RPC integration for blob submission and Merkle inclusion verification). Adding a Filecoin adapter follows the exact same SettlementAdapter trait pattern, dramatically reducing implementation risk. The existing OmniaRollup.sol Solidity verifier contract on Ethereum (using BN254 precompiles) can be adapted for Filecoin's FEVM with minimal modifications, as both chains support the same EVM precompiles.

The team's existing work on the Physical Domain Shard (append-only provenance log with BLAKE3 hash-chain integrity, CRDT-friendly ownership tracking, and ZK query capabilities) provides the foundation for the provenance-to-storage pipeline. The provenance data structures are already defined; the integration work is primarily about connecting existing outputs to Filecoin's storage APIs and serializing data in CAR format.

Team Code Repositories


Additional Information

How did you learn about the Open Grants Program? Through research into Web3 grant programs aligned with Omnia Protocol's settlement-agnostic architecture. Filecoin's focus on durable decentralized storage makes it a natural integration target for Omnia's provenance system.

Additional context: The Omnia Protocol operates under the CC0 1.0 Universal license — the most permissive open-source license available, dedicating all code to the public domain. This means the Filecoin community and any other party can use, modify, and distribute the integration code without restriction.

The project maintains an active bug bounty program ranging from $100 to $50,000 per finding, providing ongoing security validation. A three-node BFT testnet has been validated over real libp2p connections, and 7 high-priority audit findings have already been remediated.

The project's commitment to radical transparency includes a published stub inventory that explicitly lists all incomplete implementations, and every claim in the README is traceable to a specific repository file, benchmark, or API response.

# Filecoin Open Grant Proposal ## Omnia-Filecoin Provenance Integration

Integrating ZK-verified supply chain provenance with Filecoin's decentralized storage network

Field Details
Category Integrations
Proposer Willow7737
Repositories [omnia-protocol](https://github.com/Willow7737/omnia-protocol), [omnia-web](https://github.com/Willow7737/omnia-web)
License MIT/Apache-2 dual-license (new code); CC0 (existing codebase)
Total Budget $50,000
Duration 24 weeks (6 months)

Project Name

Omnia-Filecoin Provenance Integration

Proposal Category

Integrations

Individual or Entity Name

Individual (Willow7737)

Project Repos

Filecoin Ecosystem Affiliations

None

Technical Sponsor

None

Open Source Agreement

Yes. The existing Omnia Protocol codebase is released under CC0 1.0 Universal, which is more permissive than MIT/Apache-2. All new integration code developed under this grant will be dual-licensed under MIT/Apache-2 as required.


Project Summary

Supply chains are opaque. Pharmaceuticals, electronics, agricultural commodities, and high-value goods traverse complex multi-party paths from raw material to end consumer, and at every step the provenance record is either missing, fragmented, or easily falsified. Existing blockchain provenance solutions attempt to solve this by recording supply chain events on a single ledger, but they suffer from three fundamental limitations:

  1. Sequential consensus creates throughput bottlenecks that cannot keep pace with real-time supply chain event streams.
  2. The provenance data itself is stored on-chain without meaningful privacy protection, exposing commercially sensitive logistics information.
  3. The data is not anchored to decentralized storage, meaning the provenance records are only as durable as the chain itself — if the chain forks, the provenance history can be rewritten or lost.

Omnia Protocol addresses the first two limitations through its causal graph consensus architecture (achieving ~7,190 events per second with sub-100-microsecond finality latency) and its Physical Domain Shard, which implements an append-only provenance log with BLAKE3 hash-chain integrity, CRDT-friendly ownership tracking, and zero-knowledge proof capabilities. However, the third limitation — durable, verifiable, decentralized storage of provenance data — remains an open problem. This is where Filecoin becomes essential.

This project integrates Omnia Protocol's Physical Domain Shard with Filecoin's decentralized storage network, creating an end-to-end pipeline where:

  • Supply chain events are processed through Omnia's causal graph consensus
  • Provenance records are anchored to Filecoin for durable storage
  • Zero-knowledge proofs generated by Omnia's Groth16 settlement layer enable privacy-preserving verification of provenance claims without exposing the underlying logistics data

The integration adds a Filecoin Settlement Adapter to Omnia's existing settlement-agnostic architecture (which already includes live Ethereum and Celestia adapters), enabling Filecoin to serve as both a data availability layer and a proof verification layer for Omnia's provenance events.


Impact

The current state of supply chain verification is a mess of paper certificates, centralized databases, and mutual distrust. Counterfeit pharmaceuticals alone kill an estimated 1 million people per year according to the WHO, and the economic cost of counterfeit goods globally exceeds $4.5 trillion annually.

Blockchain-based provenance solutions have been proposed for years, but none have achieved meaningful adoption because they cannot simultaneously deliver high throughput, data privacy, and storage durability — all three of which are non-negotiable for enterprise supply chain applications. Projects that achieve only one or two of these properties fail in practice:

  • High-throughput chains without privacy expose trade secrets
  • Private chains without decentralized storage create single points of failure
  • Durable storage without fast consensus cannot capture events in real time

The Omnia-Filecoin integration addresses all three requirements simultaneously:

  • Throughput: Omnia's causal graph consensus delivers thousands of provenance events per second, compared to ~15 TPS on Ethereum-based solutions
  • Privacy: Omnia's Physical Shard and ZK-rollup layer allow provenance claims to be verified without revealing logistics details
  • Durability: Filecoin delivers storage durability with cryptographic guarantees of redundancy and retrievability

The combination creates a provenance system that enterprises can actually deploy: fast enough for real-time tracking, private enough for competitive logistics data, and durable enough for regulatory compliance and audit requirements.

The impact extends beyond supply chain. Any application requiring verifiable data provenance with durable storage — scientific data integrity, regulatory compliance records, carbon credit verification, digital rights management — benefits from this integration.

Success looks like: a supply chain operator can submit a provenance event to Omnia, have it finalized in microseconds, generate a ZK proof of the provenance claim, and anchor both the data and proof to Filecoin — all in a single automated pipeline that requires no trusted intermediaries.


Outcomes

The final deliverable is a production-ready integration between Omnia Protocol's provenance pipeline and Filecoin's storage network, implemented as three components:

1. Filecoin Settlement Adapter

A new SettlementAdapter implementation for Filecoin within Omnia's existing settlement-agnostic architecture. This adapter will:

  • Submit provenance data batches and ZK proofs to Filecoin via the Filecoin.Eth JSON-RPC API, leveraging Filecoin's EVM compatibility (FEVM)
  • Deploy a Solidity verifier contract (OmniaProvenanceVerifier.sol) that verifies Groth16 proofs on-chain
  • Handle proof submission, deal tracking, and finality confirmation
  • Follow the same SettlementLayer trait pattern used by the existing Ethereum and Celestia adapters

2. Provenance-to-Storage Pipeline

A Rust module that automatically:

  • Batches provenance events from Omnia's Physical Shard
  • Serializes them into CAR (Content Addressable aRchive) format for IPFS/Filecoin compatibility
  • Generates Merkle roots and inclusion proofs
  • Submits data storage deals to Filecoin via the boost client or programmatically through the Filecoin JSON-RPC API

The pipeline ensures that every provenance event recorded in Omnia's causal graph is also durably stored on Filecoin with content-addressed integrity.

3. ZK Provenance Verification on FEVM

A Solidity smart contract deployed on Filecoin's FEVM that:

  • Accepts Groth16 proof submissions from Omnia's settlement layer
  • Verifies them on-chain using BN254 precompiles
  • Enables any party to verify a provenance claim (e.g., "this pharmaceutical batch originated from facility X and was handled by carriers Y and Z") without accessing the underlying logistics data

Success Metrics

  • End-to-end latency from Omnia event finalization to Filecoin data deal submission: under 60 seconds for batched provenance records
  • ZK proof verification on FEVM: under 5 seconds, targeting less than 5M gas per proof
  • Data integrity: 100% of provenance events anchored to Omnia must also be retrievable from Filecoin via content address
  • Integration test coverage: at least 95% for the Filecoin adapter and pipeline modules
  • Documentation: Complete integration guide, API reference, and deployment walkthrough

Data Onboarding

Timeframe Projected Data Description
Month 1 ~10 GB Development and testing with synthetic supply chain event data (simulated pharmaceutical supply chain with 10,000 items)
Month 3 ~100 GB Expanded testnet with multi-commodity supply chain simulations (pharmaceuticals, electronics, agricultural goods)
Month 6 ~500 GB Production pilot deployment with 2–3 early adopter supply chain operators generating real provenance events
Month 12 ~2 TB Scaled production deployment with expanded operator onboarding, historical data migration, and continuous provenance stream

Adoption, Reach, and Growth Strategies

Primary audience: Supply chain operators and logistics technology providers who need cryptographically verifiable provenance records that meet regulatory requirements (FDA Drug Supply Chain Security Act, EU Falsified Medicines Directive, etc.)

Secondary audience: Developers building provenance-aware applications on Filecoin who need a high-throughput event source with ZK proof capabilities.

The global supply chain management software market is valued at $17 billion and growing at 11% CAGR, while the immediate addressable market for blockchain-based provenance is estimated at $500M–$1B.

First 10 users: Target supply chain technology companies already interested in blockchain provenance but blocked by throughput, privacy, or durability limitations. Existing GitHub Discussions community and Discord server include logistics technology professionals who have inquired about production deployment. We will offer dedicated integration support and co-development of custom provenance schemas.

First 100 users: Publish the integration as an open-source reference implementation with comprehensive documentation, tutorial videos, and a demo deployment. Present at Filecoin and supply chain technology conferences (LogiMAT, FILECON, EthCC). The demo deployment will include a publicly accessible dashboard (extending omnia-web) that visualizes end-to-end provenance flows from Omnia through Filecoin.

Ongoing growth: The Omnia-Filecoin integration creates a network effect — each new supply chain operator that anchors provenance data to Filecoin increases the value of the entire provenance verification ecosystem. We will foster this flywheel by publishing verification tools, creating a provenance explorer on omnia-web, and establishing a provenance schema registry.


Development Roadmap

Milestone 1: Filecoin Settlement Adapter & FEVM Verifier Contract

Duration: 8 weeks (July 1 – August 24, 2026)
Team: 1 protocol engineer (lead), 1 smart contract developer

Implement FilecoinSettlementAdapter as a new SettlementAdapter implementation within the omnia-adapters crate, following the existing pattern established by EthereumSettlementAdapter and CelestiaSettlementAdapter. The adapter will connect to Filecoin nodes via the Filecoin.Eth JSON-RPC API (compatible with FEVM), supporting proof submission, transaction tracking, and finality confirmation. Deploy OmniaProvenanceVerifier.sol on Filecoin Calibration Testnet — a Solidity contract that verifies Groth16 proofs using BN254 precompiles, based on the existing production-quality OmniaRollup.sol Ethereum verifier.

Deliverables:

  • omnia-adapters/src/settlement/filecoin.rs — complete Filecoin settlement adapter implementation
  • contracts/OmniaProvenanceVerifier.sol — FEVM-compatible Groth16 verifier contract with deployment scripts
  • Integration test suite with at least 90% coverage for the adapter module
  • ADR (Architecture Decision Record) documenting the Filecoin settlement design
  • Deployment guide for Filecoin Calibration Testnet

Milestone 2: Provenance-to-Storage Pipeline

Duration: 8 weeks (August 25 – October 19, 2026)
Team: 1 protocol engineer (lead), 1 Rust developer

Implement ProvenancePipeline module within the omnia-node crate that subscribes to Physical Shard events and automatically batches them for Filecoin storage. Implement CAR (Content Addressable aRchive) serialization for provenance records, converting Omnia's BLAKE3-hash-chained provenance log entries into IPFS/Filecoin-compatible content-addressed format with IPLD DAG structure. Implement data deal submission to Filecoin storage providers via the boost client API and/or programmatic JSON-RPC, including deal negotiation, tracking, and renewal. Add pipeline status monitoring and health checks to the existing Prometheus/Grafana monitoring stack.

Deliverables:

  • omnia-node/src/provenance_pipeline.rs — complete pipeline implementation
  • omnia-node/src/car_serializer.rs — CAR/IPLD serialization module
  • Pipeline configuration (batch size, deal duration, provider selection) with sensible defaults
  • Extended Prometheus metrics and Grafana dashboard panels for pipeline monitoring
  • Integration test suite with at least 95% coverage for pipeline and serialization modules
  • Data integrity verification tool that audits Omnia provenance events against Filecoin data deals

Milestone 3: ZK Provenance Verification Integration & Production Hardening

Duration: 8 weeks (October 20 – December 14, 2026)
Team: 1 protocol engineer (lead), 1 Rust developer, 1 documentation/community lead

Integrate the Filecoin settlement adapter and provenance pipeline with Omnia's ZK-rollup settlement layer, creating an end-to-end flow:

Physical Shard event → consensus finalization → ZK proof generation → Filecoin data deal + FEVM proof submission → on-chain verification

Implement privacy-preserving provenance verification: generate ZK proofs that attest to specific provenance claims without revealing the full provenance chain, and submit these proofs to the OmniaProvenanceVerifier.sol contract on FEVM. Build a verification API endpoint in the existing REST API. Extend the omnia-web dashboard with a provenance explorer. Production hardening: comprehensive error handling, retry logic for Filecoin deal submissions, gas optimization for FEVM interactions, and load testing.

Deliverables:

  • End-to-end integration of Filecoin adapter + provenance pipeline + ZK settlement layer
  • Privacy-preserving ZK provenance verification on FEVM (verified proof submission + on-chain verification)
  • REST API endpoint for provenance claim verification with Filecoin content address resolution
  • omnia-web provenance explorer extension (React components for Filecoin deal visualization)
  • Production hardening: error handling, retry logic, gas optimization, load test results
  • Complete documentation: integration guide, API reference, tutorial, deployment walkthrough
  • Demo deployment on Filecoin Calibration Testnet with synthetic supply chain data

Total Budget Requested

Milestone Description Completion Date Funding
1 Filecoin Settlement Adapter & FEVM Verifier August 24, 2026 $18,000
2 Provenance-to-Storage Pipeline October 19, 2026 $17,000
3 ZK Provenance Verification & Production Hardening December 14, 2026 $15,000
Total $50,000

Maintenance and Upgrade Plans

The Omnia Protocol is a long-term infrastructure project with an active development roadmap extending through Phase 9 (Universality). The Filecoin integration will be maintained as a core component of the protocol going forward.

Ongoing Maintenance (post-grant): The Filecoin Settlement Adapter will be maintained alongside the existing Ethereum and Celestia adapters as a first-class settlement target. Bug fixes, compatibility updates for Filecoin network upgrades, and performance improvements will be included in the regular Omnia Protocol release cycle (currently biweekly). The existing bug bounty program ($100–$50,000 per finding) covers the Filecoin adapter code once merged.

Upgrade Roadmap:

  1. FVM-native provenance verification using Filecoin's native actor model instead of EVM compatibility, reducing gas costs and improving performance
  2. DataCap allocation for subsidized storage of public-interest provenance data (e.g., pharmaceutical anti-counterfeiting records)
  3. Snap-deal integration for real-time provenance data onboarding without waiting for sector sealing
  4. Cross-settlement verification enabling a provenance claim proven on Filecoin FEVM to be verified on Ethereum or other supported chains

Community Support: The Omnia Protocol maintains active GitHub Discussions and a Discord server for community support. The Filecoin integration will be documented with the same level of detail as existing adapters, and community contributions to the adapter will be welcomed under the project's CC0 license.


Team

Team Members

Willow7737 — Project Lead & Protocol Engineer

Team Website

https://github.com/Willow7737/omnia-protocol

Relevant Experience

The project lead (Willow7737) has single-handedly designed and implemented the entire Omnia Protocol codebase over 18 months — 81,000+ lines of production Rust across 224 source files with 1,382 passing tests. This demonstrates deep expertise in distributed systems, consensus algorithms, zero-knowledge proofs, post-quantum cryptography, and systems programming in Rust. The codebase includes production-grade implementations of:

  • BFT consensus with VRF leader selection
  • Groth16 zero-knowledge proofs on BN254
  • ML-KEM-768 post-quantum cryptography
  • Feldman VSS distributed key generation
  • A complete slashing engine

All built from scratch with zero production unwrap() calls and #![forbid(unsafe_code)] enforced across all crates.

Critically, this project requires extending Omnia's existing settlement-agnostic architecture with a new Filecoin adapter. The team has already successfully implemented two settlement adapters (Ethereum via Alloy with live RPC integration, and Celestia with real HTTP RPC integration for blob submission and Merkle inclusion verification). Adding a Filecoin adapter follows the exact same SettlementAdapter trait pattern, dramatically reducing implementation risk. The existing OmniaRollup.sol Solidity verifier contract on Ethereum (using BN254 precompiles) can be adapted for Filecoin's FEVM with minimal modifications, as both chains support the same EVM precompiles.

The team's existing work on the Physical Domain Shard (append-only provenance log with BLAKE3 hash-chain integrity, CRDT-friendly ownership tracking, and ZK query capabilities) provides the foundation for the provenance-to-storage pipeline. The provenance data structures are already defined; the integration work is primarily about connecting existing outputs to Filecoin's storage APIs and serializing data in CAR format.

Team Code Repositories


Additional Information

How did you learn about the Open Grants Program? Through research into Web3 grant programs aligned with Omnia Protocol's settlement-agnostic architecture. Filecoin's focus on durable decentralized storage makes it a natural integration target for Omnia's provenance system.

Additional context: The Omnia Protocol operates under the CC0 1.0 Universal license — the most permissive open-source license available, dedicating all code to the public domain. This means the Filecoin community and any other party can use, modify, and distribute the integration code without restriction.

The project maintains an active bug bounty program ranging from $100 to $50,000 per finding, providing ongoing security validation. A three-node BFT testnet has been validated over real libp2p connections, and 7 high-priority audit findings have already been remediated.

The project's commitment to radical transparency includes a published stub inventory that explicitly lists all incomplete implementations, and every claim in the README is traceable to a specific repository file, benchmark, or API response.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions