How CryptoLegacy Works

CryptoLegacy securely automates crypto inheritance and recovery through smart contracts, predefined schedules, guardian approvals, and recovery addresses.

Inheritance

Step 1: Setup

You deploy a personal smart contract from a factory, pay a small DAO fee, set up Beneficiaries with their shares and schedules (including delays and distribution periods), approve token transfers from your main wallets to the contract, and encrypt asset data individually for each beneficiary. Every 6 months, you update the timeout by sending a transaction that includes the DAO fee.

Step 2: Challenge

If the timeout expires, any Beneficiary can initiate a 3-month challenge period, during which you can still cancel the process. Once the challenge period ends, Beneficiaries can decrypt asset data (previously hidden) and transfer assets from your main wallets to the CryptoLegacy contract for distribution.

Step 3: Distribution

After that, Beneficiaries can claim assets based on their shares and schedules (delay and distribution periods). They can update their addresses anytime if compromised. Assets stay in the CryptoLegacy contract during the distribution period.

Recovery

Step 1: Add Guardians and Recovery

During contract setup, two plugins are automatically added. By default, your Beneficiaries become guardians with a 2-of-3 approval requirement and a 30-day challenge period. You can adjust Guardians, thresholds, and timeout anytime. You can also add Recovery addresses with custom approval thresholds (like 1-of-3 or 3-of-5). Guardian and Recovery addresses are stored securely as hashes, keeping them separate from your CryptoLegacy contract.

Step 2: Emergency Withdrawal

Each Guardian must send a transaction to start distribution before the main 6-month timeout ends. Once the required approvals are met, an optional Guardian Challenge Period (0 to 30 days) begins. During this period, you or any Recovery address can cancel the process. After the challenge period, Guardians can decrypt asset data (previously hidden) and transfer assets to your personal contract for distribution. Guardians never have direct access to your funds.

Step 3: Distribution and Recovery

Beneficiaries claim assets based on their preset shares and schedules. You keep full control and can recover all assets anytime using your securely hashed recovery addresses, which stay separate from the CryptoLegacy contract.

Management

Step 1: Add Plugins for Asset Management

You can add plugins that let Beneficiaries manage assets during distribution — like swapping tokens, staking ETH in Lido, moving assets cross-chain, or managing liquidity on Uniswap. Most plugins require a specific number of Beneficiary confirmations (similar to a multisig), which you can configure.

Step 2: Allow Beneficiaries to Add Plugins

You can let Beneficiaries add plugins once distribution begins, which helps if integrated protocols need updates. But for security reasons, Beneficiaries can’t remove existing plugins.

Step 3: Manage Assets During Distribution

During distribution, Beneficiaries can use plugins to manage assets, which stay securely in your personal CryptoLegacy contract. Each action needs a specific number of confirmations. Beneficiaries keep claiming assets according to their predefined shares and schedules.

Customization

Step 1: Add Plugins with Custom Logic

You can add plugins to customize your CryptoLegacy logic — for example, transferring NFTs, automatically closing Uniswap NFT positions, distributing fixed amounts (instead of shares) to Beneficiaries, or creating entirely new rules.

Step 2: Allow Beneficiaries to Add Custom Logic

You can let Beneficiaries add plugins themselves once distribution starts. These plugins can include custom logic, like transferring shares, adding new Beneficiaries, or creating other custom rules.

Step 3: Plugin Security Check

All plugins are verified through the Plugin Registry — a smart contract managed by the core team, partnered protocols, and leading security firms. This ensures your contract stays secure by allowing only plugins that have passed multiple thorough audits.

Last updated