Please note: In Ğ1 and Ğ1-test networks, the V10 and V11 blocks and some transactions in these blocks are signed with a buggy version of TweetNaCl: [version 20131229](http://tweetnacl.cr.yp.to/software.html). As a result, some V10 and V11 blocks have an invalid signature (as well as some transactions in V10 or V11 blocks).
#### Line endings
No new line character exists in a signature. However, a signature may be followed by a new line character, hence denoting the end of the signature.
...
...
@@ -1033,7 +1035,7 @@ The document must be ended with a `BOTTOM_SIGNATURE` [Signature](#signature).
##### Data
* `Version` equals `10` or `11`
* `Version` equals `10` or `11` or `12`
* `Type` equals `Block`
### Peer
...
...
@@ -1226,6 +1228,9 @@ If HEAD.number == 0, HEAD.dividend must equal `null`.
* A block must have a valid signature over the content from `Hash: ` to `Nonce: NONCE\n`, where the associated public key is the block's `Issuer` field.
Please note: In Ğ1 and Ğ1-test networks, the V10 and V11 blocks and some transactions in these blocks are signed with a buggy version of TweetNaCl: [version 20131229](http://tweetnacl.cr.yp.to/software.html). As a result, some V10 and V11 blocks have an invalid signature (as well as some transactions in V10 or V11 blocks).
A complete list of invalid signatures in each currency will be compiled when the Ğ1 and Ğ1-test networks have successfully migrated to DUBP v12.
##### Dates
* A block must have its `Time` field be between [`MedianTime` ; `MedianTime` + `maxAcceleration`].
...
...
@@ -1254,6 +1259,8 @@ A block cannot contain revocations whose signature does not match the revocation
* Signatures are ordered by issuer
* Signatures are made over the transaction's content, signatures excepted
Please note: In Ğ1 and Ğ1-test networks, some transactions in V10 and V11 blocks have an invalid signature. A complete list of invalid signatures in each currency will be compiled when the Ğ1 and Ğ1-test networks have successfully migrated to DUBP v12.