# US 12,602,724 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,602,724 B2
- Document ID: US12602724B2
- Status: Granted
- Kind: B2
- Application number: 19/286,621
- Filed: 2025-07-31
- Published: 2025-11-20
- Granted: 2026-04-14
- Earliest claimed: 2023-03-24
- Assignees: TRETE Inc.
- Applicants: TRETE Inc.
- Inventors: Damien Patton; Christian Gratton; Rish Mehta
- Web page: https://patentgrep.com/patent/US12602724B2

## 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/405: {Establishing or using transaction specific rules}
- 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/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/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 database. The computer-implemented method includes recording at least part of the data entries written on the database to a blockchain.

## Claims

### Claim 1

A computer-implemented method comprising:
accessing transaction data resulting from a settled transaction changing ownership in an asset at an Alternative Trading System (ATS) and including evidence of a currency conversion between a stablecoin and another currency, the stablecoin selected based on stablecoin characteristics maintained in a stablecoin record;
accessing an intentional lag time defining a fixed amount of time to delay between detecting a data entry being written to a mutable database and subsequently syncing a blockchain with the mutable database, the specified amount of time increasing the likelihood of written data entries being complete and correct at the mutable database prior to syncing;
detecting a part of the transaction data captured to the mutable database during monitoring the mutable database, the part of the transaction data reflecting the currency conversion and the stablecoin characteristics used during transaction settlement at the mutable database;
delaying syncing the blockchain with the mutable database by the fixed amount of time upon detecting the part of the transaction data being captured; and
responsive to completion of the delay, syncing the blockchain with the mutable database by recording at least a portion of the transaction data from the mutable database to the blockchain, the at least a portion of the transaction data including another part of the transaction data written to the mutable database during the delay.

### 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 blockchain with the database relative to update 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 database during the monitoring;
delaying syncing the blockchain with the database by the specified amount of time after detecting the other data being written; and
after the delay, syncing the blockchain with the database by recording at least a portion of the other data from the database to the blockchain.

### Claim 5 (depends on 1)

The computer-implemented method of claim 1, further comprising auditing the integrity of the database including:
comparing a selected data entry written on the 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 syncing the blockchain with the 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 database comprises detecting a part of the transaction data that incudes personally identifiable information; and
wherein syncing the blockchain with the database comprises recording the transaction data to the blockchain obscuring the personally identifiable information.

### Claim 8 (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 fixed amount of time to delay between detecting a data entry being written to the database and syncing the blockchain with the 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 based on business practices implemented at an Alternative Trading System (ATS).

### Claim 11 (depends on 1)

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

### Claim 12

A system comprising;
a hardware processor;
system memory coupled to the hardware processor and storing instructions configured to cause the hardware processor to:
access transaction data resulting from a settled transaction changing ownership in an asset at an Alternative Trading System (ATS) and including evidence of a currency conversion between a stablecoin and another currency, the stablecoin selected based on stablecoin characteristics maintained in a stablecoin record;
access an intentional lag time defining a fixed amount of time to delay between detecting a data entry being written to a mutable database and subsequently syncing a blockchain with the mutable database, the specified amount of time increasing the likelihood of written data entries being complete and correct at the mutable database prior to syncing;
detect a part of the transaction data captured to the mutable database during monitoring the mutable database, the part of the transaction data reflecting the currency conversion and the stablecoin characteristics used during transaction settlement at the mutable database;
delay syncing the blockchain with the mutable database by the fixed amount of time upon detecting the part of the transaction data being captured; and
responsive to completion of the delay, sync the blockchain with the mutable database by recording at least a portion of the transaction data from the mutable database to the blockchain, the at least a portion of the transaction data including another part of the transaction data written to the mutable database during the delay.

### Claim 13 (depends on 12)

The system of claim 12, 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 blockchain with the database relative to an update frequency at the blockchain.

### Claim 14 (depends on 12)

The system of claim 12, 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 15 (depends on 12)

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

### Claim 16 (depends on 12)

The system of claim 12, further comprising instructions configured to cause the hardware processor to audit the integrity of the database including:
compare a selected data entry written on the 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.

### Claim 17 (depends on 12)

The system of claim 12, wherein instructions configured to cause the hardware processor to detect a part of the transaction data comprises instructions configured to cause the hardware processor to detect personally identifiable information and other transaction information;
further comprising instructions configured to cause the hardware processor to generate a hashID of the personally identifiable information;
further comprising instructions configured to cause the hardware processor store the hashID at a storage location outside the blockchain; and
wherein instructions configured to cause the hardware processor to sync the blockchain with the database comprise instructions configured to cause the hardware processor to record the other transaction information along with the hashID to the blockchain.

### Claim 18 (depends on 12)

The system of claim 12, 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 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 19 (depends on 12)

The system of claim 12, 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 a specified amount of time to delay based on business practices implemented at an Alternative Trading System (ATS).

### Claim 20 (depends on 12)

The system of claim 12, 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 24 hours to delay between detecting a data entry being written to the database and syncing the blockchain with the database.