# US 2026/0089008 A1 · Data truncation from cryptographic data structures

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2026/0089008 A1
- Document ID: US20260089008A1
- Status: Published application
- Kind: A1
- Application number: 19/402,331
- Filed: 2025-11-26
- Published: 2026-03-26
- Earliest claimed: 2020-05-29
- Assignees: Microsoft Technology Licensing, LLC
- Applicants: Microsoft Technology Licensing, LLC
- Inventors: Panagiotis ANTONOPOULOS; Jakub J. SZYMASZEK; Raghav KAUSHIK; Conor J. CUNNINGHAM
- Web page: https://patentgrep.com/patent/US20260089008A1

## CPC

- H04L 9/3239: {involving non-keyed hash functions, e.g. modification detection codes [MDCs], MD5, SHA or RIPEMD}
- G06F 16/2282: {Tablespace storage structures; Management thereof}
- G06F 16/2379: {Updates performed during online database operations; commit processing}
- G06F 16/284: {Relational databases}
- H04L 9/3247: {involving digital signatures}
- H04L 9/3297: {involving time stamps, e.g. generation of time stamps}
- H04L 9/50: {using hash chains, e.g. blockchains or hash trees}
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

Methods for asynchronously determining relational data integrity using cryptographic data structures are performed by systems and devices. Changes in current tables of relational databases are reflected in associated history tables. Cryptographic hybrid blockchain ledgers are updated with transaction records, for entry changes in current and history tables, including transaction information and hash values of corresponding entry changes. Hybrid blockchain ledgers also include root hash values of Merkle trees of transaction records in current blocks, and hash values of prior blocks. A current block receipt is asynchronously generated and provided as a single hash value from which the validity states of the tables and ledger are able to be verified. Cryptographic receipts of specific transactions reflected in table entry changes are generated and provide immutable evidence of specific transaction existence for users. Ledger-enabled tables are provided for mixed database operations with ledger-disabled tables, and temporal history table database operations are enabled.

## Claims

### Claim 1

A method performed by a computing system, the method comprising:
designating a first record in a ledger for truncation based on the first record satisfying a truncation criterion;
generating state capture data comprising a first hash indicative of a valid state of the first record;
inserting the state capture data into the ledger; and
truncating the first record from the ledger.

### Claim 2 (depends on 1)

The method of claim 1, further comprising:
including, in a history table, a first entry from a current table of a relational database based on the first entry from the current table being designated in a first transaction that results in deletion of a first entry from the current table;
generating a first transaction hash value by hashing at least the first entry in the history table; and
inserting, into the first record, at least the first transaction hash.

### Claim 3 (depends on 2)

The method of claim 2, wherein the truncation criterion comprises a determination that at least one of the first record in the ledger or the first entry in the history table is unassociated with an entry in the current table.

### Claim 4 (depends on 1)

The method of claim 1, further comprising:
including in a history table a first entry from a current table of a relational database based on the first entry from the current table being designated in a transaction that specifies a change to the first entry;
generating a first transaction hash value by hashing the first entry in the history table and a changed first entry in the current table that is generated by the transaction that was performed on the first entry;
inserting, into the first record, at least the first transaction hash;
designating the first entry in the history table for truncation based on the first entry in the history table satisfying the truncation criterion; and
truncating the first entry from the history table,
wherein the first hash is further indicative of a valid state of the first entry in the history table.

### Claim 5 (depends on 4)

The method of claim 4, wherein the truncation criterion comprises at least one of:
an age of data associated with at least one of the first record in the ledger or the first entry in the history table satisfying a first temporal threshold; or
an access frequency associated with at least one of the first record in the ledger or the first entry in the history table satisfying a frequency threshold.

### Claim 6 (depends on 5)

The method of claim 5, wherein the first temporal threshold comprises temporal period associated with a data preservation requirement.

### Claim 7 (depends on 1)

The method of claim 1, wherein the state capture data provides proof of the presence and integrity of the first record at the time of truncation of the first record from the ledger.

### Claim 8

