TECHNICAL FIELD

[0001] The present disclosure in general relates to block chain technology, and more particularly to a record-keeping and record-verification system based on hybrid block chain.

BACKGROUND

[0002] The background description includes information that may be useful in understanding the present invention. It is not an admission that any of the information provided herein is prior art or relevant to the presently claimed invention, or that any publication specifically or implicitly referenced is prior art.

[0003] A record is a document that memorializes and can provide an objective evidence of activities performed, events occurred, results achieved, or statements made. Generally speaking, records can function as evidence of activities or events that have transpired.

[0004] Good record keeping practices involve systematic and efficient control of creation, receipt, maintenance, use and disposition of records, including also the processes for capturing and maintaining evidence of and information about business activities and transactions in the form of records. Records can have access controls to regulate who can access them and under what circumstances.

[0005] Records can be classified as physical records and electronic or digital records. Digital or electronic record systems can include role-based access controls, allowing permissions (to view, change and/or delete) to be allocated to staff depending on their role in the organization. An audit trail showing all access and changes can be maintained to ensure integrity of the records. Electronic records, however, can raise specific issues. It is more difficult to ensure that the content, context, and structure of records is preserved and protected when the records do not have a physical existence. This can have important implications for authenticity, reliability, and trustworthiness of records.

[0006] Blockchain is a revolutionary technology that powers today's crypto currencies such as Bitcoin, Ethereum, Litecoin, AltCoin, etc. Blockchain as a data structure and distributed storage mechanism, is a perfect model for general record keeping (like public records, health records, contracts, etc.), where data privacy assumes extreme importance.

[0007] A blockchain is fundamentally a data structure that provides strong semantics of immutability of data that is stored in it. A blockchain consists of a ledger of records that are arranged in data batches that use cryptographic validation to link themselves together. Each piece of data that is stored in a Blockchain is called a Block, and its contents are hashed using an irreversible hashing algorithm. Put simply, each Block references and identifies the previous Block by a hashing function, thus forming an unbroken chain or a Blockchain. ABlockchain is a database with built-in validation. Another distinguishing feature of the blockchain is that the ledger is not stored in a master location, or managed by any particular body. Instead, it is said to be distributed, existing on multiple computers at the same time in such a way that anybody with an interest can maintain a copy of it. The block validation system ensures that nobody can tamper with the records. Rather, old transactions are preserved forever and new transactions are added to the ledger irreversibly. Anyone on the network can check the ledger and see the same transaction history as everyone else. Effectively a blockchain is a kind of independent, transparent, and permanent database coexisting in multiple locations and shared by a community.

[0008] Generally, the current blockchains being used are either maintained by central authorities within a controlled network of storage devices that are called permissioned Blockchains, or in peer-to-peer network devices by anyone on Internet, which are called public Blockchains. Permissioned Blockchains provide privacy of data and a centralized trust for the data, whereas peer to peer Blockchains provide decentralized trust for the data.

[0009] However, a limitation of the current Blockchains is that if a permissioned blockchain is chosen for data privacy, the onus of sanity or integrity of the record lies with a single authority, which leaves a trust deficit. However, if a public Blockchain is used for record keeping, privacy of the data is not possible. Therefore, both the models of Blockchain technologies that currently exist cannot be efficiently and effectively used for a general record keeping purposes.

[0010] Therefore, there is a need in the art to provide a record keeping and verification system that provides utmost record keeping and data privacy and integrity for the record producers and creators and simultaneously provides a decentralized trust based system to verify integrity of record data.

OBJECTS OF THE INVENTION

[0011] An object of the present disclosure is to provide utmost data privacy for record producers and creators.

[0012] Another object of the present disclosure is to provide a strong and tamper proof decentralized trust based system for trusting and verifying integrity of record data for record consumers. SUMMARY

[0013] The present disclosure in general relates to blockchain technology, and more particularly to a record-keeping and record-verification system based on hybrid blockchain.

