
π Memento Mori
Pass on crypto with on-chain trusts
Demo
About
The problem it solves # π Memento Mori ### What happens to your crypto when you die? Itβs tough to think about death, but itβs essential to plan for your future. Thats why were building Memento Mori: a concept in philosophy - a reminder that weβre all mortal, and will die. **Existing will and recovery options in crypto are flawed:** - Require using a centralized intermediary to send crypto to your heirs - Split your private keys across multiple people: creates a stalemate where heirs are incentivized to not share their part of the private key before another **We need a system that is structured like traditional trusts: something proven for nearly a thousand years.** - If person found still alive, ownership is kept - Funds not transferred to heirs, rather held in the trust - Person can configure how trust is used - not blindly giving money to hairs - ZK verification of what funds are used on - timed release of funds (like standard trust) ## How it Works 1. Trust funder creates trust - Submit information on beneficiary (name, password, how funds should be used, when can be claimed, proof of death requirement, etc) (βοΈ Name + PW are proofs w Hyli) 2. Trust funder shares trust link with Beneficiary - Beneficiary should keep trust link and secret password somewhere safe 3. Upon death, Beneficiary can claim funds - Log in w ZK Passport, verify identity (βοΈ using ZK Passport + Hyli) - Verify secret password (βοΈ compaired w prior proof w Hyli) - Can submit proof of death - Can then withdraw funds if all conditions met ### Sponsors - Hyli - ZKPassport ## Features - Trust fund setup with funds stored in the smart contract and custom set of programmable instructions for the will - Initiating social recovery using: - ZKPassport proofs to verify Beneficiary is who they say - Secret password previously generated by trust creator and given to the trust beneficiary on Hyli, Beneficiary name also stored in hash, compared with ZK Passport identity to authenticate beneficiary
How it's made
Challenges we ran into Devfolio - We could not add my team member Daniel!!! We are two people working on this project. Hyli - Some issues w setting things up on M1/M2 chip computers. Team was able to resolve promptly. - Testnet down. We were trying to deploy but had issues for some time. In end was not required to deploy there - could have been better communicated from team. - Testnet requires invite code for users - wasn't communicated well. ZK Passport <> Hyli - They use different proof types. Made using both together complex.