Pay-to-Script-Hash Address

Overview

A Pay-to-Script-Hash Address lets a payer send funds to a compact address while the recipient defines more complex spending conditions. In Bitcoin’s P2SH design, the address encodes a hash of a redeem script. The locking script checks that the revealed script matches that hash, then evaluates the signatures, timelocks, or other conditions contained in the redeem script. The payer does not need to know the full policy when creating the payment.

This design shifted the burden of complex script construction from the sender to the recipient. A merchant could publish one address representing a Multisignature Address, escrow rule, or recovery policy, while ordinary wallet software created a standard-looking output. When spending, the recipient reveals the script and the data needed to satisfy it, making the policy visible at that time.

The term should not be treated as a universal address type across all blockchains. Bitcoin also supports native SegWit and Taproot output forms, each with different encoding and fee characteristics. A script address is likewise not the same as a smart-contract account on an account-based chain. Address validation must identify the network, script version, and supported wallet format before funds are sent.

Payment systems should store the exact address and network rather than inferring ownership from its visual prefix alone. They should verify checksum and format, generate payment URIs correctly, and avoid converting one address type into another without protocol-aware tooling. When a pay-to-script output is spent, monitoring should validate the resulting Transaction Signature and script execution, not merely the presence of a redeem script.