Systems and methods for blockchain-based cloud storage document integrity
Embodiments are directed to the protection and verification of documents. In some embodiments, this is achieved by generating checksum data describing a document and storing that and a time stamp on a publicly available blockchain. By recording a checksum of a document on a blockchain, the disclosed systems and methods may be used later to validate the integrity of the document. In one embodiment, this validation is performed by comparing the recorded checksum from a previous time when the document or files were stored to a recalculated checksum generated at the present time. If the checksums match, then it is assumed that the document has not been altered since the checksum data was first calculated.
1. A computer-implemented method comprising:
accessing an electronically stored data set;
generating a checksum of the accessed data set;
creating a payload comprising
the generated checksum of the data set; and
an identifier for the data set;
downloading a stored instance of the data set;
generating a recomputed checksum of the downloaded stored instance of the data set; and
prior to committing a transaction, validating the stored instance of the data set by comparing the checksum of the data set with the recomputed checksum of the downloaded stored instance of the data set; and
committing the transaction comprising the payload to a blockchain.
2. The computer-implemented method of claim 1 , wherein the identifier of the data set comprises at least one of:
a document identifier designating a stored instance of the data set; and
a uniform resource locator designating the stored instance of the data set.
3. The computer-implemented method of claim 1 , wherein the blockchain records a time of the transaction.
4. The computer-implemented method of claim 1 , wherein the payload further comprises at least one of:
a time at which the checksum of the data set was generated;
a time at which the data set was accessed; and
a time at which the electronically stored data set was uploaded to a document store.
5. The computer-implemented method of claim 1 , wherein the data set comprises a document file or a set of document files with a common attribute.
6. The computer-implemented method of claim 1 , wherein the stored instance of the data set is located in an element of a remote server or platform.
7. The computer-implemented method of claim 1 , further comprising storing a transaction identifier of the transaction in association with a stored instance of the data set.
8. The computer-implemented method of claim 7 , further comprising:
receiving a request to verify integrity of the data set; and
in response to the request, retrieving and providing the transaction identifier.
9. A system comprising:
at least one electronic processor;
a non-transitory computer-readable memory comprising computer-executable instructions that, when executed by the processor, cause the system to:
access an electronically stored data set;
generate a checksum of the accessed data set;
create a payload comprising
the generated checksum of the data set; and
an identifier for the data set; and
commit a transaction comprising the payload to a blockchain;
wherein the instructions further cause the system to:
download a stored instance of the data set;
generate a recomputed checksum of the downloaded stored instance of the data set; and
prior to committing the transaction, validate the stored instance of the data set by comparing the checksum of the data set with the recomputed checksum of the downloaded stored instance of the data set.
10. The system of claim 9 , wherein the blockchain records a time of the transaction.
11. The system of claim 9 , wherein the payload further comprises at least one of:
a time at which the checksum of the data set was generated;
a time at which the data set was accessed; and
a time at which the electronically stored data set was uploaded to a document store.
12. The system of claim 9 , wherein the data set comprises a document file or a set of document files with a common attribute.
13. The system of claim 9 , wherein the stored instance of the data set is located in an element of a remote server or platform.
14. The system of claim 9 , further comprising storing a transaction identifier of the transaction in association with a stored instance of the data set.
15. The system of claim 9 , further comprising:
receiving a request to verify integrity of the data set; and
in response to the request, retrieving and providing the transaction identifier.
16. The system of claim 9 , wherein the identifier of the data set comprises at least one of a document identifier designating a stored instance of the data set and a uniform resource locator designating the stored instance of the data set.
17. One or more non-transitory computer-readable media comprising one or more computer-executable instructions that, when executed by at least one processor of a computing device, cause the computing device to:
access an electronically stored data set;
generate a checksum of the accessed data set;
create a payload comprising
the generated checksum of the data set; and
an identifier for the data set; and
commit a transaction comprising the payload to a blockchain;
wherein the instructions further cause the system to:
download a stored instance of the data set;
generate a recomputed checksum of the downloaded stored instance of the data set; and
prior to committing the transaction, validate the stored instance of the data set by comparing the checksum of the data set with the recomputed checksum of the downloaded stored instance of the data set.
18. The non-transitory computer-readable medium of claim 17 , wherein the payload further comprises at least one of:
a time at which the checksum of the data set was generated;
a time at which the data set was accessed; and
a time at which the electronically stored data set was uploaded to a document store.