BIP 0018: Difference between revisions

From Bitcoin Wiki
Jump to navigation Jump to search
Luke-jr (talk | contribs)
Created page with "<pre> BIP: 18 Title: hashScriptCheck Author: Luke Dashjr <luke+bip17@dashjr.org> Status: Draft Type: Standards Track Created: 27-01-2012 </pre> Details to be fina..."
 
Luke-jr (talk | contribs)
No edit summary
Line 7: Line 7:
   Created: 27-01-2012
   Created: 27-01-2012
</pre>
</pre>
==Abstract==
This BIP modifies the basic format of transaction inputs and outputs, replacing the current scriptSig and scriptPubKey (scripts executed to validate a transaction) with new contents: dataSig, scriptCheck, and hashScriptCheck.
==Motivation==
The purpose of pay-to-script-hash is to move the responsibility for supplying the conditions to redeem a transaction from the sender of the funds to the redeemer.
The benefit is allowing a sender to fund any arbitrary transaction, no matter how complicated, using a fixed-length 20-byte hash that is short enough to scan from a QR code or easily copied and pasted.
==Specification==


Details to be finalized when BIP 16 or 17 is deployed.
Details to be finalized when BIP 16 or 17 is deployed.
==See Also==
* The [[BIP 0013|Address format for Pay to Script Hash BIP]]
* [[BIP 16: Pay to Script Hash (aka "/P2SH/")]]
* [[BIP 17: CHECKHASHVERIFY (P2SH)]]
* M-of-N Multisignature Transactions [[BIP 0011|BIP 11]]

Revision as of 23:07, 7 March 2012

  BIP: 18
  Title: hashScriptCheck
  Author: Luke Dashjr <luke+bip17@dashjr.org>
  Status: Draft
  Type: Standards Track
  Created: 27-01-2012

Abstract

This BIP modifies the basic format of transaction inputs and outputs, replacing the current scriptSig and scriptPubKey (scripts executed to validate a transaction) with new contents: dataSig, scriptCheck, and hashScriptCheck.

Motivation

The purpose of pay-to-script-hash is to move the responsibility for supplying the conditions to redeem a transaction from the sender of the funds to the redeemer.

The benefit is allowing a sender to fund any arbitrary transaction, no matter how complicated, using a fixed-length 20-byte hash that is short enough to scan from a QR code or easily copied and pasted.

Specification

Details to be finalized when BIP 16 or 17 is deployed.

See Also