Systems, methods, and apparatuses for adding a document history graph and corresponding hash value to a blockchain in a cloud based computing environment

1. A method performed by a hosted computing environment, the hosted computing environment having at least one processor and a memory therein, the method comprising:

receiving, at a web server in the hosted computing environment, a document history graph;

performing, at the web server, a hash function, providing the document history graph as input to the hash function, the hash function providing a hash value as output;

generating, at a blockchain services interface in the hosted computing environment, a blockchain block that includes the hash value in a block payload hash field and the document history graph in a block payload field of the blockchain block, wherein the blockchain block is generated independently of one or more of: (i) a user client device, and (ii) an application executing on a user client device;

proposing, via a blockchain consensus manager in the hosted computing environment, adding the blockchain block to a private blockchain;

receiving at the blockchain consensus manager an indication of consensus among authorized blockchain nodes in the private blockchain to add the blockchain block to the private blockchain; and

adding, via a block validator in the hosted computing environment, the blockchain block to the private blockchain responsive to receiving the indication of consensus.

2. The method of claim 1 , wherein performing the hash function comprises performing the hash function in response to the web server receiving from a document management application an indication of change to the document history graph.

3. The method of claim 1 , wherein performing the hash function comprises periodically performing the hash function without regard to the web server receiving an indication of change to the document history graph.

4. The method of claim 1 , wherein generating, at the blockchain services interface in the hosted computing environment, the blockchain block, comprises generating the blockchain block in response to the web server receiving from a document management application an indication of change in the document history graph.

5. The method of claim 1 , wherein generating, at the blockchain services interface in the hosted computing environment, the blockchain block, comprises periodically generating the blockchain block without regard to the web server receiving from a document management application an indication of change in the document history graph.

6. The method of claim 1 , wherein receiving, at the web server in the hosted computing environment, the document history graph, comprises:

receiving an initial version of a document and creating a node in the document history graph, the node comprising metadata for the initial version of the document;

receiving additional versions of the document and creating corresponding nodes in the document history graph each comprising metadata for the respective versions of the document; and

receiving a final version of the document and creating a leaf node in the document history graph comprising metadata for the final version of the document.

7. The method of claim 1 , wherein the metadata for each of the initial, respective, and final versions of the document comprises a previous version number associated with an earlier version of the document dating back to the root node, a version number for the version of the document, a pointer to a location in a data store at which the version of the document is stored, a hash value of the version of the document, and a signature of one or more signatories to the version of the document.

8. A system to execute within a hosted computing environment, wherein the system comprises a processor and a memory to execute instructions on the system, the instructions providing:

means for receiving, at a web server in the hosted computing environment, a document history graph;

means for performing, at the web server, a hash function, providing the document history graph as input to the hash function, the hash function providing a hash value as output;

means for generating, at a blockchain services interface in the hosted computing environment, a blockchain block that includes the hash value in a block payload hash field and the document history graph in a block payload field of the blockchain block, wherein the blockchain block is generated independently of one or more of: (i) a user client device, and (ii) an application executing on a user client device;

means for proposing, via a blockchain consensus manager in the hosted computing environment, adding the blockchain block to a private blockchain;

means for receiving at the blockchain consensus manager an indication of consensus among authorized blockchain nodes in the private blockchain to add the blockchain block to the private blockchain; and

means for adding, via a block validator in the hosted computing environment, the blockchain block to the private blockchain responsive to receiving the indication of consensus.

9. The system of claim 8 , wherein the means for performing the hash function comprises means for performing the hash function in response to the web server receiving from a document management application an indication of change to the document history graph.

10. The system of claim 8 , wherein the means for performing the hash function comprises means for periodically performing the hash function without regard to the web server receiving an indication of change to the document history graph.

11. The system of claim 8 , wherein the means for generating, at the blockchain services interface in the hosted computing environment, the blockchain block, comprises means for generating the blockchain block in response to the web server receiving from a document management application an indication of change in the document history graph.

12. The system of claim 8 , wherein the means for generating, at the blockchain services interface in the hosted computing environment, the blockchain block, comprises means for periodically generating the blockchain block without regard to the web server receiving from a document management application an indication of change in the document history graph.

13. The system of claim 8 , wherein the means for receiving, at the web server in the hosted computing environment, the document history graph, comprises:

means for receiving an initial version of a document and creating a node in the document history graph, the node comprising metadata for the initial version of the document;

means for receiving additional versions of the document and creating corresponding nodes in the document history graph each comprising metadata for the respective versions of the document; and

means for receiving a final version of the document and creating a leaf node in the document history graph comprising metadata for the final version of the document.

14. Non-transitory computer readable storage media having instructions stored thereon that, when executed in a hosted computing environment by a processor and a memory therein, cause the hosted computing environment to perform the following operations:

receiving, at a web server in the hosted computing environment, a document history graph;

performing, at the web server, a hash function, providing the document history graph as input to the hash function, the hash function providing a hash value as output;

generating, at a blockchain services interface in the hosted computing environment, a blockchain block that includes the hash value in a block payload hash field and the document history graph in a block payload field of the blockchain block, wherein the blockchain block is generated independently of one or more of: (i) a user client device, and (ii) an application executing on a user client device;

proposing, via a blockchain consensus manager in the hosted computing environment, adding the blockchain block to a private blockchain;

receiving at the blockchain consensus manager an indication of consensus among authorized blockchain nodes in the private blockchain to add the blockchain block to the private blockchain; and

adding, via a block validator in the hosted computing environment, the blockchain block to the private blockchain responsive to receiving the indication of consensus.

15. The non-transitory computer readable storage media of claim 14 , wherein performing the hash function comprises performing the hash function in response to the web server receiving from a document management application an indication of change to the document history graph.

16. The non-transitory computer readable storage media of claim 14 , wherein performing the hash function comprises periodically performing the hash function without regard to the web server receiving an indication of change to the document history graph.

17. The non-transitory computer readable storage media method of claim 14 , wherein generating, at the blockchain services interface in the hosted computing environment, the blockchain block, comprises generating the blockchain block in response to the web server receiving from a document management application an indication of change in the document history graph.

18. The non-transitory computer readable storage media of claim 14 , wherein generating, at the blockchain services interface in the hosted computing environment, the blockchain block, comprises periodically generating the blockchain block without regard to the web server receiving from a document management application an indication of change in the document history graph.

19. The non-transitory computer readable storage media of claim 14 , wherein receiving, at the web server in the hosted computing environment, the document history graph, comprises:

receiving an initial version of a document and creating a node in the document history graph, the node comprising metadata for the initial version of the document;

receiving additional versions of the document and creating corresponding nodes in the document history graph each comprising metadata for the respective versions of the document; and

receiving a final version of the document and creating a leaf node in the document history graph comprising metadata for the final version of the document.

20. The non-transitory computer readable storage media method of claim 14 , wherein the metadata for each of the initial, respective, and final versions of the document comprises a previous version number associated with an earlier version of the document dating back to the root node, a version number for the version of the document, a pointer to a location in a data store at which the version of the document is stored, a hash value of the version of the document, and a signature of one or more signatories to the version of the document.