> For the complete documentation index, see [llms.txt](https://docs.10102.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.10102.io/user-guide/legacy/legacy-contract-details.md).

# Legacy Contract Details

After creating a legacy, clicking it from the home page opens its details view. This is also where beneficiaries land when they open a legacy left to them.

## Sections of the details page

### Header

* **Name** and **Legacy ID**: the on-chain identifier, useful for claiming via Etherscan and for cross-referencing with emails.
* **Contract address**: where allocations, approvals, and native token deposits live.
* **Status**: see [Status values](#status-values) below.
* **Creator** (Safe legacies only): the wallet that originally submitted the creation transaction. Relevant because notification settings (watchers, reminders) are creator-only; see the callout on the affected settings pages.

### Activity and trigger

* **Last activity**: the most recent activity the legacy knows about. For Safe legacies that's the Safe's last transaction (every Safe transaction counts). For EOA legacies it's your last interaction with the legacy itself; see [The owner's view](#on-an-eoa-legacy) below.
* **Activation trigger**: the inactivity threshold you configured. The details page shows how much of the window has elapsed.
* **Heartbeat action**: resets the trigger timer in a single transaction when you don't have another qualifying action to make naturally. On a Safe legacy, any Safe transaction already counts; on an EOA legacy, only interactions with the legacy count (unless you enable [auto-renew](/user-guide/concepts.md#auto-renew-eoa-legacies)), so the dedicated action is the standard way to check in.

### Assets (Transfer legacies)

Shows the ERC-20s approved to the legacy contract, their current allowances, and the per-beneficiary distribution that would happen on activation.

* Only tokens with a non-zero approved amount are shown, keeping the view focused on what actually moves on activation. To see the full list of held tokens with zero allowance, enter edit mode.
* ETH is not shown in the assets table: ETH can't be approved as an ERC-20, so it's represented by whatever storage token (WETH, a liquid staking token, …) you swapped into. The home page shows your wallet's current ETH balance separately, independent of the legacy.

### Beneficiaries

The configured addresses, their allocations (for Transfer legacies), and, for Safe legacies, the role they'll take on activation.

### Danger zone

* **Edit contract**: adjust beneficiaries, allocations, trigger window, or asset approvals.
* **Delete contract**: tear the legacy down and return any native tokens; see [Edit or Delete](/user-guide/legacy/edit-or-delete-a-legacy-contract.md).

## Status values

| Status                           | Meaning                                                                                                             | Typical next step                                                                            |
| -------------------------------- | ------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------- |
| **Needs finalizing** (Safe only) | A Safe transaction has been submitted but not enough signers have finalized it                                      | Collect the remaining signatures in our app or on [app.safe.global](https://app.safe.global) |
| **Live**                         | The legacy is active; allocations are in effect; the activation trigger is counting down                            | Include assets, manage watchers, etc.                                                        |
| **Activated**                    | A beneficiary has successfully activated the legacy and distribution has started (Transfer) or completed (Multisig) | For Transfer with >100 transactions, keep claiming until done                                |

{% hint style="info" %}
**"Needs finalizing" threshold is inclusive.** When the number of signers who've approved equals or exceeds the Safe's threshold, the transaction is ready to finalize. (This was recently aligned with Safe's own semantics, so having *more* signatures than strictly needed no longer blocks finalization.)
{% endhint %}

## The owner's view

### On a Safe legacy

* You'll see a banner if the legacy needs finalizing. Your Safe co-signers can add signatures there, or at [app.safe.global](https://app.safe.global). Finalizing is a gas-paying transaction that any Safe signer can submit once the threshold is met.
* The heartbeat action is available to any Safe signer; the Safe's own transactions already reset the timer.
* Notification settings (watchers, reminders) are managed by the creator of the legacy, which may or may not be you. If it isn't, you'll see a "Notification settings managed by 0x…abcd" badge pointing to the creator. See [Creator vs. signer](/user-guide/concepts.md#creator-vs-signer-safe-legacies).

### On an EOA legacy

* No finalizing step: on-chain changes happen as soon as you sign. Simpler flow, less coordination.
* Interactions with the legacy count as heartbeats: edits, deposits, withdrawals, or the dedicated heartbeat action. Generic wallet activity elsewhere does **not** reset the timer by itself.
* If you'd rather have your wallet's general on-chain activity keep the timer fresh, enable **auto-renew** (Premium, opt-in, per legacy): an attestor service observes your wallet's public transaction count and renews for you near the deadline, within strict on-chain bounds. See [Automatic Renewal](/user-guide/premium-features/automatic-renewal.md).

## The beneficiary's view (Legacies for Me)

Beneficiaries see a legacy left to them on the home page under **Legacies for Me**, starting with status **Not activated**. The details page shows:

* **When they can activate**: based on the owner's last recorded activity and the activation trigger.
* **What they'd receive**: their allocation and the current list of approved assets (Transfer) or the Safe they'll take over (Multisig).
* **Activation button**: enabled once the window has elapsed. Any designated beneficiary can trigger it; distribution happens to *all* beneficiaries according to the allocations, not just the one who activated.

See [Activate a Legacy Contract and Claim Funds](/user-guide/legacy/activate-a-legacy-contract-and-claim-funds.md) for the beneficiary flow.

## Watcher and contingent-beneficiary views

* A **watcher** sees the legacy under **My Watchlist** with either full or limited visibility, depending on what the owner configured. See [Manage Authorized Watchers](/user-guide/premium-features/manage-authorized-watchers.md).
* A **contingent beneficiary** sees the legacy under **My Watchlist** until their line activates, then it moves to **Legacies for Me**.

## See also

* [Edit or Delete a Legacy Contract](/user-guide/legacy/edit-or-delete-a-legacy-contract.md)
* [Legacy Claim Card](/user-guide/legacy/legacy-claim-card.md)
* [Activate a Legacy Contract and Claim Funds](/user-guide/legacy/activate-a-legacy-contract-and-claim-funds.md)