Asset management techniques

Beginner Intermediate Expert

Backups are not a one-off task. Holdings grow, devices age, people move house, standards change. Treat your self-custody like any other asset: documented, reviewed and tested.

Last fact-checked 24 October 2026 (time-sensitive claims re-checked against the linked sources).

How this page is layeredBeginner: what to record (and never record), a starter register, the inventory table and recovery drills. Intermediate: tax records for the UK and US, multi-wallet and multisig housekeeping, a testing cadence, key rotation and operational security. Expert: descriptor and xpub record-keeping, descriptor backups and decoy and duress wallets. For physical threats see coercion; for scams see current scam patterns.

What to record, and what never to record Beginner

Good records answer three questions for you, a helper or an executor: what exists, where the pieces are and how to check it still works. They never contain anything that can spend the funds.

Safe to record, private, and never to record
CategoryExamplesWhy
Safe to recordWallet labels, coin, device make and model, backup standard (BIP39 12/24 words, SLIP-39, multisig quorum), whether a passphrase is used (yes/no only), location codes, date last tested, exchange names and account emails, who to contactTells someone what exists and how to approach recovery without giving them the ability to spend
Private (store carefully)Master fingerprints, first receive address, output descriptors, xpubs, transaction history, cost-basis recordsCannot spend funds, but an xpub or descriptor lets anyone who sees it follow the wallet's addresses and balance. BIP32 also warns that an xpub together with any one non-hardened child private key reveals the whole account (xpub leaks; BIP32)
Never record hereSeed words, passphrases, PINs, private keys, share contents, photos or scans of any backupAnyone who finds the record could take the funds. Seeds live only in the backup system described on Physical storage
Real examplesA UK estates lawyer told the BBC about a family who believed a relative had owned bitcoin but had to give up because nobody had the information to access it (BBC News; case file). In Ireland, codes for about 6,000 BTC were printed on one sheet of paper and hidden where nobody else knew to look (case file). A register of what exists and where addresses the first problem; a second, separately stored backup addresses the second.

A starter register in five lines Beginner

  1. What: "Bitcoin savings on a hardware wallet (make/model), 24-word BIP39 backup, passphrase: yes/no."
  2. Where: "Backup at L1; device at L2." Keep the key to the location codes somewhere else.
  3. Check: master fingerprint and first receive address, so a restore can be confirmed without looking at balances.
  4. When: date last tested, and the next test date.
  5. Who: a trusted technical helper (who holds no keys), plus any exchange or custody accounts.

Printable versions: backup inventory and location map and recovery drill log.

Keep an inventory (without secrets) Beginner

A non-secret register lets you — and later your executor — know what exists and where to look. Keep it on paper or in an encrypted file; it must never contain seed words, passphrases or PINs.

Wallet labelTypeDevice(s)StandardFingerprint / first addressBackup locations (codes)Last tested
"Savings vault"2-of-3 multisig BTCVendor X, Y, ZBIP39 ×3 + descriptore.g. 1a2b3c4d (fictional)L1, L2, L3Mar 2026
"Spending"Single-sig, mobilePhone appBIP39 12bc1q…(fictional)L1Jan 2026
"ETH"Single-sig + passphraseVendor XBIP39 24 + passphrase0x… (fictional)L1 (seed), L4 (passphrase)Mar 2026

Use location codes ("L1 = home safe") with the key to codes held separately, so the inventory alone is not a treasure map.

Recovery drills Beginner

  1. At setup: restore from every backup before funding.
  2. Every 6–12 months: use the device's "check backup" mode or restore onto a spare device; confirm the fingerprint and first address.
  3. Inspect each location: physical condition, tamper-bag serial numbers, legibility.
  4. Firmware: update devices from official sources; read release notes for backup-format changes.
  5. Rehearse the heir's path: could your executor follow your letter? Walk a trusted person through it with a test wallet.

Tax records: UK and US pointers Intermediate

Not tax, legal or financial adviceThe tax notes below summarise official guidance as read on 24 October 2026. Rules change and depend on your circumstances. Check the linked source and speak to a qualified adviser before relying on them.

Tax records and backup records are different things. Tax records are about transactions (dates, amounts, values and costs); backup records are about access. Neither should contain a seed. Both tax authorities say exchange reports alone are not enough.

