diff options
| author | Omar Shibli <omarshib@gmail.com> | 2017-09-16 08:55:14 +0300 |
|---|---|---|
| committer | Omar Shibli <omarshib@gmail.com> | 2017-09-16 08:55:14 +0300 |
| commit | 39a5c1bf7e458f281949e75da691676decaabe86 (patch) | |
| tree | 7ec032bb6e4370a0e9b04a8490465820179da206 | |
| parent | 3afd4bd57f985ddb5758dbde0fb7ffc11061c8bd (diff) | |
| download | bips-39a5c1bf7e458f281949e75da691676decaabe86.tar.xz | |
updated license
| -rw-r--r-- | bip-draft.mediawiki | 7 |
1 files changed, 4 insertions, 3 deletions
diff --git a/bip-draft.mediawiki b/bip-draft.mediawiki index 41e718d..65a9919 100644 --- a/bip-draft.mediawiki +++ b/bip-draft.mediawiki @@ -9,6 +9,7 @@ Status: Draft Type: Informational Track Created: 2017-07-17 + License: BSD-2-Clause </pre> * 999 is a temporary BIP number. @@ -23,9 +24,9 @@ The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "S ==Motivation== -A Bitcoin transaction represents a "real world" contract between two parties transferring value. Counterparties in a business interaction traditionally keep track of a payment with bills (invoices) and receipts. Delivery of a good is made by the payee once the payor has signed the receipt, agreeing to pay for the items on the invoice. Gerhardt and Hanke [0] formulate this interaction within the confines of the Bitcoin protocol using homomorphic payment addresses and the multiparty pay-to-contract protocol. +A Bitcoin transaction represents a "real world" contract between two parties transferring value. Counterparties in a business interaction traditionally keep track of a payment with bills (invoices) and receipts. Delivery of a good is made by the payee once the payor has signed the receipt, agreeing to pay for the items on the invoice. Gerhardt and Hanke [0] formulate this interaction within the confines of the Bitcoin protocol using homomorphic payment addresses and the multiparty pay-to-contract protocol. -The protocol is constructed in such a way that all parties have cryptographic proof of both who is being paid and for what. Using the technique described in this BIP, an address can be provably derived from the terms of a contract and the payee's public key. This derivation scheme does not bloat the UTXO and is completely hidden to network participants; the derived address looks like any other P2(W)PKH or P2(W)SH address. Redemption of the funds requires knowledge of the contract and the payee's private key. +The protocol is constructed in such a way that all parties have cryptographic proof of both who is being paid and for what. Using the technique described in this BIP, an address can be provably derived from the terms of a contract and the payee's public key. This derivation scheme does not bloat the UTXO and is completely hidden to network participants; the derived address looks like any other P2(W)PKH or P2(W)SH address. Redemption of the funds requires knowledge of the contract and the payee's private key. This scheme utilizes the foundations of BIP-0032, providing a consistent way for preexisting wallet developers to implement the specification. @@ -247,4 +248,4 @@ Verification operation will succeed only if we use identical documents to ones t ==Copyright== -This document is placed in the public domain. +This BIP is licensed under the 2-clause BSD license. |