BIP 48 guide covering its Deployed status, m/48 hierarchy, hardened script type, nested and native SegWit branches, key sorting, recovery and compatibility.
This guide explains BIP 48 Multi-Script Hierarchy for Multi-Sig Wallets in plain English. It covers the problem behind the BIP, why it matters and whether the proposal is part of Bitcoin today.
BIP 48 Multi-Script Hierarchy for Multi-Sig Wallets: The hierarchy is m / 48 hardened / coin type hardened / account hardened / script type hardened / change / address index. Preserve every hardening marker exactly.
A node operator is checking BIP 48 Multi-Script Hierarchy for Multi-Sig Wallets. Script type 1 represents nested P2SH-P2WSH and 2 native P2WSH.
The BIP is Deployed, Applications and Specification. It standardises an existing wallet derivation practice and does not alter Bitcoin consensus.
The hierarchy is m / 48 hardened / coin type hardened / account hardened / script type hardened / change / address index. Preserve every hardening marker exactly.
Coin type separates mainnet zero from testnet one in the specification. Accounts increment from zero and should isolate different wallet identities and policies.
Script type 1 represents nested P2SH-P2WSH and 2 native P2WSH; native P2WSH is the recommended default. Do not infer future script values without a versioned standard.
BIP 48 relies on deterministic key sorting through BIP 67 so all participants derive the same script. Store cosigner origins and verify resulting key order rather than sorting display strings.
Change zero is external receiving and one internal change; address indexes increase from zero. Coordinate issuance and preserve gap and highest-used evidence for both branches.
Developers test the proposal with made-up data on an isolated test network. They check normal cases and deliberately invalid cases. Different implementations should reach the same result before anyone relies on the proposal.
BIP 48 Multi-Script Hierarchy for Multi-Sig Wallets: The hierarchy is m / 48 hardened / coin type hardened / account hardened / script type hardened / change / address index.
The BIP is Deployed, Applications and Specification. It standardises an existing wallet derivation practice and does not alter Bitcoin consensus.
The hierarchy is m / 48 hardened / coin type hardened / account hardened / script type hardened / change / address index.
Coin type separates mainnet zero from testnet one in the specification. Accounts increment from zero and should isolate different wallet identities and policies.
BIP 48 makes multisig derivation more interoperable by giving script type an explicit hardened branch. Safe recovery still requires the entire multisig policy and every cosigner record, not one path or seed.
Check the current specification status and the documentation for the exact implementation you operate before moving production funds or changing a mining node.
BIP 450 guide to Draft Formosa themed mnemonic stories, entropy and checksum mapping, theme JSON, BIP39 conversion, passphrases and recovery safety.
BIP 393 guide to Draft descriptor annotations for birth height, gap limit and Silent Payment max label, checksum rules, parsing and recovery safety.
BIP 392 guide to Draft sp() descriptors, spscan and spspend encodings, watch-only and full-wallet forms, key origins, recovery and validation.
Join the ASIC Mining Discussion
Members can read and join the discussion
Log in to read comments from other miners. Create a free account if you would like to ask a question or share your experience.
Membership helps us protect the discussion from spam and keep answers useful.