Secure processing of electronic transactions by a decentralized, distributed ledger system

Patent metadata

Field	Value
Publication number	US-10521775-B2
Application number	US-201615364213-A
Country	US
Kind code	B2
Filing date	Nov 29, 2016
Priority date	Apr 18, 2016
Publication date	Dec 31, 2019
Grant date	Dec 31, 2019

Abstract

A method and system are provided to support a decentralized distributed ledger in which transactions are recorded by parties to the transactions without the use of a blockchain. A distributed ledger system provides a protocol framework that supports the development of protocol flows. A protocol flow is computer code that controls the performance of a transaction by the party or parties to the transaction. Protocol flows can be developed for different types of transactions. The distributed ledger system allows transactions to be proposed, accepted, and notarized by a notary and stored without the use of a blockchain ledger. The distributed ledger system can avoid the expense of the computational and storage resources needed to redundantly verify a transaction and store evidence on the many nodes of a blockchain distributed ledger.

First claim

The invention claimed is:

1. A computing system of a second party for accepting a proposed transaction between at least a first party and the second party, the first party and the second party having nodes of a distributed ledger system that is not a blockchain, each node being a computing system, the computing system of the second party comprising:
a computer-readable storage medium storing computer-executable instructions of a protocol flow for controlling the computing system to:
receive a proposed transaction between the first party and the second party, the proposed transaction being proposed and signed by the first party and specifying state that includes at least an input state or an output state, the state having contract code for verifying the proposed transaction complies with terms of a contract;
verify the proposed transaction has been signed by the first party;
verify the proposed transaction by verifying that the input state is valid and executing the contract code of the state to ensure that the proposed transaction complies with the terms of the contract;
generate a notarized transaction by signing the proposed transaction with a signature of the second party, submitting to a notary of the distributed ledger system the signed proposed transaction, and receiving from the notary the notarized transaction;
send the notarized transaction to the first party; and
record the notarized transaction in a decentralized storage of the distributed ledger system so that the notarized transaction is accessible by the second party; and

a processor that executes the computer-executable instructions stored in the computer-readable storage medium.

2. The computing system of claim 1 , wherein the decentralized storage allows notarized transactions to be recorded by the parties to the notarized transaction as proof of the notarized transactions without the need for third parties to record the notarized transactions, wherein the third parties include the notary and any party not directly involved in the transaction.

3. The computing system of claim 1 , wherein a signature is a hash of a transaction that is signed using a private key of a signer.

4. The computing system of claim 1 , wherein the computer-executable instructions further include instructions of a protocol framework that control the computing system to
generate checkpoints during execution of the protocol flow, each checkpoint including state of the protocol flow at the time of the checkpoint;
and store the checkpoints persistently so that if execution of the protocol flow is suspended, execution can be resumed from the latest checkpoint.

5. The computing system of claim 4 , wherein the generating of the checkpoints is transparent to the protocol flow.

6. The computing system of claim 1 , wherein the computer-executable instructions further include instructions of a protocol framework that control the computing system to track a status of the protocol flow for reporting to the second party.

7. The computing system of claim 1 , wherein the computer-executable instructions further include instructions of a protocol framework that control the computing system to prior to execution of the instructions of the protocol flow, rewrite the instructions of the protocol flow so that the protocol flow is resumable.

8. The computing system of claim 1 , wherein the proposed transaction includes zero or more input states and zero or more output states, as long as the transaction has at least one input state or one output state.

9. The computing system of claim 1 , wherein the transaction further includes a command as an input parameter to the contract code.

10. The computing system of claim 4 , wherein the command has one or more associated identification of parties, and
wherein verification of the proposed transaction by the contract code ensures that the proposed transaction has been signed by the identified parties.

11. The computing system of claim 10 , wherein the identification of a party is a public key.

12. The computing system of claim 1 , wherein the processor executes the instructions by executing a virtual machine the executes bytecodes of the instructions.

13. The computing system of claim 12 , wherein the virtual machine is a Java virtual machine.

14. The computing system of claim 1 , wherein the computer-executable instructions further include instructions of the protocol framework that control the computing system to prior to the first execution of the instructions of the contract code, rewrite the instructions of the contract code so that the contract code is deterministic and store the rewritten instructions for future executions.

15. The computing system of claim 1 , wherein the state is input state that is an output state of an input transaction and the computer-executable instructions that verify that the state is valid further control the computing system to execute contract code of the output state of the input transaction to determine whether input transaction and the input state are valid.

16. The computing system of claim 15 , wherein the computer-executable instructions to verify that the state is valid further control the computing system to transitively verify the validity of input states on which the proposed transaction depends.

17. The computing system of claim 1 , wherein the computer-executable instructions further include instructions that control the computing system to send to the first party a request to provide the notarized transaction on which the proposed transaction depends and receive from the first party the requested notarized transaction.

18. The computing system of claim 1 , wherein the computer-executable instructions further include instructions of the protocol flow further control the computing system to request assistance for the protocol flow when an error condition is detected.

19. The computing system of claim 1 , wherein the computer-executable instructions further include instructions of a protocol framework that controls the computing system to securely and reliably send messages between a node of an entity and a node of another entity.

20. The computing system of claim 19 , wherein the computer-executable instructions further include instructions of the protocol framework that control the computing system to provide receipts to confirm delivery of messages.

21. The computing system of claim 19 , wherein the computer-executable instructions further include instructions of the protocol framework that control the computing system to translate an identifier of an entity to a network address for delivery of a message to that entity.

Assignees

• R3 Ltd

Inventors

• Hearn Michael Christopher
• Asari Qurratul Ain Shams

Classifications

• G06Q20/389

  Keeping log of transactions for guaranteeing non-repudiation of a transaction · CPC title

• G06Q20/381

  Currency conversion · CPC title

• H04L9/3239

  involving non-keyed hash functions, e.g. modification detection codes [MDCs], MD5, SHA or RIPEMD · CPC title

• G06Q20/3825

  Use of electronic signatures · CPC title

• G06Q40/12

  Accounting · CPC title