From dd18e39624cd15897cebaa738577b87e30bf23ad Mon Sep 17 00:00:00 2001 From: Omar Shibli Date: Mon, 18 Sep 2017 15:58:21 +0300 Subject: [PATCH] updated compatibility section --- bip-pay-to-contract-labeled-wallets.mediawiki | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/bip-pay-to-contract-labeled-wallets.mediawiki b/bip-pay-to-contract-labeled-wallets.mediawiki index f80cf1bf..faeea9b4 100644 --- a/bip-pay-to-contract-labeled-wallets.mediawiki +++ b/bip-pay-to-contract-labeled-wallets.mediawiki @@ -16,8 +16,6 @@ Utilizing hierarchical deterministic wallets as described in BIP-0032 and the "Purpose Field" in BIP-0043, this document specifies the multiparty pay-to-contract key derivation scheme outlined by Ilja Gerhardt and Timo Hanke.[0] -This BIP is a particular application of BIP-0043 and is based on BIP-0044. - The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119. ==Motivation== @@ -234,7 +232,8 @@ Verification operation will succeed only if we use identical documents to ones t ==Compatibility== -This specification is BIP-0043 compliant. Communication between payor and payee as well as hashing the contract and generating the path requires significant modification to the wallet. +This specification is not backward compatibile with BIP32 specification, the proposed derivation scheme in this BIP is a BIP32 compliant. +Communication between payor and payee as well as hashing the contract and generating the path requires significant modification to the wallet. ==Reference implementations==