Mirrored from filpgf.io — ProPGF Batch 3 (Karma program 1479, application 6a31e330d747b346a0b8a344, status: pending). Contact details redacted; canonical application lives on filpgf.io. 1.1 Project Name Velic 1.2 Project Github https://github.com/justmert/velic 1.3 Project Website https://velic.app 1.4 Team Lead/Point of Contact Mert Köklü - Cofounder - YK Labs, [redacted], TG:@mertkklu 1.5 Category [ "RFP 1 - Customer-facing products built on Filecoin" ] 1.6 Open Source Status Fully Open Source 2.1 Project Summary **Velic** is a SaaS web application that stores professional video master files on the Filecoin Onchain Cloud and gives each customer continuous, independent, on-chain proof that every master remains present and bit-for-bit intact. That assurance comes from Proof of Data Possession (PDP), a cryptographic check the network performs on a recurring schedule and publishes on-chain, so anyone can re-verify it without trusting us. Velic is sold, priced, and supported as our own product: customers sign in, upload masters, read an auditor-ready preservation dashboard, download a certificate of continuous preservation, and restore the original file on demand, while Filecoin, tokens, and wallets stay hidden. The gap it closes is that conventional archives such as LTO tape, cloud cold storage, and digital-preservation suites rely on self-attested integrity, where the party that stores the data also vouches for it, whereas Velic surfaces proof that any third party can check independently. Because every stored master is a paid Filecoin Warm Storage deal settled in the USDFC stablecoin through Filecoin Pay, fiat media-archive budgets become recurring, paid usage of the network. This serves both the storage providers, who earn proof-gated revenue for large, long-lived datasets, and the studios, libraries, estates, and archives, which become paying Filecoin users without ever touching a wallet or token. App: https://velic.app Docs: https://docs.velic.app Pilot Video: **Overview** *A master* is the authoritative, highest-quality source file from which every distribution copy of a film, show, or recording is made. It is business-critical and is often contractually required to be retained intact for decades. Velic treats it as a long-lived asset that must be provably preserved, and it makes that proof both independent and public, so the customer never has to trust the operator's word. The customer experience is an ordinary SaaS one: create a workspace, upload a master, browse a library, watch an auditor-ready proof dashboard, export a certificate, restore the original on demand, and pay a normal USD invoice, while everything related to Filecoin stays hidden on the operator side. The defensible core is not storage on Filecoin, which is commoditising across many providers on the same substrate, but the productised, auditor-ready proof-of-preservation experience paired with a focused media go-to-market. **The Problem and the Opportunity** Masters today live on LTO tape, in cloud cold storage such as Amazon Glacier, or inside digital-preservation suites such as Preservica and Arkivum. Those suites do check data integrity and issue proof reports, but that proof is self-attested: the custodian's own system asserts the bytes are intact. There is no continuous, independent, third-party-verifiable proof that a specific master is present and bit-in …[truncated] 2.2 Who does this work support? [ "Storage Providers" ] 2.3 Total Funding Requested (USD) 165000 2.4 Milestones & Budget [ { "title": "Milestone 1: Mainnet Deployment, Hardening, and Security", "description": "This milestone takes the production service live on Filecoin mainnet and hardens it.\n\nDeliverables:\n- Deploy the production service to Filecoin mainnet, bringing the storage, proof, and settlement path live on mainnet with a funded operator.\n- Deepen observability and alerting on proof gaps and rail-buffer depletion, and strengthen the deployment and release pipeline.\n- Complete a security review and hardening of the application and the treasury and custody layer.\n- Finalise the operator-side USDFC entity and jurisdiction handling for growth.\n\nKPI / Growth Target:\n- ≥ 1 TB of paid FWSS storage\n- Across ≥ 10 masters on mainnet (data onboarded)\n- Continuous daily on-chain PDP proofs across every stored master.\n- Recurring USDFC settlement on mainnet, verifiable on the Filecoin Pay explorer (paid-deal revenue / on-chain economic activity).\n- At least 1 named reference customer has masters stored on mainnet as paid FWSS deals\n \nProduct traction: \n- ≥ 50 registered accounts;\n- ≥ 30% of sign-ups activate by uploading their first master.", "dueDate": "2026-08-17", "fundingRequested": "65000", "completionCriteria": "The production service is deployed and running reliably on Filecoin mainnet, with the storage, proof, and settlement path live under a funded operator, observability and alerting active on proof gaps and rail-buffer depletion, and the deployment and release pipeline strengthened. At least 1 TiB of paid FWSS storage is under management across at least 10 master datasets, each held in at least two independent copies with continuous daily on-chain possession proofs across every stored master, all independently verifiable on Filecoin block explorers such as Beryx and Filfox. At least 1 named reference customer has masters stored on mainnet as paid FWSS deals. A full-master restore reproduces the original byte-identically, confirmed by a matching SHA-256 hash. Recurring USDFC settlement runs on mainnet, verifiable on the Filecoin Pay explorer. The security review and hardening of the application and the treasury and custody layer are complete with findings resolved or triaged, and the operator-side USDFC entity and jurisdiction handling is finalised. At least 50 accounts are registered and at least 30% of sign-ups have activated by uploading their first master." }, { "title": "Milestone 2: Customer Growth and Public Verification", "description": "The paying customer base is grown with additional named reference customers, supported by a public way for any auditor or third party to verify a stored master independently.\n\nDeliverables:\n- A public, no-login verify-it-yourself page where any third party can independently re-check a stored master's on-chain proofs and export per-asset proof, without ou …[truncated] 3.1 Impact pathway Output: A hardened, scaled production Velic on mainnet, with a public verify-it-yourself page for independent third-party verification; additional named customers' video masters stored as paid FWSS deals under continuous on-chain PDP; and growth in recurring, fiat-funded, USDFC-settled storage. Outcome: Fiat media-archive budget, paid today to tape vendors and cloud archives, is converted into recurring, paid, on-chain Filecoin storage deals settled in USDFC. More named media-archive clients become paying Filecoin users. Storage providers earn proof-gated revenue for storing and serving large, long-lived masters. Auditors and insurers receive independently verifiable preservation evidence that a self-attested incumbent cannot provide. Impact: This advances Filecoin's 2026 shift from supply to paid demand. It grows recurring paid-deal revenue, a direct contribution to Objective 1; paying on-chain clients in a high-credibility vertical, a direct contribution to Objective 3; and additional recurring on-chain economic activity that strengthens network economics, an indirect contribution to Objective 2. Each referenceable, independently verifiable customer outcome feeds the credibility flywheel the strategy describes, because a visible paid success in media preservation makes the next library, estate, or studio easier to convert. 3.2 Verification metrics | Metric | Data source | How it's measured | Target (end of grant) | | --- | --- | --- | --- | | Paid FWSS storage on mainnet (TiB) | FWSS datasets and payment rails bound to Velic's operator address, read via FWSS and Filecoin explorers such as Beryx and Filfox | Sum of stored piece sizes across datasets on rails funded by Velic's operator | ≥ 10 TiB across ≥ 100 master datasets on mainnet | | Active paying client(s) | Internal billing records cross-checked against on-chain rails | Count of paying customers whose USD invoices fund live mainnet FWSS datasets | ≥ 4 paying customers storing >1 TiB | | Paid-deal settlement in USDFC via Filecoin Pay | `FilecoinPayV1` settlement events on the Filecoin Pay explorer | Cumulative USDFC settled to providers for customer datasets, traceable on-chain | Recurring USDFC settlement on mainnet, growing as the paying base grows, publicly verifiable on the Filecoin Pay explorer | | Continuity of on-chain proofs (`PossessionProven`) | `PDPVerifier` on-chain events, via a PDP explorer or Beryx | Presence and continuity of daily proof events across all customer datasets | Continuous daily proofs across every stored master, with no gaps beyond the daily cadence | 3.3 References The people below can vouch for our work. These are ecosystem relationships from our project Walsy (MVP) - a decentralized video-streaming and storage infrastructure built on Walrus and Sui, developed during a Walrus grant process. - Carter Morgan is Developer Relations at Mysten Labs. You can reach him at [redacted] or https://x.com/cartermorgandev. - Daniel Daun is Strategic Adoption and Programs Lead at Walrus. He engaged with the YK Labs team during the Walsy grant process. You can reach him at [redacted] or https://www.linkedin.com/in/daniel-daun-b535345. Besides, our work is fully open and independently verifiable: the complete source is public at github.com/justmert/velic, the product is live at velic.app, and every preservation proof can be checked directly on-chain. We're glad to arrange references on request. 4.1 Monthly Operating Burn [ "$10-$100K (small team)" ] 4.2 What % of total team monthly burn depends on this grant? %40 4.3 If this grant is not awarded, what happens? If the grant is not awarded, Velic continues - the product is already live and open-source, and we are committed to it independently. What changes is pace and reach. Without the grant, we would proceed on a slower, self-funded timeline: hardening for production scale, security review, and the auditor-grade evidence layer (public verify-it-yourself page, signed certificates) would take significantly longer, and we would onboard paying customers more gradually, constrained by a leaner runway. The grant's role is acceleration, not survival. It lets us harden the live service, complete the security and treasury/jurisdiction work, and onboard named paying customers onto paid Filecoin storage within six months instead of stretching that over a much longer period, bringing real, paid on-chain demand to the network sooner. We would also continue exploring the broader Filecoin ecosystem for the right design partners regardless of the outcome. 4.4 Core Team YK Labs has delivered projects across more than 20 blockchain protocols, building web applictions, developer tooling, SDKs, infrastructure, online IDEs, editor extension, and analytics engines. Our work spans a wide range of ecosystems, including Stellar, NEAR, Arbitrum, IOTA, Hedera, Cardano, and the Internet Computer, with a consistent record of shipping production-grade tools that. Tolga Yaycı, Co-founder and Software Engineer GitHub: https://github.com/tolgayayci · LinkedIn: https://www.linkedin.com/in/tolgayayci/ · Telegram: @tolga0x Software engineer with over four years of blockchain development experience, focused on developer tooling, infrastructure, and frontend systems. Holds a Bachelor's degree in Computer Science, with a track record of delivering funded projects across multiple ecosystems. Selected work: - NearPlay, online IDE for NEAR smart contracts: https://nearplay.app/ - Wizard, online IDE for Arbitrum Stylus smart contracts: https://thewizard.app/ - IOTA Playground, online IDE for IOTA Move smart contracts: https://iotaplay.app/ - Hedera VS Code Extension, toolkit for building on Hedera: https://marketplace.visualstudio.com/items?itemName=tolgayayci.hedera-vscode - Sora, desktop app for the Stellar network, funded and delivered across two grant rounds: https://github.com/tolgayayci/sora - ICP Dashboard, desktop app for the Internet Computer: https://github.com/tolgayayci/dfx-dashboard Mert Köklü, Co-founder and Software Engineer GitHub: https://github.com/justmert · LinkedIn: https://www.linkedin.com/in/mertkoklu · Telegram: @mertkklu Holds a degree in Computer Engineering and previously led an engineering team at an NVIDIA partner company. Has received and delivered grants from Arbitrum, Cardano, Stellar, and other ecosystems, with deep experience in SDK architecture, API design, and backend systems. Selected work: - SoroReveal, decompiles Soroban smart contracts back to readable source: https://sororeveal.com/ - Timeboost Analytics, analytics engine for Arbitrum's Timeboost express-lane auctions: https://github.com/justmert/timeboost-analytics - Arbitrum Python SDK, the leading community Python SDK for Arbitrum: https://github.com/justmert/arbitrum-python-sdk - Koios Rust SDK, a published Apache-2.0 typed async Rust SDK for the Koios Cardano API, with a typed error model and full docs: https://github.com/justmert/koios.rs - ICP Agent Kit, SDK for natural-language interaction with the Internet Computer: https://github.com/justmert/icp-agent-kit Together, this background in smart contracts, developer tooling, SDKs, and on-chain infrastructure is the skill set required to build and ship verifiable, developer-ready infrastructure on Filecoin. 4.5 Has your team received a ProPGF grant or funding from PLFIF before? [ "No" ] 5.1 Key risks & dependencies - Filecoin Onchain Cloud contract maturity is the primary technical risk. FWSS and PDP are recent and still beta and the payment rails are young, but the components are operational and the product already runs on them; we mitigate the immaturity the way the live system is built, resolving contract addresses from the SDK rather than hardcoding, pinning versions, treating the chain as the source of truth, and running behind monitoring with conservative limits. - Large masters and the per-piece limit. Video masters far exceed the per-piece upload ceiling, already solved by chunking below the roughly 1 GiB per-piece maximum and restoring by direct provider retrieval, with no content-delivery dependency and the path verified byte-identical. - Reliance on third-party explorers. Historical proof reads depend on external explorers, so we cache proof history locally and read live status directly from the on-chain verifier, avoiding a hard dependency on any single indexer. Anything else you want to share that we didn't ask? Roadmap beyond this grant. The following capabilities are deliberately out of this grant and sit on a clear roadmap. Each is a natural extension of the current architecture, and none is needed to prove the funded thesis: - Protocol-enforced retention-lock through an on-chain time-lock, which requires a contract audit. - Integration beneath existing media-asset managers, plus an S3-compatible ingest path for bulk libraries. - Region and sovereign placement for EU, public-sector, and heritage buyers. - A full provenance product with active C2PA signing. - Erasure-coded durability and premium service tiers. - Proxy preview (stream) Objective 1 Direct Objective 2 Indirect Objective 3 Direct Open Source Context The entire codebase is released under Apache-2.0 as a public good: the web application, the backend services, the Filecoin integration adapter, and the documentation site. Velic is open-sourced as a working product, not packaged or resold as a reusable SDK, library, or developer toolkit. That boundary is the lane of the pods, the platform-building teams within the Filecoin Onchain Cloud, and one we deliberately avoid. Open-sourcing a complete, independently verifiable preservation product gives the ecosystem a reference implementation for converting fiat storage demand into paid, on-chain Filecoin deals. It also lets any customer, auditor, or competitor self-host the product and inspect exactly how the proofs they rely on are produced, which is the whole point of a service built on verifiable claims.