A blockchain cross-chain gateway data interaction method based on time locking and middle platform

Abstract

The present invention designs a method for data interaction of a cross-chain gateway of a blockchain based on time locking and operation of a middle platform, and belongs to the field of cross-chain technical solutions of blockchain systems. The method of the present invention is based on a transaction execution scheme of time locking, which ensures the simultaneous execution of things on different business chains and ensures the execution security of the same transaction. The execution receipt and transaction rollback design ensure the safe execution of both parties of the transaction, and the atomicity of the transaction is guaranteed to avoid the occurrence of mistakes, fraud, cross-chain transactions and the like. The cross-chain transaction consensus chain design ensures that each legal cross-chain transaction can be safely recorded, cross-chain transactions can be traced, and the legality and security of transaction execution can be guaranteed. The transaction consensus chain is separated from the execution, which reduces the pressure of the consensus chain, improves the throughput of the system, and improves the execution efficiency of the cross-chain gateway.

Description

Technical Field

[0001] The present invention designs a cross-chain gateway data interaction method of blockchain based on time locking and operation of a middle platform, which belongs to the field of cross-chain technical solutions of blockchain systems. Background Art

[0002] In the mainstream industry, the main solutions to solve the problem of information interaction and interoperability between heterogeneous alliance chains are hash locking algorithm, relay chain / side chain technology, and intermediate notary mode. In addition, there is the contract implementation method of Changan Chain forward / reverse operation. Baidu Super Chain is based on the XIP underlying protocol and provides three solutions: cross-chain relay, relay chain and trusted relay. The three mainstream cross-chain operation technologies are deconstructed as follows.

[0003] 1. Hash locking algorithm

[0004] Hash lock mode refers to a mechanism in which users pay for transactions by guessing the original value of the hash value within a specified time period. The hash lock algorithm is based on the smart contract. Both parties first lock the assets. If both enter the correct original hash value within a limited time, the transaction can be completed. Under such a mechanism, small payments can be quickly confirmed, that is, the goal of lightning network fast confirmation can be achieved.

[0005] 2. Relay chain / side chain technology

[0006] Relay chain is to construct a third-party public chain, which connects other chains in the blockchain network through the cross-chain message transmission protocol. By adding a channel between the two chains and creating a set data structure in the channel, the two chains can interact with each other through the data structure in the channel.

[0007] 3. Notary Public Mechanism

[0008] The notary mechanism is a mechanism that achieves cross-chain through an intermediary. Two independent blockchains cannot directly interoperate with each other. The notary mechanism introduces a mutually trusted third party as an intermediary, and this mutually trusted intermediary verifies and forwards cross-chain messages. Its advantage is that it supports cross-chain of heterogeneous blockchains, but its disadvantage is that there is a risk of centralization, and it can only achieve exchange but not transfer.

[0009] 4. Contract implementation method of Changan Chain forward / reverse operation

[0010] In order to be compatible with multiple heterogeneous chains, the Changan Chain solution adopts a forward / reverse operation contract implementation method, that is, users need to provide specific forward and reverse business transactions. Based on the global design and proxy support, a variety of cross-chain transactions can be realized.

[0011] The cross-chain proxy adopts a modular layered design, which is mainly divided into three layers: basic layer, component layer and business layer.

[0012] Basic layer: provides basic services for various components of cross-chain proxy, mainly including logs, databases, and network processing;

[0013] Component layer: provides various components for business process calls, including but not limited to channels, routers, listeners, provers, adapters, etc.;

[0014] Business layer: Main business process control, including various handlers and transaction managers.

[0015] 5. Baidu Superchain’s XIP-based underlying protocol

[0016] Baidu Superchain solves the interoperability problem between heterogeneous blockchain systems (including public chains, private chains, and alliance chains, etc.) through the XIP underlying protocol. It describes the problems to be solved by cross-chain in an abstract way and designs a general solution. XIP contains a series of sub-protocols, including a naming system for cross-chain networks, a consistency protocol for cross-chain transactions, data authentication, and communication protocols.

