Indexing Ethereum addresses without exposing seed phrases

Clients often ask whether we need to “see inside” their wallets. We do not. We need consistent labels and verified public balances.

Our indexing order

1. Client powers device in our room (or brings pre-printed address list).
2. We read aloud each address while client confirms on their screen.
3. Client copies balance from their own app; we write what they confirm.
4. We assign a binder tab: device name, derivation note if they use one, date.

Labels that work for heirs

Avoid “Wallet 1.” Use “Ledger Nano — long-hold ETH” or “Trezor — monthly USDC sweep source.” Heirs inherit words, not intuition.

When we pause the session

If a client cannot verify a balance without connecting to an unfamiliar app, we stop and reschedule after they practice on home equipment. Rushing produces wrong numbers on permanent paper.

Duplicate detection

We compare new lists against prior sessions. Duplicate addresses on separate pages caused two inheritance disputes referrals last year — both resolved once the paper record was corrected.