Audit chain for hashes using tokenization
A first hash of a record is retrieved. The first hash is tokenized by storing the first hash in a tokenization table that has a corresponding hash token. A request is received to validate the record. The request to validate the record comprises a second hash of the record and a second hash token. In response to receiving the request to validate the record, the record is validated by looking up the first hash in the tokenization table using the second hash token and comparing the looked up first hash to the second hash. In response to the looked up first hash being the same as the second hash, the record is validated. In response to the looked up first hash not being the same as the second hash, the record is not validated.
1 . A system comprising:
a microprocessor; and
a computer readable medium, coupled with the microprocessor and comprising microprocessor readable and executable instructions that, when executed by the microprocessor, cause the microprocessor to:
retrieve a first hash of a record;
tokenize the first hash by storing the first hash in a tokenization table that has a corresponding hash token, the corresponding hash token not being mathematically related to the first hash;
receive a request to validate the record, wherein the request to validate the record comprises a second hash of the record and a second hash token, wherein the record is a blockchain, wherein the second hash token comprises a plurality of bash tokens, and wherein the plurality of hash tokens are stored in separate tokenization tables based on a plurality of different types of blocks and/or different tenants;
in response to receiving the request to validate the record, validate the record by:
looking up the first hash in the tokenization table using the second hash token; and
comparing the looked-up first hash to the second hash;
in response to the looked-up first hash being the same as the second hash, validating the record; and
in response to the looked-up first hash not being the same as the second hash, not validating the record.
2 . The system of claim 1 , wherein the second hash token is stored in the record and wherein storing the second hash token in the record comprises one of: replacing the first hash with the second hash token or adding the second hash token to the record.
3 . The system of claim 2 , wherein storing the second hash token in the record comprises adding the second hash token to the record.
4 . The system of claim 3 , wherein the record is a newly added block in a blockchain and wherein the second hash token is for a hash of a previous block in the blockchain.
5 . The system of claim 3 , wherein the record is a transaction block in a blockchain, wherein the second hash token is for a hash of the blockchain and/or a hash of the transaction block, and wherein the second hash token is not mathematically related to the second hash.
6 . The system of claim 2 , wherein storing the second hash token in the record comprises replacing the first hash with the second hash token.
7 . The system of claim 6 , wherein the second hash token replaces a hash of a previous block in a blockchain.
8 . The system of claim 2 , wherein the second hash token comprises a plurality of hash tokens of previous blocks in a blockchain that are stored in the blockchain and wherein each of the plurality of hash tokens has a corresponding hash in the tokenization table.
9 . The system of claim 1 , wherein the record is a blockchain that comprises a plurality of different types of blocks and wherein the second hash token comprises a plurality of hash tokens for each of the plurality of different types of blocks.
10 . The system of claim 1 , wherein the corresponding hash token has an associated authentication level in order to access the tokenization table.
11 . The system of claim 1 , wherein the corresponding hash token comprises a plurality of corresponding hash tokens associated with a plurality of tenants and wherein each of the plurality of corresponding hash tokens has an associated authentication level to access each of the corresponding hash tokens.
12 . The system of claim 1 , wherein the request to validate the record comprises a tokenization table identifier and wherein the tokenization table identifier is used to find the tokenization table in order to look up the first hash in the tokenization table.
13 . A method comprising:
retrieving, by a microprocessor, a first hash of a record;
tokenizing, by the microprocessor, the first hash by storing the first hash in a tokenization table that has a corresponding hash token, the corresponding hash token not being mathematically related to the first hash;
receiving, by the microprocessor, a request to validate the record, wherein the request to validate the record comprises a second hash of the record and a second hash token, wherein the record is a blockchain that comprises a plurality of different types of blocks and wherein the second hash token comprises a plurality of bash tokens for each of the plurality of different types of blocks;
in response to receiving the request to validate the record, validating the record by:
looking up the first hash in the tokenization table using the second hash token; and
comparing the looked-up first hash to the second hash;
in response to the looked-up first hash being the same as the second hash, validating the record; and
in response to the looked-up first hash not being the same as the second hash, not validating the record.
14 . The method of claim 13 , wherein the second hash token is not mathematically related to the second hash, wherein the second hash token is stored in the record and wherein storing the second hash token in the record comprises one of: replacing the first hash with the second hash token or adding the second hash token to the record.
15 . The method of claim 14 , wherein storing the second hash token in the record comprises adding the second hash token to the record.
16 . The method of claim 15 , wherein the record is a newly added block in a blockchain and wherein the second hash token is for a hash of a previous block in the blockchain.
17 . The method of claim 14 , wherein storing the second hash token in the record comprises replacing the first hash with the second hash token.
18 . A system comprising:
a microprocessor; and
a computer readable medium, coupled with the microprocessor and comprising microprocessor readable and executable instructions that, when executed by the microprocessor, cause the microprocessor to:
receive a first hash of a record from a communication device;
tokenize the first hash by storing the first hash in a tokenization table that has a corresponding hash token, the corresponding hash token not being mathematically related to the first hash;
send the corresponding hash token to the communication device;
receive a request to validate the record from the communication device, wherein the request to validate the record comprises a second hash of the record and a second hash token, wherein the request to validate the record comprises a tokenization table identifier and wherein the tokenization table identifier is used to find the tokenization table to look up the first hash in the tokenization table;
in response to receiving the request to validate the record, validate the record by:
looking up the first hash in the tokenization table using the second hash token; and
comparing the looked-up first hash to the second hash;
in response to the looked-up first hash being the same as the second hash, validating the record; and
in response to the looked-up first hash not being the same as the second hash, not validating the record.
19 . The system of claim 18 , wherein the second hash token is not mathematically related to the second hash.
20 . The system of claim 18 , wherein the record is a blockchain, wherein the second hash token comprises a plurality of hash tokens, and wherein the plurality of hash tokens are stored in separate tokenization tables based on a plurality of different types of blocks and/or different tenants.