Work
Lab productPrivate alpha · Unaudited

Lab 03 / Crypto · Self-custody · Continuity

Continuity rules
without a custodian.

Mortal Vault is a self-custodial continuity vault: an owner checks in, inactivity opens a delayed beneficiary claim, and owner activity can still cancel it before execution.

EngagementMaydaLabs lab product
StatusPrivate alpha · Contracts unaudited
ScopeSolidity · Hardhat · Next.js · EVM testnets
OwnershipMaydaLabs-owned, no public release
Stack

Context

Bitcoin and crypto self-custody has a hard human problem: what happens to funds when the owner can no longer act? Mortal Vault explores a continuity lifecycle with no administrator, no custody service, and no emergency override — the rules live in the contract, and the risks stay visible.

Constraint

Make a high-consequence self-custody lifecycle understandable without hiding the irreversible risks or implying legal and security guarantees the product cannot make.

MaydaLabs' exact scope

  • The continuity model: owner check-ins, inactivity windows, delayed claims
  • Solidity contract lifecycle and its bounded state machine
  • Owner and beneficiary interfaces in Next.js, with network, contract, and transaction state exposed
  • Event-backed activity history and deterministic reminder planning
  • Security work treated as a release gate: threat model, adversarial tests, fuzzing, invariants, static analysis, balance caps

What was built

  • A bounded contract lifecycle: create, fund, update, check in, withdraw, close, request a claim, cancel it through owner activity, and execute only after both time gates
  • Separated owner control and a shareable beneficiary claim path
  • Contract events parsed into bounded activity views that survive refreshes
  • Adversarial, fuzz, invariant, and static-analysis gates inside the repository
  • Testnet-first network and release configuration with explicit release blockers

Verifiable evidence

The repository is private; the demo capture below shows the working owner-facing surface from the local application. Wallet connection and chain actions stay outside this public frame. Deeper evidence — the contract lifecycle, tests, and threat model — can be walked through in a conversation.

Current status

Private alpha in active development. Mainnet remains blocked by independent review, external wallet exercises, monitoring, and demonstrated demand.

Ownership

A MaydaLabs-owned lab product. Mehmet owns the product definition and implementation, with every security and release claim kept behind explicit evidence gates.

What this is not

  • Contracts are unaudited and must not hold meaningful funds.
  • No administrator, custody service, legal determination, or emergency override exists.
  • This is not legal inheritance, probate, identity verification, or key recovery.
  • No mainnet claim is made before independent review and the other release gates pass.

Building a trust-critical product?

Make the state explicit. Make the risk legible.