Canonical Definitions
Protocol
The CryptoLegacy Protocol is the complete set of on-chain rules, state transitions, and execution constraints enforced by the CryptoLegacy smart contracts.
The protocol defines:
valid execution paths,
allowed state transitions,
authority boundaries between roles,
conditions under which asset movement is permitted.
The protocol does not interpret off-chain intent and does not perform discretionary decision-making.
Personal CryptoLegacy Contract
An owner-specific smart contract instance that:
stores configuration, roles, and execution state,
enforces protocol invariants,
may temporarily hold assets during Distribution,
holds no assets during the Normal Period.
Each personal contract operates independently and deterministically.
Asset Holder
An Asset Holder is an external address that holds assets governed by a personal CryptoLegacy contract.
An Asset Holder:
is an externally owned account (EOA) or a smart contract wallet (for example, a multisig),
holds assets outside the personal CryptoLegacy contract,
grants approval for specific assets to be transferred by the protocol when execution conditions are met.
During Normal and Challenge Periods:
assets remain in Asset Holder addresses,
no assets are moved into the personal contract.
During Distribution Period (or via recovery execution paths):
pre-approved assets may be transferred from Asset Holder addresses into the personal CryptoLegacy contract,
transfers are executed strictly via protocol-defined execution paths and conditions.
Asset Holders are not execution roles and do not possess protocol authority.
Execution Path
A protocol-defined, on-chain execution route that specifies:
required on-chain state conditions,
authorized roles that may submit transactions,
permitted state transitions,
allowed asset movements and destinations (if any).
Execution paths are fixed by protocol logic. Roles may only trigger the conditions for an execution path and cannot modify, combine, or create new ones.
Execution Period
A high-level protocol state that defines which execution paths are available.
CryptoLegacy defines exactly three execution periods:
Normal Period
Challenge Period
Distribution Period
Execution periods are mutually exclusive and ordered.
Normal Period
The default execution period in which:
assets remain in Asset Holder addresses (external owner-controlled wallets),
the personal contract holds no assets,
configuration and maintenance actions are allowed,
inactivity-based and guardian-based execution paths that move assets are disabled,
recovery-specific execution paths may remain available, subject to recovery conditions.
Challenge Period
A transitional execution period preceding Distribution.
Entered via:
Beneficiary-Initiated Challenge (fixed 3 months), or
Guardian-Initiated Challenge (bounded 0β30 days).
During this period:
no asset transfer into the personal contract is permitted,
execution proceeds to Distribution only if the challenge completes uncancelled.
Distribution Period
The execution period in which:
protocol-defined execution paths that move assets are enabled,
pre-approved assets may be transferred into the personal contract,
beneficiaries may claim assets,
recovery execution paths may withdraw remaining contract-held assets.
Distribution introduces asset-level finality.
Roles
Owner Configures and maintains the personal contract during Normal Period. Once Distribution begins, owner-only operational actions are disabled.
Beneficiary May initiate a Beneficiary Challenge and claim assets during Distribution. Never has custody before Distribution.
Guardian May collectively trigger a guardian execution path before inactivity expires. Never gains custody and cannot transfer assets to arbitrary addresses.
Recovery Address Enables a recovery-specific execution path. Under recovery-specific thresholds, Recovery addresses may (1) transfer pre-approved assets from Asset Holder addresses (external owner-controlled wallets) into the personal contract without waiting for beneficiary or guardian challenge periods, and (2) withdraw contract-held assets to arbitrary new recipient addresses according to the recovery execution rules. Recovery cannot reverse, modify, or invalidate finalized beneficiary claims.
Asset-Level Finality
Finality applies independently to each asset. Once a transfer or claim is finalized, it cannot be reversed by any role, plugin, or governance mechanism.
Last updated