# US 2026/0074910 A1 · Time-ordered cryptographic ledgers

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

- Number: US 2026/0074910 A1
- Document ID: US20260074910A1
- Status: Published application
- Kind: A1
- Application number: 19/102,760
- Filed: 2023-08-10
- Published: 2026-03-12
- Earliest claimed: 2022-08-11
- Assignees: The Regents of the University of Colorado, a body corporate
- Applicants: The Regents of the University of Colorado, A Body Corporate
- Inventors: Jasper E.T. Palfree; Lynden K. Shalm
- Web page: https://patentgrep.com/patent/US20260074910A1

## CPC

- H04L 9/3236: {using cryptographic hash functions}
- H04L 67/104: Peer-to-peer [P2P] networks
- G06F 21/64: Protecting data integrity, e.g. using checksums, certificates or signatures
- 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

A method includes receiving mix-in data from a remote computer node storing a remote ledger of a plurality of time-ordered cryptographic ledgers forming a tapestry. The mix-in data includes a remote identifier that uniquely identifies the remote ledger among the plurality of time-ordered cryptographic ledgers. The mix-in data also includes a remote hash value stored in a block of the remote ledger. The method includes generating a new hash value by hashing local event data, the mix-in data, a local identifier that uniquely identifies a local ledger among the plurality of time-ordered cryptographic ledgers, and a most-recent hash value of the local ledger. The method also includes constructing a new block that stores the local event data, the mix-in data, the local identifier, the most-recent hash value, and the new hash value. The method also includes updating the local ledger with the new block.

## Claims

### Claim 1

A method performed by a local computer node, comprising:
receiving mix-in data from a remote computer node of one or more remote computer nodes storing one or more remote ledgers, respectively, of a plurality of time-ordered cryptographic ledgers forming a tapestry, the mix-in data comprising:
a remote identifier that uniquely identifies a remote ledger, of the one or more remote ledgers, among the plurality of time-ordered cryptographic ledgers, the remote ledger being stored on the remote computer node; and
a remote hash value stored in a block of the remote ledger;
generating a new hash value by hashing (i) local event data, (ii) the mix-in data, (iii) a local identifier that uniquely identifies a local ledger among the plurality of time-ordered cryptographic ledgers, and (iv) a most-recent hash value of a most-recent block of the local ledger;
constructing a new block that stores (i) the local event data, (ii) the mix-in data, (iii) the local identifier, (iv) the most-recent hash value, and (v) the new hash value; and
updating the local ledger with the new block.

### Claim 2 (depends on 1)

The method of claim 1, further comprising transmitting, to at least one of the one or more remote computer nodes, (i) the new hash value and (ii) the local identifier.

### Claim 3 (depends on 1)

The method of claim 1, further comprising receiving the local event data.

### Claim 4 (depends on 1)

The method of claim 1, further comprising generating a time stamp, the local event data including the time stamp.

### Claim 5 (depends on 1)

The method of claim 1, further comprising generating one or more random numbers, the local event data including the one or more random numbers.

### Claim 6 (depends on 1)

The method of claim 1, wherein said updating comprises transmitting the new block to a local computer system storing the local ledger.

### Claim 7 (depends on 1)

The method of claim 1, further comprising receiving the local identifier and the most-recent hash value from a local computer system storing the local ledger.

### Claim 8 (depends on 1)

The method of claim 1, wherein:
the method further comprises storing the local ledger; and
said updating comprises appending the new block to the local ledger.

### Claim 9 (depends on 1)

The method of claim 1, further comprising:
traversing the tapestry in reverse order to search for a path that (i) starts with a first event stored in a first block of a first ledger of the plurality of time-ordered cryptographic ledgers and (ii) ends with a second event stored in a second block of a second ledger of the plurality of time-ordered cryptographic ledgers; and
outputting, in response to the path being found, an indication that the second event preceded the first event.

### Claim 10 (depends on 9)

The method of claim 9, further comprising:
traversing, in response to the path not being found, the tapestry in reverse order to search for an alternative path that (i) starts with the second event and (ii) ends with the first event; and
outputting, in response to the alternative path being found, an indication that the first event preceded the second event.