[0017] The above implementation schemes have some hidden dangers:

[0018] 1. Hash locking algorithm: This solution is based on on-chain asset transfer and has certain business limitations and low scalability.

[0019] 2. Relay chain / side chain technology: The implementation of cross-chain transactions relies on the relay chain, resulting in low transaction throughput and is not suitable for large-scale scenario applications.

[0020] 3. Intermediate notary: There is a centralization risk, and the problem of untrustworthy notaries is difficult to solve.

[0021] 4. Changan Chain and Baidu Chain: Both are led by the setting company, technical details are not available, and security and scalability cannot be guaranteed. Summary of the invention

[0022] The purpose of the present invention is to address the security threats, poor applicability, insufficient scalability and other defects in the existing blockchain cross-chain technology solutions, and to propose a blockchain cross-chain gateway data interaction method based on time locking and operation of the middle platform.

[0023] In order to achieve the above object, the present invention adopts the following technical scheme.

[0024] A blockchain cross-chain gateway data interaction method based on time locking and operation middle platform, the business chain, cross-chain operation consensus chain, cross-chain gateway management account, smart contract, operation middle platform, time locking, shared memory transaction and shared memory transaction dock used in this method are defined as follows:

[0025] Definition 1: Business chain is the alliance chain responsible for specific business in the blockchain cross-chain system. It is the service object connected to the cross-chain gateway, responsible for executing specific business contracts, and is the data source of cross-chain information.

[0026] Definition 2: Cross-chain operation consensus chain: maintain a gateway-accessed cross-chain operation consensus chain between heterogeneous business chains, responsible for the consensus of cross-chain operations in the blockchain cross-chain system, record all operations designed to update cross-chain data, and finally form a cross-chain operation consensus;

[0027] Definition 3: Cross-chain gateway management account. For specific cross-chain scenarios, the cross-chain gateway needs to proxy a specific account to obtain the specific permissions of the account and perform specific operations. In particular, for operations such as on-chain data query, no changes to on-chain data are involved, so only a unified on-chain account is required for service. However, for operations that require specific on-chain data updates, specific account permissions need to be granted before cross-chain data updates can be completed.

[0028] Definition 4: Smart contracts. Smart contracts are mainly divided into two categories. One is the service contract, which is mainly deployed on the business chain and is responsible for completing various specific business scenarios. The other is the cross-chain operation consensus contract, which is mainly deployed on the cross-chain operation consensus chain and is mainly responsible for consensus recording of all cross-chain operations.

[0029] Definition 5: Operation platform. For heterogeneous alliance chains, the way nodes and chain data interact is different. By establishing an operation platform, the underlying interaction details of different alliance chains can be shielded, and different chains can be managed by the same platform, which simplifies the operation process and improves the flexibility of operation.

[0030] Definition 6: Time lock. For data modification operations on different alliance chains, time lock is used to ensure the simultaneity and atomicity of operations on each chain. Operations are performed within a limited time, and state synchronization is performed after the operation is completed. If synchronization fails, the transaction is rolled back to ensure the security of data on the chain.

[0031] Definition 7: Shared memory transaction, a shared memory transaction is a transaction that has been locked to be executed. Because the transaction logic and transaction execution are two independent processes, the transaction is shared memory;

[0032] Definition 8: Shared memory transaction dock. The shared memory transaction dock is in the internal memory and stores all locked shared memory transactions.

[0033] A method for data interaction between blockchain cross-chain gateways based on time locking and operation of a middle platform, including four macro steps: transaction initiation, transaction locking, time locking, and execution receipt. The specific steps of the method include:

[0034] Step 1: Connect the cross-chain gateway to the business chain. Configure the port information of the business chain and the cross-chain gateway management account on the connected business chain, including the information query operation account and the data update operation account.

