How CryptoLegacy works

The owner defines the rules in advance. Assets stay under owner control until transfer or recovery conditions are met.

Execution flow
Setup

Rules set in advance

Normal

Normal period

Owner keeps control

Trigger

Timeout or guardian confirmations

Challenge

Challenge period

Gate before distribution

Outcome

Distribution and claim

Recovery

Recovery path

Separate governed path

1. Setup

Rules set in advance

2. Normal

Owner keeps control

3. Trigger

Timeout or guardian confirmations

4. Challenge

Gate before distribution

5. Outcome

Distribution and claim

Recovery

Recovery path

Separate governed path

Control model

Owner-defined rules

The owner defines the rules in advance. No one gets open control. Each path opens only when its conditions are met.

Who can act

Beneficiaries and guardians are set in advance. Separate recovery addresses are authorized for recovery. None of them become co-owners or custodians.

When they can act

No path is open by default. Transfer or recovery opens only when its conditions are met.

What they can do

Guardians help open governed paths. Beneficiaries claim after distribution. Recovery addresses complete recovery under recovery rules.

Execution path

Transfer path

Transfer is governed, not automatic. Timeout expiry or guardian confirmations can open the path, but challenge still gates distribution and claim.

Step 1Trigger

Path opens under predefined conditions

The owner defines the transfer path in advance. Assets stay under owner control until those conditions are met.

Step 2Challenge

Challenge comes before distribution

Once the path opens, a challenge period begins. It is the gate before distribution and the last point where the process can still be stopped.

Step 3Distribution

Assets move into the contract, then beneficiaries claim

If the challenge completes, designated assets move into the contract. Beneficiaries then claim under the transfer rules.

During Distribution, approved plugins can extend execution on contract-held assets.

Approved plugins

Enabled in advance, or later if the setup allows it.

Allowed actions

Swap, stake, lend, or manage positions where allowed.

Thresholded execution

Extra actions still follow configured confirmations.

Boundary
Access restoration

Recovery path

Recovery handles broken access, not beneficiary transfer. Guardians can help move assets into the contract, and authorized recovery addresses can later withdraw under recovery rules.

Step 1Recovery

Path opens under recovery conditions

Recovery is for broken access, not ordinary transfer. It opens only when recovery conditions are met.

Step 2Boundary

Support does not equal ownership

Guardians may help move assets into the contract. They do not become beneficiaries or gain arbitrary control.

Step 3Outcome

Recovery follows its own governed path

Once recovery is available, authorized recovery addresses can withdraw to a new address under recovery rules. Finalized transfer claims are not reversed.

Boundary
Boundary clarification

What the system does not do

CryptoLegacy does not move assets during normal operation, grant open-ended control to invited roles, or turn setup into early custody transfer. All later actions remain owner-defined.

Next step

Ready to define the rules?

Go to the app to define the setup, or continue into Documentation for deeper verification.

Nothing changes. Your assets stay under your control. Self-custody does not define what happens if you cannot act.

Yes. During normal operation, your assets stay fully in your wallet. The contract holds permissions, not funds. It only defines what may happen if you cannot act.

Multisig requires real-time coordination. Key sharing exposes secrets. CryptoLegacy defines rules in advance β€” no one needs to hold your keys or coordinate at the right moment.