System and method for interoperability of blockchains

• US 10,642,825 B2
• Filed: 06/28/2019
• Issued: 05/05/2020
• Est. Priority Date: 11/09/2018
• Status: Active Grant

• Current Assignee: Innoplexus AG
• Original Assignee: Innoplexus AG
• Inventors: Keskar, Abhijit
• Primary Examiner(s): Ho, Binh V
• Application Number:
  US16/456,217
• Publication Number:
  US 20190317936A1
• Time in Patent Office: 312 Days
• Field of Search: 707703
• CPC Class Codes: G06F 16/1734 Details of monitoring file system events, e.g. by the use of hooks, filter drivers, logs
• CPC Class Codes: G06F 16/183 Provision of network file services by network file servers, e.g. by using NFS, CIFS network file access protocols H04L67/1097
• CPC Class Codes: G06F 16/2379 Updates performed during online database operations; commit processing
• CPC Class Codes: H04L 63/0428 wherein the data content is protected, e.g. by encrypting or encapsulating the payload
• CPC Class Codes: H04L 63/0442 wherein the sending and receiving network entities apply asymmetric encryption, i.e. different keys for encryption and decryption cryptographic mechanisms or cryptographic arrangements for public-key encryption H04L9/30
• CPC Class Codes: H04L 9/0637 Modes of operation, e.g. cipher block chaining [CBC], electronic codebook [ECB] or Galois/counter mode [GCM]
• CPC Class Codes: H04L 9/0643 Hash functions, e.g. MD5, SHA, HMAC or f9 MAC
• CPC Class Codes: H04L 9/0891 Revocation or update of secret information, e.g. encryption key update or rekeying
• CPC Class Codes: H04L 9/0894 Escrow, recovery or storing of secret information, e.g. secret key escrow or cryptographic key storage
• 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/50 using hash chains, e.g. blockchains or hash trees

Abstract

Disclosed herein is a system and method for interoperability of blockchains thereby allowing use of smart contracts across blockchains in real time and in a secured manner. A plurality of blockchains are connected to each other and allow use of smart contracts written on them by other connected blockchains without the need of rewriting and/or downloading the smart contract on other blockchain. The disclosed system and methods use a distributed file system storage for secured processing of information flowing from one blockchain to other connected blockchain. Further, each connected blockchain is associated with distinct private and public key in order to encrypt and decrypt the data flowing across blockchains.

Claims

1. A system configured to enable interoperability amongst a plurality of blockchains communicably coupled to a distributed file storage system and a server arrangement, wherein the server arrangement comprises at least one processor and is configured to:

initiate an execution of a smart contract on a host blockchain of the plurality of blockchains;

append a first transaction to the host blockchain, the first transaction comprising a method name of a smart contract method not associated with the smart contract on the host blockchain and one or more input parameters associated with the smart contract method, wherein server arrangement is further configured to cause the host blockchain to;

defer an execution of the first transaction for a predetermined time period;

store the method name and the one or more input parameters on the distributed file storage system at a first storage location;

receive a first hash address and the method name from the host blockchain wherein the first hash address identifies a first storage location for the method name, and the one or more input parameters on the distributed file storage system;

identify a non-host blockchain of the plurality of blockchains that is configured to execute the smart method contract;

append a second transaction to the non-host blockchain, the second transaction comprising the first hash address;

receive a second hash address from the non-host blockchain wherein the second hash address identifies a second storage location on the distributed file storage system, the second storage location configured to store a method output from an execution of the smart contract method with the one or more input parameters by the non-host blockchain;

append a third transaction to the host blockchain, the third transaction comprising the second hash address;

receive, at the end of the predetermined time period, the method output; and

indicate the execution of the first transaction, wherein

the server arrangement is further configured to identify the non-host blockchain with the smart contract method based on a method index, the method index comprising a list of one or more method names mapped against at least one of the plurality of blockchains.

2. The system of claim 1 wherein both the host blockchain and the non-host blockchain comprise an initial smart contract, the initial smart contract further comprising one or more standard method calls for a communication with the distributed file storage system.

3. The system of claim 2 wherein the initial smart contract further comprises a data structure repository configured to maintain a list of one or more transactions along with an execution status of the one or more transactions, the first transaction being included in the one or more transactions.

4. The system of claim 1 wherein both the host blockchain and the non-host blockchain is configured to encrypt communications with the distributed file storage system.

5. The system of claim 4 wherein the host blockchain and the non-host blockchain are respectively assigned a private key and a public key.

6. The system of claim 1 wherein the predetermined time period is based on an execution time of the smart contract method on the non-host blockchain.

7. A system for interoperability of a plurality of blockchains communicably coupled to a distributed file storage system and a server arrangement, the system comprising a processor, wherein the processor is configured to:

receive a first transaction from a host blockchain for execution of a smart contract method not associated with the host blockchain, the transaction comprising a method name corresponding to the smart contract method and one or more input parameters;

encrypt and transmit to the distributed file storage system, the method name and the one or more input parameters;

defer execution of the first transaction for a predetermined time period;

identify a non-host blockchain from the plurality of blockchains, the non-host blockchain configured with the smart contract method associated with the method name;

receive a second hash address;

decrypt and read from the distributed file storage system, a method output from an execution of the smart contract method associated with the method name on the non-host blockchain with the one or more input parameters;

receive and store on the host blockchain the method output pertaining to the execution of the smart contract method by with the one or more input parameters by the non-host block chain; and

execute the first transaction at the end of the predetermined time period and indicate the execution of the first transaction, wherein

the server arrangement is further configured to identify the non-host blockchain with the smart contract method based on a method index, the method index comprising a list of one or more method names mapped against at least one of the plurality of blockchains.

8. The system of claim 7, wherein the second hash address identifies a second storage location on the distributed file storage system, the second storage location configured to store the method output from the execution of the smart contract method with the one or more input parameters on the non-host blockchain.

9. A method for executing a dynamic smart contract on a host blockchain, wherein the dynamic smart contract comprises one or more smart contract methods to be processed in a sequence of execution, the one or more smart contract methods deployed across a plurality of blockchains, separate from the host blockchain, the method comprising the steps of:

a) accepting a smart contract method from the one or more smart contract methods;

b) determining an availability of the smart contract method on the host blockchain;

c) deferring an execution of the dynamic smart contract on the host blockchain for a predetermined time period when the smart contract method is not available on the host blockchain;

d) identifying a non-host blockchain deployed with the first smart contract method from the plurality of blockchains, wherein identifying the non-host blockchain comprises identifying the non-host blockchain from on a method index, the method index comprising a list of one or more method names mapped against at least one of the plurality of blockchains;

e) receiving a method output resulting from an execution of the smart contract method executed on the non-host blockchain;

f) resuming the execution of the dynamic smart contract method at the end of the predetermined time period;

looping to step (a) until a last smart contract method of the one or more smart contract methods of the dynamic smart contract is processed as per the sequence of execution.