# Architecture 10102 Computing Legacy is deliberately layered so that the **on-chain layer is self-sufficient**, and the **off-chain layer is strictly additive**. If the off-chain services disappeared tomorrow, every existing legacy and timelock would still function — you'd lose email reminders and the pretty UI, but you'd keep the plan. ## The layers ### 1. On-chain: the core plan Solidity contracts on Ethereum. Deployed behind upgradeable proxies owned by a Safe multisig. Verified on Etherscan and published at [github.com/10102-io/computing-sc](https://github.com/10102-io/computing-sc). * **Legacy routers** — `MultisigLegacyRouter`, `TransferLegacyRouter` (Safe owners), `TransferEOALegacyRouter` (plain EOAs). * **Timelock router** — `TimeLockRouter`. * **Per-user legacy contracts** — deployed deterministically via `LegacyDeployer` using `CREATE2`, so the address is predictable before deployment. * **Safe integration** — a Safe Guard tracks last-activity timestamps; a Safe Module executes activation (adding owners or transferring assets). * **Premium contracts** — `PremiumSetting` stores watcher/reminder configuration; `PremiumRegistry` records subscriptions. Full address list, for every deployed contract and network, lives in `contract-addresses.json` of the `computing-sc` repository. ### 2. Indexing: The Graph A single subgraph per chain provides fast, reliable read access to the parts of the system that would be painful to query from raw RPC: * **Legacy/timelock/reminders subgraph** — indexes every event emitted by the routers and 10102-enabled Safes: creations, edits, deletions, activations, reminder configurations. The UI reads the bulk of its state from here. Everything else is direct on-chain. Token balances for the "your assets" pickers during legacy creation are fetched via viem against the canonical `TokenWhitelist` contract plus per-token ERC-20 `balanceOf` (`src/services/web3-assets-service.ts`). System-wide aggregates (total value locked across all legacies, timelocks and 10102-enabled Safes) are computed by the admin panel via `Multicall3` plus ERC-20 `balanceOf` / `allowance` walks against the entity set returned by the subgraph — see the `computing-admin` repository for the implementation. The UI prefers subgraph reads for the indexed data but falls back to direct on-chain reads (via viem) for post-mutation freshness, so stale subgraph data never blocks a newly-valid action. ### 3. Off-chain services Strictly additive layers that improve UX but can fail without breaking the plan: * **Chainlink Functions** — bridges Moralis API data into on-chain activation checks for EOA legacies (where the EVM can't natively read a wallet's last-tx timestamp). * **Chainlink Automation** — daily cron job that drives the email reminder evaluation. * **Mailjet** — SMTP delivery for reminder emails. * **Public RPC providers + Etherscan** — fallback read paths the UI can switch to. ## Section index * [Legacy Contracts Created with Safe SDK](/architecture/legacy-contracts-created-with-safe-sdk.md) — how Multisig and Safe-backed Transfer legacies work, including the Safe Guard and Safe Module integration. * [Legacy Contracts Created with EOAs](/architecture/legacy-contracts-created-with-eoas.md) — how pure-EOA Transfer legacies work, including the approval model and CREATE2 deployment. * [New Account Generation for Beneficiaries](/architecture/new-account-generation-for-beneficiaries.md) — client-side keypair generation for beneficiaries without an Ethereum address. * [Indexing & Activity Tracking](/architecture/indexing-and-activity-tracking.md) — how The Graph and the hybrid Chainlink/Moralis path feed the app. * [Email Reminders](/architecture/email-reminders.md) — the Chainlink Automation + Mailjet workflow for out-of-band notifications. ## A note on upgradeability Every contract deployed by 10102 sits behind a transparent upgradeable proxy whose admin is a Safe multisig held by the 10102 team. We can patch bugs and ship improvements — we *cannot* silently drain assets or retroactively alter an existing legacy's terms. Beneficiaries, owners, allocations, and activation windows are stored in per-legacy state that upgrades leave intact. Migration to a community-governed admin is on the public roadmap. --- # 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/architecture.md?ask= ``` 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.