updated compatibility section

Author: omarshibli

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==