Memoir
Coverage
What Memoir checks—and what remains unknown.
Memoir currently investigates one Ethereum or Base address at a time. It combines bounded public-index history, current returned assets, selected protocol state, direct relationships, and public intelligence signals. 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. |
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.
- Continuous transaction monitoring, KYT alerts, or a legal AML decision.
See public sources for provider-specific boundaries and methodology for interpretation rules.