[0035] Step 2: The cross-chain gateway registers on the cross-chain operation consensus chain and connects to the cross-chain operation consensus chain after successful registration. The cross-chain operation record contract is deployed on the cross-chain operation consensus chain. Each successfully registered cross-chain gateway has a corresponding account on the cross-chain operation consensus chain. The cross-chain gateway can call the cross-chain operation record contract through this account; at the same time, the cross-chain gateways register each other's addresses to find the operation nodes of adjacent business chains;

[0036] Step 3: After completing steps 1 and 2, the cross-chain gateway enters the initialization listening state and listens to user operations. User operations include local business chain data interaction, cross-chain data query, and cross-chain data update. The specific description is as follows:

[0037] Step 3.1: The user performs data interaction operations on the local business chain. The cross-chain gateway detects that the user's operation does not involve cross-chain and can be completed based only on the business chain managed by the current gateway. The cross-chain gateway management account then initiates the operation to the local business chain and completes it, returning the execution result to the user.

[0038] Step 3.2: The user performs a cross-chain data query operation. The cross-chain gateway detects that the user operation is to obtain data on another target business chain (the target business chain is the business chain managed by the target cross-chain gateway that has registered with this gateway), but the cross-chain data query operation does not involve data changes. The cross-chain gateway obtains the target cross-chain gateway address information of the target business chain in the registration information, sends a request to obtain information to the target cross-chain gateway, and if it receives the request acceptance information sent from the target cross-chain gateway, it waits for the target cross-chain gateway to reply, and at the same time executes the cross-chain operation contract in the cross-chain operation consensus chain to record the operation.

[0039] Step 3.3: The user performs a cross-chain data update operation. The cross-chain gateway detects that the user's operation is to update the data on the target business chain (the target business chain is the business chain managed by the target cross-chain gateway that has registered with this gateway), and uses a time-lock-based solution to perform the operation. Finally, the operation is recorded on the cross-chain operation consensus chain, completing a cross-chain data operation. The specific steps include the following:

[0040] The local cross-chain gateway is referred to as Gateway 1, and the target business chain gateway is referred to as Gateway 2:

[0041] Step 3.3.1: Gateway 1 checks whether the cross-chain transaction of the local account is legal (whether the local account has permission, whether the account assets are sufficient, whether the account is legal, etc.). If the cross-chain transaction initiated by the local account is illegal, the execution of the cross-chain transaction is rejected; if the transaction initiated by the local account is legal, Gateway 1 sends a cross-chain transaction request to Gateway 2, and Gateway 1 enters the cross-chain transaction stage 1 (initiating transaction) state, waiting for the reply from Gateway 2.

[0042] Step 3.3.2: Gateway 2 detects the cross-chain transaction request raised by Gateway 1, and first checks whether the target account for transaction execution is legal (whether the account exists, whether it has account operation authority, etc.). If the cross-chain transaction raised by Gateway 1 is illegal, it will refuse to execute and send a rejection receipt to Gateway 1; if the cross-chain transaction raised by Gateway 1 is legal, Gateway 2 accepts the transaction, generates a shared memory transaction for the transaction, and adds it to the shared memory transaction dock of the local memory, and sends a transaction execution receipt to Gateway 1. Gateway 2 enters the cross-chain transaction phase 2 (locking the transaction), and locks the target chain account of the cross-chain transaction to prevent data invalidation. At the same time, Gateway 2 executes the cross-chain operation record contract on the cross-chain operation consensus chain to record this cross-chain transaction.

[0043] Step 3.3.3: If Gateway 1 receives a rejection receipt from Gateway 2, it will release its own stage 1 status and terminate the cross-chain transaction execution. Gateway 1 will return the failure reason to the local account. If Gateway 2 receives a transaction execution receipt, Gateway 1 will generate a shared memory transaction for the transaction and add it to the shared memory transaction dock in the local memory. At the same time, Gateway 1 will execute the cross-chain operation record contract in the cross-chain operation consensus chain to record the cross-chain transaction. After that, Gateway 1 will send a proposed lock time to Gateway 2, and then enter the cross-chain transaction stage 2 (lock transaction).

