“BLOCKCHAIN-BASED DATA INTEGRITY VERIFICATION SYSTEM”

Abstract

This invention relates to a blockchain-based system for verifying data integrity by utilizing cryptographic hashing and a decentralized ledger. The system comprises a hashing module that generates a cryptographic hash for a data file, which is then stored on a blockchain ledger along with a timestamp and associated metadata. A verification module retrieves and compares the stored hash with a newly generated hash to detect any unauthorized modifications to the data file. This approach ensures tamper-resistance and provides a secure, immutable record of data authenticity. The system can be implemented on either public or permissioned blockchain networks and is adaptable for use with off-chain storage solutions to enhance scalability. Additional features include access control, automated integrity checks, and alert mechanisms to notify users of data discrepancies, making the system suitable for applications in industries requiring high data security and trust, such as finance, healthcare, and supply chain management.

Specification

Description:In the following description, for the purposes of explanation, various specific details are set forth in order to provide a thorough understanding of embodiments of the present disclosure. It will be apparent, however, that embodiments of the present disclosure may be practiced without these specific details. Several features described hereafter can each be used independently of one another or with any combination of other features. An individual feature may not address all of the problems discussed above or might address only some of the problems discussed above. Some of the problems discussed above might not be fully addressed by any of the features described herein.

The ensuing description provides exemplary embodiments only and is not intended to limit the scope, applicability, or configuration of the disclosure. Rather, the ensuing description of the exemplary embodiments will provide those skilled in the art with an enabling description for implementing an exemplary embodiment. It should be understood that various changes may be made in the function and arrangement of elements without departing from the spirit and scope of the disclosure as set forth.

Specific details are given in the following description to provide a thorough understanding of the embodiments. However, it will be understood by one of ordinary skill in the art that the embodiments may be practiced without these specific details. For example, circuits, systems, networks, processes, and other components may be shown as components in block diagram form in order not to obscure the embodiments in unnecessary detail. In other instances, well-known circuits, processes, algorithms, structures, and techniques may be shown without unnecessary detail to avoid obscuring the embodiments.

Also, it is noted that individual embodiments may be described as a process that is depicted as a flowchart, a flow diagram, a data flow diagram, a structure diagram, or a block diagram. Although a flowchart may describe the operations as a sequential process, many of the operations can be performed in parallel or concurrently. In addition, the order of the operations may be re-arranged. A process is terminated when its operations are completed but could have additional steps not included in a figure. A process may correspond to a method, a function, a procedure, a subroutine, a subprogram, etc. When a process corresponds to a function, its termination can correspond to a return of the function to the calling function or the main function.

The word "exemplary" and/or "demonstrative" is used herein to mean serving as an example, instance, or illustration. For the avoidance of doubt, the subject matter disclosed herein is not limited by such examples. In addition, any aspect or design described herein as "exemplary" and/or "demonstrative" is not necessarily to be construed as preferred or advantageous over other aspects or designs, nor is it meant to preclude equivalent exemplary structures and techniques known to those of ordinary skill in the art. Furthermore, to the extent that the terms "includes," "has," "contains," and other similar words are used in either the detailed description or the claims, such terms are intended to be inclusive in a manner similar to the term "comprising" as an open transition word without precluding any additional or other elements.

Reference throughout this specification to "one embodiment" or "an embodiment" or "an instance" or "one instance" means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the present disclosure. Thus, the appearances of the phrases "in one embodiment" or "in an embodiment" in various places throughout this specification are not necessarily all referring to the same embodiment. Furthermore, the particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.

The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure. As used herein, the singular forms "a", "an", and "the" are intended to include the plural forms as well, unless the context indicates otherwise. It will be further understood that the terms "comprises" and/or "comprising," when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof. As used herein, the term "and/or" includes any and all combinations of one or more of the associated listed items.

This invention leverages blockchain technology to create a tamper-resistant system for verifying data integrity. By recording cryptographic hashes of data on a blockchain, it ensures that any attempt to alter or tamper with the data can be detected, offering a secure and reliable method of data verification across various applications.

In first embodiment, the data integrity verification system utilizes a public blockchain, such as Ethereum or Bitcoin, for maximum transparency and decentralization. The system comprises a hashing module that generates a unique cryptographic hash for each data file. When data is first stored, the hashing module computes a hash, which is then embedded in a blockchain transaction. The transaction, containing the hash and a timestamp, is propagated across all nodes in the public blockchain network.

When data needs to be verified, the system rehashes the data file and retrieves the previously stored hash from the blockchain. If the two hashes match, the data remains unaltered. This embodiment is particularly useful for applications where transparency and public verifiability are essential, such as public record-keeping or government documentation. However, it may involve higher transaction fees and lower throughput, given the limitations of public blockchains.