[0014] In an aspect, the proposed system can include a non-transitory storage device having embodied therein one or more routines operable to configure a hybrid blockchain; and one or more processors coupled to the non-transitory storage device and operable to execute the one or more routines, wherein the one or more routines include: a named blockchain creation module, which when executed by the one or more processors, creates a permissioned blockchain (PBC) configured to store a plurality of records, said PBC being configured as a set of blocks, each block of said set of blocks having a block header portion and a record data portion; and a shadow chain creation module, which when executed by the one or more processors, creates a shadow chain (SC) corresponding to the PBC, said SC being configured as a second set of blocks, each block of said second set of blocks being configured to store respective block header portion of the block chain and a shadow chain header portion such that blocks of the PBC are accessible, for integrity check of the PBC, to one or more users using the SC, and wherein the plurality of records stored in the PBC are not alterable.

[0015] In an aspect, the block header portion of the block chain can be configured to store metadata information pertaining to the respective block and the record data portion stored therewith.

[0016] In another aspect, the named blockchain creation module can be configured to create the PBC under instructions by a registered organization, wherein the plurality of records are only accessible to said registered organization or users permitted thereby.

[0017] In yet another aspect, the SC can be decentralized in a manner such that multiple instances of said SC can be created by said one or more users on their respective computing devices, and wherein each said instance of said SC is synchronized with said SC in real-time or at defined intervals.

[0018] In another aspect, the one or more users can be selected from any or a combination of an individual user, a target organization, a verifying organization, or an unregistered organization.

[0019] In another aspect, the set of blocks of the PBC can be created dynamically as new records are created, based on which corresponding second set of blocks are created.

[0020] In an aspect, the block header portion can be a hash of the record data portion it corresponds to.

[0021] In another aspect, a user can be given access to a specific record of the plurality of records by sending a verification link to the email address of the user, based on verification of which, said user is given access to the specific record, wherein the verification link can include a first portion of original record data stored in internal system of registered organization that created the PBC, a second portion of record data stored in the PBC, and a third portion of corresponding records' SC block details such that verification is said to have been performed based on matching of the first portion with the second portion, and based on matching of corresponding block header portion of PBC with the one stored in the SC.

[0022] Aspects of the present disclosure further relate to a method comprising the steps of creating, at a server, a permissioned blockchain (PBC) configured to store a plurality of records, said PBC being configured as a set of blocks, each block of said set of blocks having a block header portion and a record data portion; and creating, at the server, a shadow chain (SC) corresponding to the PBC, said SC being configured as a second set of blocks, each block of said second set of blocks being configured to store respective block header portion of the block chain and a shadow chain header portion such that blocks of the PBC are accessible, for integrity check of the PBC, to one or more users using the SC, and wherein the plurality of records stored in the PBC are not alterable.

BRIEF DESCRIPTION OF DRAWINGS

[0023] The accompanying drawings are included to provide a further understanding of the present disclosure, and are incorporated in and constitute a part of this specification. The drawings illustrate exemplary embodiments of the present disclosure and together with the description, serve to explain the principles of the present disclosure.

[0024] FIG. 1 illustrates an exemplary schematic diagram of a Hybrid Blockchain network system (BlockRec.IO)for record keeping and record verification in accordance with the embodiments of the present disclosure.

[0025] FIGs. 2A and 2B illustrate, via an exemplary flow diagram, the method of working of proposed Hybrid Blockchain network system in accordance with an exemplary embodiment of the present disclosure.

[0026] FIG. 3 illustrates an exemplary functional module diagram of the proposed system in accordance with an exemplary embodiment of the present disclosure.

DETAILED DESCRIPTION OF THE INVENTION

[0027] All publications herein are incorporated by reference to the same extent as if each individual publication or patent application were specifically and individually indicated to be incorporated by reference. Where a definition or use of a term in an incorporated reference is inconsistent or contrary to the definition of that term provided herein, the definition of that term provided herein applies and the definition of that term in the reference does not apply.

