Verifiable outsourced ledgers

• US 10,587,628 B2
• Filed: 09/29/2016
• Issued: 03/10/2020
• Est. Priority Date: 09/29/2016
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Inventors: Setty, Srinath, Venkatesan, Ramarathnam
• Primary Examiner(s): Huang, Cheng-Feng
• Application Number:
  US15/280,806
• Publication Number:
  US 20180091524A1
• Time in Patent Office: 1,258 Days
• CPC Class Codes: H04L 2209/56 Financial cryptography, e.g. electronic payment or e-cash
• CPC Class Codes: H04L 63/12 Applying verification of the received information cryptographic mechanisms or cryptographic arrangements for data integrity or data verification H04L9/32
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 9/0643 Hash functions, e.g. MD5, SHA, HMAC or f9 MAC
• CPC Class Codes: H04L 9/3239 involving non-keyed hash functions, e.g. modification detection codes [MDCs], MD5, SHA or RIPEMD
• CPC Class Codes: H04L 9/3247 involving digital signatures
• CPC Class Codes: H04L 9/50 using hash chains, e.g. blockchains or hash trees

Abstract

A digital ledger built upon a blockchain to provide users with the ability to securely, accurately, and verifiably share state information between distrustful parties is provided herein. The Verifiable Outsourced Ledger is hosted in a networked environment, accessible by multiple parties, and maintains an immutable view of the transactions submitted by authorized parties and a continuous view of the states shared between the parties that the parties can replicate independently locally to verify the integrity of the ledger.

Claims

1. A method for sharing state data between mutually distrustful parties, comprising:

receiving a request from a first party of the mutually distrustful parties, the request including;

an identifier for a Verifiable Outsourced Ledger (VOL) maintaining the state data to be shared;

a transaction to record within the VOL; and

a user receipt for a state of the VOL known to the first party, wherein the user receipt is a digital signature of a known state of the VOL as known to the first party, wherein a ledger server compares the user receipt with a current state of the VOL to determine if the first party has an up-to-date view of the VOL, which ensures that the transactions requested can be made on the VOL;

based on receiving the request from the first party of the mutually distrustful parties, comparing the user receipt to a digital signature of the current state, wherein;

in response to the user receipt not matching the digital signature, rejecting the transaction;

or

in response to the user receipt matching the digital signature;

assembling a transaction block, the transaction block including the transaction and the current state of the VOL;

hashing the transaction block to produce an updated state of the VOL;

digitally signing the updated state to produce a receipt;

transmitting the receipt to the mutually distrustful parties;

implementing the transaction to affect the state data; and

updating the current state to the updated state.

2. The method of claim 1, wherein the state data of the VOL comprises a height representing the number of transactions that have occurred during a history of the VOL, wherein the height is included in a tail value, and wherein the tail value can represent the known state of the VOL.

3. The method of claim 1, further comprising:

determining whether the first party is authorized to affect the VOL based on an identity of the first party based on one of;

the request being digitally signed by a public key associated with the first party;

the IP address from which the request was received being associated with the first party;

or

the request including an access token identifying the first party.

4. The method of claim 1, wherein digitally signing the updated state uses a signing key associated with the VOL.

5. The method of claim 1, further comprising:

receiving a query for the current state of the state data from the first party; and

transmitting the current state to the first party.

6. The method of claim 1, further comprising:

receiving a query for one or more transactions stored in the VOL from the first party; and

transmitting the one or more transactions to the first party.

7. The method of claim 6, wherein the query for one or more transactions includes a continuation token, the continuation token identifying a range in the VOL from which the one or more transactions are selected for transmission to the first party.

8. The method of claim 1, wherein the transaction block includes more than one transaction.

9. A system for sharing state data between mutually distrustful parties, comprising:

a processor;

a memory storage device including instructions, which when executed by the processor provide a Verifiable Outsourced Ledger (VOL) including;

a state machine, maintaining the state data;

a chaining service, operable to receive transactions from the mutually distrustful parties and store the transactions in a sequential order of effect on the state machine;

a blockchain, providing a hashed value of a transaction block, the transaction block including;

one or more of the transactions in the sequential order of effect; and

a prior hashed value provided by the blockchain; and

a secure storage service, operable to;

store the transactions in the VOL according to the sequential order of effect;

digitally sign the hashed value to produce a receipt; and

transmit the receipt to the mutually distrustful parties in response to the transaction block being hashed, wherein the receipt represents a digital signature of a current state of the VOL that will be known to the mutually distrustful parties, wherein the receipt is sent in a second transaction in which a ledger server compares the user receipt with a current state of the VOL to determine if a first party sending the user receipt has an up-to-date view of the VOL, which ensures that the second transaction requested can be made on the VOL.

10. The system of claim 9, wherein the secure storage service is further operable to:

receive a query from a client for a prior transaction block, the query including a prior hashed value associated with the prior transaction block;

get the prior transaction block; and

transmit the prior transaction block to the client.

11. The system of claim 9, wherein the transactions received from the mutually distrustful parties include a user receipt, wherein the user receipt is a receipt that has been previously transmitted to the mutually distrustful parties that indicates a state or a height of the blockchain known to a given party to the mutually distrustful parties.

12. The system of claim 11, further operable to:

determine whether the user receipt matches a most recently transmitted receipt; and

when it is determined that the user receipt does not match the most recently transmitted receipt, ignore the transactions associated with the user receipt.

13. The system of claim 9, wherein the transactions received from the mutually distrustful parties are digitally signed by a requesting party to enable the system to determine whether the requesting party is authorized to make transactions.

14. The system of claim 9, wherein the blockchain is initialized based on a seed value known to each of the mutually distrustful parties.

15. The system of claim 9, further comprising:

a query service, operable to receive a sync request from a requesting party of the mutually distrustful parties and, in response, transmit the hashed value of the blockchain and a specified number of stored transactions to the requesting party.

16. The system of claim 15, wherein the sync request includes a continuation token indicating a last-received transaction by the requesting party that specifies the specified number of stored transactions to be transmitted as the transactions that the requesting party has not previously received.

17. The system of claim 9, wherein the hashed value replaces a tail-value of the blockchain and is thereby used as the prior hashed value for a subsequent transaction block.

18. A hardware computer-readable memory storage medium including instructions for sharing state data between mutually distrustful parties, comprising:

receiving a request from a first party of the mutually distrustful parties, the request including;

an identifier for a Verifiable Outsourced Ledger (VOL) maintaining the state data to be shared;

a transaction to record within the VOL; and

a user receipt for a state of the VOL known to the first party, wherein the user receipt is a digital signature of a known state of the VOL as known to the first party, wherein a ledger server compares the user receipt with a current state of the VOL to determine if the first party has an up-to-date view of the VOL, which ensures that the transactions requested can be made on the VOL;

assembling a transaction block, the transaction block including the transaction and a current state of the VOL;

hashing the transaction block to produce an updated state of the VOL;

digitally signing the updated state to produce a receipt;

transmitting the receipt to the mutually distrustful parties;

implementing the transaction to affect the state data; and

updating the current state to the updated state.

19. The hardware computer-readable memory storage medium of claim 18, wherein the VOL is accessible to the mutually distrustful parties via a cloud service provider.