A Real Example

You create a CryptoLegacy contract.

During setup, you:

  • define beneficiaries and transfer rules

  • approve specific wallets and tokens for future execution

  • intentionally allocate only a limited portion of your assets, not everything

  • add guardians to avoid long delays

  • add recovery as a safety fallback

CryptoLegacy governs a dedicated execution pool β€” assets you explicitly choose to cover situations where you cannot act.

Your remaining assets stay fully outside the system and remain under your direct control.

You continue using crypto normally and periodically update the activity timer.

Nothing happens. Your assets stay in your wallets.


A situation where you cannot act

You are traveling for work across regions with unstable or unavailable internet access.

Your primary device is lost or damaged. Backups are not immediately reachable.

For an extended period of time, you cannot:

  • access your wallets

  • sign transactions

  • cancel or update anything on-chain

You are safe, but completely unable to act.

At the same time, your family needs funds:

  • for regular living expenses

  • to handle an unexpected situation

  • without waiting weeks or months

No one has your private keys. No mnemonic fragments can be reconstructed. People who could help cannot coordinate or act on your behalf.


What the system does

CryptoLegacy detects that required activity has stopped and starts a waiting (Challenge) period.

Nothing is transferred yet.


If guardians are configured, they can act earlier so execution does not need to wait for the inactivity timer to complete.

This allows execution to begin even while the owner is temporarily unreachable.


Two possible outcomes

Outcome 1 β€” Access is restored

You regain access before execution is finalized.

Or a recovery address acts on your behalf.

In this case:

  • execution is canceled

  • guardian actions are reset

  • no assets are transferred

The dedicated execution pool remains untouched.

CryptoLegacy returns to normal operation.


Outcome 2 β€” Execution proceeds

If no one intervenes before the waiting period ends:

  • execution is allowed

  • only the pre-approved assets are transferred

  • distribution follows the rules you defined

Funds reach the intended recipients without reconstructing keys and without requiring coordination.

Your other assets remain unaffected.


The key point

CryptoLegacy does not assume that all assets should be governed by one mechanism.

It allows you to:

  • segment capital

  • define different risk profiles

  • limit execution scope intentionally

Nothing is decided at execution time.

The system does not ask why you were unavailable. It does not try to interpret intent or circumstances.

It checks only one thing:

Were the predefined on-chain conditions met or not?

CryptoLegacy executes exactly what you defined in advance.

Last updated