[0028] In some embodiments, the numbers expressing quantities of ingredients, properties such as concentration, reaction conditions, and so forth, used to describe and claim certain embodiments of the invention are to be understood as being modified in some instances by the term "about." Accordingly, in some embodiments, the numerical parameters set forth in the written description and attached claims are approximations that can vary depending upon the desired properties sought to be obtained by a particular embodiment. In some embodiments, the numerical parameters should be construed in light of the number of reported significant digits and by applying ordinary rounding techniques. Notwithstanding that the numerical ranges and parameters setting forth the broad scope of some embodiments of the invention are approximations, the numerical values set forth in the specific examples are reported as precisely as practicable. The numerical values presented in some embodiments of the invention may contain certain errors necessarily resulting from the standard deviation found in their respective testing measurements.

[0029] As used in the description herein and throughout the claims that follow, the meaning of "a," "an," and "the" includes plural reference unless the context clearly dictates otherwise. Also, as used in the description herein, the meaning of "in" includes "in" and "on" unless the context clearly dictates otherwise.

[0030] The recitation of ranges of values herein is merely intended to serve as a shorthand method of referring individually to each separate value falling within the range. Unless otherwise indicated herein, each individual value is incorporated into the specification as if it were individually recited herein. All methods described herein can be performed in any suitable order unless otherwise indicated herein or otherwise clearly contradicted by context. The use of any and all examples, or exemplary language (e.g. "such as") provided with respect to certain embodiments herein is intended merely to better illuminate the invention and does not pose a limitation on the scope of the invention otherwise claimed. No language in the specification should be construed as indicating any non-claimed element essential to the practice of the invention.

[0031] Groupings of alternative elements or embodiments of the invention disclosed herein are not to be construed as limitations. Each group member can be referred to and claimed individually or in any combination with other members of the group or other elements found herein. One or more members of a group can be included in, or deleted from, a group for reasons of convenience and/or patentability. When any such inclusion or deletion occurs, the specification is herein deemed to contain the group as modified thus fulfilling the written description of all Markush groups used in the appended claims.

[0032] The following is a detailed description of embodiments of the disclosure depicted in the accompanying drawings. The embodiments are in such detail as to clearly communicate the disclosure. However, the amount of detail offered is not intended to limit the anticipated variations of embodiments; on the contrary, the intention is to cover all modifications, equivalents, and alternatives falling within the spirit and scope of the present disclosure as defined by the appended claims. Each of the appended claims defines a separate invention, which for infringement purposes is recognized as including equivalents to the various elements or limitations specified in the claims. Depending on the context, all references below to the "invention" may in some cases refer to certain specific embodiments only. In other cases it will be recognized that references to the "invention" will refer to subject matter recited in one or more, but not necessarily all, of the claims.

[0033] All methods described herein can be performed in any suitable order unless otherwise indicated herein or otherwise clearly contradicted by context. The use of any and all examples, or exemplary language (e.g., "such as") provided with respect to certain embodiments herein is intended merely to better illuminate the invention and does not pose a limitation on the scope of the invention otherwise claimed. No language in the specification should be construed as indicating any non-claimed element essential to the practice of the invention.

[0034] The present disclosure in general relates to blockchain technology, and more particularly to a record-keeping and record-verification system based on hybrid blockchain.

[0035] In an aspect, the proposed system can include a non-transitory storage device having embodied therein one or more routines operable to configure a hybrid blockchain; and one or more processors coupled to the non-transitory storage device and operable to execute the one or more routines, wherein the one or more routines include: a named blockchain creation module, which when executed by the one or more processors, creates a permissioned blockchain (PBC) configured to store a plurality of records, said PBC being configured as a set of blocks, each block of said set of blocks having a block header portion and a record data portion; and a shadow chain creation module, which when executed by the one or more processors, creates a shadow chain (SC) corresponding to the PBC, said SC being configured as a second set of blocks, each block of said second set of blocks being configured to store respective block header portion of the block chain and a shadow chain header portion such that blocks of the PBC are accessible, for integrity check of the PBC, to one or more users using the SC, and wherein the plurality of records stored in the PBC are not alterable.