[0044] Step 3.3.4: Gateway 2 detects the lock time proposed by Gateway 1, and first checks whether the lock time is legal (whether it exceeds the current time, etc.). If the time is illegal, it returns a receipt for rejecting the proposed time and waits for the next lock time (if the lock time fails more than five times, the cross-chain transaction is terminated); if the time is legal, it returns a receipt for receiving the lock time to Gateway 1, and Gateway 2 enters Phase 3 (lock time).

[0045] Step 3.3.5: Gateway 1 detects the lock time receipt proposed by Gateway 2. If it is the time for receiving the lock, Gateway 1 enters Phase 3 (lock time); if it receives a lock time rejection receipt, it re-proposes the lock time and waits for the receipt.

[0046] This step adopts a separation structure design, specifically: the cross-chain gateway maintains two main processes, one process is the transaction review and locking process, which mainly determines whether the transaction can be executed. When a thing is locked in the shared memory transaction dock, it means that the thing will definitely be executed. When a thing has locked the execution time, it means that the thing will definitely be executed at the locked time; the other process is the chain interaction thing execution process, which will detect the state of things in the shared memory transaction dock in real time. When a thing has locked the time and has reached the locking time, the process will execute the thing and return the execution result, which can ensure the simultaneity of the execution of things on heterogeneous business chains and the atomicity of cross-chain transaction operations, and maintain the security of cross-chain operations.

[0047] Step 3.3.6: After detecting that the cross-chain transaction is successfully executed, Gateway 1 and Gateway 2 each send a transaction execution success receipt to the other party, and update the operation status in the cross-chain operation consensus chain to complete a cross-chain transaction.

[0048] Step 4: The cross-chain gateway records the cross-chain operation log in real time, monitors the cross-chain transaction request port, and distributes services according to the request.

[0049] Step 5: After the cross-chain gateway completes the cross-chain transaction, the cross-chain operation consensus chain saves the cross-chain gateway registration information, and the cross-chain gateway ends the monitoring state after releasing the account control.

[0050] Beneficial Effects

[0051] The present invention proposes a cross-chain gateway data interaction solution based on time locking and operation of the middle platform blockchain, which has the following beneficial effects compared with the prior art:

[0052] 1. The transaction execution solution based on time locking can ensure the simultaneous execution of transactions on different business chains and ensure the execution security of the same transaction.

[0053] 2. The execution receipt and transaction rollback design ensures the safe execution of both parties of the transaction, and the atomicity of the transaction is guaranteed to avoid errors, fraud, cross-chain transactions, etc.

[0054] 3. The cross-chain transaction consensus chain design ensures that every legal cross-chain transaction can be securely recorded, cross-chain transactions are traceable, and the legality and security of transaction execution are guaranteed.

[0055] 4. The transaction consensus chain is separated from execution, which reduces the pressure on the consensus chain, improves the system throughput, and improves the execution efficiency of the cross-chain gateway. BRIEF DESCRIPTION OF THE DRAWINGS

[0056] Figure 1 It is an execution interaction relationship diagram of a method for data interaction of a cross-chain gateway of a blockchain based on time locking and operation of a middle platform of the present invention;

[0057] Figure 2 This is a top-level data flow diagram of the present invention's cross-chain gateway data interaction method based on time locking and operation of the middle-end blockchain. DETAILED DESCRIPTION

[0058] The following is combined with Figure 1 , 2 and specific implementation methods are used to describe in detail the specific implementation of the present invention's cross-chain gateway data interaction method based on time locking and operation of the middle platform blockchain.

[0059] Example 1: Requesting local on-chain data services

[0060] This example describes the business process of a user requesting only local on-chain data services:

[0061] 1. The user submits a transaction request to the cross-chain gateway operation platform, and the cross-chain gateway detects that the transaction is a data request that is completed only on the local chain.

[0062] Step 1: The cross-chain gateway detects that the request belongs to a local transaction request. The gateway analyzes the request type, queries the data, and performs on-chain data operations.

