Solo Mining Calculator: Estimate Odds and Timeframes
Use a solo mining calculator correctly: enter productive hashrate, network conditions, uptime and time horizon, then read expected time and probability without.
Read article
ASIC mining knowledge centre
BIP 13 P2SH Address Format Explained for Bitcoin Wallets
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.
TL;DR
- What it is: BIP 13 P2SH address format defines the familiar Base58Check representation used to pay a hash of a redeem script without asking the sender to understand that script. BIP 13 is the application-layer encoding, while BIP 16 defines the consensus validation of pay-to-script-hash outputs.
- Why it matters: 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.
- Current position: BIP 13 P2SH address format defines the familiar Base58Check representation used to pay a hash of a redeem script without asking the sender to understand that script.
What this means in simple English
A BIP is a document that proposes or explains a Bitcoin idea, standard or rule. A BIP number does not mean the idea is active. Some BIPs are widely used, while others are drafts or historical proposals.
You do not need to read code to understand the main point. Start with the status, the problem being addressed and the practical effect on ordinary users, wallets, miners or node operators.
Simple example
Think of the transaction as a form passed between several authorised signers. Each person or device checks the same payment details before adding approval. Passing the form around does not make the payment safe unless every signer checks what it contains.
Key terms in plain English
- BIP:
- Bitcoin Improvement Proposal: a document describing a proposed rule, standard or process. Its status must be checked separately.
- Consensus:
- The shared rules full nodes use to decide whether blocks and transactions are valid.
- Taproot:
- A Bitcoin upgrade that added new signature and script options for spending outputs.
- Node:
- A computer running Bitcoin software that checks data and communicates with other peers.
Why a script needed an address
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.
Hash and Base58Check construction
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 and BIP 16 have different jobs
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.
Redeem-script custody
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 sufficient recovery evidence.
Network and substitution risks
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.
Legacy and modern script types
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.
How specialists test it
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.
Frequently asked questions
What is BIP 13 P2SH Address Format Explained for Bitcoin Wallets?
BIP 13 defines the familiar Base58Check representation used to pay a hash of a redeem script without asking the sender to understand that script. BIP 13 is the application-layer encoding, while BIP 16 defines the consensus validation of pay-to-script-hash outputs.
Is BIP 13 Explained for Bitcoin Wallets active or supported today?
BIP 13 defines the familiar Base58Check representation used to pay a hash of a redeem script without asking the sender to understand that script.
Why does BIP 13 Explained for Bitcoin Wallets matter?
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.
Do beginners need to use the technical details?
No. Most readers only need to understand the idea and its current status. Developers and node operators can use the primary sources when they need the exact technical rules.
Conclusion
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.
Primary sources
Check the current specification status and the documentation for the exact implementation you operate before moving production funds or changing a mining node.
On this page
Search More Guides
BIP-110 Explained: Rules, Signalling and Why It Closed
BIP-110 Explained made simple. See the main facts, costs, risks and practical checks before you make a decision.
Read article
Bitcoin Core 29.4 Release: Chainstate Disk I/O Guide
Bitcoin Core 29.4 guide covering repeated chainstate rewrites, regular compaction, LevelDB seek compaction, transaction-data lifetime and wallet sizing fixes.
Read article
Need Advice for Your Mining Setup?
Use our guidance to build your shortlist, then speak to our team when you want help comparing hardware, power, hosting or repairs.