Record-keeping for crypto tax, UK and US (read 24 October 2026)
Topic🇬🇧 United Kingdom (HMRC)🇺🇸 United States (IRS)
How it is treatedDisposals (selling, swapping, spending, giving away other than to a spouse, civil partner or charity) can be subject to Capital Gains Tax (GOV.UK)Digital assets are property, not currency, for US tax (IRS)
Cost methodPool each token type ("section 104" pooling), with same-day and 30-day matching rules taking priority (GOV.UK; CRYPTO22200)Specific identification where you can substantiate it, otherwise first in, first out (Rev. Proc. 2024-28 summarising the IRS FAQs). From 1 January 2025, basis is tracked wallet by wallet or account by account; the Rev. Proc. gave a safe harbour to allocate unused basis to each wallet as of that date
What to keepFor each pool and transaction: token type, date of disposal, number disposed of and left, value in pounds, bank statements, and pooled costs before and after. HMRC adds that you "may also want to keep other records such as wallet addresses" (GOV.UK)Records of each purchase, receipt, sale, exchange or other disposal, and US dollar fair market value of anything received as income. For a gain or loss: asset type, date and time, units, fair market value and basis (IRS)
Exchange reportsUseful, but "they're not tax calculations" and "will not keep track of your pooled costs"; you must keep your own records (GOV.UK)Brokers report gross proceeds on Form 1099-DA for transactions from 1 January 2025, and basis for certain transactions from 1 January 2026. Non-custodial ("decentralised") brokers are not covered (IRS; 1099-DA instructions). Self-custody activity is yours to track
Where it is reportedSelf Assessment has a cryptoasset section from the 2024–25 tax year, completed in pounds (GOV.UK)Form 8949 and Schedule D; the 2025 instructions say digital asset sales go in boxes G, H or I (short term) and J, K or L (long term), not C or F (Form 8949 instructions). Every Form 1040 asks the digital asset question
Moving between your own walletsKeep a record so the transfer is not mistaken for a disposal. HMRC's records list above includes wallet addresses as optionalAnswer "No" to the digital asset question for transfers between wallets or accounts you own or control, unless you paid the fee in a digital asset (IRS)
What providers report about youSince 1 January 2026, crypto service providers must collect your name, date of birth, address and National Insurance number or UTR under the Cryptoasset Reporting Framework. Inaccurate or missing details to a UK provider can mean a penalty of up to £300 (GOV.UK). First reports are due to HMRC by 31 May 2027 (IEIM8000050)Brokers file Form 1099-DA with the IRS and send you a copy (IRS)
Lost keysLosing a private key is not a disposal. If there is no prospect of recovery, a negligible value claim may be possible (CRYPTO22400)Two IRS Chief Counsel memos matter: 202302011 (a collapsed coin that still trades is not a loss) and 202511015 (some theft losses from scams entered into for profit may be deductible). Personal theft and casualty losses stay limited to declared disasters after Public Law 119-21. Summary and sources: lost or stolen crypto. Take advice before claiming
Scam alert from the IRSThe IRS warns about letters with a QR code that claim to be from the IRS and ask you to register your crypto on a "Digital Assets Compliance Portal". It says it does not require registration of digital assets and is not sending those letters (IRS digital assets page). No tax authority needs your seed phrase.

Pros of keeping your own records

  • Accurate returns, and evidence if HMRC or the IRS asks
  • Executors can value the estate at the date of death
  • Separates transfers between your own wallets from disposals

Cons

  • Time-consuming across many wallets and exchanges
  • Records of addresses and balances are a privacy risk if leaked

Pitfalls

  • Relying on an exchange report that does not track pooled costs (UK) or covers only that broker (US)
  • Exchanges closing or deleting history: export it while you can
  • Uploading xpubs or full histories to online tools without thinking about privacy

Community advice

  • Export exchange CSVs at least once a year and store them encrypted
  • Label each transfer between your own wallets when you make it
  • Prefer tax tools that accept addresses or CSVs over ones asking for wallet logins; never give one a seed

Multi-wallet and multisig housekeeping Intermediate

  • One label, everywhere. Use the same wallet label on the device, in the coordinator, in the register and on the backup's location code, so nobody has to guess which backup goes with which wallet.
  • Fewer wallets is easier. Every extra wallet adds a backup to test and a line for an executor to chase. Retire wallets you no longer use (see clean-up).
  • Watching-only copies let you check balances and receive addresses without exposing keys, but they hold the xpubs, so protect the computer. Sparrow notes that Bitcoin Core stores public keys and balances unencrypted on the machine it runs on (Sparrow best practices).
  • US wallet-by-wallet basis: since 1 January 2025 basis is tracked per wallet or account (Rev. Proc. 2024-28), so keep each wallet's transactions separate in your records.
  • Multisig: keep the configuration with every key. BIP-129 (BSMS) warns that an attacker who can change a multisig configuration "can steal or hold funds for ransom", and one who can read it can monitor the wallet (BIP-129). Register the wallet on each signing device so it can check addresses, and re-check the configuration whenever you replace a device or rotate a key.
  • Spread vendors and places. Sparrow's expert-stage advice is at least 2-of-3, hardware wallets from different vendors, and keys and backups in different locations (Sparrow; community advice).

How often to test: a recovery-testing cadence Intermediate