### Claim 11 (depends on 10)

The method of claim 10, further comprising outputting, in response to the alternative path not being found, an indication that the first and second events occurred simultaneously.

### Claim 12 (depends on 9)

The method of claim 9, wherein the local ledger is one of the first ledger and the second ledger.

### Claim 13

A local computer node, comprising:
a processor; and
a memory in communication with the processor, the memory storing machine-readable instructions that, when executed by the processor, control the local computer node to:
receive mix-in data from a remote computer node of one or more remote computer nodes storing one or more remote ledgers, respectively, of a plurality of time-ordered cryptographic ledgers forming a tapestry, the mix-in data comprising:
a remote identifier that uniquely identifies a remote ledger, of the one or more remote ledgers, among the plurality of time-ordered cryptographic ledgers, the remote ledger being stored on the remote computer node, and
a remote hash value stored in a block of the remote ledger,
generate a new hash value by hashing (i) local event data, (ii) the mix-in data, (iii) a local identifier that uniquely identifies a local ledger among the plurality of time-ordered cryptographic ledgers, and (iv) a most-recent hash value of a most-recent block of the local ledger,
construct a new block that stores (i) the local event data, (ii) the mix-in data, (iii) the local identifier, (iv) the most-recent hash value, and (v) the new hash value, and
update the local ledger with the new block.

### Claim 14 (depends on 13)

The local computer node of claim 13, the memory storing additional machine-readable instructions that, when executed by the processor, control the local computer node to transmit, to at least one of the one or more remote computer nodes, (i) the new hash value and (ii) the local identifier.

### Claim 15 (depends on 13)

The local computer node of claim 13, further comprising a local event generator configured to generate the local event data.

### Claim 16 (depends on 15)

The local computer node of claim 15, the local event generator comprising a random number generator configured to generate one or more random numbers, the local event data including the one or more random numbers.

### Claim 17 (depends on 13)

The local computer node of claim 13, further comprising a clock configured to generate a time stamp, the local event data including the time stamp.

### Claim 18 (depends on 13)

The local computer node of claim 13, the memory storing additional machine-readable instructions that, when executed by the processor, control the local computer node to transmit the new block to a local computer system storing the local ledger.

### Claim 19 (depends on 13)

The local computer node of claim 13, the memory storing additional machine-readable instructions that, when executed by the processor, control the local computer node to receive the local identifier and the most-recent hash value from a local computer system storing the local ledger.

### Claim 20 (depends on 19)

The local computer node of claim 19, being one of a tablet, a smartphone, and a laptop computer.

### Claim 21 (depends on 13)

The local computer node of claim 13, wherein:
the memory stores the local ledger; and
the machine-readable instructions that, when executed by the processor, control the local computer node to update the local ledger include machine-readable instructions that, when executed by the processor, control the local computer node to append the new block to the local ledger.

### Claim 22 (depends on 13)

The local computer node of claim 13, the memory storing additional machine-readable instructions that, when executed by the processor, control the local computer node to:
traverse the tapestry in reverse order to search for a path that (i) starts with a first event stored in a first block of a first ledger of the plurality of time-ordered cryptographic ledgers and (ii) ends with a second event stored in a second block of a second ledger of the plurality of time-ordered cryptographic ledgers, and
output, in response to the path being found, an indication that the second event preceded the first event.

### Claim 23 (depends on 22)

The local computer node of claim 22, the memory storing additional machine-readable instructions that, when executed by the processor, control the local computer node to:
traverse, in response to the path not being found, the tapestry in reverse order to search for an alternative path that (i) starts with the second event and (ii) ends with the first event, and
output, in response to the alternative path being found, an indication that the first event preceded the second event.

### Claim 24 (depends on 23)

The local computer node of claim 23, the memory storing additional machine-readable instructions that, when executed by the processor, control the local computer node to output, in response to the alternative path not being found, an indication that the first and second events occurred simultaneously.

### Claim 25 (depends on 22)

The local computer node of claim 22, the local ledger being one of the first ledger and the second ledger.