[0063] Step 2.1: If the request is for data query, the gateway will automatically execute the data query operation on the chain and return the execution result to the user.

[0064] Step 2.2: If the request belongs to a data operation, the gateway will check the calling contract and parameters, call the contract execution on the chain, and return the execution result.

[0065] 2. The user obtains the contract execution result and completes a local chain service operation.

[0066] Example 2: Obtaining data services on the target chain

[0067] The following will be combined with the attached embodiment of the present invention Figure 1 and 2 , clearly and completely describe the technical solutions in the embodiments of the present invention. The described embodiments are only part of the embodiments of the present invention, not all of them. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0068] In this example, business chain A interacts with cross-chain gateway A, and business chain B interacts with cross-chain gateway B. This example describes the business process of a user on business chain A only requesting to obtain data from the target business chain B:

[0069] 1. The user submits a transaction request to the cross-chain gateway operation center, and the cross-chain gateway A detects that the transaction is a transaction request to obtain data on the target business chain B.

[0070] Step 1: Cross-chain gateway A checks the legitimacy of the transaction proposed by user 1, whether user 1 has the authority to propose, whether the data on the chain is safe, etc. If it is a legitimate request, proceed to step 2.

[0071] Step 2: Cross-chain gateway A initiates data query service to target cross-chain gateway B and waits for cross-chain gateway B to request receipt. If the receipt is received, wait for the execution result and put the request transaction on the chain for recording; otherwise, cross-chain gateway A returns the reason for execution failure to user 1.

[0072] Step 3: Cross-chain gateway A returns the cross-chain data execution result to user 1 and updates the transaction status on the cross-chain transaction consensus chain.

[0073] 2. Once the user receives an execution receipt, if it is an execution failure receipt, the user can view the reason for the failure; if it is a successful execution receipt, the user will receive the request result of the cross-chain data.

[0074] Example 3: Update the data on the target chain

[0075] The following will be combined with the attached embodiment of the present invention Figure 1 and 2 , clearly and completely describe the technical solutions in the embodiments of the present invention. The described embodiments are only part of the embodiments of the present invention, not all of them. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0076] In this example, business chain A interacts with cross-chain gateway A, and business chain B interacts with cross-chain gateway B. This example describes the business process of a user on business chain A requesting to update data on the target business chain B:

[0077] 1. The user submits a cross-chain transaction request to the cross-chain gateway operation platform, and the cross-chain gateway A detects that the transaction is to update the data on the target business chain B.

[0078] Step 1: Cross-chain gateway A detects the legitimacy of the cross-chain transaction request made by user 1, whether user 1 has the authority to make the request, whether the on-chain data is secure, etc. If it is a legitimate request, a transaction proposal data packet is sent to the target cross-chain gateway B.

[0079] Step 2: The target business chain B cross-chain gateway B detects the cross-chain transaction request proposed by user 1, performs a legitimacy check on the request, and locks the relevant execution account. If it is a legal transaction, it replies to the cross-chain gateway A to generate a transaction data packet, indicating that the transaction is received and locked; otherwise, it replies to reject the transaction proposal data packet, indicating that the transaction is rejected. After that, the transaction-related information is collected, and a shared memory transaction is generated, the entity is added to the shared memory transaction dock, and the cross-chain transaction data is stored in the business chain B.

[0080] Step 3: Cross-chain gateway A receives the generated transaction data packet, collects the transaction-related information, generates a shared memory transaction, adds the entity to the shared memory transaction dock, and stores the cross-chain transaction data in business chain A. After that, cross-chain gateway A proposes a lock time, sends the lock time to cross-chain gateway B in the proposed lock time data packet, and waits for the reply information of the lock time proposal.

[0081] Step 4: Cross-chain gateway B receives the lock time data packet proposed by cross-chain gateway A, checks the legitimacy of the proposed time, and if the time has expired (exceeds the current time, unified transaction time overlaps), returns a rejection lock time data packet and waits for a new lock time; otherwise, receives the lock time, returns a lock time data packet to cross-chain gateway A, and updates the transaction information in the local shared memory transaction dock, and updates the cross-chain transaction consensus chain information. Wait for another process to execute the cross-chain transaction.

