# US 12,222,961 B2 · Dual ledger syncing

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

- Number: US 12,222,961 B2
- Document ID: US12222961B2
- Status: Granted
- Kind: B2
- Application number: 18/616,165
- Filed: 2024-03-26
- Published: 2024-12-26
- Granted: 2025-02-11
- Earliest claimed: 2023-03-24
- Assignees: TRETE Inc.
- Applicants: TRETE Inc.
- Inventors: Damien Patton
- Web page: https://patentgrep.com/patent/US12222961B2

## CPC

- G06Q 40/04: Trading; Exchange, e.g. stocks, commodities, derivatives or currency exchange
- G06F 16/215: Improving data quality; Data cleansing, e.g. de-duplication, removing invalid entries or correcting typographical errors
- G06F 16/2358: {Change logging, detection, and notification (replication G06F16/27)}
- G06F 16/2379: {Updates performed during online database operations; commit processing}
- G06F 16/275: {Synchronous replication}
- G06Q 20/02: involving a neutral party, e.g. certification authority, notary or trusted third party [TTP]
- G06Q 20/065: {using e-cash}
- G06Q 20/363: {with the personal data of a user}
- G06Q 20/3674: {involving authentication}
- G06Q 20/381: {Currency conversion}
- G06Q 20/3829: {involving key management}
- G06Q 20/389: {Keeping log of transactions for guaranteeing non-repudiation of a transaction}
- G06Q 20/401: {Transaction verification}
- G06Q 20/42: Confirmation, e.g. check or permission by the legal debtor of payment
- G06Q 30/0613: {using intermediate agents}
- G06Q 40/06: Asset management; Financial planning or analysis
- H04L 9/3239: {involving non-keyed hash functions, e.g. modification detection codes [MDCs], MD5, SHA or RIPEMD}
- H04L 9/50: {using hash chains, e.g. blockchains or hash trees}
- H04L 67/1097: for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
- G06F 16/2365: {Ensuring data consistency and integrity}
- G06F 16/27: Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
- G06Q 2220/00: Business processing using cryptography
- G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- 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

In certain aspects, a computer-implemented method includes monitoring data entries written on a private primary ledger. The computer-implemented method includes recording the data entries written on the private primary ledger to an immutable public secondary ledger.

## Claims

### Claim 1

A computer-implemented method comprising:
settling a transaction at an Alternative Trading System (ATS) changing ownership in an asset;
accessing transaction data resulting from the settled transaction;
accessing an intentional lag time defining a specified amount of time to delay between detecting a data entry being written to a Web2 database and semi-redundantly-syncing a blockchain with the Web2 database, the specified amount of time increasing the likelihood of written data entries being fully complete and correct at the Web2 database prior to syncing;
monitoring activity at the Web2 database;
detecting a part of the transaction data captured to the Web2 database reflecting the asset ownership change in a capitalization table tracking ownership in the asset at the Web2 database during the monitoring, the part of the transaction data and another part of the transaction data included in a plurality of parts of the transaction data;
intentionally delaying syncing the blockchain with the Web2 database by the specified amount of time subsequent and responsive to detecting the part of the transaction data being captured;
writing the other part of the transaction data to the Web2 database during the intentional delay; and
after the intentional delay, automatically semi-redundantly syncing the blockchain with the Web2 database by recording at least a portion of the transaction data, including data from the other part of the transaction data, from the Web2 database to the blockchain.

### Claim 2 (depends on 1)

The computer-implemented method of claim 1, wherein accessing an intentional lag time comprises accessing an intentional lag time defining the amount length of time to balance data integrity risk associated with syncing the immutable public ledger with the mutable ledger relative to update date frequency at the immutable public ledger.

### Claim 3 (depends on 1)

The computer-implemented method of claim 1, wherein accessing an intentional lag time comprises accessing a random lag time defining the specified amount of time selected randomly by a randomizer.

### Claim 4 (depends on 1)

The computer-implemented method of claim 1, further comprising:
detecting other data written to the Web2 database during the monitoring;
delaying syncing the blockchain with the Web2 database by the specified amount of time after detecting the part of the second written other data being written entry; and
after the delay, automatically semi-redundantly syncing the immutable public ledger blockchain with the mutable ledger Web2 database by recording at least a portion of the other data to the blockchain.

### Claim 5 (depends on 1)

The computer-implemented method of claim 1, further comprising auditing the integrity of the Web2 database including:
comparing a selected data entry written on the Web2 database at a particular date with a corresponding data entry on the blockchain at a present date back to the particular date;
detecting a mismatch between the selected data entry and the corresponding data entry; and
facilitating transmission of an alert based on the detected mismatch.

### Claim 6 (depends on 1)

