Skip to content

Open Grant Proposal: Legacy Vault — ZK Digital Estate Planning & Decentralized Archive #2127

Description

@Ahmetcemil1

Open Grant Proposal: Legacy Vault

Project Name: Legacy Vault

Proposal Category: FVM

Individual or Entity Name: Individual

Proposer: Ahmetcemil1

Project Repo(s): https://github.com/Ahmetcemil1/legacy-vault

(Optional) Filecoin ecosystem affiliations: None

(Optional) Technical Sponsor: None

Do you agree to open source all work you do on behalf of this RFP under the MIT/Apache-2 dual-license?: Yes

Project Summary

Legacy Vault is a client-side zero-knowledge digital estate planning and multi-signature inheritance platform. It bridges the gap between digital asset custody and inheritance law, allowing users to securely store sensitive digital credentials, passwords, medical records, and video messages, which are only released to designated beneficiaries upon death validation via a decentralized, multi-signature consensus protocol or certified death claim administrative verification.

The project is fully built with 100% cryptographic parity across its React Web and Flutter Mobile clients using 2048-bit RSA-OAEP asymmetric keypairs and Shamir's Secret Sharing (SSS) over Galois Field GF(256). We are requesting funding to integrate decentralized archiving and backup layers utilizing IPFS and Filecoin.

Impact

Legacy Vault addresses the "single point of failure" risk inherent in current digital inheritance solutions, where centralized servers store unencrypted data or rely on insecure recovery mechanisms. By decentralizing this architecture, we eliminate censorship risks and ensure that user data remains under their sovereign control, protected from institutional failure or external interference.

Integrating this project into the Filecoin ecosystem provides a high-utility, security-focused use case for decentralized archives. Successfully implementing this will create a continuous stream of recurring transaction volume as users upload encrypted digital estate payloads. If we fail to establish this decentralized layer, users will remain trapped in centralized, vulnerable Web2 cloud solutions, which undermines the core mission of Web3 data sovereignty.

Success for Legacy Vault means establishing a professional, verifiable, and decentralized standard for digital estate management. This project will serve as a bridge, introducing security-conscious general users to the Filecoin network, thereby increasing the ecosystem's adoption rate through practical, real-world utility.

Outcomes

The final outcome will be a fully integrated Legacy Vault system where encrypted user archives are automatically pinned to IPFS and anchored on the Filecoin network.

  • Deliverables:
    1. Updated React Web and Flutter Mobile clients capable of direct IPFS/Filecoin uploads.
    2. Automated Filecoin storage deals for permanent archiving.
    3. Integrated CID retrieval within the recovery/heir dashboards.
  • Success Metrics:
    • Successful upload and retrieval of encrypted payloads (min. 10MB test objects).
    • Verification of CID persistence on the Filecoin network.
    • Seamless "one-click" archive retrieval for heirs using the existing multi-sig consensus flow.

Data Onboarding

Adoption, Reach, and Growth Strategies

Legacy Vault targets crypto asset holders, security-conscious individuals, and estate planners. We reach this audience through developer-focused communities (GitHub/Dev.to) and security-focused forums.

We intend to onboard our first 10 users through direct beta testing within the existing open-source community. The first 100 users will be onboarded via public launch and integration with existing Web3 estate planning forums. Our growth strategy relies on the platform’s "Zero-Knowledge" marketing—highlighting that even we (the developers) cannot access user data, which is a major selling point for our target demographic.

Development Roadmap

Milestone 1 — IPFS Dynamic Encryption & Upload Integration

  • Functionality: Update clients to encrypt and upload payloads directly to IPFS pinning services.
  • Team: 1 Developer (Lead Architect).
  • Timeframe: 4 weeks from project start.
  • Funding: $7,500 USD

Milestone 2 — Filecoin Decentralized Archiving & Backup Layer

  • Functionality: Implementation of automated Filecoin storage deals for permanent archiving and CID retrieval integration.
  • Team: 1 Developer.
  • Timeframe: 4 weeks after Milestone 1.
  • Funding: $7,500 USD

Total Budget Requested

| Milestone # | Description | Deliverables | Completion Date | Funding |
|===|===|===|===|===|
| 1 | IPFS Integration | Client-side IPFS upload logic | Month 1 | $7,500 |
| 2 | Filecoin Archiving | Filecoin storage deal automation | Month 2 | $7,500 |

Maintenance and Upgrade Plans

We plan to maintain Legacy Vault as a long-term open-source project. Post-grant, we will implement periodic updates to the cryptographic standards (e.g., migrating to post-quantum resistant signatures) and continue to optimize Filecoin storage deal costs for users. All updates will remain open-source under the MIT/Apache-2.0 dual license.

Relevant Experience

I have extensive experience in full-stack architecture (React/Flutter) and applied cryptography. I have successfully built the complete cryptographic parity framework for Legacy Vault, including the implementation of SSS over GF(256) and RSA-OAEP, ensuring it functions flawlessly across mobile and web environments.

Team code repositories

Additional Information

  • I learned about the Open Grants Program through Filecoin ecosystem documentation and the devgrants GitHub repository.
  • Email for contact: [ahmetcemil2000@gmail.com]
  • Note: This proposal is a resubmission/migration of PR Open Grant Application: Legacy Vault #2118, which received technical approval from @Tinsri027. I am submitting this as an Issue to align with the official grant review queue.

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