CryptoLegacy: Privacy is Important for Recovery and Inheritance

CryptoLegacy securely stores your data locally, encrypts it on-chain, and ensures Beneficiaries and Guardians access info only when required.

We believe privacy is crucial for asset recovery and inheritance.

While it’s challenging to implement a fully private solution within an architecture where assets are approved from main wallets to the CryptoLegacy personal contract, we concluded it’s highly unlikely that Guardians or Beneficiaries will inspect the code or develop custom indexing tools.

Thus, sensitive data isn’t revealed prematurely in the UI, and asset information remains encrypted until the challenge timeout expires or the Guardian threshold (and optional Guardian timeout) is reached.

Key privacy points: • Names, Beneficiaries, Guardians, Recovery addresses, Asset holders (your wallets), ERC20 addresses, and Public encryption keys are stored locally in your browser. Backups are encrypted using your personal public encryption key and stored on-chain as transaction events in a separate contract. • Asset holders (your wallets) and ERC20 addresses are encrypted individually for each Beneficiary, Guardian, and Recovery address using their respective public encryption keys, then saved on-chain as transaction events in the CryptoLegacy contract. • We utilize MetaMask’s built-in encryption (eth-sig-util), employing robust elliptic curve cryptography (x25519-xsalsa20-poly1305). For wallets without encryption support, we will implement an alternative solution.

Future Developments

To enhance CryptoLegacy privacy, we plan to develop the ZK Approval Plugin, which will operate as follows:

• Owner adds the plugin to their personal CryptoLegacy contract.

• Owner approves assets not directly to their CryptoLegacy contract but to the ZK CryptoLegacy Transfer Contract.

• Owner sends a transaction to the CryptoLegacy contract via the plugin and stores a Merkle Tree containing their wallets, assets, and CryptoLegacy contract.

• When transferring assets from main wallets to the CryptoLegacy contract is required, Beneficiaries or Guardians generate a ZK proof and submit it to the ZK CryptoLegacy Transfer Contract. This allows withdrawal of assets from main wallets and transfers them into the CryptoLegacy contract.

Ultimately, this process ensures that it's impossible to track any connection between wallets and CryptoLegacy contracts.

By combining robust encryption practices with careful data management strategies, CryptoLegacy offers practical privacy protection for asset inheritance and recovery without sacrificing usability.