The primary advantage of this embodiment is that it eliminates the need for a trusted intermediary, as the public blockchain provides a decentralized record that anyone can access. This setup ensures data authenticity and tamper-resistance without relying on a single authority, making it highly resilient to attacks.

In second embodiment, the system employs a permissioned blockchain, suitable for enterprise environments that prioritize security, scalability, and controlled access. The permissioned blockchain is maintained by a consortium of authorized entities, such as multiple departments within an organization or collaborating companies. Unlike the public blockchain, this setup restricts access to verified participants, ensuring that only authorized nodes can read, write, or verify data on the blockchain.

The permissioned blockchain ledger stores cryptographic hashes generated by the hashing module, along with metadata, such as data type, source, and timestamp. When a data file is modified, the system generates a new hash, which is then recorded on the permissioned blockchain after being validated by authorized nodes. The verification module continuously monitors for hash discrepancies, ensuring data integrity and alerting the system if any hash does not match the stored value.

This embodiment is ideal for use cases in finance, healthcare, or supply chain management, where data integrity is critical, but privacy and access control are also important. By using a permissioned blockchain, the system can achieve high throughput and low latency, suitable for enterprise-scale data processing. Additionally, permissioned blockchains provide the flexibility to implement customized access policies and improve data privacy by limiting blockchain access to specific participants.

In the third embodiment, a hybrid approach combines blockchain for integrity verification with off-chain storage for the data itself. This setup is particularly suited for applications with large data files or high-frequency data generation, as it allows the system to handle scalability and storage concerns more effectively. Only the cryptographic hash, timestamp, and minimal metadata are stored on the blockchain, while the actual data resides in an external, decentralized storage system, such as IPFS (InterPlanetary File System) or a private cloud.
When a data file is created or modified, the hashing module computes its hash, and this hash is stored on the blockchain with a pointer or link to the off-chain storage location. When verifying the integrity of the data, the system retrieves the data from the off-chain storage, hashes it, and compares it with the blockchain-stored hash. If the hashes match, the data is deemed authentic; otherwise, a discrepancy indicates possible tampering.

This hybrid approach provides significant advantages in terms of scalability and cost-efficiency. By storing only hashes on the blockchain and keeping large files off-chain, the system minimizes blockchain storage demands and transaction costs. This embodiment is highly suitable for IoT applications, where devices may generate data continuously, as well as for multimedia storage solutions, where data files are large and frequent verification is required. The off-chain storage solution is robust, allowing for data redundancy and fault tolerance without overloading the blockchain network.

While considerable emphasis has been placed herein on the preferred embodiments, it will be appreciated that many embodiments can be made and that many changes can be made in the preferred embodiments without departing from the principles of the invention. These and other changes in the preferred embodiments of the invention will be apparent to those skilled in the art from the disclosure herein, whereby it is to be distinctly understood that the foregoing descriptive matter to be implemented merely as illustrative of the invention and not as limitation. , Claims:1.A blockchain-based system for data integrity verification, comprising:
a hashing module configured to generate a cryptographic hash for a data file based on its content;
a blockchain ledger configured to store the cryptographic hash in an immutable format, along with a timestamp and metadata associated with the data file;
a verification module configured to retrieve the cryptographic hash stored on the blockchain ledger and compare it with a newly generated cryptographic hash of the data file;
wherein the verification module identifies and flags discrepancies between the newly generated cryptographic hash and the stored cryptographic hash, indicating potential unauthorized modifications to the data file.

2.The system of claim 1, wherein the hashing module uses the SHA-256 cryptographic hashing algorithm to generate the cryptographic hash.

3.The system of claim 1, wherein the blockchain ledger is a public blockchain network that allows any participant to verify data integrity by retrieving stored cryptographic hashes.

4.The system of claim 1, wherein the blockchain ledger is a permissioned blockchain that restricts access to authorized nodes, allowing only verified participants to store and retrieve cryptographic hashes.

5.The system of claim 1, further comprising an access control module using public and private key cryptography to authenticate users before they are allowed to access or modify the data file.

6.The system of claim 1, wherein the metadata stored on the blockchain includes the origin of the data file, a unique identifier, and information regarding the last modification, enhancing the traceability of the data file.

7.The system of claim 1, further comprising an alerting module that generates a warning or notification when the verification module identifies a discrepancy between the newly generated cryptographic hash and the stored cryptographic hash.

8.The system of claim 1, wherein the cryptographic hash is stored on the blockchain ledger alongside a pointer or link to an off-chain storage location, where the data file is stored, enabling scalable data integrity verification without storing the full data on the blockchain.

9.The system of claim 1, wherein the verification module automatically performs periodic integrity checks by rehashing the data file at predetermined intervals and comparing the newly generated cryptographic hash with the hash stored on the blockchain ledger.

Documents