[0036] In an aspect, the block header portion of the block chain can be configured to store metadata information pertaining to the respective block and the record data portion stored therewith.

[0037] In another aspect, the named blockchain creation module can be configured to create the PBC under instructions by a registered organization, wherein the plurality of records are only accessible to said registered organization or users permitted thereby.

[0038] In yet another aspect, the SC can be decentralized in a manner such that multiple instances of said SC can be created by said one or more users on their respective computing devices, and wherein each said instance of said SC is synchronized with said SC in real-time or at defined intervals.

[0039] In another aspect, the one or more users can be selected from any or a combination of an individual user, a target organization, a verifying organization, or an unregistered organization.

[0040] In another aspect, the set of blocks of the PBC can be created dynamically as new records are created, based on which corresponding second set of blocks are created.

[0041] In an aspect, the block header portion can be a hash of the record data portion it corresponds to.

[0042] In another aspect, a user can be given access to a specific record of the plurality of records by sending a verification link to the email address of the user, based on verification of which, said user is given access to the specific record, wherein the verification link can include a first portion of original record data stored in internal system of registered organization that created the PBC, a second portion of record data stored in the PBC, and a third portion of corresponding records' SC block details such that verification is said to have been performed based on matching of the first portion with the second portion, and based on matching of corresponding block header portion of PBC with the one stored in the SC.

[0043] Aspects of the present disclosure further relate to a method comprising the steps of creating, at a server, a permissioned blockchain (PBC) configured to store a plurality of records, said PBC being configured as a set of blocks, each block of said set of blocks having a block header portion and a record data portion; and creating, at the server, a shadow chain (SC) corresponding to the PBC, said SC being configured as a second set of blocks, each block of said second set of blocks being configured to store respective block header portion of the block chain and a shadow chain header portion such that blocks of the PBC are accessible, for integrity check of the PBC, to one or more users using the SC, and wherein the plurality of records stored in the PBC are not alterable.

[0044] In an aspect, a hybrid block chain system(also interchangeably referred to as BlockRec.IO)with permission data privacy and decentralized trust is disclosed, wherein the BlockRec. IOcan be used as a platform for record keeping and record verification. In an aspect, terms Hybrid Blockchain network system, and BlockRec.IO platform shall be used interchangeably hereinafter. In an aspect, BlockRec.IO platform can include a distributed network of centrally controlled servers that can store various types of Blockchains. In an aspect, the hybrid Blockchain network system can include a combination of a Permissioned Blockchain and a distributed block chain, wherein blocks in the Permissioned Blockchains can form a global and distributed Blockchain that can be shared, and can be referred to as a Shadow chain. In an aspect, actual data/records can be stored in Permissioned Blockchain on centrally controlled systems and records once entered in permissioned Blockchain cannot be changed /altered/deleted by anyone.

[0045] In another aspect, Hybrid Blockchain, together with global/shared distributed chain hereinafter referred to as Shadowchain(or Shadow Chain), which can store metadata that mayinclude just Block identification data. In an aspect, Block identification data can just includea block header (without actual record data) from an original permissioned block chain, wherein the Shadowchain can be distributed across a plurality of devices on the Internet.

[0046] FIG. 1 illustrates an exemplary schematic diagram 100 of a Hybrid Block chain network system 102for record keeping and record verification in accordance with the embodiments of the present disclosure. In an aspect, Hybrid Blockchain network system (BlockRec.IO) 102 can include a Centralized Blockchain computer network that can be accessible to registered organization/entity 104. In an aspect, Hybrid Blockchain network system 102 can have a plurality of registered organizations on its network, wherein an organization 104, after registering with BlockRec.IO 102, can create a named Blockchain 106, and wherein the named Blockchain 106 can be visible and accessible to only the registered organization 104 that has created it. In an aspect, terms Named Blockchains/Permissioned Blockchains shall be used interchangeably hereinafter.

