Dual ledger syncing

1 . A computer-implemented method comprising:

settling a transaction at a trading system including initiating capturing change of ownership data, including personally identifiable information and further transaction information, for an asset at a mutable Web2 ledger;

generating a hashID of the personally identifiable information;

accessing transaction data resulting from the settled transaction, the transaction data including the change of ownership data and other transaction data corresponding to another part of the transaction;

accessing an intentional lag time defining a fixed amount of time to delay between detecting the change of ownership data being written to the mutable Web2 ledger and syncing a publicly accessible immutable Web3 ledger with the mutable Web2 ledger, the intentionally lag time balancing integrity risk associated with syncing the mutable Web3 ledger with the immutable Web2 ledger relative to update frequency at the mutable Web3 ledger, the fixed amount of time increasing the likelihood of written data entries being complete and correct at the mutable Web2 ledger prior to syncing;

storing the hashID at a storage location outside the immutable Web3 ledger;

monitoring activity at the mutable Web2 ledger;

detecting the change of ownership data captured to the mutable Web2 ledger during the monitoring;

delaying syncing the immutable Web3 ledger with the mutable Web2 ledger by the fixed amount of time upon detecting the change of ownership data being captured; and

responsive to completion of the delay, syncing the immutable Web3 ledger with the mutable Web2 ledger by recording at least a portion of the transaction data from the mutable Web2 ledger to the immutable Web3 ledger, the at least a portion of the transaction data including the other transaction data, the further transaction data, and the hashID.

2 . The computer-implemented method of claim 1 , further comprising:

detecting other data written to the mutable Web2 ledger during the monitoring;

delaying syncing the immutable Web3 ledger with the mutable Web2 ledger by the specified amount of time after detecting the other data being written; and

after the delay, syncing the immutable Web3 ledger with the mutable Web2 ledger by recording at least a portion of the other data from the mutable Web2 ledger to the immutable Web3 ledger.

3 . The computer-implemented method of claim 1 , further comprising auditing the integrity of the mutable Web2 ledger including:

comparing a selected data entry written on the mutable Web2 ledger at a particular date with a corresponding data entry on the immutable Web3 ledger 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.

4 . 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 mutable Web2 ledger and syncing the immutable Web3 ledger with the mutable Web2 ledger.

5 . 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 immutable Web3 ledger after the at least a portion of the transaction data is recorded to the immutable Web3 ledger.

6 . 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 the trading system.

7 . 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 Web2 ledger and syncing the Web3 ledger with the Web2ledger.

8 . 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 a trading system including initiating capturing change of ownership data, including personally identifiable information and further transaction information, for an asset at a mutable Web2 ledger;

generate a hashID of the personally identifiable information;

access transaction data resulting from the settled transaction, the transaction data including the change of ownership data and other transaction data corresponding to another part of the transaction;

access an intentional lag time defining a fixed amount of time to delay between detecting the change of ownership data being written to the mutable Web2 ledger and syncing a publicly accessible immutable Web3 ledger with the mutable Web2 ledger, the intentionally lag time balancing integrity risk associated with syncing the mutable Web3 ledger with the immutable Web2 ledger relative to update frequency at the mutable Web3 ledger, the fixed amount of time increasing the likelihood of written data entries being complete and correct at the mutable Web2 ledger prior to syncing;

store the hashID at a storage location outside the immutable Web3 ledger;

monitor activity at the mutable Web2 ledger;

detect the change of ownership data captured to the mutable Web2 ledger during the monitoring;

delay syncing the immutable Web3 ledger with the mutable Web2 ledger by the fixed amount of time upon detecting the change of ownership data being captured; and

responsive to completion of the delay, sync the immutable Web3 ledger with the mutable Web2ledger by recording at least a portion of the transaction data from the mutable Web2 ledger to the Web3 ledger, the at least a portion of the transaction data including the other transaction data, the further transaction data, and the hashID.

9 . The system of claim 8 , further comprising instructions configured to cause the hardware processor to audit the integrity of the mutable Web2 ledger including:

compare a selected data entry written on the mutable Web2 ledger at a particular date with a corresponding data entry on the immutable Web3 ledger 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.

10 . The system of claim 8 , 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 the trading system.

11 . The system of claim 8 , 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 mutable Web2 database and syncing the immutable Web3 database with the mutable Web2 database.