BIP 13 P2SH address format explained: understand Base58Check version bytes, script hashes, network validation and the relationship to BIP 16.
This guide explains BIP 13 P2SH address format in plain English. It covers the problem behind the BIP, why it matters and whether the proposal is part of Bitcoin today.
BIP 13 P2SH address format: P2SH remains part of Bitcoin, including nested SegWit constructions, but native SegWit and Taproot addresses offer different weight, error-detection and privacy properties.
A node operator is checking BIP 13 P2SH address format. Funds are recoverable only when the spender has the complete redeem script and the necessary keys.
A recipient may require multisignature or another redeem script, but a payer should not need to parse that policy. A P2SH address encodes a hash commitment that ordinary wallet interfaces can handle like a destination. The recipient bears responsibility for preserving the redeem script and later satisfying it; the address alone cannot reconstruct a lost policy.
The payload contains a network-specific version byte and the 20-byte HASH160 of the redeem script, followed by a checksum before Base58 encoding. Mainnet and test networks use different version values. Implementations should decode and verify the checksum and network rather than accepting a familiar first character as proof that the entire string is valid.
BIP 13 describes how applications represent and recognise the destination. BIP 16 specifies the scriptPubKey pattern and the upgraded validation that checks the redeem-script hash and executes the supplied script. An application can parse an address without proving that its node enforces or relays the related spending rules correctly.
Funds are recoverable only when the spender has the complete redeem script and the necessary keys. A seed backup might reproduce keys but not an independently assembled multisignature script, key order or recovery branch. Wallet descriptors and tested exports should accompany backups. Showing the P2SH address in a screenshot is not enough recovery evidence.
A wrong-network address can decode correctly but be unusable for the intended payment. Clipboard malware can substitute a different valid address with a correct checksum. QR codes can carry the same substitution. Wallets should display the decoded network and full destination, and high-value procedures should verify through an independently trusted channel.
P2SH remains part of Bitcoin, including nested SegWit constructions, but native SegWit and Taproot addresses offer different weight, error-detection and privacy properties. A wallet should identify the exact output type rather than call everything a multisig address. Migration must consider hardware support, recovery policy and fee implications.
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 13 P2SH address format: P2SH remains part of Bitcoin, including nested SegWit constructions, but native SegWit and Taproot addresses offer different weight, error-detection and privacy properties.
A recipient may require multisignature or another redeem script, but a payer should not need to parse that policy.
The payload contains a network-specific version byte and the 20-byte HASH160 of the redeem script, followed by a checksum before Base58 encoding.
BIP 13 describes how applications represent and recognise the destination. BIP 16 specifies the scriptPubKey pattern and the upgraded validation that checks the redeem-script hash and executes the supplied script.
BIP 13 made complex script commitments usable as compact wallet destinations, while BIP 16 supplies their consensus meaning. Safe P2SH operation depends on strict network decoding, protected redeem-script or descriptor backups and independent payment verification.
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.