[0082] Step 5: Cross-chain gateway A receives the lock time data packet, updates the transaction information in the local shared memory transaction dock, and updates the cross-chain transaction consensus chain information. Wait for another process to execute the cross-chain transaction.

[0083] Step 6: After the transaction is executed, cross-chain gateway A and cross-chain gateway B each send a transaction execution completion data packet to the other gateway. After receiving the other party's confirmation information, they update the transaction information in the local shared memory transaction dock and update the cross-chain transaction consensus chain information. A cross-chain transaction is completed.

[0084] Step 7: Cross-chain gateway A returns the execution result of the cross-chain transaction to user 1.

[0085] 2. Once the user receives an execution receipt, if it is an execution failure receipt, the user can view the reason for the failure; if it is a successful execution receipt, the user will receive the cross-chain data update execution result.

Claims

1. A method for data interaction between blockchain cross-chain gateways based on time locking and operation of the middle platform, characterized in that The steps of the method include: Step 1: Connect the cross-chain gateway to the business chain, then configure the cross-chain gateway with the port information of the business chain and configure the cross-chain gateway management account on the connected business chain; Step 2: The cross-chain gateway registers on the cross-chain operation consensus chain and connects to the cross-chain operation consensus chain after successful registration; Step 3: The cross-chain gateway enters the initialization monitoring state and monitors user operations, including local business chain data interaction, cross-chain data query, and cross-chain data update; The local business chain data interaction refers to the user performing a local business chain data interaction operation. The cross-chain gateway detects that the user's operation does not involve cross-chain and is only completed based on the business chain managed by the current gateway. Then the cross-chain gateway management account initiates the operation to the local business chain and completes it, and returns the execution result to the user; The cross-chain data query refers to the user performing a cross-chain data query operation. The cross-chain gateway detects that the user operation is to obtain data on another target business chain. The target business chain is the business chain managed by the target cross-chain gateway that has been registered with the gateway. The cross-chain data query operation does not involve data changes. The cross-chain gateway obtains the target cross-chain gateway address information of the target business chain in the registration information, and sends a request to obtain information to the target cross-chain gateway. If the request acceptance information sent from the target cross-chain gateway is obtained, the target cross-chain gateway is waited for the information receipt, and the cross-chain operation contract is executed in the cross-chain operation consensus chain to record the operation; The cross-chain data update refers to the user performing a cross-chain data update operation. The cross-chain gateway detects that the user's operation is to update the data on the target business chain. The target business chain is the business chain managed by the target cross-chain gateway that has registered with the gateway. The operation is executed using a time-locking scheme, and the operation is finally recorded on the cross-chain operation consensus chain to complete a cross-chain data operation. The specific steps of the cross-chain data operation are as follows: hereinafter, the local cross-chain gateway is referred to as Gateway 1, and the target business chain gateway is referred to as Gateway 2: Gateway 1 checks whether the cross-chain transaction of the local account is legal. If the cross-chain transaction initiated by the local account is illegal, the execution of the cross-chain transaction is rejected. If the transaction initiated by the local account is legal, Gateway 1 sends a cross-chain transaction request to Gateway 2. Gateway 1 enters the cross-chain transaction phase 1 state and waits for the response from Gateway 2. Gateway 2 detects the cross-chain transaction request proposed by Gateway 1, and first checks whether the target account for transaction execution is legal. If the cross-chain transaction proposed by Gateway 1 is illegal, it will refuse to execute and send a rejection receipt to Gateway 1. If the cross-chain transaction proposed by Gateway 1 is legal, Gateway 2 accepts the transaction, generates a shared memory transaction for the transaction, and adds it to the shared memory transaction dock in the local memory, and sends a transaction execution receipt to Gateway 1. Gateway 2 enters the cross-chain transaction phase 2, and locks the target chain account of the cross-chain transaction to prevent data invalidation. At the same time, Gateway 2 executes the cross-chain operation record contract on the cross-chain operation consensus chain to record this cross-chain transaction. If Gateway 1 receives a rejection receipt from Gateway 2, it will release its own stage 1 status and terminate the cross-chain transaction execution. Gateway 1 will return the failure reason to the local account. If Gateway 2 receives a transaction execution receipt, Gateway 1 will generate a shared memory transaction for the transaction and add it to the shared memory transaction dock in the local memory. At the same time, Gateway 1 will execute the cross-chain operation record contract on the cross-chain operation consensus chain to record the cross-chain transaction. After that, Gateway 1 will send a proposal to Gateway 2 to lock the time and then enter the cross-chain transaction stage 2. Gateway 2 detects the lock time proposed by Gateway 1, and first checks whether the lock time is legal. If the time is illegal, it returns a receipt of rejecting the proposed time and waits for the next lock time. If the time is legal, it returns a receipt of receiving the lock time to Gateway 1, and Gateway 2 enters Phase 3. Gateway 1 detects the lock time receipt proposed by Gateway 2. If it is the time to accept the lock, Gateway 1 enters Phase 3. If it receives a lock time rejection receipt, Gateway 1 re-proposes the lock time and waits for the receipt. After detecting that the cross-chain transaction is successfully executed, Gateway 1 and Gateway 2 each send a transaction execution success receipt to the other party and update the operation status in the cross-chain operation consensus chain to complete a cross-chain transaction; Step 4: The cross-chain gateway records the cross-chain operation log in real time, monitors the cross-chain transaction request port, and distributes services according to the request; Step 5: After the cross-chain gateway completes the cross-chain transaction, the cross-chain operation consensus chain saves the cross-chain gateway registration information. After the cross-chain gateway releases the account control, the monitoring state ends, and the cross-chain gateway data interaction method based on time lock and time lock blockchain is completed; The business chain refers to the alliance chain responsible for specific business in the blockchain cross-chain system. It is the service object of the cross-chain gateway, responsible for executing specific business contracts, and is the data source of cross-chain information; The cross-chain operation consensus chain refers to a cross-chain operation consensus chain that maintains a gateway access between heterogeneous business chains, is responsible for the consensus of cross-chain operations in the blockchain cross-chain system, records all operations designed to update cross-chain data, and finally forms a cross-chain operation consensus; The cross-chain gateway management account means that for setting a cross-chain scenario, the cross-chain gateway needs to proxy a specific account to obtain the specific permissions of the account and perform specific operations; The operation platform mentioned above has different modes of interaction between nodes and chain data for heterogeneous alliance chains. By establishing an operation platform, the underlying interaction details of different alliance chains can be shielded, and different chains can be managed by the same platform. The time lock mentioned above uses a time lock method for data modification operations on different alliance chains to ensure the simultaneity and atomicity of operations on each chain, perform operations within a limited time, and synchronize the status after the operation is completed. If the synchronization fails, the transaction is rolled back to ensure the security of the data on the chain; The shared memory transaction is a transaction that has been locked and is to be executed. Since the transaction logic and transaction execution are two independent processes, the transaction is shared memory. The shared memory transaction dock stores all locked shared memory transactions in the internal memory.

2. According to claim 1, a method for data interaction between blockchain cross-chain gateways based on time locking and operation of the middle platform is characterized by: In step 1, the cross-chain gateway management account includes an information query operation account and a data update operation account.

3. A method for data interaction between blockchain cross-chain gateways based on time locking and operation of a middle platform according to claim 1 or 2, characterized in that: In step 2, the cross-chain operation record contract is deployed on the cross-chain operation consensus chain. Each successfully registered cross-chain gateway has a corresponding account on the cross-chain operation consensus chain. The cross-chain gateway calls the cross-chain operation record contract through the account. At the same time, the cross-chain gateways register each other's addresses to find the operation nodes of adjacent business chains.

Images