Vaultra

Mirrored from filpgf.io — ProPGF Batch 3 (Karma program 1479, application 6a31cf9cf2d3da25b237fc1e, status: pending). Contact details redacted; canonical application lives on filpgf.io. 1.1 Project Name Vaultra 1.2 Project Github https://github.com/Izi-27/Vaultra 1.4 Team Lead/Point of Contact Name: Olaoluwa Emmanuel Oyetibo Title: Lead Developer Telegram: @mike_1456 1.5 Category [ "RFP 1 - Customer-facing products built on Filecoin" ] 1.6 Open Source Status Fully Open Source 2.1 Project Summary **Vaultra** will accomplish the creation of a production-ready, cross-platform desktop backup application that enables developers, SMBs, and DAOs to schedule automated, encrypted folder backups to Filecoin's Warm Storage Service. The project supports application builders and end-users by providing a simple, non-technical onramp to Filecoin storage, eliminating the need for custom scripting or blockchain expertise. It addresses the specific gap of missing customer-facing tooling that converts real-world backup demand into paid, onchain storage deals. By offering client-side AES-256 encryption, cron-based scheduling, a graphical user interface for Windows, Mac, and Linux, and a public metrics dashboard, Vaultra lowers the barrier to Filecoin adoption and creates a repeatable reference implementation for backup applications. This directly supports Filecoin's 2026 Network: (Driving Paid Onchain Deals), (Scaling Flagship Client Adoption) by turning everyday backup needs into sustainable, verifiable, onchain storage revenue. 2.2 Who does this work support? [ "Pods", "Onramps", "Storage Providers", "Application Builders", "Application Users", "Network Infrastructure" ] 2.3 Total Funding Requested (USD) $35000 2.4 Milestones & Budget [ { "title": "Vaultra Core Engine & Command-Line Interface", "description": "Build the foundational backup and restore engine that interfaces with Filecoin's Warm Storage Service API. Develop the complete CLI tool with all commands including backup, restore, list, status, and cancel. Implement cron-based scheduling for automated recurring backups. Create YAML/JSON configuration management for backup sets, exclusion rules, and schedules. Add structured logging with rotation. Write comprehensive Jest unit tests achieving 80% line coverage on core modules.", "dueDate": "2026-07-14", "fundingRequested": "$10000", "completionCriteria": "All seven deliverables signed off with passing test suite. Backup engine successfully uploads a 1GB folder to Warm Storage. Restore engine returns data byte-for-byte identical to original. All CLI commands function with --help flag. Scheduler triggers backups at specified times. Config file loads and validates. Logs written to ~/.vaultra/logs/ with rotation. Jest test suite achieves 80% line coverage." }, { "title": "Vaultra Desktop GUI Application", "description": "Build a cross-platform desktop application using Tauri that runs on Windows, macOS, and Linux. Develop a step-by-step backup wizard that guides users through folder selection, schedule configuration, and encryption setup — all completable in under 5 minutes. Create a restore interface with backup history browsing and progress bars. Build a status dashboard showing last backup, next backup, storage used, and deal count with real-time updates. Add settings panel for API key, encryption key, and notification preferences. Implement system tray for background operation. Add desktop notifications for backup success or failure events.", "dueDate": "2026-08-11", "fundingRequested": "$10000", "completionCriteria": "All seven deliverables signed off and application runs on all three platforms (Windows, Mac, Linux). Non-technical user can complete a full backup setup in under 5 minutes. Restore completes with visible progress bar. Dashboard updates in real time. Settings persist across application restarts. Application runs in system tray without main window. Desktop notifications appear on backup completion." }, { "title": "Vaultra Security & Production Hardening", "description": "Implement client-side AES-256-GCM encryption that encrypts all data before upload, with the user holding the encryption key and it never leaving their machine. Build key management allowing user-provided keys or generated passphrases. Create API key isolation with separate keys per backup set so revocation doesn't affect other sets. Add exponential backoff with jitter for network resilience up to 5 retries. Implement configurable bandwidth throttling. Add SHA-256 integrity verification with checksums generated before upload and verified aft …[truncated] 3.1 Impact pathway **Output:** **Vaultra** produces a fully functional, open-source desktop backup application with CLI, GUI, encryption, scheduling, and metrics dashboard — all integrated with Filecoin's Warm Storage Service. The project also produces documentation, video tutorials, beta user feedback, and a public metrics dashboard. **Outcome:** Non-technical users (SMBs, DAOs, developers, researchers) can now easily schedule automated, encrypted backups to Filecoin without writing custom code or understanding blockchain. Storage Providers receive recurring, predictable paid deal flow. The ecosystem gains a measurable understanding of backup demand through the metrics dashboard. Application builders gain a reference implementation they can fork and extend. **Impact:** Everyday real-world backup demand is converted into paid, onchain Filecoin deals at scale. This directly drives Network Objective #1 (Paid Onchain Deals) by creating a new category of recurring storage demand. It strengthens Network Objective #2 (Network Profitability) by providing Storage Providers with sustainable, predictable revenue that reduces reliance on block rewards. And it advances Network Objective #3 (Flagship Client Adoption) by onboarding entirely new categories of paying customers — SMBs, DAOs, researchers, and AI teams — who previously could not use Filecoin due to technical barriers. **Long-term systemic change:** **Vaultra** establishes a repeatable pattern for backup applications on Filecoin. As more teams fork and build upon the codebase, a whole ecosystem of backup tools will emerge, creating durable, recurring demand that makes Filecoin indispensable infrastructure for data durability — not just speculative storage. 3.2 Verification metrics | Metric | Data source | How it's measured | Target (end of grant) | | Paid onchain deals created | Filecoin blockchain via Lotus RPC or FilFox API | Query the number of deals attributed to Vaultra user activity | 50+ paid deals. | Gigabytes stored on Filecoin | Warm Storage Service API combined with Filecoin blockchain data | Summing total data sizes of Warm Storage deals initiated by Vaultra users | 500+ GB stored | Active beta users | Vaultra usage logs and opt-in telemetry | Counting unique users who complete at least one full backup and restore cycle | 10+ active users. | Successful restore rate | Vaultra integrity verification logs | Calculating the percentage of restores where SHA-256 checksums match original files | 100% successful restores | Cross-platform compatibility | CI test matrix on GitHub Actions | Automated tests passing on Windows, macOS, and Linux | 100% test pass rate | GitHub adoption | GitHub API | Counting stars, forks, and clones | 50+ stars 3.3 References 1. Blockchain Developer / Technical Collaborator A developer I collaborated with on Fractal Protocol where I led product strategy, managed the full lifecycle across 3 development sprints, and delivered working cross-chain smart contracts and an interactive frontend that ranked Top 3 among 93 global projects. Can vouch for my technical project management, agile execution, and ability to ship on time. 2. Hackathon Judge / Mentor / Investor An evaluator from hackathon competitions where my projects ranked Top 3 among 93 global projects and won prize money. Can confirm my ability to articulate technical vision, synthesize feedback, and deliver projects that win recognition. 3. Web3 Development Peer A technical collaborator from previous blockchain projects who can validate my ability to build smart contracts, decentralized applications, and full-stack Web3 systems. 4.1 Monthly Operating Burn [ "< $10K (basic solo operation or part-time team)" ] 4.2 What % of total team monthly burn depends on this grant? 100% 4.3 If this grant is not awarded, what happens? If this grant is not awarded, I will scale back the scope and timeline of Vaultra significantly. I would build a minimal command-line only version in my spare time over 6 to 12 months, likely without the desktop GUI, advanced security hardening, or metrics dashboard. The full vision of a production-ready, cross-platform backup suite accessible to non-technical users would be delayed or potentially never realized. However, I remain committed to contributing to the Filecoin ecosystem and would continue building in a reduced capacity. The grant accelerates what would otherwise be a slow, part-time effort into a focused 14-week delivery that maximizes immediate impact on Filecoin's 2026 objectives. 4.4 Core Team Olaoluwa Emmanuel Oyetibo — Lead Developer Role: Full-stack development of Vaultra including CLI, desktop GUI, encryption layer, API integrations, and metrics dashboard. Relevant Experience: · Full-Stack Developer at OrangeServers — built hosting management tools with React, Next.js, and backend APIs. · AI Evaluator at Parsewave — designed real-world engineering challenges for training frontier AI models. · 1st place hackathon winner for Sprout (generational savings platform) and 2nd place for Med-Map (AI healthcare solution). · Built blockchain payment gateways (Direct) and cryptocurrency tracking platforms (CryptoStats). · Technical Skills: TypeScript, Node.js, React, Next.js, Solana, Web3.js, Python, LangChain, Git/GitHub. 4.5 Has your team received a ProPGF grant or funding from PLFIF before? [ "No" ] 5.1 Key risks & dependencies **External Dependencies** **Warm Storage API changes**. The primary external dependency is the Filecoin Warm Storage Service API. If it undergoes breaking changes during development, milestones could be delayed. Mitigation: abstract all API calls behind an adapter layer and monitor the changelog weekly. **Network congestion or gas spikes.** Filecoin network conditions could affect deal creation costs or speed. Mitigation: build retry logic with exponential backoff and allow flexible deal parameters. **Beta user participation.** Recruiting 10–15 beta users depends on community engagement. Mitigation: leverage the Filecoin Slack (#fil-builders has 5,000+ members) and start recruitment early. **Technical Risks** **Cross-platform compatibility.** Desktop apps behave differently on Windows, Mac, and Linux — file systems, permissions, and UI rendering vary. Mitigation: test on all three platforms after every commit using CI with an OS test matrix. Use Tauri which provides consistent cross-platform behavior. **Encryption performance.** Very large folders (100GB+) could slow down encryption. Mitigation: stream encryption in chunks rather than loading entire files into memory. Use native Node.js crypto module which is highly optimized. **Windows scheduling.** Cron-style scheduling works differently on Windows. Mitigation: use node-schedule-win32 to integrate with native Windows Task Scheduler. **User key loss.** If a user loses their encryption key, data cannot be recovered. Mitigation: clear warnings during setup, optional key hints (non-recoverable), and educational documentation. **Team Risks** **Solo developer capacity.** As a solo developer, illness or personal emergency could delay delivery. Mitigation: build a small buffer into the schedule, deliver early where possible, and communicate proactively with the grant committee. **Scope creep.** The temptation to add features beyond milestones could derail the timeline. Mitigation: strict scope control with grant committee approval required for any significant additions. Any feedback you have on the application process? This application is comprehensive, milestone-based, has clear alignment with 2026 strategy Anything else you want to share that we didn't ask? First, I'm in this for the long haul. Vaultra isn't just a grant project for me. I plan to maintain it actively after the grant ends. Bug fixes, community support, and feature updates will continue as long as people are using it. I see this as a long-term contribution to the ecosystem, not a one-off delivery. Second, everything will be open source. The full codebase, documentation, and brand assets will be released under MIT license. No proprietary components, no closed-source dependencies, no paid tiers. The ecosystem can fork, extend, and build on Vaultra however they want. Third, I designed Vaultra specifically around the 2026 strategy. Every feature, automated scheduling, encryption, cross-platform GUI exists to drive paid deals and onboard new users. I'm not building a generic backup tool; I'm building a Filecoin-native tool that moves the network's objectives forward. Fourth, I'm actively engaged with the community. I'm in the Filecoin Slack, following FIP discussions, and watching the #fil-builders channel. I want Vaultra to evolve with feedback from real users and ecosystem stakeholders. Fifth, I'm ready to start immediately. The 14-week timeline is aggressive but achievable. I've already scoped the work, chosen the stack, and planned the milestones. Upon approval, I can begin development right away. Contributing to Core Infrastructure? Vaultra is a customer-facing desktop backup application that enables developers, SMBs, and DAOs to schedule automated, encrypted folder backups to Filecoin's Warm Storage Service. It directly converts real-world storage demand into paid, onchain deals by making Filecoin storage accessible to non-technical users. The product includes a cross-platform GUI (Windows, Mac, Linux) and a CLI for automation, with client-side AES-256 encryption, scheduling, and a public metrics dashboard. Vaultra lowers the barrier to entry for Filecoin adoption and creates a repeatable integration pattern for backup applications — directly supporting Network Objective #1 (Driving Paid Onchain Deals) and #3 (Scaling Flagship Client Adoption). All code will be open-sourced under MIT or Apache-2.0 license. Objective 1 Direct Objective 2 Indirect Objective 3 Direct