Why it exists
BIP 329 defines a portable wallet-label export format. Recovery words can recreate keys, but they do not recreate the notes explaining who paid you, which output belongs to a project, or why a coin was deliberately excluded from spending.
How it works
The file uses UTF-8 JSON Lines: each line is a separate JSON object. A record identifies its type, reference and label, with optional origin information. Record types distinguish transactions, addresses, keys, inputs, outputs and other supported wallet objects.
An output reference identifies a transaction output rather than merely an address. This makes it possible to preserve useful context for individual UTXOs. The format can also record whether an output is spendable according to wallet preferences; that flag is local metadata, not a Bitcoin consensus restriction.
A practical example
A label might identify one received output as a customer payment and another as a personal transfer. After moving wallets, importing those records can restore the context needed to avoid accidentally combining unrelated coins. The keys and transaction data still need to be restored separately.
What to keep in mind
The export can reveal counterparties and financial relationships, even without private keys. Protect it as sensitive wallet information. A receiving application may ignore unsupported record types or fields, so inspect important labels and frozen-coin settings after importing.
Status & implementation
The specification remains Draft and links to the Python-BIP329 reference package. Its import rules explicitly permit ignoring unsupported records. A successful file import therefore does not prove complete preservation: compare important labels and frozen-output settings in the destination wallet.
Specification status: Draft · Sources checked 13 November 2026
