US 12,265,522 B2
Confidential blockchain database with a distributed ledger
Ronald John Kamiel Euphrasia Bjones, Dilbeek (BE); Wei-Lun Tsai, Seattle, WA (US); Mark Eugene Russinovich, Bellevue, WA (US); Sylvan W. Clebsch, Cambridge (GB); and Amaury Pierre Paul Chamayou, Cambridge (GB)
Assigned to Microsoft Technology Licensing, LLC, Redmond, WA (US)
Filed by Microsoft Technology Licensing, LLC, Redmond, WA (US)
Filed on Jul. 29, 2022, as Appl. No. 17/877,033.
Prior Publication US 2024/0037092 A1, Feb. 1, 2024
Int. Cl. G06F 16/00 (2019.01); G06F 7/00 (2006.01); G06F 16/23 (2019.01); G06F 16/27 (2019.01)
CPC G06F 16/2379 (2019.01) [G06F 16/27 (2019.01)] 18 Claims
OG exemplary drawing
 
1. An apparatus, comprising:
a device including at least one memory having processor-executable code stored therein, and at least one processor that is adapted to execute the processor-executable code, wherein the processor-executable code includes processor-executable instructions that, in response to execution, enable the device to perform actions, including:
verifying, by a first node using trusted execution environment (TEE) attestation, that a plurality of other nodes complies with a governance process defined by a consortium blockchain, wherein the consortium blockchain comprises the first node and the plurality of other nodes;
executing, in a TEE of the first node, database code and distributed ledger code, such that the distributed ledger code is distributed among the first node and the plurality of other nodes of the consortium blockchain to provide a distributed ledger, and such that execution of the database code of the first node instantiates a first instance of a database, wherein the database is distributed among the first node and the plurality of other nodes, wherein the TEE comprises a portion of the processor that provides confidentiality and integrity to loaded code and data;
receiving a first transaction that is associated with modifying the database;
executing the first transaction;
receiving a second transaction that is associated with modifying the database;
executing the second transaction;
persisting changes associated with the first and second transactions to the distributed ledger by updating a journal of effects in the distributed ledger, wherein the journal of effects comprises a first entry generated for the first transaction and a second entry generated for the second transaction, and wherein the journal of effects further comprises a commit point after the first entry and the second entry; and
upon reaching the commit point, updating the database based on entries in the journal of effects since a last commit point, wherein the entries in the journal of effects since the last commit point comprise the first entry and the second entry.