Systems and methods for synchronizing database operations with a distributed blockchain

Patent metadata

Field	Value
Publication number	US-11379455-B2
Application number	US-202017023020-A
Country	US
Kind code	B2
Filing date	Sep 16, 2020
Priority date	Feb 19, 2019
Publication date	Jul 5, 2022
Grant date	Jul 5, 2022

Abstract

Systems and methods for synchronizing database operations with a distributed blockchain are disclosed. The database operations are performed on a database that is shared between multiple users including a first user. Exemplary implementations may: receive database information reflecting one or more database operations performed by the first user on a first version of the database; verify whether the one or more database operations are allowed to be performed by the first user; record on the distributed blockchain, responsive to the verification being affirmative, a message that describes or refers to a description of one or more modifications to the database; effectuate transmissions of notifications to the first version of the database; subsequent to the transmissions, propagate or revert the one or more database operations, based on the verification result.

First claim

What is claimed is:

1. A system configured for synchronizing database operations with a distributed blockchain, the database operations being performed on a database that is hosted on one or more database servers that are accessible by multiple users including a first user and a second user, the system comprising:
a database server configured to host the database, wherein the database server is accessible by the first user through a first client computing platform and by the second user through a second client computing platform, wherein the database server is further configured to receive notifications and propagate database operations to different local versions of the database, wherein the different local versions include a first local version of the database and a second local version of the database, wherein the first local version of the database is accessible by the first user through the first client computing platform and not accessible by the second user, and wherein the second local version of the database is accessible by the second user through the second client computing platform and not accessible by the first user; and
one or more hardware processors configured by machine-readable instructions to:
receive, from the first client computing platform, a first set of database information reflecting a first set of one or more database operations performed locally by the first user on the first local version of the database, wherein the first set of one or more database operations effectuates changes to a first set of one or more cells of the first local version of the database;
receive, from the second client computing platform, a second set of database information reflecting a second set of one or more database operations performed locally by the second user on the second local version of the database, wherein the second set of one or more database operations effectuates changes to a second set of one or more cells of the second local version of the database, wherein the second set of one or more cells of the second local version of the database is different from the first set of one or more cells of the first local version of the database;
record on the distributed blockchain a first message, wherein the first message describes or refers to a description of a first set of one or more modifications to the database, wherein the first set of one or more modifications corresponds to the first set of one or more database operations;
record on the distributed blockchain a second message, wherein the second message describes or refers to a second description of a second set of one or more modifications to the database, wherein the second set of one or more modifications corresponds to the second set of one or more database operations;
perform a first verification whether the first set of one or more database operations is allowed to be performed by the first user;
perform a second verification whether the second set of one or more database operations is allowed to be performed by the second user;
effectuate transmission to the database server, responsive to the first verification verifying the first user is allowed to perform the first set of one or more database operations, of a first notification, wherein, subsequent to receipt by the database server of the first notification, the first set of one or more database operations is propagated to the second local version of the database, such that the second local version of the database, upon being accessed by the second user, reflects that the first set of one or more database operations has been performed on the second local version of the database;
record on the distributed blockchain a third message, responsive to the second verification verifying the second user is not allowed to perform the second set of one or more database operations, wherein the third message describes or refers to a third description of a third set of one or more modifications to the database, wherein the third set of one or more modifications to the database reverts the changes to the second set of one or more cells of the second local version of the database, that were due to the second set of one or more modifications to the database, as previously recorded through the second message; and
effectuate transmission to the database server, responsive to the second verification verifying the second user is not allowed to perform the second set of one or more database operations, of a second notification, wherein, subsequent to receipt by the database server of the second notification, the second set of one or more database operations on the second local version of the database is reverted such that the second local version of the database no longer includes the changes to the second set of one or more cells of the second local version of the database, and wherein the second set of one or more database operations is not propagated to the first local version of the database, such that the first local version of the database, upon being accessed by the first user, reflects that the second set of one or more database operations has not been performed on the first local version of the database.

2. The system of claim 1 , wherein the one or more hardware processors are further configured by the machine-readable instructions to:
responsive to receipt of the first set of database information reflecting performance of the first set of one or more database operations, effectuate locking the first set of one or more cells of the first local version of the database to prevent the first user from making further modifications to the first set of one or more cells of the first local version of the database; and
effectuate unlocking of the first set of one or more cells of the the first local version of the database, subsequent to transmission of the first notification to the database server such that the first user is able to perform database operations locally on the first set of one or more cells of the first local version of the database.

3. The system of claim 1 , wherein performing the first verification includes verifying whether the first user has permission to modify the first set of one or more cells of the first local version of the database.

4. The system of claim 1 , wherein performing the first verification includes verifying whether the first set of one or more cells of the first local version of the database had been locked prior to the first set of one or more database operations performed locally by the first user on the first local version of the database.

5. The system of claim 1 , wherein the first message is encrypted.

6. The system of claim 1 , wherein the one or more hardware processors are further configured by the machine-readable instructions to:
reconstruct a reconstructed database based on messages recorded on the distributed blockchain.

7. The system of claim 6 , wherein the reconstructed database is reconstructed such that:
(i) subsequent to recording the first message, the reconstructed database is consistent with the database hosted by the database server, including the first set of one or more database operations.

8. The system of claim 7 , wherein the reconstructed database is further reconstructed such that:
(ii) subsequent to recording the second message, the reconstructed database is consistent with the database hosted by the database server, including the second set of one or more database operations.

9. The system of claim 8 , wherein the reconstructed database is further reconstructed such that:
(iii) subsequent to recording the third message, the reconstructed database is consistent with the database hosted by the database server, such that the reconstructed database no longer i

Assignees

• Mythical Inc

Inventors

• Cunningham Stephan
• Thacker Cameron
• Linden John

Classifications

• G06F16/219

  Managing data history or versioning (querying versioned data G06F16/2474; querying temporal data G06F16/2477) · CPC title

• H04L9/12

  Transmitting and receiving encryption devices synchronised or initially set up in a particular manner · CPC title

• G06F16/2379

  Updates performed during online database operations; commit processing · CPC title

• G06F16/27

  Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor · CPC title

• G06F16/2343 Primary

  Locking methods, e.g. distributed locking or locking implementation details · CPC title