[0047] In an aspect, Organization 104 can store records into the named Blockchain 106created by it in BlockRec.IO 102, which records can go into the named Blockchain 106 maintained by BlockRec.IO 102 and can be accessible to only its permitted users on the distributed network of computers and storage devices 110a, 110b within the organization 104. In an aspect, no other user can have access to the named Blockchain 106 other than the permitted users. In an aspect, permitted users can be administrators of the named Blockchain 106 who have been granted express permission to view records on the named Blockchain 106. In an aspect, a new user can view records on the named Blockchain 106 after taking express permission for the same from the administrator of the named Blockchain 106.

[0048] In an aspect, when a named block chain 106 is created and records are put in the named Blockchain 106, metadata of the record data can also simultaneously be generated. In an aspect, the metadata can be a cryptographic hash of the record in the named Blockchain 106. In an aspect, the cryptographic hashes can be stored in the form of blocks and another Blockchain can be continuously created out of blocks from corresponding named Blockchain 106ref erred to as Shadowchain 106a that can be created from the metadata of the records available in the NamedBlockchain 106. In an aspect, the input of the Shadowchain 106a can be the metadata of a record. In an aspect, metadata of a record can be a cryptographic hash. In an aspect, only permitted users can have access to the Shadowchain 106a. In an aspect, any new user can be granted access to the shadow chain by the administrator of the named Blockchain 106. In an aspect, it is not possible for either permitted or unpermitted user to change or delete the records in the named Blockchain 106 and Shadowchain 106a.In an aspect, Shadowchain 106a can include blocks whose data part contains the block headers of corresponding named Blockchain 106.

[0049] In an aspect, on specific permission, the Shadowchain 106acan be shared between registered organization 104 and any other target organization or individual user 112. In an aspect, the target organization or individual user 112 with whom the Shadowchain 106a can be shared can be a registered entity or unregistered entity with BlockRec.IO platform 102. In another aspect, the registered organization 104 can declare the Shadowchain 106a as open to everyone or permitted Shadowchain that requires permission for access.

[0050] In an aspect, the original records in the Named Blockchain 106 can be accessed only in specific instances. In an aspect, the original records in the Named Blockchain 106 can be accessed by the administrator of the Named Blockchain 106. In another aspect, the original records in the Named Blockchain 106 can be accessed if a verification link is sent to any individual user or target organization 112 in which case, they can access only a specific record for which the verification link has been sent and no other record can be accessed.

[0051] In an aspect, the sharing feature of BlockRec.IO platform 102 can provide a decentralized mechanism for its users to verify the integrity of records in a Blockchain or with everyone. [0052] In an aspect, the Shadowchain 106a can be downloaded and maintained as Shadowchain 114 on their own network of systems, by the target organization or individual user/verifying organization 112 with whom the Shadowchain 106a is shared by the organization 104.

[0053] In an aspect, the BlockRec.IOplatform 102 can include a network service herein referred to as ShadowSync 116. In an aspect, ShadowSync 116 can continuously update the Shadowchain 114 maintained by the target organizationby synchronization with BlockRec.IOplatform 102.

[0054] In another embodiment of the present disclosure, an organization can get its record verified by a 3 ^rd party. In an aspect, the 3 ^rd party can be BlockRec.IO 102 platform itself without any manual intervention. In an aspect, the organization initiating verification of records or verifier can request the registered organization 104 whose records the verifier wants to verify to generate a verification link on the BlockRec.IO platform 102.

