Account (HD Wallet)

In a hierarchical deterministic wallet, an account is a distinct branch of the key tree that holds a self-contained pool of funds. Under the BIP44 path structure m/purpose'/coin_type'/account'/change/address_index, the account sits at the third level and is hardened. Accounts are numbered sequentially from 0, and each carries its own external (receive) and internal (change) address chains — a complete, independent sub-wallet grown from the same seed.

Why separate accounts exist

Accounts let a single seed phrase back several independent identities or money pools without ever mixing their coins — much like holding multiple bank accounts under one login, except the separation is enforced by key derivation rather than a bank's database. Typical splits: personal spending, business income, a donation address, mining payouts, and long-term savings you want operationally distinct. The separation is real at the UTXO level, which matters for privacy and bookkeeping: coins received into account 0 never automatically commingle with account 1's, and a business account's history can be disclosed to an accountant without exposing your savings. It is worth being precise about the privacy claim, though — all accounts still descend from one seed, so this is compartmentalization of visibility, not of custody. Whoever holds the seed holds every account.

Hardened isolation and watch-only use

Because the account level uses hardened derivation, compromise is contained: exposing one account's extended keys does not endanger sibling accounts or the master seed. Each account exports its own extended public key (xpub), so you can hand a single account's xpub to an accountant, a point-of-sale system, or a watch-only monitoring node while the rest of the wallet stays entirely private — and no private key material leaves the hardware wallet at all. This is the pattern behind serious self-custody setups: keys cold, per-account xpubs warm, and each observer seeing only the slice it needs.

Account discovery and practical discipline

During recovery, wallets perform account discovery: scan account 0's address chains for history, proceed to account 1 only if account 0 shows activity, and stop at the first account with no transactions. The standard's gap-limit logic means a recovering wallet will not find account 5 if accounts 1–4 were never used — so create accounts sequentially and don't skip numbers. Two further habits pay off: record which accounts you actually use (a seed backup restores keys, not your mental map of what each account was for), and remember that not all wallet software exposes multiple accounts equally well, so test a restore before you depend on the scheme. For a home miner, a dedicated payout account is a small structure that keeps mining income cleanly auditable and separate from spending — self-custody with bookkeeping built into the key tree itself. The account model is built directly on BIP32's tree derivation and is one of the quiet reasons a single properly backed-up seed can run an entire financial life. It is also worth distinguishing accounts from the adjacent tool for the job: a passphrase-protected wallet creates an entirely separate seed-derived universe (different keys, deniable, and lost forever if the passphrase is), while accounts are branches inside one universe, recoverable from the seed alone. Use accounts for organization and disclosure control; reserve passphrases for genuine security compartmentalization. Confusing the two — expecting account separation to hide funds from someone holding your seed, or expecting a forgotten passphrase to be recoverable — is one of the classic self-custody mistakes, and it costs real money every year. Know which boundary each tool draws, document your own setup for your future self, and the account model will quietly do exactly what it was designed to do.