Legacy Contract Details
The details page is where you operate a legacy day-to-day: check status, add or remove assets, reset the activation timer, or tear it down.
After creating a legacy, clicking it from the home page opens its details view. This is also where beneficiaries land when they open an inherited legacy.
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 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 β your (or the Safe's) most recent outgoing transaction.
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 transaction to make naturally. Any outgoing transaction from your wallet (or Safe) already counts as a heartbeat; the dedicated action is for when you want a quick, explicit reset.
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.
Status values
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
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
"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.)
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. 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.
On an EOA legacy
No finalizing step: on-chain changes happen as soon as you sign. Simpler flow, less coordination.
Any outgoing transaction from your wallet already counts as a heartbeat. The dedicated action is a convenience when you haven't transacted in a while.
The beneficiary's view (Inherited Legacy)
Beneficiaries see an inherited legacy on the home page under My Inherited Legacy, starting with status Not activated. The details page shows:
When they can activate β based on the owner's last outgoing transaction and the activation trigger.
What they'd receive β their allocation and the current list of approved assets (Transfer) or the Safe they'll inherit (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 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.
A contingent beneficiary sees the legacy under My Watchlist until their line activates, then it moves to My Inherited Legacy.
See also
Last updated