Suggested recovery-testing cadence
WhenWhat to testBasis
At set-up, before fundingRestore or check every backup and confirm the fingerprint and first addressWidely given advice; see Start here, step 5
Before every firmware update and before wiping a deviceUse the device's check-backup modeTrezor recommends testing the backup before wiping and before every firmware update (Trezor)
Every 6–12 monthsCheck backup on the device (or restore on a spare), inspect each location, update the registerCommunity advice; pick a fixed date such as a birthday
After a life eventMarriage, divorce, birth, death, house move, new wallet: update the register and letter of instruction, and re-test anything movedSee estate planning principles
After moving or replacing a backupTest the new backup before destroying the old oneAvoids a window with no working backup
When an heir, executor or co-signer changesRehearse their path with a test wallet; rotate keys they heldSee key rotation

Pros of regular tests

  • Finds corroded, illegible or mislabelled backups while you can still fix them
  • Keeps the procedure familiar for you and your helper

Cons

  • Every handling of a seed is a small exposure risk
  • Travel to several locations takes time

Pitfalls

  • Typing words into a computer or phone "just to check"
  • Testing only one share of a multi-share or multisig set-up
  • Forgetting the passphrase step, so the test opens an empty wallet

Community advice

  • Test on the hardware device itself, never on a website
  • Write the result in a drill log with the date, not the words

Key rotation and clean-up Intermediate

  • If a backup may have been seen, photographed or lost: create a new wallet and move funds. You cannot "change" a seed.
  • When a co-signer, employee or relative leaves the plan: rotate their key.
  • Consolidate old wallets you no longer track; dust in forgotten wallets is a common estate headache.
  • Securely destroy obsolete backups (cross-cut shred and burn paper; grind or deface stamped metal).

Operational security habits Intermediate

  • Don't discuss amounts publicly or on social media; use a separate email for crypto purchases.
  • Verify receive addresses on the hardware screen; beware clipboard-swapping malware.
  • Use a dedicated, updated computer for coordinating large transactions.
  • Bookmark official sites; never use search ads to reach wallet sites.
  • Record cost basis and transaction history for tax (see tax records, and for estates UK / US).
  • Insurance: home policies rarely cover crypto; specialist cover exists for some custody models — read the exclusions.

Descriptor and xpub record-keeping Expert

  • Keep the full descriptor with its checksum. A descriptor may end with # and an eight-character checksum. BIP380 says it is optional for parsing, but some applications reject descriptors without one, and it catches copying errors (BIP380).
  • Record the creation date (wallet "birthday"). Bitcoin Core's listdescriptors output includes a creation timestamp for each descriptor, which helps a later restore scan from the right point (Bitcoin Core RPC).
  • Export public descriptors only. listdescriptors shows private descriptors only when its private argument is set to true; the default is false (Bitcoin Core RPC). A private descriptor contains keys and must be treated like a seed.
  • Wallet policies. For devices that use BIP-388 wallet policies, keep the registered policy and its name with the descriptor (BIP-388). See descriptors and the BIP380 family.
  • Xpubs are private, not secret. They cannot spend, but they reveal every address and balance. Do not paste them into online tools you do not control, and remember the BIP32 warning above.
  • Check the record against reality. After any change, confirm the first receive address shown by the coordinator, the device screen and your record all match.

Back up wallet descriptors and configuration Expert

An output descriptor describes exactly how a wallet derives addresses: script type, keys (xpubs), fingerprints and derivation paths, plus quorum for multisig.

  • Single-sig: the seed plus "address type + path" is usually enough, but a descriptor removes guesswork.
  • Multisig: essential. Without all xpubs and the exact script, even M valid seeds may not be enough to find the coins.
  • Store a printed copy (or QR) with every key, plus encrypted digital copies. It reveals balances, so treat it as private.
  • Coordinators such as Sparrow and Nunchuk export descriptors and printable PDF backups.
Example (fictional, shortened): wsh(sortedmulti(2,[aaaaaaaa/48'/0'/0'/2']xpub…A/<0;1>/*,[bbbbbbbb/48'/0'/0'/2']xpub…B/<0;1>/*,[cccccccc/48'/0'/0'/2']xpub…C/<0;1>/*))

Decoy and duress wallets Expert

Pros

  • Something plausible to hand over under threat
  • Hides the main balance from casual discovery

Cons

  • Sophisticated attackers know about passphrases
  • More to manage and explain

Pitfalls

  • Empty decoys are unconvincing — keep a believable balance
  • Forgetting which is which

Options

  • Empty-passphrase wallet with small funds
  • COLDCARD duress/trick PINs
  • Seed XOR parts as standalone wallets

Primary sources for this page

Educational information only, not tax, legal or financial advice.

Last reviewed: · Educational information only — verify current details with official sources.