Memoir
Coverage
What Memoir checks—and what remains unknown.
Memoir checks public Ethereum and Base activity through task-specific browser tools. Investigate one address or transaction, follow selected transfers, compare balance observations, inspect public flags, or keep a local list of addresses and watch rules. Every module reports its own coverage; an unavailable source is never presented as an empty or clear result.
Current coverage at a glance
| Area | Currently covered | Important limit |
|---|---|---|
| Chains | Ethereum and Base | Bitcoin and other address formats are not currently supported. |
| Account | Account type, earliest configured index observation, chain counters, current native balance | Indexer lag and source availability can change the returned result. |
| Activity | External transactions, token transfers, bounded internal calls and non-transfer logs, selected decoded actions | Large histories load in bounded windows; arbitrary traces and calldata are not guaranteed. |
| Assets | Returned fungible and NFT holdings plus selected direct contract checks | Missing, staked, custody-transferred, or out-of-bound assets can remain unknown. |
| Positions | Selected Aave, Morpho, Compound, Uniswap, Aerodrome, and Lido position types | This is protocol-specific, point-in-time, bounded coverage—not a complete DeFi portfolio. |
| Intelligence | Named public sources, exact designations, public labels, contract verification, deterministic loaded-evidence metrics | No source is universal; no match is not proof that an address is safe. |
| Relationships | Direct counterparties and per-asset flows derived from loaded evidence | No automatic multi-hop ownership graph or common-control inference. |
| AI | User-selected evidence and workspace context with cited structured output | AI does not receive a guaranteed complete lifetime history. |
Task-specific bounds
- Transactions: receipt outcome, execution fee, supported asset and permission events, and an optional bounded public-index trace. Missing traces remain unknown; receipt success does not prove an exchange credited a customer account.
- Funds paths: up to six hops, 16 retained steps, and 48 path-source requests per investigation. Expansion is explicit. Cross-chain settlement requires protocol-specific evidence; unsupported routes stay unverified.
- Balance checks: one chain and asset, at most 2,000 blocks and 2,000 retained events, within a 40-request budget. Native indexed changes retain at most four pages. Contract events and canonical balance differences are separate observations, not interchangeable proof.
- Address Public signals: each configured source reports separately in the address workspace, where you can refresh sources and export evidence. Duplicate original datasets are not independent corroboration. A failed refresh preserves the earlier result with its original date.
- Multi-wallet overview: up to 12 explicitly added addresses on Ethereum and Base; at most 201 returned holdings per address and chain. Latest and previous observations stay locally, subject to an 8 MB bound. Missing reads are not included as zero; totals are not a complete net worth or PnL calculation.
- Local watch rules: up to four rules, 200 retained alerts, and 80 check-history entries. A rolling 240-request hourly budget is shared between Watch tabs in this browser. Checks pause when the page is hidden or offline; closing the browser ends polling. This is not a 24/7 alarm service.
These are application bounds, not guarantees that public providers will return every requested item. Every result preserves more specific source failures and limitations.
Coverage states
Why history loads progressively
High-activity addresses can contain hundreds of thousands of indexed records. Memoir requests bounded pages and appends older evidence as the user continues into the past. The visible ledger remains newest-first, and virtualization prevents the browser from mounting every row at once.
A selected time range can include newly loaded records that fall inside that range. An analysis already in progress remains pinned to the exact snapshot present when it started.
What this coverage cannot establish
- A real person's verified identity from behavioral resemblance.
- That two addresses share an owner merely because they interacted.
- That an address is safe because configured sources returned no match.
- A complete net worth, historical cost basis, or complete protocol portfolio.
- Unattended or closed-browser transaction monitoring, guaranteed alert delivery, or a legal AML decision.
See public sources for provider-specific boundaries and methodology for interpretation rules.