Three independent signing devices placed on separate mats, with two screens illuminated, editorial illustration
BIP 388 / MULTISIG

A policy a signing device can understand.

Wallet policies describe descriptor-based accounts using a compact template and separate key information.

Read the explanation
← All standards

Why it exists

BIP 388 describes wallet accounts in a compact form suited to signing devices. It separates the script template from the list of keys, helping a user and a small device review the policy without repeatedly displaying long extended public keys.

How it works

A descriptor template uses placeholders such as @0 for entries in a separate key-information list. The policy includes the receive and change derivation behavior, letting the signer recognize wallet outputs rather than trusting a computer to label them as change.

A user can review and register a policy before using it for transactions. The device must check that the policy and key information match what was approved. The format restricts general descriptor syntax to patterns that suit account-based wallet behavior.

PUT IT IN CONTEXT

A practical example

A 2-of-3 policy can show a compact threshold template referencing three separately identified cosigner records. During a payment, the signer can determine whether an output belongs to that registered account and distinguish it from the recipient payment.

What to keep in mind

Policy registration is not a seed backup and does not make arbitrary host-provided information trustworthy. A registered wallet can still be misconfigured. Different devices support different policy subsets, and a wallet-policy template is not itself an ordinary descriptor that every desktop wallet will import.

Status & implementation

The BIP is Complete and lists implementations in Ledger, BitBox02, Jade and BTCPay Server, with differing supported subsets. Adoption is opt-in. For interchange with software that does not understand wallet policies, the specification recommends exporting ordinary descriptors.

Specification status: Complete · Sources checked 13 November 2026

Read the sources

Put the standard in context.

Explore the practical guide

Find your next answer.

Search the complete field guide · Esc to close