# US 2021/0334176 A1 · High performance distributed system of record with Unspent Transaction Output (UTXO) database snapshot integrity

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

- Number: US 2021/0334176 A1
- Document ID: US20210334176A1
- Status: Published application
- Kind: A1
- Application number: 17/011,626
- Filed: 2020-09-03
- Published: 2021-10-28
- Earliest claimed: 2020-04-28
- Assignees: Akamai Technologies, Inc.
- Applicants: Akamai Technologies, Inc.
- Inventors: William R. Sears; Leen AlShenibr; Samuel Erb
- Web page: https://patentgrep.com/patent/US20210334176A1

## CPC

- G06F 11/1474: in transactions (updating of structured data in databases G06F16/23)
- H04L 9/3239: {involving non-keyed hash functions, e.g. modification detection codes [MDCs], MD5, SHA or RIPEMD}
- G06F 11/1004: {to protect a block of data words, e.g. CRC or checksum (G06F11/1076 takes precedence; security arrangements for protecting computers or computer systems against unauthorized activity G06F21/00)}
- G06F 11/1448: {Management of the data involved in backup or backup restore}
- G06F 16/2379: {Updates performed during online database operations; commit processing}
- G06F 16/27: Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
- G06F 21/602: {Providing cryptographic facilities or services}
- G06F 21/64: Protecting data integrity, e.g. using checksums, certificates or signatures
- H04L 9/0643: {Hash functions, e.g. MD5, SHA, HMAC or f9 MAC}
- H04L 9/50: {using hash chains, e.g. blockchains or hash trees}
- G06F 2201/80: Database-specific techniques
- G06F 2201/82: Solving problems relating to consistency
- G06F 2201/84: Using snapshots, i.e. a logical point-in-time copy of the data
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

A method operative in association with a set of transaction handling computing elements that comprise a network core that receive and process transaction requests into an append-only immutable chain of data blocks, wherein a data block is a collection of transactions, and wherein presence of a transaction recorded within a data block is verifiable via a cryptographic hash, and wherein Unspent Transaction Output (UTXO) data structures supporting the immutable chain of data blocks are maintained in a UTXO database, wherein a UXTO is an output from a finalized transaction that contains a value. The technique herein includes periodically snapshotting a given portion of the UTXO database to generate a hash. The hash of the snapshot is recorded within the immutable chain of data blocks, and preferably within a given block header. In responsive to a receipt of a recovery request, and to facilitate recovery of the system to a provably-known state, a consensus algorithm is executed over the UXTO snapshot.

## Claims

### Claim 1

A method operative in association with a set of transaction handling computing elements that comprise a network core that receive and process transaction requests into an append-only immutable chain of data blocks, wherein a data block is a collection of transactions, and wherein presence of a transaction recorded within a data block is verifiable via a cryptographic hash, and wherein Unspent Transaction Output (UTXO) data structures supporting the immutable chain of data blocks are maintained in a UTXO database, wherein a UXTO is an output from a finalized transaction that contains a value, comprising:
periodically snapshotting a given portion of the UTXO database to generate a snapshot;
applying a given function to the snapshot to generate a hash of the snapshot;
recording the hash of the snapshot within the immutable chain of data blocks; and
responsive to a receipt of a recovery request, executing a consensus algorithm over the UXTO snapshot to recover the given portion of the UTXO database.

### Claim 2 (depends on 1)

The method as described in claim 1 wherein the given portion of the UTXO database is a shard of the UTXO database.

### Claim 3 (depends on 1)

The method as described in claim 1 wherein the append-only immutable chain of data blocks is a blockchain.

### Claim 4 (depends on 1)

The method as described in claim 1 wherein the hash certifies authenticity of the snapshot.

### Claim 5 (depends on 1)

The method as described in claim 1 wherein the hash is recorded into a block header of a block in the append-only immutable chain of data blocks.

### Claim 6 (depends on 5)

The method as described in claim 5 wherein the hash in included in a hash used to form a next block of the append-only immutable chain of data blocks.

### Claim 7 (depends on 1)

The method as described in claim 1 wherein the recovery request is associated with an attempt to restore the set of transaction handling computing elements into a provably-known state.

### Claim 8 (depends on 7)

The method as described in claim 7 wherein a restore into the provably-known state includes:
obtaining the snapshot, together with a chain of transactions included in the immutable chain of data blocks while the snapshot was being created and the hash recorded therein;
restoring the UTXO database;
while the UTXO database is being restored, re-generating the hash of the snapshot;
replaying each of the transactions generated starting with a first block, and continuing until a given block that contains the snapshot hash is reached; and
verifying the re-generated snapshot hash and the hash of the given block.

### Claim 9 (depends on 1)

The method as described in claim 1 wherein at least one UTXO data structure is configured to include information either in addition to or in lieu of the address and value to define a Transaction Output (TXO).

### Claim 10 (depends on 9)

The method as described in claim 9 wherein the TXO has an associated type.

### Claim 11 (depends on 10)

The method as described in claim 10 wherein the associated type is one of: a Reference TXO (RTXO), and an idempotency TXO (ITXO).

### Claim 12

A method operative in association with a set of transaction handling computing elements that comprise a network core that receive and process transaction requests into an append-only immutable chain of data blocks, wherein a data block is a collection of transactions, and wherein presence of a transaction recorded within a data block is verifiable via a cryptographic hash, and wherein Unspent Transaction Output (UTXO) data structures supporting the immutable chain of data blocks are maintained in a UTXO database, wherein a UXTO is an output from a finalized transaction that contains a value, comprising:
sharding the UTXO database into a set of partitions;
storing each partition of the UTXO database independently from other partitions in the set of partitions;
for at least one partition:
periodically snapshotting UTXOs therein to generate a hash;
recording the hash of the snapshot within the immutable chain of data blocks.

### Claim 13 (depends on 12)

The method as described in claim 12 further including:
responsive to a receipt of a recovery request, executing a consensus algorithm over the UXTO snapshot for the at least one partition.

### Claim 14 (depends on 13)

The method as described in claim 13 wherein the recovery request is associated with an attempt to restore the set of transaction handling computing elements into a provably-known state.

### Claim 15 (depends on 14)

The method as described in claim 14 wherein a restore into the provably-known state includes:
for the at least one partition:
obtaining the snapshot, together with a chain of transactions included in the immutable chain of data blocks while the snapshot was being created and the hash recorded therein;
restoring the UTXO database;
while the UTXO database is being restored, re-generating the hash of the snapshot;
replaying each of the transactions generated starting with a first block, and continuing until a given block that contains the snapshot hash is reached; and
verifying the re-generated snapshot hash and the hash of the given block.

### Claim 16 (depends on 12)

The method as described in claim 12 further including snapshotting at least one other partition of the set of partitions.

### Claim 17 (depends on 16)

The method as described in claim 16 further computing a checksum for a UTXO snapshot that comprises the at least one partition and the at least one other partition.

### Claim 18 (depends on 16)

The method as described in claim 16 wherein the at least one partition and the at least other partition are snapshotted concurrently.
