Table
Quick scan of wallet activity
A · scan| Asset | Amount | Counterparty |
|---|---|---|
| BTC | 4.2000 | bc1q…9f4 |
| ETH | 18.400 | 0x…22c |
| BTC | 1.1000 | bc1q…7ae |
Purpose
Contracts, not appearances
They share a layout, so an agent working from visuals alone would reuse one for the other. Step through the fields to find where they stop being the same.
Table
Quick scan of wallet activity
A · scan| Asset | Amount | Counterparty |
|---|---|---|
| BTC | 4.2000 | bc1q…9f4 |
| ETH | 18.400 | 0x…22c |
| BTC | 1.1000 | bc1q…7ae |
Purpose
Table
Auditable source-of-wealth investigation
B · investigate| Asset | Amount | Counterparty | Evidence | Conf. |
|---|---|---|---|---|
| BTC | 4.2000 | bc1q…9f4 | row 12 | verified |
| ETH | 18.400 | 0x…22c | row 15 | verified |
| BTC | 1.1000 | bc1q…7ae | none | unknown |
Purpose
Yes
No
Do not reuse A’s hierarchy for B. Scan and investigation are different jobs.