A system, comprising:
a processor; and
a memory comprising instructions that, when executed by the processor, cause the processor to:
designate a first record in a ledger for truncation based on the first record satisfying a truncation criterion;
generate state capture data comprising a first hash indicative of a valid state of the first record;
insert the state capture data into the ledger; and
truncate the first record from the ledger.

### Claim 9 (depends on 8)

The system of claim 8, wherein the instructions, when executed by the processor, further cause the processor to:
include, in a history table, a first entry from a current table of a relational database based on the first entry from the current table being designated in a first transaction that results in deletion of a first entry from the current table;
generate a first transaction hash value by hashing at least the first entry in the history table; and
insert, into the first record, at least the first transaction hash.

### Claim 10 (depends on 9)

The system of claim 9, wherein the truncation criterion comprises a determination that at least one of the first record in the ledger or the first entry in the history table is unassociated with an entry in the current table.

### Claim 11 (depends on 8)

The system of claim 8, wherein the instructions, when executed by the processor, further cause the processor to:
include in a history table a first entry from a current table of a relational database based on the first entry from the current table being designated in a transaction that specifies a change to the first entry;
generate a first transaction hash value by hashing the first entry in the history table and a changed first entry in the current table that is generated by the transaction that was performed on the first entry;
insert, into the first record, at least the first transaction hash;
designate the first entry in the history table for truncation based on the first entry in the history table satisfying the truncation criterion; and
truncate the first entry from the history table,
wherein the first hash is further indicative of a valid state of the first entry in the history table.

### Claim 12 (depends on 11)

The system of claim 11, wherein the truncation criterion comprises at least one of:
an age of data associated with at least one of the first record in the ledger or the first entry in the history table satisfying a first temporal threshold; or
an access frequency associated with at least one of the first record in the ledger or the first entry in the history table satisfying a frequency threshold.

### Claim 13 (depends on 12)

The system of claim 12, wherein the first temporal threshold comprises temporal period associated with a data preservation requirement.

### Claim 14 (depends on 8)

The system of claim 8, wherein the state capture data provides proof of the presence and integrity of the first record at the time of truncation of the first record from the ledger.

### Claim 15

A computer-readable storage medium comprising instructions that, when executed by a processor, cause the processor to:
designate a first record in a ledger for truncation based on the first record satisfying a truncation criterion;
generate state capture data comprising a first hash indicative of a valid state of the first record;
insert the state capture data into the ledger; and
truncate the first record from the ledger.

### Claim 16 (depends on 15)

The computer-readable storage medium of claim 15, wherein the instructions, when executed by the processor, further cause the processor to:
include, in a history table, a first entry from a current table of a relational database based on the first entry from the current table being designated in a first transaction that results in deletion of a first entry from the current table;
generate a first transaction hash value by hashing at least the first entry in the history table; and
insert, into the first record, at least the first transaction hash.

### Claim 17 (depends on 16)

The computer-readable storage medium of claim 16, wherein the truncation criterion comprises a determination that at least one of the first record in the ledger or the first entry in the history table is unassociated with an entry in the current table.

### Claim 18 (depends on 15)

The computer-readable storage medium of claim 15, wherein the instructions, when executed by the processor, further cause the processor to:
include in a history table a first entry from a current table of a relational database based on the first entry from the current table being designated in a transaction that specifies a change to the first entry;
generate a first transaction hash value by hashing the first entry in the history table and a changed first entry in the current table that is generated by the transaction that was performed on the first entry;
insert, into the first record, at least the first transaction hash;
designate the first entry in the history table for truncation based on the first entry in the history table satisfying the truncation criterion; and
truncate the first entry from the history table,
wherein the first hash is further indicative of a valid state of the first entry in the history table.

### Claim 19 (depends on 18)

The computer-readable storage medium of claim 18, wherein the truncation criterion comprises at least one of:
an age of data associated with at least one of the first record in the ledger or the first entry in the history table satisfying a first temporal threshold; or
an access frequency associated with at least one of the first record in the ledger or the first entry in the history table satisfying a frequency threshold.

### Claim 20 (depends on 15)

The computer-readable storage medium of claim 15, wherein the state capture data provides proof of the presence and integrity of the first record at the time of truncation of the first record from the ledger.