[0055] In an aspect, this verification link can include three parts. In an aspect, Part-1 of the verification link can contain the original record data that is stored in registered organization's 104 own internal systems. In another aspect, Part-2 of verification link can include a record that is stored in the Named Blockchain 106 of registered organization's 104 in the BlockRec.IO platform 102 with a given unique record identifier.In an aspect, the unique record identifier can be an alphabet, number or an alphanumeric symbol. In yet another aspect, Part -3 of the verification link can contain the corresponding record's Shadowchain block details.

[0056] In an aspect, verification can be initiated by the verifier by clicking on the verification link of a recordthat is sent by the registered organization 104. In an aspect, upon initiation of the verification by the 3 ^rd party, BlockRec.IOplatform 102canmatch Part-1 with Part-2 of the verification link. In another aspect, upon successful matching of Part-1 and Part- 2 of the verification link, BlockRec.IOplatform 102can provide Part-3 of the verification link back to the verifying organization/verifier 112. In an aspect, the verifier can use Part-3 data to check the integrity of the record from the verifying organization's 112 own copy of Shadowchain 114 by providing a URL to their local shadow chain network. In yet another aspect, the verifier can use the Part-3 data to check the integrity of the record from a Peer-to- Peer network of Shadowchains maintained by a community.

[0057] In an aspect, the BlockRec.IO platform 102 can be accessible through an Application programming Interface (API), wherein the API can be accessible through a web application that can run on laptops, desktops and mobile devices, among other computing devices. Any other implementation means is completely within the scope of the present disclosure.

[0058] In an aspect, the Shadowchain 106a does not contain any information about the original records stored by registered organization 104 in its named Blockchain 106. In an aspect, Shadowchain 106a can be distributed to anyone without data privacy concerns. In an aspect, ability to distribute a Shadowchain 106a to anyone gives the BlockRec.IO platform 102 a unique capability of providing a decentralized trust system of record data.

[0059] In an aspect, the Hybrid Blockchain network system 102 can provide a strong and tamper-proof mechanism of trusting and verification of transactions by users. In an aspect, the Hybrid Blockchain network system 102 can provide enhanced data privacy for record producers and creators. In yet another aspect, the Hybrid Blockchain network system 102 can provide decentralized trust for record consumers.

[0060] FIG. 2A illustrates via a flow diagram, the method of working of proposed Hybrid Blockchain network system 102, in accordance with an exemplary embodiment of the present disclosure.

[0061] In an aspect, the method can include, at step 202, registering the organization 104 with the Hybrid Blockchain network(BlockRec.IO) 102. The method can include, at step 204, creating a named Blockchain 106, and at step 206, putting/entering records into the named Blockchain 106. At step 208, the method can enable generation of a Shadowchain 106a of records in the Named Blockchain 106, and at step 210, share the shadow chain 106a with other Registered/Unregistered target organizations/Individual users 112. The method can include, at step 212, downloading of shadow chain 106a by a target organization/Individual user 112, and at step 214, enabling continuous synchronization / updation of downloaded Shadowchain by ShadowSync 116. The method can include, at step 216, initiating verification of record by a verifying/target organization/Individual user 112 by requesting registered organization 104 to generate verification link on the BlockRec.IO platform 102. At step 218, a verification link is generated on BlockRec.IO platform 102 by registered organization 104, wherein, at step 220, Part-1 and Part-2 of the verification link can be matched by the verifying organization 112. At step 222, the method can send Part-3 of verification link back to the verifying organization 112, if matching successful, and at step 224, the method can check integrity of the record by the verifying organization 112 from its own copy of shadow chain downloaded on its network. At step 226, the method will not send Part-3 of verification link back to the verifying organization 112, if matching fails.

[0062] FIG. 2B illustrates another exemplary flow diagram 250 in accordance with an aspect of the present invention. In an aspect, step 252 involves creating, at a server, a permissioned blockchain (PBC) configured to store a plurality of records, said PBC being configured as a set of blocks, each block of said set of blocks having a block header portion and a record data portion; and step 254 involves creating, at the server, a shadow chain (SC) corresponding to the PBC, said SC being configured as a second set of blocks, each block of said second set of blocks being configured to store respective block header portion of the block chain and a shadow chain header portion such that blocks of the PBC are accessible, for integrity check of the PBC, to one or more users using the SC, and wherein the plurality of records stored in the PBC are not alterable.

