They also reduce the complexity of the encoding, and shift the burden in terms of fees from the sender to the recipient – after all it’s their request to have the complexity in the conditions for the release of the funds.
This is done by transferring the script used to spend the transactions to the <ScripSig> and making the <ScriptPubKey> hold a hash of the script. This means that a new address has been created – a script address.
Script addresses are not made through the usual process of elliptic curve cryptography but are instead the hash of the <ScriptPubKey> of a multi signature transaction. A script address is appended with a value of five before being hashed, resulting in hashed script addresses starting with the number 3 – remember that standard Bitcoin addresses start with a 1 – with other variances for the testnet.
Structuring P2SH transactions should be done with care as an error can make the transaction unspendable. Another important point is that the details of the transaction script are not stored in the blockchain, only the hash, and therefore the creator of the transaction must keep a copy of the script or remember the route to generate the specific hash.
- Bitcoin Transactions - Pay-to-Public-Key?
- Bitcoin Transactions – Multi Signature Transactions?
- What is a Bitcoin block?
- Bitcoin Transactions Pay-to-Address - Pay-to-Public-Key-Hash?
- What is a Bitcoin Fork?
- How does a hashing algorithm work?
- Bitcoin Transactions – Scriptsig and Scriptpubkey – locking and unlocking a transaction?