Data validation and storage

1. A method for recording data describing a first entity, the data endorsed by a second entity, the method comprising the steps of:

at the second entity:

validating data describing the first entity, wherein an identifier is associated with the data, the identifier being generated from a public key of the first entity;

cryptographically signing data corresponding with the data describing the first entity using at least a private key of the second entity; and

posting a first transaction to a block chain including the cryptographically signed data;

at a third entity:

validating the data describing the first entity;

cryptographically signing data corresponding with the data describing the first entity using a private key of the third entity;

posting a second transaction including the data cryptographically signed by the third entity; and

at a fourth entity:

determining that the data describing the first entity is sufficiently validated if one or more characteristics of each of the second entity and third entity meet validation criteria.

2. The method of claim 1 further comprising the step of the first entity publishing the data describing the first entity.

3. The method according to claim 1 further comprising the step of adding a block containing one or more posted transactions to the block chain, wherein the step of adding a block to the block chain further comprises hashing at least a part of the block chain and the one or more posted transactions, wherein the step of adding the block to the block chain is carried out by the fourth entity and the fourth entity adding a transaction to the block comprising a public key of the fourth entity.

4. The method according to claim 3 , wherein the step of adding a block to the block chain further comprises storing the block in a Merkle tree structure.

5. The method according to claim 1 , wherein the block chain comprises a block having a transaction including a public key of the second entity.

6. The method according to claim 1 further comprising the step of posting a further transaction containing a public key of a fifth entity able to endorse data of other entities.

7. The method according to claim 1 , wherein the identifier of the data is further generated from a random factor generated by the first entity.

8. The method according to claim 1 further comprising the step of hashing at least a part of the data describing the first entity.

9. The method according to claim 1 , wherein the data corresponding with the data describing the first entity includes an identifier of the data describing the first entity, wherein the data describing the first entity is stored by posting a transaction to the block chain separate from the transaction posted including the data cryptographically signed by the second entity.

10. A non-transitory computer-readable medium carrying a computer program comprising program instructions that, when executed on a computer, cause the computer to perform the method of claim 1 .

11. The method of claim 1 , wherein the data describing the first entity includes an assertion by the first entity about an attribute of the first entity.

12. A system for recording data describing a first entity, the data endorsed by a second entity, the system comprising:

one or more computer processors; and

memory storing executable instructions configured to, when executed by the one or more processors, cause the system to:

at the second entity:

validate data describing the first entity, wherein an identifier is associated with the data, the identifier being generated from a public key of the first entity;

cryptographically sign data corresponding with the data describing the first entity using at least a private key of the second entity; and

post a first transaction to a block chain including the cryptographically signed data;

at a third entity:

validate the data describing the first entity;

cryptographically sign data corresponding with the data describing the first entity using a private key of the third entity;

post a second transaction including the data cryptographically signed by the third entity; and

at a fourth entity:

determine that the data describing the first entity is sufficiently validated if one or more characteristics of each of the second entity and third entity meet validation criteria.

13. The system of claim 12 , wherein executable instructions further cause the system to:

receive an identifier of data describing the first entity;

retrieve an entry from the block chain based on the received identifier;

authenticate the entry using a public key of the second entity; and

extract the data describing the first entity from the retrieved entry.

14. The system according to claim 12 , wherein the first entity publishes the data describing the first entity.

15. The system of claim 12 , wherein executable instructions further cause the system to add a block containing one or more posted transactions to the block chain, wherein the step of adding a block chain further comprises hashing at least a part of the block chain and the one or more posted transactions, wherein the step of adding the block to the block chain is carried out by the fourth entity and the fourth entity adding a transaction to the block comprising a public key of the fourth entity.

16. The system of claim 15 , wherein when the executable instructions cause the system to add a block to the block chain, the block is stored in a Merkle tree structure.

17. The system of claim 12 , wherein the block chain comprises a block having a transaction including a public key of the second entity.

18. The system of claim 12 , wherein executable instructions further cause the system to post a further transaction containing a public key of a fifth entity able to endorse data of other entities.

19. The system of claim 12 , wherein the identifier of the data is further generated from a random factor generated by the first entity.

20. The system of claim 12 , wherein executable instructions further cause the system to hash at least a part of the data describing the first entity.

21. The system of claim 12 , wherein the data corresponding with the data describing the first entity includes an identifier of the data describing the first entity, wherein the data describing the first entity is stored by posting a transaction to the block chain separate from the transaction posted including the data cryptographically signed by the second entity.

22. The system of claim 12 , wherein the data describing the first entity includes an assertion by the first entity about an attribute of the first entity.