The computer-implemented method of claim 1:
wherein detecting a part of the transaction data comprises detecting personally identifiable information and other transaction information;
further comprising generating a hashID of the personally identifiable information;
further comprising storing the hashID at a storage location outside the blockchain; and
wherein semi-redundantly syncing the blockchain with the Web2 database comprises recording the other transaction information along with the hashID to the blockchain.

### Claim 7 (depends on 1)

The computer-implemented method of claim 1, wherein detecting a part of the transaction data captured to the Web2 database during the monitoring comprises detecting a part of the transaction data that incudes personally identifiable information; and
wherein automatically semi-redundantly syncing the blockchain with the Web2 database comprises recording the transaction data to the blockchain without the personally identifiable information.

### Claim 8 (depends on 1)

The computer-implemented method of claim 1, wherein accessing an intentional lag time defining a specified amount of time to delay between detecting a data entry being written to a Web2 database and semi-redundantly syncing a blockchain with the Web2 database comprises accessing an intentional lag time defining a specified fixed amount of time to delay between detecting a data entry being written to the Web2 database and semi-redundantly syncing the blockchain with the Web2 database.

### Claim 9 (depends on 1)

The computer-implemented method of claim 1, wherein accessing an intentional lag time comprises accessing a lag time defining a specified amount of time to delay minimizing the likelihood of having to update the transaction data within the blockchain after the at least a portion of the transaction data is recorded to the blockchain.

### Claim 10 (depends on 1)

The computer-implemented method of claim 1, wherein accessing an intentional lag time comprises accessing an intentional lag time defining a specified amount of time to delay between detecting a data entry being written to a Web2 database and semi-redundantly syncing the blockchain with the Web2 database based on business practices implemented at the Alternative Trading System (ATS).

### Claim 11 (depends on 1)

The computer-implemented method of claim 1, wherein accessing an intentional lag time defining a specified amount of time to delay between detecting a data entry being written to a Web2 database and semi-redundantly syncing a blockchain with the Web2 database comprises accessing an intentional lag time defining 24 hours to delay between detecting a data entry being written to the Web2 database and semi-redundantly syncing the blockchain with the Web2 database.

### Claim 12 (depends on 1)

The computer-implemented method of claim 1,
wherein, after the intentional delay, automatically semi-redundantly syncing the blockchain with the Web2 database comprises automatically semi-redundantly syncing the blockchain with the Web2 database bridging data across Web2 and Web3.

### Claim 13

A system comprising;
a hardware processor;
system memory coupled to the hardware processor and storing instructions configured to cause the hardware processor to:
settle a transaction at an Alternative Trading System (ATS) changing ownership in an asset;
access transaction data resulting from the settled transaction;
access an intentional lag time defining a specified amount of time to delay between detecting a data entry part written to a Web2 database and semi-redundantly syncing a blockchain with the Web2 database, the specified amount of time increasing the likelihood of written data entries being fully complete and correct at the Web2 database prior to syncing;
monitor activity at the Web2 database mutable ledger;
detect a part of the transaction data captured to the Web2 database reflecting the asset ownership change in a capitalization table tracking ownership in the asset at the Web2 database during the monitoring, the part of the transaction data and another part of the transaction data included in a plurality of parts of the transaction data;
intentionally delay syncing the blockchain with the Web2 database by the specified length of time subsequent and responsive to detecting the part of the transaction data being captured;
write the other part of the transaction data to the Web2 database during the intentional delay; and
after the intentional delay, automatically semi-redundantly sync the blockchain with the Web2 database by recording at least a portion of the transaction data, including data from the other part of the transaction data, from the Web2 database to the blockchain.

### Claim 14 (depends on 13)

The system of claim 13, wherein instructions configured to cause the hardware processor to access an intentional lag time comprise instructions configured to cause the hardware processor to access an intentional lag time defining the specified amount of time to balance data integrity risk associated with syncing the immutable public ledger with the mutable ledger relative to update date frequency at the immutable public ledger.

### Claim 15 (depends on 13)

The system of claim 13, wherein instructions configured to cause the hardware processor to access an intentional lag time comprise instructions configured to cause the hardware processor to access a random lag time defining the specified amount of time selected randomly by a randomizer.

### Claim 16 (depends on 13)

The system of claim 13, further comprising instructions configured to cause the hardware processor to:
detect other data written to the Web2 database during the monitoring;
delay syncing the blockchain with the Web2 database by the specified length of time after detecting the other data being written; and
after the delay, automatically semi-redundantly sync the blockchain with the Web2 database by recording at least a portion of the other data to the blockchain.

### Claim 17 (depends on 13)

The system of claim 13, further comprising instructions configured to cause the hardware processor to audit the integrity of the Web2 database including:
compare a selected data entry written on the Web2 database at a particular date with a corresponding data entry on the blockchain at a present date back to the particular date;
detect a mismatch between the selected data entry and the corresponding data entry; and
facilitate transmission of an alert based on the detected mismatch.