Update of the expected version for each document

rfc/0010_Duniter_Blockchain_Protocol_V12.md

@@ -354,7 +354,7 @@ Field | Description
 
 A [Membership](#membership) is to be considered having valid format if:
 
-* `Version` equals `2`
+* `Version` equals `10`
 * `Type` equals `Membership` value.
 * `Currency` is a valid currency name
 * `Issuer` is a public key
@@ -423,7 +423,7 @@ Field | Description
 
 A Transaction structure is considered *valid* if:
 
-* Field `Version` equals `2` or `3`.
+* Field `Version` equals `10`.
 * Field `Type` equals `Transaction`.
 * Field `Currency` is not empty.
 * Field `Blockstamp` is a block UID
@@ -1033,7 +1033,7 @@ The document must be ended with a `BOTTOM_SIGNATURE` [Signature](#signature).
 
 ##### Data
 
-* `Version` equals `6`
+* `Version` equals `10` or `11`
 * `Type` equals `Block`
 
 ### Peer
@@ -1101,7 +1101,7 @@ To be valid, a peer document must match the following rules:
 
 ##### Format
 
-* `Version` equals `2` or `3`
+* `Version` equals `10`
 * `Type` equals `Peer`
 * `Currency` is a valid currency name
 * `PublicKey` is a [Public key](#publickey)
@@ -1249,7 +1249,7 @@ A block cannot contain revocations whose signature does not match the revocation
 * A transaction must have at least 1 source
 * A transaction cannot have `SIG(INDEX)` unlocks with `INDEX >= ` issuers count.
 * A transaction **must** have signatures matching its content **for each issuer**
-* A transaction's version must be equal to `3`
+* Transaction's version must be equal to `10`.
 * Signatures count must be the same as issuers count
 * Signatures are ordered by issuer
 * Signatures are made over the transaction's content, signatures excepted