Audit chain for private blockchain
Provided is a system and method for verifying a blockchain using an external audit chain. The system may include an engine which facilitates communication between two or more independent blockchains. In one example, the method may include reading block data of a source data block that is stored among a hash-linked chain of data blocks on a blockchain, verifying a hash of the source block based on the block data that is read, generating a token based on the hash verification of the source block and storing the generated token in a verification block among the hash-linked chain of blocks on the blockchain to create a verification point on the blockchain, and storing a copy of the generated token in a block among a hash-linked chain of blocks on an audit blockchain that is independent from the blockchain.
1. A computing system comprising:
a processor configured to
detect a triggering event associated with a blockchain ledger,
in response to detection of the triggering event, verify block hashes of a subset of blocks on the blockchain ledger and generate a verification token for the subset of blocks on the blockchain ledger based on the verification of the block hashes, and
store the verification token and block details of the subset of blocks in a block on a different blockchain ledger.
2. The computing system of claim 1 , wherein the triggering event comprises detecting, by the processor, that a threshold number of blocks have been committed to the blockchain ledger since a previous verification token was created.
3. The computing system of claim 1 , wherein the triggering event comprises detecting, by the processor, that a predetermined period of time has elapsed since a previous verification token was created.
4. The computing system of claim 1 , wherein the triggering event comprises detecting a random request from a software application.
5. The computing system of claim 1 , wherein the processor is further configured to store a chain identifier of the blockchain ledger with the verification token in the block on the different blockchain ledger.
6. The computing system of claim 1 , wherein the processor is further configured to verify block hashes of a plurality of blocks on the different blockchain ledger and store a global verification token on the blockchain ledger based on the block hash verifications of the different blockchain ledger.
7. The computing system of claim 1 , wherein the processor is configured to store identifiers of the subset of blocks and an indicator of whether the verification of the block hashes were successful via the block details in the block on the different blockchain ledger.
8. The computing system of claim 1 , wherein the subset of blocks on the blockchain ledger comprise a partial and continuous sequence of blocks that were previously committed to the blockchain ledger.
9. The computing system of claim 1 , wherein the processor is further configured to generate an additional verification token for a different subset of blocks on the blockchain ledger in response to an additional trigger, and store the additional verification token for the different subset of blocks in another block on the different blockchain ledger.
10. A method comprising:
detecting a triggering event associated with a blockchain ledger;
in response to detection of the triggering event, verifying block hashes of a subset of blocks on the blockchain ledger and generating a verification token for the subset of blocks on the blockchain ledger based on the verification of the block hashes; and
storing the verification token and block details of the subset of blocks in a block on a different blockchain ledger.
11. The method of claim 10 , wherein the detecting the triggering event comprises detecting that a threshold number of blocks have been committed to the blockchain ledger since a previous verification token was created.
12. The method of claim 10 , wherein the detecting the triggering event comprises detecting that a predetermined period of time has elapsed since a previous verification token was created.
13. The method of claim 10 , wherein the detecting the triggering event comprises detecting a random request from a software application.
14. The method of claim 10 , wherein the storing comprises storing a chain identifier of the blockchain ledger with the verification token in the block on the different blockchain ledger.
15. The method of claim 10 , wherein the method further comprises verifying block hashes of a plurality of blocks on the different blockchain ledger and store a global verification token on the blockchain ledger based on the block hash verifications of the different blockchain ledger.
16. The method of claim 10 , wherein the storing comprises storing identifiers of the subset of blocks and an indicator of whether the verification of the block hashes were successful via the block details in the block on the different blockchain ledger.
17. The method of claim 10 , wherein the subset of blocks on the blockchain ledger comprise a partial and continuous sequence of blocks that were previously committed to the blockchain ledger.
18. The method of claim 10 , wherein the method further comprises generating an additional verification token for a different subset of blocks on the blockchain ledger in response to an additional trigger, and storing the additional verification token for the different subset of blocks in another block on the different blockchain ledger.
19. A non-transitory computer-readable medium comprising instructions which when executed by a processor cause a computer to perform a method comprising:
detecting a triggering event associated with a blockchain ledger;
in response to detection of the triggering event, verifying block hashes of a subset of blocks on the blockchain ledger and generating a verification token for the subset of blocks on the blockchain ledger based on the verification of the block hashes; and
storing the verification token and block details of the subset of blocks in a block on a different blockchain ledger.
20. The non-transitory computer-readable medium of claim 19 , wherein the detecting the triggering event comprises detecting one or more of a threshold number of blocks being committed to the blockchain ledger since a previous verification token was created, detecting that a predetermined period of time has elapsed since a previous verification token was created, and detecting a random request from a software application.