Integration Grants Application ’25: DeepFamily Decentralized Digital Family Tree
Application Introduction
DeepFamily is a decentralized family-tree protocol for families, historians, and cultural institutions worldwide. It aims to move family records away from fragmented, centralized platforms and into verifiable, collaborative, and permanent on-chain infrastructure. Traditional genealogy services rely on closed databases, making provenance hard to verify, limiting cross-generational collaboration, and offering weak privacy guarantees. DeepFamily uses zero-knowledge proofs to keep parent-child submissions private, while community endorsements and incentive mechanisms maintain a trustworthy set of coexisting versions. This creates a public-good use case in the Conflux ecosystem that preserves global cultural memory. The project positions itself as open infrastructure with no stable revenue stream today; all requested funding will be dedicated to protocol upgrades, historical data curation, and community outreach. The protocol follows a dual-layer value system: a privacy layer for private tree construction and cross-border collaboration, and an asset layer that turns endorsed versions into NFTs, augments them with “Person Wiki” pages, and maintains evolving StoryChunk records to reward ongoing contributions. DeepFamily is expected to generate sticky on-chain records, long-tail NFT activity, and opportunities for culture-oriented DApps within Conflux. Its competitive edge lies in three aspects: the Groth16 + Poseidon privacy design, community-driven governance across multiple coexisting versions, and the built-in story sharding and sealing mechanism for cultural assets. The GitHub repository, demo endpoints, and documentation are already public.
- Project Webpage: https://deepfamily.org
- X: DeepFamilyLabs
- Conflux eSpace Grant Wallet: 0x0F90933447C9fd612B9380dE8e2E1fB9DDF5a279
Technical Introduction
DeepFamily’s overarching goal is to deliver an on-chain family system that supports “private submissions, public verification, and continuous governance.” The project already ships initial zero-knowledge circuits, hash commitment logic, the DEEP incentive economy, multi-version management for personas, story sharding, and a full-featured front-end toolchain. Today’s ecosystem still lacks a genealogy solution that balances privacy with public memory. DeepFamily addresses the problem by combining Poseidon commitments with Groth16 proofs so that contributors can confirm relationships without exposing personal data. Documentation covers the contract stack, ZK architecture, front-end structure, and historical data import workflows, with terminology and procedures clearly defined. The current feature map centers on persona submissions, parent linkage checks, community endorsements, and reward distribution, while extending to the asset layer for the Person Wiki, NFTs, StoryChunk lifecycle management, and supporting pagination queries.
Technical Proposal
-
Functional Overview: The protocol operates on a dual-layer value system. The privacy layer governs zero-knowledge submissions, and the asset layer handles endorsed data as NFTs, Person Wiki entries, and sealed story shards.
- Privacy Layer: Persona onboarding combines Groth16 proofs with Poseidon/keccak double hashing, ensuring no plaintext is revealed during submissions.
- Asset Layer: Once a version is endorsed, it can mint an NFT, present a full biography via the Person Wiki, and capture supplemental details in ≤2 KB StoryChunks that can later be sealed for immutability.
- Core Components: DeepFamily core contract, DeepFamilyToken incentive module, PersonHashVerifier and NamePoseidonVerifier circuits, the React front end, and historical data scripting utilities.
- Legal / Licensing: Distributed under the MIT License. Historical figures are sourced from public-domain materials. The project will comply with Conflux’s No-Sale rule and additional governance requirements.
Total Budget
Requested grant amount: 18,000 USDT (or equivalent CFX). Because the protocol is a public-good infrastructure project, day-to-day operations depend entirely on external support. The grant will be deployed in phases:
- Protocol and ZK integration enhancements: 6,000
- Front-end UX and multilingual improvements: 4,000
- Cultural data expansion and community programs: 3,000
- Testing, DevOps, and infrastructure: 3,000
Development Roadmap
- Milestone 1 (Months 1–2): Ship a Conflux eSpace public test deployment, refresh protocol interface docs, and publish the testnet demo endpoint and technical handbook. Payment: 6,000. Acceptance criteria: latest deployment addresses and interaction scripts are public; interface docs are synced to the knowledge base.
- Milestone 2 (Months 3–4): Release a usable front-end demo supporting wallet login, tree exploration, endorsement flows, and the Person Wiki, accompanied by a user feedback report. Payment: 7,000. Acceptance criteria: public demo available for external testing, with an operations guide and feedback summary.
- Milestone 3 (Months 5–6): Launch multilingual UI, publish partner integration APIs, and kick off a community growth initiative. Payment: 5,000. Acceptance criteria: localized interface live, API documentation published, first-wave community activities and channel roadmap announced.
Team
- HappyCode – Full-stack engineer (Solidity, ZK circuits, Front)
- GitHub Repos: https://github.com/deepfamilylabs/DeepFamily
Terms of Use
- I have read and understood the Conflux Grants Ecosystem Overview.
- I have read about and understood that the Conflux Technical Grants are subject to a No-Sale rule.
- I agree to provide KYC information to the Conflux Foundation for the sake of overall ecosystem security.
- I understand that I will be required to follow public grant reporting requirements.