# Legacy Claim Card

A Legacy Claim Card is the paper safety net for your digital inheritance. It's a one-pager, generated by the app, that documents the minimum on-chain information a beneficiary needs to activate and claim a legacy without depending on 10102's UI.

The point: **your legacy lives on Ethereum, not on our website.** As long as beneficiaries can reach any Ethereum interface (Etherscan, a wallet's built-in contract interaction, a future app we haven't built yet), a printed card is enough.

## What's on the card

* **Legacy ID** — the on-chain identifier, used directly with the router contract.
* **Legacy contract address** — where the allocations and approvals live.
* **Router contract address** — the router beneficiaries call to activate.
* **Activation instructions** — short, plain-language steps describing the function to call and what arguments it expects.
* **Network** — mainnet, Sepolia, etc.
* **QR codes** — scannable links for the contract address and router address, so beneficiaries don't have to hand-type 42-character hex strings.

## What's intentionally *not* on the card

* **The owner's wallet address.** Many owners don't want beneficiaries to know which wallet the legacy belongs to until activation. The card is designed to be handable to a beneficiary in advance (inside a sealed envelope, with a lawyer, in a safety deposit box) without leaking that link.
* **The list of assets.** This intentionally isn't pinned to paper. Asset lists change over time (you approve more, you remove some) and the card shouldn't go stale. Beneficiaries can look up the current asset list from the contract via any explorer.
* **Personal data or email addresses.** The card is purely on-chain coordinates.

## When to print it

Print (or regenerate) the card whenever:

* You first deploy a legacy.
* You change the legacy's address (e.g. you delete and recreate).
* You change beneficiaries and want the new ones to have a fresh copy.
* Your previous copies are unaccounted for.

## How beneficiaries use it without our app

If `app.10102.io` is unreachable for any reason, a beneficiary can still claim. The card includes step-by-step instructions, but the short version is:

1. Wait until the activation window has elapsed (time since the owner's last outgoing transaction exceeds the configured threshold).
2. Open any Ethereum interface that supports calling an arbitrary contract — Etherscan's *Contract → Write* tab works.
3. Connect the beneficiary's wallet.
4. Call the router's activation function with the **Legacy ID** from the card.
5. Sign. Pay gas. Assets are distributed according to the allocations the owner configured.

This is the same function our UI calls behind the scenes. The contracts don't know where the call came from.

{% hint style="success" %}
**Self-test.** If you're unsure the card is complete, hand a copy to a technically-minded friend and ask them: "If I disappeared and 10102's website didn't exist, could you initiate the claim for my beneficiaries from this alone?" If yes, the card is doing its job.
{% endhint %}

## Where to find it

* On a legacy's details page after creation, an action downloads the card as a printable PDF.
* Regenerate at any time — the card is derived from on-chain data, so it's always up to date.
* We don't store a copy on our servers. Keep the PDF (or a print) somewhere your beneficiaries can reach it when they need it.

## Privacy considerations

* Treat a Legacy Claim Card like you'd treat a will document: give it to people who need it, store copies securely, update when things change.
* The card doesn't contain private keys or anything sensitive beyond on-chain public coordinates — but it *does* contain the pre-activation pointer to a specific legacy, which is information some owners treat as private.
* If you've given someone a copy and want to revoke their ability to claim, delete and recreate the legacy (which generates a new contract address).

## See also

* [Create a Legacy Contract](/user-guide/legacy/create-a-legacy-contract.md) — the card is generated from here.
* [Activate a Legacy Contract and Claim Funds](/user-guide/legacy/activate-a-legacy-contract-and-claim-funds.md) — the beneficiary's side.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.10102.io/user-guide/legacy/legacy-claim-card.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.