[0063] FIG. 3 illustrates an exemplary set of functional modules 300that form part of the proposed system architecture in accordance with an aspect of the present invention. In an aspect, the proposed system includes a non-transitory storage device having embodied therein one or more routines operable to configure a hybrid blockchain; andone or more processors coupled to the non-transitory storage device and operable to execute the one or more routines, wherein the one or more routines include:a named blockchain creation module 302, which when executed by the one or more processors, creates a permissioned blockchain (PBC) configured to store a plurality of records, said PBC being configured as a set of blocks, each block of said set of blocks having a block header portion and a record data portion; and a shadow chain creation module304, which when executed by the one or more processors, creates a shadow chain (SC) corresponding to the PBC, said SC being configured as a second set of blocks, each block of said second set of blocks being configured to store respective block header portion of the block chain and a shadow chain header portion such that blocks of the PBC are accessible, for integrity check of the PBC, to one or more users using the SC, and wherein the plurality of records stored in the PBC are not alterable.

[0064] In an aspect, the block header portion of the block chain can be configured to store metadata information pertaining to the respective block and the record data portion stored therewith.

[0065] In another aspect, the named blockchain creation module can be configured to create the PBC under instructions by a registered organization, wherein the plurality of records are only accessible to said registered organization or users permitted thereby.

[0066] In yet another aspect, the SC can be decentralized in a manner such that multiple instances of said SC can be created by said one or more users on their respective computing devices, and wherein each said instance of said SC is synchronized with said SC in real-time or at defined intervals. [0067] In another aspect, the one or more users can be selected from any or a combination of an individual user, a target organization, a verifying organization, or an unregistered organization.

[0068] In another aspect, the set of blocks of the PBC can be created dynamically as new records are created, based on which corresponding second set of blocks are created.

[0069] In an aspect, the block header portion can be a hash of the record data portion it corresponds to.

[0070] In another aspect, a user can be given access to a specific record of the plurality of records by sending a verification link to the email address of the user, based on verification of which, said user is given access to the specific record, wherein the verification link can include a first portion of original record data stored in internal system of registered organization that created the PBC, a second portion of record data stored in the PBC, and a third portion of corresponding records' SC block details such that verification is said to have been performed based on matching of the first portion with the second portion, and based on matching of corresponding block header portion of PBC with the one stored in the SC.

[0071] In an aspect, an exemplary technical effect of the present invention is a subtle combination of a permissioned blockchain and a public Blockchain as to enable review of records being entered and verify their integrity, and at the same time maintain privacy of the actual record data, which prevents records from being kept decentralized across a network of computers, and still allows public to view and verify integrity of the records being kept.

[0072] Although the proposed system has been explained to include all the main modules/components/elements, it is completely possible that actual implementations may include only a part of the proposed components/elements/modules or a combination of those or a division of those into sub-modules/sub-components/sub-elements in various combinations across multiple devices that can be operatively coupled with each other, including in the cloud. All such modifications and embodiments are completely within the scope of the present disclosure.

[0073] While some embodiments of the present disclosure have been illustrated and described, those are completely exemplary in nature. The disclosure is not limited to the embodiments as elaborated herein only and it would be apparent to those skilled in the art that numerous modifications besides those already described are possible without departing from the inventive concepts herein. All such modifications, changes, variations, substitutions, and equivalents are completely within the scope of the present disclosure. The inventive subject matter, therefore, is not to be restricted except in the spirit of the appended claims. ADVANTAGES OF THE INVENTION

[0074] Present disclosure provides a mechanism for utmost data privacy for the record producers and creators.

[0075] Present disclosure provides a strong and a tamper proof decentralized trust based system for trusting and verifying the integrity of the record data for the record consumers.