Holdings Log Guide
A reference framework for maintaining your own offline wallet holdings log — fields, conventions, and review cadence for long-hold records.
What a Holdings Log Is
A holdings log is a personal record that lists each wallet address you control, what it holds (as you understand it), when you acquired the position, and any transfers in or out. It lives offline — on paper or in an encrypted file — and is updated by you, not pulled from a live feed.
Panel Ashcore prepares tracking pages using this framework. You can also maintain a log yourself using the structure below.
Recommended Fields
For each wallet address, record:
| Field | Example | Notes |
|---|---|---|
| Label | Ledger #1 — BTC reserve | Human-readable, unique |
| Address | bc1q… (full string) | Copy from device; verify visually |
| Asset | BTC | As you classify it |
| Acquisition date | 14 Mar 2019 | Approximate is acceptable |
| Cost basis | ₩4,200,000 | As reported at purchase; not live value |
| Source | Withdrawn from Exchange A | Where it originated |
| Last reviewed | 25 Aug 2025 | Date you confirmed accuracy |
| Notes | Moved from old Ledger Oct 2022 | Transfers, device changes |
Review Cadence
We recommend reviewing your holdings log:
- After every new address you generate or receive funds to
- After device replacement or firmware migration
- Annually even if nothing changed — confirm labels still make sense
- Before any family handoff or accountant meeting
Common Gaps We See
- Test addresses — small sends to verify a device, then forgotten
- Dust accounts — negligible balances on old software wallets
- Duplicate labels — same name used on two devices after a migration
- Missing transfer dates — knowing an address exists but not when it was funded
A reconciliation review session addresses gaps in existing logs. A tracking page setup session builds the log from scratch.
Sample Page Layout
Each page in our folio format dedicates one section per address:
- Header: label and device name
- Body: address string, acquisition details, transfer history
- Footer: blank lines for handwritten updates
The layout is intentionally sparse. Dense tables age poorly when you add entries by hand over years.
Microsoft Store Companion
Our companion listing provides blank templates matching this layout for personal reference. It does not sync with wallets or exchanges.
Get it from Microsoft Available on the Microsoft StoreReady for a Prepared Folio?
If maintaining the log yourself feels overwhelming, request a tracking page session and we will build the folio with you during a 45-minute appointment.