InheritVault - A Simple Timelock Inheritance Vault on Nervos CKB (Web MVP)

English CKB Development & Technical Discussion
,
1

Hello Nervos Community

I’m currently working on a project called InheritVault: a simple, non-custodial inheritance vault built on Nervos CKB.

The goal is to allow users to lock assets for future beneficiaries (children, family, etc.), with unlock conditions enforced directly on-chain.

I’m starting with a very small web-based MVP, and I’d really appreciate feedback from the community before expanding further.

This is the mvp link for checking it out: Click here

About Me
I am a Software Engineer with several years of experience building scalable applications across the stack. My core expertise lies in TypeScript, React, Node.js, and Python, but my recent focus has shifted toward the frontier of decentralized technology.

Leveraging my full-stack background, I’ve deeply immersed myself in the Nervos ecosystem, where I build at the intersection of performance and blockchain utility. I’m passionate about bridging the gap between traditional software excellence and the future of Web3

The Problem

Managing crypto inheritance is still a major challenge:

  • Most wallets don’t support inheritance flows

  • Users either:

    • share private keys (unsafe), or

    • rely on centralized custody (trust risk)

  • There is no simple way to lock assets for future access (e.g., “unlock when my child is 18”)

This creates a need for a simple, trust-minimized inheritance solution.

The Idea

InheritVault allows users to lock CKB in a vault that can only be unlocked by a beneficiary after a specified time.

Basic Flow

  1. User creates a vault

  2. Inputs:

    • Beneficiary address

    • Unlock time (timestamp / block height)

    • Amount

  3. Signs transaction

  4. Funds are locked on-chain

  5. After the unlock time → beneficiary can claim

Everything is enforced on-chain.
No custody. No backend holding keys.

Why CKB

CKB provides a strong foundation for this:

  • Cell model - Each vault is a programmable cell

  • Time-based constraints - Enables delayed unlock logic

  • Non-custodial design - Funds are controlled by scripts, not servers

This makes it suitable for long-term asset storage and inheritance use cases.

MVP Scope (Web App)

I’m intentionally keeping the first version very minimal:

Features

  • Create a vault (beneficiary + unlock time)

  • View vault details (locked amount, unlock time, status)

  • Withdraw after unlock (beneficiary only)

Out of Scope (for now)

  • Dead-man switch

  • Multi-beneficiary / multisig

  • Notifications

  • Identity integrations (.bit, DID)

  • Backend services

Tech Stack (MVP)

  • Frontend: React (TypeScript)

  • Blockchain: Nervos CKB

  • SDK: CCC (for transaction building & signing)

  • Chain Access: CKB RPC + Indexer

  • Storage: Client-side only

No backend, no custody.

Architecture (Current Approach)

  • Vaults are represented as CKB cells

  • Unlock conditions enforced by CKB rules

  • Transactions built client-side using CCC

  • Vault metadata stored locally (or derived from chain)

The goal is to keep the system simple, transparent, and trust-minimized.

Future Direction

If the MVP is validated, I plan to extend the project with:

  • Dead-man switch (heartbeat mechanism)

  • Multi-beneficiary vaults

  • Trust fund model (e.g., unlock at age milestones)

  • Notification system

  • Mobile app (React Native)

  • Optional backend for monitoring (non-custodial)

Open Questions

I would really appreciate feedback on the following:

Concept

  • Does inheritance / timelock vault make sense as a use case on CKB?

  • Would this be better as a standalone dApp or wallet feature?

Technical Design

  • Recommended approach for time-locked spending on CKB?

  • Is it better to:

    • use existing lock patterns

    • or write a custom script early on?

UX

  • How should beneficiaries discover a vault?

    • Direct sharing (tx hash / address)?

    • QR code?

    • Indexer lookup?

Architecture

  • Is a fully client-side MVP acceptable for a first version?

  • Any best practices for tracking vault cells efficiently?

Security

  • Any pitfalls to consider when designing inheritance systems on CKB?

Goal

The goal is to build a simple but practical MVP that demonstrates:

  • a real-world use case (inheritance / long-term storage)

  • effective use of the CKB cell model

  • a non-custodial architecture

If validated, I plan to develop this further and potentially apply for a grant.

Feedback Welcome

I’m still exploring the design and would really appreciate:

  • technical suggestions

  • architecture feedback

  • UX ideas

  • references to similar projects

All feedback is welcome

14 Likes
CKB Ecosystem Biweekly Update
2

The time capsule idea is great. Keep it up mate

2 Likes