CN115348262B

CN115348262B - Cross-link operation execution method and network system based on cross-link protocol

Info

Publication number: CN115348262B
Application number: CN202110460384.5A
Authority: CN
Inventors: 冯治波; 申子熹
Original assignee: Tencent Technology Shenzhen Co Ltd
Current assignee: Tencent Technology Shenzhen Co Ltd
Priority date: 2021-04-27
Filing date: 2021-04-27
Publication date: 2024-02-20
Anticipated expiration: 2041-04-27
Also published as: CN115348262A

Abstract

The embodiment of the application discloses a cross-link operation execution method and a network system based on a cross-link protocol, and belongs to the technical field of computers. The method comprises the following steps: the method comprises the steps that a first proxy server receives a first contract method and a second contract method sent by a first blockchain system, a cross-link protocol generation request is sent to a manager blockchain system, the manager blockchain system generates a cross-link protocol based on the cross-link protocol generation request, the cross-link protocol is sent to the first proxy server and a second proxy server, the second proxy server stores the cross-link protocol, and the first proxy server stores the cross-link protocol; responding to a first cross-link operation request of the first block chain system to the second block chain system, sending a second cross-link operation request to a second proxy server based on a cross-link protocol and a first contract method, calling the second contract method by the second proxy server based on the cross-link protocol indicated by the cross-link protocol identification, and executing the cross-link operation based on the second contract method, so that the efficiency of the cross-link operation is improved.

Description

Cross-link operation execution method and network system based on cross-link protocol

Technical Field

The embodiment of the application relates to the technical field of computers, in particular to a cross-link operation execution method and a network system based on a cross-link protocol.

Background

With the development of computer technology, blockchain systems can be deployed in a variety of scenarios. With the increase of blockchain systems, there may be cross-chain operations between different blockchain systems, for example, cross-chain transaction operations or cross-chain query operations, and how to implement the cross-chain operations between different blockchain systems is a problem to be solved.

In the related art, a method for performing a cross-chain operation is provided, before performing the cross-chain operation between any two blockchain systems, a third party blockchain system identified by both blockchain systems needs to be determined, and when the two blockchain systems perform the cross-chain operation, the third party blockchain system is used for carrying out preparation tasks such as data collection, operation confirmation, operation verification and the like required before performing the cross-chain operation. This approach requires a significant amount of preparation before performing the cross-chain operation, resulting in inefficiency of the cross-chain operation.

Disclosure of Invention

The embodiment of the application provides a cross-link operation execution method and a network system based on a cross-link protocol, which can improve the efficiency of the cross-link operation. The technical scheme is as follows:

In one aspect, a method for executing a cross-chain operation based on a cross-chain protocol is provided, and the method is applied to a network system, wherein the network system comprises a first blockchain system, a second blockchain system, a first proxy server corresponding to the first blockchain system, a second proxy server corresponding to the second blockchain system and a manager blockchain system, and the method comprises the following steps:

the first proxy server receives a first contract method and a second contract method sent by the first blockchain system, wherein the first contract method is a contract method registered by the first blockchain system in the manager blockchain system, and the second contract method is a contract method registered by the second blockchain system in the manager blockchain system; sending a cross-link protocol generation request to the manager blockchain system, wherein the cross-link protocol generation request carries the first contract method and the second contract method;

the manager blockchain system receives the cross-link protocol generation request, generates a cross-link protocol based on the cross-link protocol generation request, and sends the cross-link protocol to the first proxy server and the second proxy server, wherein the cross-link protocol is used for indicating the authority of the first blockchain system to call the second contract method based on the first contract method;

The second proxy server receives the cross-link protocol and stores the cross-link protocol;

the first proxy server receives the cross-link protocol sent by the manager blockchain system and stores the cross-link protocol; responding to a first cross-link operation request of the first block-link system to the second block-link system, and sending a second cross-link operation request to the second proxy server based on the cross-link protocol and the first contract method, wherein the second cross-link operation request carries the cross-link protocol identification;

the second proxy server receives the second cross-link operation request, calls the second contract method based on the cross-link protocol indicated by the cross-link protocol identification, and executes cross-link operation based on the second contract method.

In another aspect, a network system is provided, where the network system includes a first blockchain system, the second blockchain system, a first proxy server corresponding to the first blockchain system, a second proxy server corresponding to the second blockchain system, and a manager blockchain system;

the first proxy server is configured to receive a first contract method and a second contract method sent by the first blockchain system, where the first contract method is a contract method that the first blockchain system registers in the manager blockchain system, and the second contract method is a contract method that the second blockchain system registers in the manager blockchain system; sending a cross-link protocol generation request to the manager blockchain system, wherein the cross-link protocol generation request carries the first contract method and the second contract method;

The manager blockchain system is used for receiving the cross-link protocol generation request, generating a cross-link protocol based on the cross-link protocol generation request, and sending the cross-link protocol to the first proxy server and the second proxy server, wherein the cross-link protocol is used for indicating the authority of the first blockchain system to call the second contract method based on the first contract method;

the second proxy server is used for receiving the cross-link protocol and storing the cross-link protocol;

the first proxy server is further configured to receive the cross-link protocol sent by the manager blockchain system, and store the cross-link protocol; responding to a first cross-link operation request of the first block-link system to the second block-link system, and sending a second cross-link operation request to the second proxy server based on the cross-link protocol and the first contract method, wherein the second cross-link operation request carries the cross-link protocol identification;

the second proxy server is configured to receive the second cross-link operation request, call the second contract method based on the cross-link protocol indicated by the cross-link protocol identifier, and execute a cross-link operation based on the second contract method.

In one possible implementation, a first node device in the first blockchain system is configured to display a first list of contract methods based on an information entry interface, the first list of contract methods including a plurality of contract methods registered by the first blockchain system in the manager blockchain system; determining the selected first contract method from a plurality of contract methods, and transmitting the first contract method to the first proxy server;

the first proxy server is configured to receive the first contract method sent by the first node device.

In another possible implementation, the first node device is configured to display, based on the information entry interface, a plurality of application identifications registered by the first blockchain system in the manager blockchain system, each application indicated by the application identification being served by the first blockchain system; in response to a selection operation of a first application identifier of the plurality of application identifiers, displaying the first contract method list in the information entry interface, wherein the first contract method list comprises a plurality of contract methods registered in the manager blockchain system by the first blockchain system and corresponding to the first application identifier.

In another possible implementation manner, the first node device is configured to display, in a first display area of the information entry interface, a plurality of application identifiers registered by the first blockchain system in the manager blockchain system; and in response to a selection operation of the first application identifier in a plurality of application identifiers, displaying the first application identifier and the first contract method list in the first display area.

In another possible implementation manner, the first node device in the first blockchain system is configured to display system identifiers corresponding to a plurality of third blockchain systems other than the first blockchain system registered on the manager blockchain system based on an information entry interface; in response to a selected operation of a system identification corresponding to the second blockchain system among the plurality of system identifications, displaying a second contract method list including a plurality of contract methods registered by the second blockchain system in the manager blockchain system; determining the selected second contract method from a plurality of contract methods, and transmitting the second contract method to the first proxy server;

The first proxy server is configured to receive the second contract method sent by the first node device.

In another possible implementation manner, the first node device is configured to display, in response to a selected operation on a system identifier corresponding to the second blockchain system among the plurality of system identifiers, a plurality of application identifiers registered by the second blockchain system in the manager blockchain system, each application indicated by the application identifier being served by the second blockchain system; in response to a selection operation of a second application identifier of the plurality of application identifiers, displaying the second contract method list in the information entry interface, wherein the second contract method list comprises a plurality of contract methods registered by the second blockchain system in the manager blockchain system and corresponding to the second application identifier.

In another possible implementation manner, the first node device is configured to display a plurality of the system identifiers in a second display area of the information input interface; and responding to the selected operation of the system identification corresponding to the second blockchain system in the system identifications, and displaying the system identification corresponding to the second blockchain system and the second contract method list in the second display area.

In another possible implementation, a first node device in the first blockchain system is configured to determine a first smart contract for which the first blockchain system is registered in the manager blockchain system, and a second smart contract for which the second blockchain system is registered in the manager blockchain system, the first smart contract including at least one third contract method, the second smart contract including at least one fourth contract method; determining a plurality of contract method combinations based on at least one of the third contract method and at least one of the fourth contract method, each contract method combination including one of the third contract method and one of the fourth contract method; determining a selected target contract method combination from a plurality of contract method combinations, wherein the target contract method combination comprises the first contract method and the second contract method, and the target contract method combination is sent to the first proxy server;

the first proxy server is configured to receive the target contract method combination sent by the first node device.

In another possible implementation, the first node device in the first blockchain system is configured to display an information registration interface; acquiring registration information of the first blockchain system based on the information registration interface, wherein the registration information at least comprises the first contract method; sending an information registration request to the first proxy server, wherein the information registration request carries the registration information;

The first proxy server is configured to receive the information registration request sent by the first node device, and send the information registration request to the management side blockchain system;

the manager blockchain system is used for receiving the information registration request and storing the registration information.

In another possible implementation, the cross-chain protocol further includes a method identification of the second contract method;

the second proxy server is configured to receive the second cross-link operation request, call the second contract method based on the method identifier in the cross-link protocol indicated by the cross-link protocol identifier, and execute a cross-link operation based on the second contract method.

In another possible implementation, the manager blockchain system is configured to send the cross-chain protocol generation request to the second blockchain system;

the second blockchain system is used for receiving the cross-link protocol generation request and sending an agreement notification to the manager blockchain system under the condition that the cross-link protocol generation request is agreed;

the manager blockchain system is configured to generate the cross-chain protocol based on the cross-chain protocol generation request in response to receiving the consent notification sent by the second blockchain system.

In another possible implementation manner, the second node device in the second blockchain system is configured to receive the request for generating the cross-link protocol, display prompt information based on the request for generating the cross-link protocol that invokes the second contract method based on the first contract method, where the prompt information is used to prompt the first blockchain system to request generation of the cross-link protocol; and responding to the confirmation operation of the prompt information, and sending the consent notification to the management side blockchain system.

The beneficial effects that technical scheme that this application embodiment provided include at least:

according to the method and the system provided by the embodiment of the invention, on the premise that the two blockchain systems register the contract method of the two blockchain systems in the management side blockchain system, the management side blockchain system generates a cross-chain protocol for the two blockchain systems, and the follow-up side blockchain system can realize the cross-chain operation between the two blockchains based on the generated cross-chain protocol without carrying out a large amount of preparation work, so that the efficiency of the cross-chain operation is improved.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are needed in the description of the embodiments will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.

Fig. 1 is a schematic structural diagram of a data sharing system according to an embodiment of the present application;

FIG. 2 is a schematic diagram of a blockchain provided in an embodiment of the present application;

FIG. 3 is a flow chart of generating blocks in a blockchain according to an embodiment of the present application;

fig. 4 is a schematic structural diagram of a network system according to an embodiment of the present application;

FIG. 5 is a flowchart of a method for performing a cross-link operation based on a cross-link protocol according to an embodiment of the present application;

FIG. 6 is a flowchart of another method for performing a cross-link operation based on a cross-link protocol provided by an embodiment of the present application;

FIG. 7 is a schematic diagram of an information registration interface provided by an embodiment of the present application;

FIG. 8 is a schematic illustration of an information entry interface provided by an embodiment of the present application;

FIG. 9 is a schematic diagram of a displayed prompt message according to an embodiment of the present application;

FIG. 10 is a schematic diagram of a cross-chain protocol provided by an embodiment of the present application;

FIG. 11 is a flow chart of generating a cross-chain protocol provided by an embodiment of the present application;

fig. 12 is a schematic structural diagram of a terminal according to an embodiment of the present application;

fig. 13 is a schematic structural diagram of a server according to an embodiment of the present application.

Detailed Description

For the purposes of making the objects, technical solutions and advantages of the embodiments of the present application more apparent, the embodiments of the present application will be described in further detail below with reference to the accompanying drawings.

The terms "first," "second," "third," "fourth," and the like as used herein may be used to describe various concepts, but are not limited by these terms unless otherwise specified. These terms are only used to distinguish one concept from another. For example, a first contract method may be referred to as a second contract method, and similarly, a second contract method may be referred to as a first contract method, without departing from the scope of the present application.

The terms "at least one," "a plurality," "each," "any one," as used herein, include one, two or more, a plurality includes two or more, and each refers to each of a corresponding plurality, any one referring to any one of the plurality. For example, the plurality of contract methods includes 3 contract methods, and each refers to each of the 3 contract methods, and any one refers to any one of the 3 contract methods, which can be the first contract method, or the second contract method, or the third contract method.

Referring to the data sharing system shown in fig. 1, the data sharing system 100 refers to a system for performing data sharing between nodes, and may include a plurality of nodes 101, where the plurality of nodes 101 may be respective clients in the data sharing system. Each node 101 may receive input information while operating normally and maintain shared data within the data sharing system based on the received input information. In order to ensure the information intercommunication in the data sharing system, information connection can exist between each node in the data sharing system, and the nodes can transmit information through the information connection. For example, when any node in the data sharing system receives input information, other nodes in the data sharing system acquire the input information according to a consensus algorithm, and store the input information as data in the shared data, so that the data stored on all nodes in the data sharing system are consistent.

Each node in the data sharing system has a node identifier corresponding to the node identifier, and each node in the data sharing system can store the node identifiers of other nodes in the data sharing system, so that the generated block can be broadcast to other nodes in the data sharing system according to the node identifiers of other nodes. Each node can maintain a node identification list shown in the following table, and the node names and the node identifications are correspondingly stored in the node identification list. The node identifier may be an IP (Internet Protocol, protocol of interconnection between networks) address, and any other information that can be used to identify the node, and the IP address is only illustrated in table 1.

TABLE 1

Node name	Node identification
		Node 1	117.114.151.174
Node 2	117.116.189.145
		…	…
Node N	119.123.789.258

Each node in the data sharing system stores one and the same blockchain. The blockchain is composed of a plurality of blocks, referring to fig. 2, the blockchain is composed of a plurality of blocks, the starting block comprises a block head and a block main body, the block head stores an input information characteristic value, a version number, a time stamp and a difficulty value, and the block main body stores input information; the next block of the starting block takes the starting block as a father block, the next block also comprises a block head and a block main body, the block head stores the input information characteristic value of the current block, the block head characteristic value of the father block, the version number, the timestamp and the difficulty value, and the like, so that the block data stored in each block in the block chain are associated with the block data stored in the father block, and the safety of the input information in the block is ensured.

When each block in the blockchain is generated, referring to fig. 3, when the node where the blockchain is located receives input information, checking the input information, after the checking is completed, storing the input information into a memory pool, and updating a hash tree used for recording the input information; then, updating the update time stamp to the time of receiving the input information, trying different random numbers, and calculating the characteristic value for a plurality of times, so that the calculated characteristic value can meet the following formula:

SHA256(SHA256(version+prev_hash+merkle_root+ntime+nbits+x))<TARGET

Wherein SHA256 is a eigenvalue algorithm used to calculate eigenvalues; version (version number) is version information of the related block protocol in the block chain; the prev_hash is the block header characteristic value of the parent block of the current block; the merkle_root is a characteristic value of input information; ntime is the update time of the update timestamp; the nbits is the current difficulty, is a fixed value in a period of time, and is determined again after exceeding a fixed period of time; x is a random number; TARGET is a eigenvalue threshold that can be determined from nbits.

Thus, when the random number meeting the formula is calculated, the information can be correspondingly stored to generate the block head and the block main body, and the current block is obtained. And then, the node where the blockchain is located sends the newly generated blocks to other nodes in the data sharing system where the newly generated blocks are located according to the node identification of other nodes in the data sharing system, the other nodes verify the newly generated blocks, and the newly generated blocks are added into the blockchain stored in the newly generated blocks after the verification is completed.

The cross-chain operation execution method based on the cross-chain protocol is applied to a network system, wherein the network system comprises a first block chain system, a second block chain system, a first proxy server corresponding to the first block chain system, a second proxy server corresponding to the second block chain system and a manager block chain system.

Optionally, the first blockchain system includes a plurality of first node devices. Optionally, the second blockchain system includes a plurality of second node devices. Optionally, the manager blockchain system includes a plurality of management node devices. Optionally, any node device of the first node device, the second node device and the management node device is a terminal or a server. In any blockchain system, the node devices included in the blockchain system can be directly or indirectly connected through wired or wireless communication, which is not limited herein.

Optionally, the server is a stand-alone physical server, or is a server cluster or a distributed system formed by a plurality of physical servers, or is a cloud server providing cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, CDN (Content Delivery Network ), and basic cloud computing services such as big data and artificial intelligence platforms. Alternatively, the first proxy server and the second proxy server can be any of the servers described above. Optionally, the terminal is a smart phone, tablet computer, notebook computer, desktop computer, smart speaker, smart watch, etc., but is not limited thereto.

Fig. 4 is a schematic structural diagram of a network system according to an embodiment of the present application. Referring to fig. 4, the implementation environment includes a first blockchain system 401, a second blockchain system 402, a first proxy server 403 corresponding to the first blockchain system 401, a second proxy server 404 corresponding to the second blockchain system 402, and a manager blockchain system 405.

The first blockchain system 401 and the first proxy server 403 can be directly or indirectly connected through a wired or wireless communication manner; the second blockchain system 402 and the second proxy server 404 can be directly or indirectly connected through wired or wireless communication; the first proxy server 403 and the second proxy server 404 can each be directly or indirectly connected to the manager blockchain system 405 through wired or wireless communication.

The first proxy server 403 and the second proxy server 404 are provided by the administrator blockchain system 405, and the first proxy server 403 and the second proxy server 404 correspond to front-end services of the administrator blockchain system 405, and are respectively used to implement interactions between the first blockchain system 401 and the second blockchain system 402 and the administrator blockchain system 405. Also, the first proxy server 403 and the second proxy server 404 are also capable of implementing a cross-chain operation between the first blockchain system 401 and the second blockchain system 402 in the presence of a cross-chain protocol between the first blockchain system 401 and the second blockchain system 402.

It should be noted that the network system shown in fig. 4 is only described by taking the first blockchain system and the second blockchain system as examples, and the network system can also include other blockchain systems and proxy servers corresponding to other blockchain systems, and the proxy servers corresponding to other blockchain systems are provided by the manager blockchain system.

Optionally, the first blockchain system 401 corresponds to at least one application and the second blockchain system 402 corresponds to at least one application, each application being serviced by the corresponding blockchain system. Optionally, each application corresponds to at least one smart contract on the corresponding blockchain system, and each smart contract includes at least one contract method.

After generating a cross-link protocol based on a first contract method registered in the manager blockchain system 405 by the first blockchain system 401 and a second contract method registered in the manager blockchain system 405 by the second blockchain system 402, a cross-link operation between an application corresponding to the first contract method and an application corresponding to the second contract method can be realized based on the cross-link protocol.

The method provided by the embodiment of the application can be used for various scenes.

For example, in the information query scenario:

the second blockchain system is an information storage system, the first blockchain system needs to query information in the second blockchain system, then a cross-chain protocol between the first blockchain system and the second blockchain system is generated by adopting the method provided by the embodiment of the invention, the cross-chain protocol is used for indicating the authority of the first blockchain system to call the query method in the second blockchain based on the first contract method, and then the information stored in the second blockchain system can be acquired based on the cross-chain protocol, so that the cross-chain operation between the first blockchain system and the second blockchain system is realized.

Fig. 5 is a flowchart of a method for executing a cross-link operation based on a cross-link protocol according to an embodiment of the present application, which is applied to a network system, as shown in fig. 5, and the method includes:

501. the first proxy server receives a first contract method and a second contract method sent by the first blockchain system and sends a cross-link protocol generation request to the management side blockchain system.

Wherein the first contract method is a contract method registered by the first blockchain system in the manager blockchain system, and the second contract method is a contract method registered by the second blockchain system in the manager blockchain system; the cross-link protocol generation request carries a first contract method and a second contract method. After the first proxy server receives the first contract method and the second contract method sent by the first blockchain system, the first proxy server indicates that the first blockchain system needs to generate a cross-link protocol of the second contract method based on the first contract method, so that the second contract method can be subsequently called based on the cross-link protocol and the first contract method, and therefore the first proxy server sends a cross-link protocol generation request to the management side blockchain system, and the rear management side blockchain system generates the cross-link protocol based on the cross-link protocol generation request.

502. The manager blockchain system receives the cross-link protocol generation request, generates the cross-link protocol based on the cross-link protocol generation request, and sends the cross-link protocol to the first proxy server and the second proxy server.

The cross-chain protocol is used for indicating the authority of the first blockchain system to call the second contract method based on the first contract method.

503. The second proxy server receives the cross-chain protocol and stores the cross-chain protocol.

504. The first proxy server receives a cross-link protocol sent by a block chain system of a management side and stores the cross-link protocol; in response to a first cross-chain operation request of the first blockchain system to the second blockchain system, a second cross-chain operation request is sent to the second proxy server based on a cross-chain protocol and a first contract method.

The second cross-link operation request carries a cross-link protocol identifier. After receiving the cross-chain protocol, the first proxy server stores the cross-chain protocol so as to execute the cross-chain operation based on the stored cross-chain protocol. And receiving a first operation request of the first blockchain system to the second blockchain system at the first proxy server, and sending a second cross-chain operation request to the second proxy server based on the cross-chain protocol and the first contract method, so that the subsequent second proxy server can realize the call to the second contract method based on the second cross-chain operation request.

505. The second proxy server receives a second cross-link operation request, invokes a second contract method based on a cross-link protocol indicated by the cross-link protocol identification, and performs the cross-link operation based on the second contract method.

After receiving the second cross-link operation request, the second proxy server determines the cross-link protocol indicated by the cross-link protocol identifier carried in the cross-link operation request, so that a second contract method corresponding to the cross-link protocol can be determined, and then the second contract method is called to execute the cross-link operation.

According to the method provided by the embodiment of the invention, on the premise that the two blockchain systems register own contract methods in the management side blockchain system, a cross-chain protocol is generated for the two blockchain systems through the management side blockchain system, and the subsequent blockchain system can realize the cross-chain operation between the two blockchains based on the generated cross-chain protocol without carrying out a large amount of preparation work, so that the efficiency of the cross-chain operation is improved.

Fig. 6 is a flowchart of a method for executing a cross-link operation based on a cross-link protocol according to an embodiment of the present application, which is applied to a network system, as shown in fig. 6, and the method includes:

601. the first node equipment in the first blockchain system displays an information registration interface, acquires registration information of the first blockchain system based on the information registration interface, and sends an information registration request to the first proxy server.

Wherein the first node device is any node device in the first blockchain system. The registration information includes at least first contract methods, each of which is a method of performing a certain function. Optionally, each first contract method is a function. For example, the first contract method is a delete function, add function, query function, or the like. The information registration interface is used for inputting registration information corresponding to the first blockchain system, and the information registration request carries the registration information.

The first node device is configured to enable a user to input registration information in the information registration interface by displaying the information registration interface, and thereafter the first node device acquires the input registration information from the information registration interface and transmits an information registration request carrying the registration information to the first proxy server for subsequent registration of the registration information in the manager blockchain system.

In one possible implementation manner, the registration information includes the first contract method, a first smart contract identifier of a first smart contract to which the first contract method belongs, and a first application identifier of a first application corresponding to the first smart contract.

In the embodiment of the application, the first blockchain system can provide services for at least one application, each first application corresponds to at least one intelligent contract, each intelligent contract comprises at least one contract method, and then the first application identifier, the first intelligent contract identifier and the first contract method included in the first intelligent contract can be acquired based on the information registration interface.

Optionally, the registration information includes a first method identifier of the first contract method, a first smart contract identifier and a first application identifier. I.e. the registration information includes a first method identification of a first contract method for indicating the first contract method.

Optionally, the registration information further includes description information of the first application and an intelligent contract address of the first intelligent contract. The description information is used for describing the corresponding first application, and the intelligent contract address is used for indicating the storage position of the corresponding first intelligent contract.

Optionally, the information registration interface includes a first input area and a second input area, and the process of acquiring the registration information of the first blockchain system includes: the method comprises the steps of obtaining a first application identifier and description information of a first application, which are contained in a first input area, obtaining a first intelligent contract identifier, an intelligent contract address of a first intelligent contract and a first method identifier, which are contained in a second input area, and forming registration information by the obtained first application identifier, the description information of the first application, the first intelligent contract identifier, the intelligent contract address of the first intelligent contract and the first method identifier.

In one possible implementation, the first node device has a target application installed thereon, where the target application is served by the first proxy server, and then the step 601 includes: the first node device displays a main interface of the target application, responds to the registration operation in the main interface, displays the information registration interface, responds to the confirmation operation in the information registration interface, acquires the registration information of the first blockchain system contained in the information registration interface, and sends an information registration request to the first proxy server.

Optionally, the main interface includes a registration option, and after the main interface is displayed, the information registration interface is displayed in response to a triggering operation on the registration option.

Optionally, the information registration interface includes a confirmation option, and in response to a triggering operation of the confirmation option, registration information included in the information registration interface is acquired, and an information registration request is sent to the first proxy server.

For example, as shown in fig. 7, an information registration interface in which an application identifier, description information, an intelligent contract identifier, an intelligent contract address, and a method identifier can be input, and registration information included in the information registration interface is acquired in response to a trigger operation of the confirmation option.

It should be noted that the embodiment of the present application is described only by taking an example in which the registration information includes one contract method, and in another embodiment, the registration information can include a plurality of contract methods.

In one possible implementation, the registration information of the first blockchain system includes at least one first application identifier, description information corresponding to each first application identifier, a first smart contract identifier of at least one first smart contract corresponding to each first application identifier, a smart contract address of each first smart contract, and a first method identifier of at least one first contract method included in each first smart contract.

The registration information includes one or more first application identifiers, one or more first smart contract identifiers corresponding to each first application identifier, and one or more first contract method identifiers included in each first smart contract identifier.

602. The first proxy server receives the information registration request sent by the first node device, and sends the information registration request to the manager blockchain system.

In the embodiment of the application, the first proxy server is used as a communication bridge between the first blockchain system and the manager blockchain system, and interaction between the first blockchain system and the manager blockchain system can be realized through the first proxy server. That is, the first proxy server can forward the information registration request transmitted by any one of the first node devices in the first blockchain system to the manager blockchain system, and the manager blockchain system processes the information registration request.

In one possible implementation, the manager blockchain system includes at least one management node device, then the step 602 includes: the first proxy server receives an information registration request sent by the first node device, and sends the information registration request to the first management node device in the management side blockchain system.

Wherein the first management node device is any one of the at least one management node device. Optionally, the first management node device is a node device allocated for the first blockchain system for the manager blockchain system.

In one possible implementation, the first proxy server includes a first sub-server and a second sub-server, and the step 602 includes: the first sub-server receives the information registration request sent by the first node device, forwards the information registration request to the second sub-server, and the second sub-server sends the information registration request to the management side blockchain system.

The first sub-server is used for interacting with a first blockchain system, the second sub-server is used for interacting with a management side blockchain system, for example, the first sub-server is used for providing a blockchain proxy sub-service, and the second sub-server is used for providing a cross-chain service. Optionally, the first node device in the first blockchain system can call a program interface of the first sub-server, and send an information registration request to the first sub-server, and the first sub-server receives the information registration request. Optionally, the program interface is an API (Application Programming Interface, application program interface).

Optionally, after receiving the information registration request, the second sub-server sends the information registration request to the first management node device in the management side blockchain system.

603. The manager blockchain system receives the information registration request and stores the registration information.

After the management side blockchain system receives the information registration request, the registration information carried in the information registration request is stored in the management side blockchain system, namely the first blockchain system is used for registering the registration information in the management side system.

In one possible implementation, this step 603 includes: a first management node device in a manager blockchain system receives an information registration request and stores the registration information in the manager blockchain system.

In the embodiment of the present application, only the first blockchain system is taken as an example to describe the process of registering the registration information of the first blockchain system in the management blockchain system, and in another embodiment, the second blockchain system, the second proxy server and the management blockchain system interact according to the steps 601-603, so that the second blockchain system can register the registration information of the second blockchain system in the management blockchain system. That is, according to the steps 601-603, any blockchain system, the proxy server corresponding to the any blockchain system and the manager blockchain interact, so that registration information of the any blockchain system can be registered in the manager blockchain system.

604. The first proxy server receives a first contract method and a second contract method sent by the first blockchain system and sends a cross-link protocol generation request to the management side blockchain system.

The cross-link protocol generation request carries a first contract method and a second contract method. After the first proxy server receives the first contract method and the second contract method sent by the first blockchain system, the first proxy server indicates that the first blockchain system needs to generate a cross-link protocol of the second contract method based on the first contract method, so that the second contract method can be subsequently called based on the cross-link protocol and the first contract method, and therefore the first proxy server sends a cross-link protocol generation request to the management side blockchain system, and the rear management side blockchain system generates the cross-link protocol based on the cross-link protocol generation request.

In one possible implementation, this step 604 includes: the first proxy server receives the first contract method and the second contract method sent by the first blockchain system, and sends the cross-chain protocol generation request to first management node equipment in the management side blockchain system.

Optionally, after receiving the first contract method and the second contract method sent by the first blockchain system, the first proxy server invokes a third intelligent contract in the manager blockchain system and sends the cross-chain protocol generation request to a first management node device in the manager blockchain system.

The third intelligent contract is an intelligent contract in the manager blockchain system, and is used for realizing interaction between the manager blockchain system and other proxy servers, and based on the third intelligent first proxy server, information can be uploaded to the manager blockchain system.

In one possible implementation, this step 604 includes two ways:

in a first manner, a process for a first proxy server to obtain a first contract method includes the following steps 6041-6042:

6041. the first node device in the first blockchain system displays a first contract method list based on the information input interface, determines a selected first contract method from a plurality of contract methods included in the first contract method list, and sends the first contract method to the first proxy server.

Wherein the first list of contract methods includes a plurality of contract methods registered by the first blockchain system in the manager blockchain system. The information entry interface is used for entering contract methods registered by the first blockchain system in the manager blockchain system.

The first node device displays a first contract method list in the information input interface after displaying the information input interface, wherein the first contract method list comprises contract methods registered in the management side blockchain system by the first blockchain system, and the first contract method is sent to the first proxy server after detecting the selection operation of the first contract method in the first contract method list.

In one possible implementation, the process of displaying the first contract method list in step 6041 includes: the first node device displays a plurality of application identifications registered by the first blockchain system in the manager blockchain system based on the information entry interface, and in response to a selection operation of a first application identification in the plurality of application identifications, displays a first contract method list in the information entry interface, wherein the first contract method list comprises a plurality of contract methods registered by the first blockchain system in the manager blockchain system and corresponding to the first application identification.

Wherein each application identified by the application identifier is served by the first blockchain system and at least one contract method corresponding to the application identified by the application identifier is registered in the manager blockchain system. The first device interface displays the information input interface, displays a plurality of application identifications of which contract methods are registered in the management side blockchain system in the information input interface, and responds to the triggering operation of a first application identification in the plurality of application identifications, displays a first contract method list in the information input interface so as to display a plurality of contract methods which are registered in the management side blockchain system by the first blockchain system and correspond to the first application identification, so that a first contract method for generating a cross-link protocol is selected from the first contract method list later.

Optionally, the information input interface includes a first display area, where the first display area is configured to display information corresponding to the first blockchain system, and the process of displaying the first contract method list includes: the first node device displays a plurality of application identifications registered by the first blockchain system in the management side blockchain system in a first display area of the information input interface, and responds to the selection operation of a first application identification in the plurality of application identifications, the first node device displays the first application identification and a first contract method list in the first display area, wherein the first contract method list comprises a plurality of contract methods registered by the first blockchain system in the management side blockchain system and corresponding to the first application identification.

After the selected first application identifier is determined, the first application identifier is displayed in the first display area, so that the contract method contained in the currently displayed first contract method list can be known to be the contract method corresponding to the first application identifier, the error of the subsequently selected first contract method is avoided, and the display effect is improved.

In one possible implementation, the process of displaying the first contract method list in step 6041 includes: the first node device displays a plurality of application identifications registered in the management side blockchain system by the first blockchain system based on the information input interface, and responds to the selection operation of the first application identification in the plurality of application identifications, displays a first contract identification list in the information input interface, wherein the first contract identification list comprises intelligent contract identifications of a plurality of intelligent contracts which are registered in the management side blockchain system by the first blockchain system and correspond to the first application identification; in response to a triggering operation for a first smart contract identification in the first list of contract identifications, a first list of contract methods is displayed in the information entry interface, the first list of contract methods including a plurality of contract methods that the first blockchain system registers in the manager blockchain system and that the first smart contract identification indicates includes. Wherein the first smart contract identification is used to indicate the first smart contract.

In one possible implementation, the first node device installs a target application, the target application being served by the first proxy server, the information entry interface being an interface in the target application.

Optionally, the process of displaying the information entry interface includes: the first node device displays a main interface of the target application, and responds to information input operation in the main interface to display the information input interface.

Optionally, the main interface includes an information input option, and after the main interface is displayed, the information input interface is displayed in response to a triggering operation on the information input option.

6042. The first proxy server receives a first contract method sent by the first node device.

The first proxy server receives a first contract method sent by the first node device, so as to obtain a cross-link protocol based on the first contract method.

In a second manner, the process of the first proxy server obtaining the second contract method includes the following steps 6043-6044:

6043. the first node equipment in the first blockchain system displays system identifiers corresponding to a plurality of third blockchain systems except the first blockchain system, which are registered on the manager blockchain system, based on the information input interface; in response to a selection operation of a system identifier corresponding to a second blockchain system in the plurality of system identifiers, a second contract method list is displayed, the selected second contract method is determined from the plurality of contract methods, and the second contract method is sent to the first proxy server.

In an embodiment of the present application, a plurality of blockchain systems that have been registered on a manager blockchain system includes a first blockchain system and a plurality of third blockchain systems. The second blockchain system is any one of a plurality of third blockchain systems, and the second list of contract methods includes a plurality of contract methods registered by the second blockchain system in the manager blockchain system.

The system identification corresponding to the third blockchain systems is displayed in the information input interface, so that a user can select the system identification of the second blockchain system needing to generate the cross-link protocol from the displayed system identifications, and then the second contract method list is displayed in the information input interface, so that the contract method registered by the second blockchain system on the manager blockchain system is displayed, and a second contract method used for generating the cross-link protocol is selected from the second contract method list.

In one possible implementation, the process of displaying the second contract method list in step 6043 includes:

the first node device displays a plurality of application identifications of the second blockchain system registered in the manager blockchain system in response to a selection operation of a system identification corresponding to the second blockchain system in the plurality of system identifications, and displays a second contract method list in the information entry interface in response to a selection operation of a second application identification in the plurality of application identifications, the second contract method list including a plurality of contract methods of the second blockchain system registered in the manager blockchain system and corresponding to the second application identification.

Wherein each application identified by the application identifier is served by the second blockchain system and at least one contract method corresponding to each application identified by the application identifier is registered in the manager blockchain system.

Displaying a plurality of application identifications registered in the manager blockchain system by the second blockchain system in the information input interface so as to be used for selecting the second application identification from the plurality of application identifications, and then displaying a second contract method list in the information input interface so as to display a plurality of contract methods registered in the manager blockchain system by the second blockchain system and corresponding to the second application identification, so as to be used for selecting a second contract method for generating a cross-link protocol from the second contract method list later.

In one possible implementation, the step 6043 includes: the first node equipment displays system identifiers corresponding to a plurality of third blockchain systems in a second display area of the information input interface; and in response to the selected operation of the system identification corresponding to the second blockchain system in the displayed plurality of system identifications, displaying the system identification corresponding to the second blockchain system and a second contract method list in a second display area.

The information input interface comprises a second display area which is used for displaying information corresponding to the second blockchain system. And displaying the system identifier corresponding to the selected second blockchain system in the second display area, so that the contract method contained in the currently displayed second contract method list can be known to be the contract method registered by the second blockchain system in the management side blockchain system, thereby avoiding the error of the subsequently selected second contract method and improving the display effect.

Optionally, after displaying the plurality of third blockchain systems in the second display area, in response to a selection operation of a second blockchain system in the plurality of third blockchain systems, displaying a system identifier corresponding to the second blockchain system and a plurality of application identifiers registered by the second blockchain system in the manager blockchain system in the second display area, and in response to a selection operation of a second application identifier in the plurality of application identifiers, displaying the second application identifier and a second contract method list in the second display area, wherein the second contract method list comprises a plurality of contract methods registered by the second blockchain system in the manager blockchain system and corresponding to the second application identifier.

In one possible implementation, the process of displaying the second contract method list in step 6043 includes: the first node device displays system identifications corresponding to a plurality of third blockchain systems based on the information input interface, displays a plurality of application identifications registered in the manager blockchain system by the second blockchain system in response to a selected operation of the system identifications corresponding to the second blockchain system in the plurality of system identifications, and displays a second contract identification list in the information input interface in response to a selected operation of the second application identifications in the plurality of application identifications, wherein the second contract identification list comprises intelligent contract identifications of a plurality of intelligent contracts registered in the manager blockchain system by the second blockchain system and corresponding to the second application identifications; in response to a triggering operation for a second smart contract identification in the second list of contract identifications, displaying a second list of contract methods in the information entry interface, the second list of contract methods including a plurality of contract methods that the second blockchain system registers in the manager blockchain system and that the second smart contract identification indicates includes.

In the process that the first node equipment acquires the second contract method, system identifiers corresponding to a plurality of third party systems displayed in an information input interface, a plurality of application identifiers registered in a management side blockchain system by a second blockchain system, intelligent contract identifiers of a plurality of intelligent contracts corresponding to the second application identifiers, and a plurality of contract methods included in the second intelligent contract indicated by the second intelligent contract identifiers are obtained through interaction between the first proxy server and the management side blockchain server.

Optionally, when the first node device initially displays the information input interface, the first node device sends a system identifier acquisition request to the first proxy server, the first proxy server sends the system identifier acquisition request to the manager blockchain system, the manager blockchain system receives the system identifier acquisition request, based on the system identifier acquisition request, the system identifiers corresponding to the plurality of third party systems are sent to the first proxy server, the first proxy server sends the system identifiers corresponding to the plurality of third party systems to the first node device, and after receiving the system identifiers corresponding to the plurality of third party systems, the first node device displays the system identifiers corresponding to the plurality of third party systems based on the information input interface.

Optionally, the first node device sends an application identifier acquisition request to the first proxy server in response to a selection operation of a system identifier corresponding to the second blockchain system in the multiple system identifiers, the application identifier acquisition request carries the system identifier corresponding to the second blockchain system, the first proxy server sends the application identifier acquisition request to the manager blockchain system, the manager blockchain system receives the application identifier acquisition request, queries multiple application identifiers registered in the manager blockchain system by the second blockchain system based on the system identifier corresponding to the second blockchain system carried by the application identifier acquisition request, sends multiple application identifiers registered in the manager blockchain system by the second blockchain system to the first proxy server, and the first proxy server sends multiple application identifiers registered in the manager blockchain system by the second blockchain system to the first proxy server.

Optionally, the first node device sends an intelligent contract identifier obtaining request to the first proxy server in response to the selection operation of the second application identifier in the plurality of application identifiers, the intelligent contract identifier obtaining request carries the second application identifier, the first proxy server sends the intelligent contract identifier obtaining request to the manager blockchain system, the manager blockchain system receives the intelligent contract identifier obtaining request, queries the intelligent contract identifiers of the plurality of intelligent contracts corresponding to the second application identifier based on the second application identifier carried by the intelligent contract identifier obtaining request, sends the intelligent contract identifiers of the plurality of intelligent contracts corresponding to the second application identifier to the first proxy server, the first proxy server sends the intelligent contract identifiers of the plurality of intelligent contracts corresponding to the second application identifier to the first node device, and the first node device displays a second contract identifier list based on the information input interface after receiving the intelligent contract identifiers of the plurality of intelligent contracts corresponding to the second application identifier.

Optionally, the first node device sends a contract method acquisition request to the first proxy server in response to a trigger operation of a second intelligent contract identifier in the second contract identifier list, the contract method acquisition request carries the second intelligent contract identifier, the first proxy server sends the contract method acquisition request to the management side blockchain system, the management side blockchain system receives the contract method acquisition request, based on the second intelligent contract identifier carried by the contract method acquisition request, queries a plurality of contract methods included in the second intelligent contract indicated by the second intelligent contract identifier, sends a plurality of contract methods included in the second intelligent contract indicated by the second intelligent contract identifier to the first proxy server, the first proxy server sends a plurality of contract methods included in the second intelligent contract indicated by the second intelligent contract identifier to the first proxy server, and after receiving the plurality of contract methods included in the second intelligent contract indicated by the second intelligent contract identifier, the first node device inputs the second contract method list based on the information interface.

6044. The first proxy server receives a second contract method sent by the first node device.

After selecting the second contract method, the first node device sends the second contract method to the first proxy server so that subsequent first proxy servers can acquire the cross-chain protocol based on the second contract method.

It should be noted that, the two ways are described by the first node device acquiring the first contract method and the second contract method respectively, and in another embodiment, the first node device acquires the first contract method and the second contract method based on the information input interface, sends the first contract method and the second contract method to the first proxy server, and the first proxy server receives the first contract method and the second contract method.

In one possible implementation manner, the first node device installs a target application, where the target application is served by the first proxy server, the information input interface is an interface in the target application, the first node device obtains a first contract method and a second contract method according to the steps 6041 and 6043 based on the displayed information input interface, and sends the first contract method and the second contract method to the first proxy server, and the first proxy server receives the first contract method and the second contract method.

In one possible implementation, this step 604 includes the following steps 6045-6046:

6045. a first node device in a first blockchain system determines a first smart contract for the first blockchain system to register in a manager blockchain system and a second smart contract for a second blockchain system to register in the manager blockchain system; determining a plurality of contract method combinations based on at least one third contract method included in the first smart contract and at least one fourth contract method included in the second smart contract; determining a selected target contract method combination from a plurality of contract method combinations, and transmitting the target contract method combination to a first proxy server.

The first intelligent contract comprises at least one third contract method, the second intelligent contract comprises at least one fourth contract method, each contract method combination comprises a third contract method and a fourth contract method, the third contract methods contained in different contract method combinations are different, or the fourth contract methods contained in different contract method combinations are different, or the third contract method and the fourth contract method contained in different contract method combinations are different, the target contract method combination comprises the first contract method and the second contract method, namely the third contract method contained in the target contract method combination is the first contract method, and the fourth contract method contained in the target contract method combination is the second contract method. In step 6045, the process of determining the first smart contract is the same as the process of determining the first smart contract identifier in step 6041, and the process of determining the second smart contract is the same as the process of determining the second smart contract identifier in step 6043, and will not be described in detail.

In the process of acquiring a plurality of contract method combinations, for any third contract method, combining the third contract method with each fourth contract method to form a contract method combination, namely, obtaining at least one contract method combination comprising the third contract method, and according to the method, obtaining at least one contract method combination corresponding to each third contract method, namely, obtaining a plurality of contract method combinations.

In one possible implementation, the step 6045 includes: the first node device displays an information input interface, displays at least one third contract method included in the first intelligent contract and at least one fourth contract method included in the second intelligent contract based on the information input interface, determines a plurality of contract party combinations based on the at least one third contract method and the at least one fourth contract method, displays a plurality of contract method combinations and target options corresponding to each contract method combination in the information input interface, and sends the target contract method combination to the first proxy server in response to a confirmation operation in the information input interface when the target options corresponding to the target contract method combinations in the plurality of contract method combinations are in a selected state.

The target option is used for selecting a corresponding contract method combination, when the target option is in a selected state, the contract method combination corresponding to the target option is selected, and when the target option is not in a selected state, the contract method combination corresponding to the target option is not selected.

In one possible implementation, the step 6045 includes: the first node device displays an information entry interface, displays a third contract method list and a fourth contract method list based on the information entry interface according to the process of displaying the first contract method list in the above step 6041 and the process of displaying the first contract method list in the above step 6043, determines a plurality of contract method combinations based on the third contract method list and the fourth contract method list, displays a plurality of contract method combinations and target options corresponding to each contract method combination in the information entry interface, and transmits the target contract method combination to the first proxy server in response to a confirmation operation in the information entry interface in a case that the target option corresponding to the target contract method combination in the plurality of contract method combinations is in a selected state.

Optionally, the information input interface further includes a confirmation option, and in case that the target option corresponding to the target contract method combination is in a selected state, the target contract method combination is sent to the first proxy server in response to a triggering operation of the confirmation option. As shown in fig. 8, a plurality of contract method combinations are displayed in the information entry interface.

6046. The first proxy server receives a target contract method combination sent by the first node device.

And the first proxy server receives the target contract party combination sent by the first node equipment, and obtains a first contract method and a second contract party in the target contract method combination.

It should be noted that, in the embodiment of the present application, only one contract method and one second contract method are sent to the manager blockchain system to describe the method, and in another embodiment, the first node device determines a plurality of contract method combinations, sends the plurality of contract method combinations to the first proxy server, and the first proxy server receives the plurality of contract method combinations and sends the cross-link protocol generation request to the manager blockchain system, where the cross-link protocol generation request carries the plurality of contract method combinations.

605. The manager blockchain system receives the cross-link protocol generation request, generates the cross-link protocol based on the cross-link protocol generation request, and sends the cross-link protocol to the first proxy server and the second proxy server.

The cross-chain protocol is used for indicating the authority of the first blockchain system to call the second contract method based on the first contract method, namely the first blockchain system can call the second contract method in the second blockchain system based on the cross-chain protocol. Optionally, the cross-link protocol includes the first contract method and the second contract method.

After the request is generated based on the cross-link protocol to carry the cross-link protocol, the cross-link protocol is sent to the first proxy server so that the subsequent first proxy server can call the second contract method based on the cross-link protocol.

In one possible implementation manner, the cross-link protocol generation request carries a first application identifier, a first intelligent contract identifier, a first method identifier of a first contract method, a second blockchain system identifier, a second application identifier, a second intelligent contract identifier and a second method identifier of a second contract method, and the generated cross-link protocol comprises the first application identifier, the first intelligent contract identifier, the first method identifier, the second blockchain system identifier, the second intelligent contract identifier and the second method identifier. As shown in FIG. 10, the generated cross-chain protocol includes a variety of information for the first blockchain system and the second blockchain system.

Optionally, the cross-chain protocol further includes first system information of the first blockchain system, and second system information of the second blockchain system, where the first system information includes at least a server address of the first proxy server, and the second system information includes at least a server address of the second proxy server. Optionally, the system information further includes a system identifier corresponding to the corresponding blockchain system.

In one possible implementation, the process of generating a cross-chain protocol in step 605 includes the following steps 6051-6052:

6051. the manager blockchain system sends a cross-chain protocol generation request to the second blockchain system.

In one possible implementation, the step 6051 includes: the manager blockchain system sends the cross-link protocol generation request to a second proxy server, the second proxy server receives the cross-link protocol generation request and sends the cross-link protocol generation request to the second blockchain system.

In one possible implementation, the step 6051 includes: the management node device in the management side blockchain system sends the cross-link protocol generation request to a second proxy server, and the second proxy server receives the cross-link protocol generation request and sends the cross-link protocol generation request to a second node device in the second blockchain system.

The management node device is any node device in a plurality of node devices included in the management side blockchain system, and the second node device is any node device in a plurality of node devices included in the second blockchain system.

6052. The second blockchain system receives the cross-chain protocol generation request and sends an approval notice to the manager blockchain system in case of approving the cross-chain protocol generation request.

Wherein the grant notification is used to indicate that the second blockchain system grants the cross-chain protocol generation request.

In one possible implementation, the step 6052 includes: a second node device in the second blockchain system receives a cross-link protocol generation request, generates a request based on the cross-link protocol, and displays prompt information; and sending a consent notification to the management side blockchain system in response to the confirmation operation of the prompt information.

The second node device is any node device in a plurality of node devices included in the second blockchain system, and the prompt information is used for prompting the first blockchain system to request generation of a cross-chain protocol for calling the second contract method based on the first contract method.

The second node device responds to the confirmation operation of the prompt information by displaying the prompt information so that a user can check that the first blockchain system requests to call the cross-link protocol of the second contract method based on the first contract method, the confirmation operation of the prompt information indicates that the request for generating the cross-link protocol is agreed, and then, an agreement notification is sent to the management side blockchain system so that the subsequent management side blockchain system can generate the cross-link protocol based on the request for generating the cross-link protocol.

In one possible implementation, the step 6052 includes: a second node device in the second blockchain system receives a cross-link protocol generation request, generates a request based on the cross-link protocol, and displays prompt information; and sending an agreement notification to the management node equipment in the management side blockchain system in response to the confirmation operation of the prompt information.

6053. The manager blockchain system generates a cross-chain protocol based on the cross-chain protocol generation request in response to receiving the consent notification sent by the second blockchain system.

And generating a cross-link protocol based on the cross-link protocol generation request when receiving an agreement notification sent by the second blockchain system, wherein the agreement notification indicates that the second blockchain system has agreed to the cross-link protocol generation request.

In one possible implementation, the step 6053 includes: the management node device in the management side blockchain system generates a cross-chain protocol based on the cross-chain protocol generation request in response to receiving an approval notification sent by the second node device in the second blockchain system.

In one possible implementation, after the cross-link protocol is generated, the cross-link protocol and the consent notification are sent to the first proxy server, and the cross-link protocol is sent to the second proxy server.

It should be noted that, in this embodiment, only the case where the second blockchain system agrees to the cross-link protocol generation request is described as an example, and in another embodiment, in response to the second blockchain system disagreeing to the cross-link protocol generation request, a rejection notification is sent to the manager blockchain system, and the manager blockchain system forwards the rejection notification to the first blockchain system. For example, as shown in fig. 9, the prompt message displayed by the second node device further displays an agreeing option and a rejecting option, and sends an agreeing notification to the manager blockchain system in response to a triggering operation of the agreeing option; and in response to the triggering operation of the rejection option, sending a rejection notification to the management side blockchain system.

In one possible implementation, in response to the second blockchain system disagreeing the cross-chain protocol generation request, the second node device sends a rejection notification to the second proxy server, the second proxy server receives the rejection notification, sends the rejection notification to the management node device, the management node device receives the rejection notification, sends the rejection notification to the first proxy server, the first proxy server receives the rejection notification, sends the rejection notification to the first node device, and the first node device displays the rejection notification.

In the case that the second blockchain system does not agree with the request for generating the cross-chain protocol, the user knows that the second blockchain system refuses to generate the cross-chain protocol by sending a refusal notification to the first node device and displaying the refusal notification by the first node device.

It should be noted that, in the embodiment of the present application, only an example is described in which the cross-link protocol generation request carries a first contract method and a second contract method, and in another embodiment, the cross-link protocol generation request carries a plurality of contract method combinations, after receiving the cross-link protocol generation request, the second blockchain system generates a plurality of prompt messages based on the plurality of contract party combinations, and according to the step 605, a confirmation operation or a rejection operation is performed on each prompt message, and then, the manager blockchain system generates a cross-link protocol based on each consent notification and the corresponding contract method combination, that is, a plurality of cross-link protocols agreed by the second blockchain system can be generated.

606. The second proxy server receives the cross-link protocol sent by the management side blockchain system and stores the cross-link protocol.

After receiving the cross-link protocol, the second proxy server stores the cross-link protocol so as to execute the cross-link operation based on the cross-link protocol.

607. The first proxy server receives a cross-link protocol sent by a block chain system of a management side and stores the cross-link protocol; in response to a first cross-chain operation request of the first blockchain system to the second blockchain system, a second cross-chain operation request is sent to the second proxy server based on a cross-chain protocol and a first contract method.

The first cross-link operation request carries a cross-link protocol identifier of a cross-link protocol, and optionally the first cross-link operation request also carries a method identifier of a first contract method. The second cross-link operation request carries a cross-link protocol identification.

After receiving the cross-chain protocol, the first proxy server stores the cross-chain protocol so as to execute the cross-chain operation based on the stored cross-chain protocol. And receiving a first operation request of the first blockchain system to the second blockchain system at the first proxy server, and sending a second cross-chain operation request to the second proxy server based on the cross-chain protocol and the first contract method, so that the subsequent second proxy server can realize the call to the second contract method based on the second cross-chain operation request.

In one possible implementation, the manager blockchain system sends a cross-chain protocol and consent notification to the first proxy server, then step 607 includes: the first proxy server receives the cross-link protocol and the consent notification sent by the management side blockchain system, stores the cross-link protocol, and sends the consent notification to the first blockchain system.

Optionally, after receiving the consent notification, the first proxy server sends the consent notification to a first node device in the first blockchain system, and the first node device receives the consent notification and displays the consent notification.

In the case that the second blockchain system agrees to the cross-chain protocol generation request, the user is informed that the second blockchain system agrees to generate the cross-chain protocol by sending an agreement notification to the first node device and displaying the agreement notification by the first node device, so that the cross-chain operation is performed based on the generated cross-chain protocol.

In one possible implementation, the cross-chain protocol includes a server address of a second proxy server corresponding to the second contract method; the process of sending the second cross-chain operation request in step 607 includes: the first proxy server responds to a first cross-link operation request of the first block chain system to the second block chain, determines a cross-link protocol indicated by a cross-link protocol identification in the first cross-link operation request, and sends the second cross-link operation request to a second proxy server indicated by a server address according to the server address contained in the cross-link protocol.

The second proxy server corresponding to the second contract method is the second proxy server corresponding to the second blockchain system to which the second contract method belongs. The server address of the second proxy server is included in the cross-chain protocol, so that interaction between the first proxy server and the second proxy server can be realized, and cross-chain operation between the first blockchain system and the second blockchain system is realized.

Optionally, the first cross-link operation request carries a cross-link protocol identifier of a cross-link protocol and a method identifier of a first contract method, and the cross-link protocol further includes the method identifier of the first contract method, so that the first proxy server receives the first cross-link operation request of the first blockchain system to the second blockchain, responds to determining that the cross-link protocol indicated by the cross-link protocol identifier in the first cross-link operation request includes the method identifier of the first contract method, and sends the second cross-link operation request to the second proxy server indicated by the server address according to the server address included in the cross-link protocol.

Under the condition that the first cross-link operation request carries the method identifier of the first contract method, the method identifier of the first contract method contained in the cross-link protocol can be verified, whether the method identifier is the same as the method identifier of the first contract method carried by the first cross-link operation request or not can be verified, and only under the condition that verification is passed, the second cross-link operation is sent to the second proxy server, so that the first contract method called by the first blockchain system is matched with the cross-link protocol, and the accuracy of the subsequent execution of the cross-link operation is guaranteed.

608. The second proxy server receives a second cross-link operation request, calls a second contract method based on a cross-link protocol indicated by a cross-link protocol identifier carried in the second cross-link operation request, and executes the cross-link operation based on the second contract method.

In one possible implementation, the cross-chain protocol also has a method identification of the second contract method; the step 608 includes:

the second proxy server receives a second cross-link operation request, invokes a second contract method based on a method identification in the cross-link protocol indicated by the cross-link protocol identification, and performs the cross-link operation based on the second contract method.

Optionally, the second cross-link operation request further carries cross-link operation information, where the cross-link operation information is used to indicate operation information that needs to call the second contract method to execute, and the second proxy server receives the second cross-link operation request, sends, based on a method identifier in the cross-link protocol indicated by the cross-link protocol identifier, a method identifier of the second contract method and the cross-link operation information to a second node device in the second blockchain system, and the second node device receives the method identifier of the second contract method and the cross-link operation information, calls, based on the cross-link operation information, the second contract method indicated by the method identifier, and executes the cross-link operation.

Optionally, the cross-chain operation information is target information to be queried, and the second contract method is a query method, and the second node device invokes the query method to query information related to the target information in the second blockchain system.

Optionally, after the second node device queries information related to the target information, the second node device sends the queried information to the second proxy server, the second proxy server forwards the queried information to the first proxy server, and the first proxy server sends the information to the first blockchain system. That is, a cross-chain operation is implemented between the first blockchain system and the second blockchain system.

Fig. 11 is a flowchart of generating a cross-link protocol according to an embodiment of the present application, as shown in fig. 11, where the flowchart includes:

1. In the embodiment of the present application, the first blockchain system and the second blockchain system are used as both cross-links, and the own contract method needs to be registered on the management blockchain system.

2. The first blockchain system is used as a cross-chain initiator, and the cross-chain resource is selected, namely the second blockchain system is selected.

3. The first blockchain system determines a first contract method and a second contract method of both cross-chain parties based on the selected cross-chain resource, and submits a cross-chain protocol generation request to the management side blockchain system through a first proxy server corresponding to the first blockchain system.

4. After receiving the request for generating the cross-link protocol, the management side blockchain system sends the request for generating the cross-link protocol to the second blockchain system through a second proxy server corresponding to the second blockchain system.

5. The second blockchain system receives the request for generating the cross-link protocol, displays prompt information, the user approves the prompt information, responds to the confirmation operation of the prompt information, and indicates that the request for generating the cross-link protocol is approved, then sends an approval notice to the blockchain system of the manager, responds to the rejection operation of the prompt information, indicates that the request for generating the cross-link protocol is rejected, and then sends a rejection notice to the blockchain system of the manager.

6. The manager blockchain system responds to the received consent notice, generates a cross-chain protocol based on the cross-chain protocol generation request, and forwards the consent notice to the first blockchain system through the first proxy server; in response to receiving the rejection notification, forwarding, by the first proxy server, the rejection notification to the first blockchain system.

In the above embodiment, the first node device in the first blockchain system, the second node device in the second blockchain system, and the management node device in the management side blockchain system can each be a computer device, where the computer device includes a processor and a memory, and at least one computer program is stored in the memory, where the at least one computer program is loaded and executed by the processor to implement the operations performed by each of the cross-chain operation execution methods based on the cross-chain protocol in the above embodiment.

Optionally, the computer device is provided as a terminal. Fig. 12 shows a block diagram of a terminal 1200 according to an exemplary embodiment of the present application. The terminal 1200 may be a portable mobile terminal such as: a smart phone, a tablet computer, an MP3 player (Moving Picture Experts Group Audio Layer III, motion picture expert compression standard audio plane 3), an MP4 (Moving Picture Experts Group Audio Layer IV, motion picture expert compression standard audio plane 4) player, a notebook computer, or a desktop computer. Terminal 1200 may also be referred to as a user device, portable terminal, laptop terminal, desktop terminal, etc.

The terminal 1200 includes: a processor 1201 and a memory 1202.

Processor 1201 may include one or more processing cores, such as a 4-core processor, an 8-core processor, or the like. The processor 1201 may be implemented in at least one hardware form of DSP (Digital Signal Processing ), FPGA (Field-Programmable Gate Array, field programmable gate array), PLA (Programmable Logic Array ). The processor 1201 may also include a main processor, which is a processor for processing data in an awake state, also called a CPU (Central Processing Unit ), and a coprocessor; a coprocessor is a low-power processor for processing data in a standby state. In some embodiments, the processor 1201 may be integrated with a GPU (Graphics Processing Unit, image processor) for taking care of rendering and rendering of content that the display screen is required to display. In some embodiments, the processor 1201 may also include an AI (Artificial Intelligence ) processor for processing computing operations related to machine learning.

Memory 1202 may include one or more computer-readable storage media, which may be non-transitory. Memory 1202 may also include high-speed random access memory, as well as non-volatile memory, such as one or more magnetic disk storage devices, flash memory storage devices. In some embodiments, a non-transitory computer readable storage medium in memory 1202 is used to store at least one computer program for execution by processor 1201 to implement the cross-chain protocol based cross-chain operation execution method provided by the method embodiments herein.

In some embodiments, the terminal 1200 may further optionally include: a peripheral interface 1203, and at least one peripheral. The processor 1201, the memory 1202, and the peripheral interface 1203 may be connected by a bus or signal lines. The individual peripheral devices may be connected to the peripheral device interface 1203 via buses, signal lines, or a circuit board. Specifically, the peripheral device includes: at least one of radio frequency circuitry 1204, a display 1205, a camera assembly 1206, audio circuitry 1207, a positioning assembly 1208, and a power supply 1209.

The peripheral interface 1203 may be used to connect at least one peripheral device associated with an I/O (Input/Output) to the processor 1201 and the memory 1202. In some embodiments, the processor 1201, the memory 1202, and the peripheral interface 1203 are integrated on the same chip or circuit board; in some other embodiments, either or both of the processor 1201, the memory 1202, and the peripheral interface 1203 may be implemented on separate chips or circuit boards, which is not limited in this embodiment.

The Radio Frequency circuit 1204 is used for receiving and transmitting RF (Radio Frequency) signals, also called electromagnetic signals. The radio frequency circuit 1204 communicates with a communication network and other communication devices via electromagnetic signals. The radio frequency circuit 1204 converts an electrical signal into an electromagnetic signal for transmission, or converts a received electromagnetic signal into an electrical signal. Optionally, the radio frequency circuit 1204 includes: antenna systems, RF transceivers, one or more amplifiers, tuners, oscillators, digital signal processors, codec chipsets, subscriber identity module cards, and so forth. The radio frequency circuit 1204 may communicate with other terminals via at least one wireless communication protocol. The wireless communication protocol includes, but is not limited to: the world wide web, metropolitan area networks, intranets, generation mobile communication networks (2G, 3G, 4G, and 5G), wireless local area networks, and/or WiFi (Wireless Fidelity ) networks. In some embodiments, the radio frequency circuit 1204 may also include NFC (Near Field Communication ) related circuits, which are not limited in this application.

The display 1205 is used to display a UI (User Interface). The UI may include graphics, text, icons, video, and any combination thereof. When the display 1205 is a touch display, the display 1205 also has the ability to collect touch signals at or above the surface of the display 1205. The touch signal may be input as a control signal to the processor 1201 for processing. At this time, the display 1205 may also be used to provide virtual buttons and/or a virtual keyboard, also referred to as soft buttons and/or a soft keyboard. In some embodiments, the display 1205 may be one and disposed on a front panel of the terminal 1200; in other embodiments, the display 1205 may be at least two, respectively disposed on different surfaces of the terminal 1200 or in a folded design; in other embodiments, the display 1205 may be a flexible display disposed on a curved surface or a folded surface of the terminal 1200. Even more, the display 1205 may be arranged in an irregular pattern that is not rectangular, i.e., a shaped screen. The display 1205 can be made of LCD (Liquid Crystal Display ), OLED (Organic Light-Emitting Diode) or other materials.

The camera assembly 1206 is used to capture images or video. Optionally, camera assembly 1206 includes a front camera and a rear camera. The front camera is arranged on the front panel of the terminal, and the rear camera is arranged on the back of the terminal. In some embodiments, the at least two rear cameras are any one of a main camera, a depth camera, a wide-angle camera and a tele camera, so as to realize that the main camera and the depth camera are fused to realize a background blurring function, and the main camera and the wide-angle camera are fused to realize a panoramic shooting and Virtual Reality (VR) shooting function or other fusion shooting functions. In some embodiments, camera assembly 1206 may also include a flash. The flash lamp can be a single-color temperature flash lamp or a double-color temperature flash lamp. The dual-color temperature flash lamp refers to a combination of a warm light flash lamp and a cold light flash lamp, and can be used for light compensation under different color temperatures.

The audio circuitry 1207 may include a microphone and a speaker. The microphone is used for collecting sound waves of a user and the environment, converting the sound waves into electric signals, and inputting the electric signals to the processor 1201 for processing, or inputting the electric signals to the radio frequency circuit 1204 for voice communication. For purposes of stereo acquisition or noise reduction, a plurality of microphones may be respectively disposed at different portions of the terminal 1200. The microphone may also be an array microphone or an omni-directional pickup microphone. The speaker is used to convert electrical signals from the processor 1201 or the radio frequency circuit 1204 into sound waves. The speaker may be a conventional thin film speaker or a piezoelectric ceramic speaker. When the speaker is a piezoelectric ceramic speaker, not only the electric signal can be converted into a sound wave audible to humans, but also the electric signal can be converted into a sound wave inaudible to humans for ranging and other purposes. In some embodiments, the audio circuitry 1207 may also include a headphone jack.

The positioning component 1208 is used to position the current geographic location of the terminal 1200 to enable navigation or LBS (Location Based Service, location-based services). The positioning component 1208 may be a positioning component based on the united states GPS (Global Positioning System ), the beidou system of china, or the galileo system of russia.

The power supply 1209 is used to power the various components in the terminal 1200. The power source 1209 may be an alternating current, a direct current, a disposable battery, or a rechargeable battery. When the power source 1209 comprises a rechargeable battery, the rechargeable battery may be a wired rechargeable battery or a wireless rechargeable battery. The wired rechargeable battery is a battery charged through a wired line, and the wireless rechargeable battery is a battery charged through a wireless coil. The rechargeable battery may also be used to support fast charge technology.

In some embodiments, terminal 1200 also includes one or more sensors 1210. The one or more sensors 1210 include, but are not limited to: acceleration sensor 1211, gyroscope sensor 1212, pressure sensor 1213, fingerprint sensor 1214, optical sensor 1215, and proximity sensor 1216.

The acceleration sensor 1211 may detect the magnitudes of accelerations on three coordinate axes of the coordinate system established with the terminal 1200. For example, the acceleration sensor 1211 may be used to detect components of gravitational acceleration in three coordinate axes. The processor 1201 may control the display 1205 to display a user interface in either a landscape view or a portrait view based on the gravitational acceleration signal acquired by the acceleration sensor 1211. The acceleration sensor 1211 may also be used for the acquisition of motion data of a game or a user.

The gyro sensor 1212 may detect a body direction and a rotation angle of the terminal 1200, and the gyro sensor 1212 may collect a 3D motion of the user on the terminal 1200 in cooperation with the acceleration sensor 1211. The processor 1201 may implement the following functions based on the data collected by the gyro sensor 1212: motion sensing (e.g., changing UI according to a tilting operation by a user), image stabilization at shooting, game control, and inertial navigation.

The pressure sensor 1213 may be disposed at a side frame of the terminal 1200 and/or at a lower layer of the display 1205. When the pressure sensor 1213 is provided at a side frame of the terminal 1200, a grip signal of the terminal 1200 by a user may be detected, and the processor 1201 performs a left-right hand recognition or a shortcut operation according to the grip signal collected by the pressure sensor 1213. When the pressure sensor 1213 is disposed at the lower layer of the display 1205, the processor 1201 controls the operability control on the UI interface according to the pressure operation of the user on the display 1205. The operability controls include at least one of a button control, a scroll bar control, an icon control, and a menu control.

The fingerprint sensor 1214 is used to collect a fingerprint of the user, and the processor 1201 identifies the identity of the user based on the fingerprint collected by the fingerprint sensor 1214, or the fingerprint sensor 1214 identifies the identity of the user based on the fingerprint collected. Upon recognizing that the user's identity is a trusted identity, the processor 1201 authorizes the user to perform relevant sensitive operations including unlocking the screen, viewing encrypted information, downloading software, paying for and changing settings, etc. The fingerprint sensor 1214 may be provided on the front, back, or side of the terminal 1200. When a physical key or a vendor Logo is provided on the terminal 1200, the fingerprint sensor 1214 may be integrated with the physical key or the vendor Logo.

The optical sensor 1215 is used to collect the ambient light intensity. In one embodiment, processor 1201 may control the display brightness of display 1205 based on the intensity of ambient light collected by optical sensor 1215. Specifically, when the intensity of the ambient light is high, the display brightness of the display screen 1205 is turned up; when the ambient light intensity is low, the display brightness of the display screen 1205 is turned down. In another embodiment, processor 1201 may also dynamically adjust the shooting parameters of camera assembly 1206 based on the intensity of ambient light collected by optical sensor 1215.

A proximity sensor 1216, also called a distance sensor, is provided on the front panel of the terminal 1200. The proximity sensor 1216 is used to collect the distance between the user and the front of the terminal 1200. In one embodiment, when the proximity sensor 1216 detects that the distance between the user and the front face of the terminal 1200 gradually decreases, the processor 1201 controls the display 1205 to switch from the bright screen state to the off screen state; when the proximity sensor 1216 detects that the distance between the user and the front surface of the terminal 1200 gradually increases, the processor 1201 controls the display 1205 to switch from the off-screen state to the on-screen state.

It will be appreciated by those skilled in the art that the structure shown in fig. 12 is not limiting and that more or fewer components than shown may be included or certain components may be combined or a different arrangement of components may be employed.

In the above embodiment, the first node device in the first blockchain system, the second node device in the second blockchain system, and the management node device in the management side blockchain system can be computer devices. Optionally, the computer device is provided as a server. The first proxy server and the second proxy server in the above embodiments may be servers described in the following embodiments.

Fig. 13 is a schematic structural diagram of a server provided in the embodiments of the present application, where the server 1300 may have a relatively large difference due to different configurations or performances, and may include one or more processors (Central Processing Units, CPU) 1301 and one or more memories 1302, where at least one computer program is stored in the memories 1302, and the at least one computer program is loaded by the processor 1301 and executed to implement the methods provided in the above-mentioned method embodiments. Of course, the server may also have a wired or wireless network interface, a keyboard, an input/output interface, and other components for implementing the functions of the device, which are not described herein.

The present application also provides a computer readable storage medium, in which at least one computer program is stored, where the at least one computer program is loaded and executed by a processor in the above-mentioned computer device or server to implement the operations performed in the cross-chain operation execution method based on the cross-chain protocol of the above-mentioned embodiment.

Embodiments of the present application also provide a computer program product or computer program comprising computer program code stored in a computer readable storage medium. The processor in the above-described computer device or server reads the computer program code from the computer-readable storage medium, and executes the computer program code, so that the above-described computer device or server implements the operations performed in the cross-chain operation execution method based on the cross-chain protocol of the above-described embodiment.

Those of ordinary skill in the art will appreciate that all or a portion of the steps implementing the above embodiments may be implemented by hardware, or may be implemented by a program for instructing relevant hardware, where the program may be stored in a computer readable storage medium, and the above storage medium may be a read-only memory, a magnetic disk or an optical disk, etc.

The foregoing description of the embodiments is merely an optional embodiment and is not intended to limit the embodiments, and any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the embodiments of the present application are intended to be included in the scope of the present application.

Claims

1. The method is characterized by being applied to a network system, wherein the network system comprises a first blockchain system, a second blockchain system, a first proxy server corresponding to the first blockchain system, a second proxy server corresponding to the second blockchain system and a manager blockchain system, and the method comprises the following steps:

2. The method of claim 1, wherein prior to the first proxy server receiving the first contract method and the second contract method sent by the first blockchain system, the method further comprises:

a first node device in the first blockchain system displays a first contract method list based on an information entry interface, wherein the first contract method list comprises a plurality of contract methods registered by the first blockchain system in the manager blockchain system;

the first node device determining the selected first contract method from a plurality of contract methods and transmitting the first contract method to the first proxy server;

the first proxy server receives a first contract method sent by the first blockchain system, and the first contract method comprises the following steps:

the first proxy server receives the first contract method sent by the first node device.

3. The method of claim 2, wherein the first node device in the first blockchain system displays a first list of contract methods based on an information entry interface, comprising:

the first node device displaying, based on the information entry interface, a plurality of application identifications registered by the first blockchain system in the manager blockchain system, each application indicated by the application identification being served by the first blockchain system;

The first node device is configured to display, in response to a selection operation of a first application identifier of a plurality of the application identifiers, the first contract method list in the information entry interface, the first contract method list including a plurality of contract methods registered by the first blockchain system in the manager blockchain system and corresponding to the first application identifier.

4. The method of claim 3, wherein the first node device displaying a plurality of application identifications registered by the first blockchain system in the manager blockchain system based on the information entry interface, comprising:

the first node device displays a plurality of application identifications registered by the first blockchain system in the management side blockchain system in a first display area of the information input interface;

the first node device displaying the first list of contract methods in the information entry interface in response to a selection operation of a first application identifier of a plurality of the application identifiers, comprising:

the first node device displays the first application identifier and the first contract method list in the first display area in response to a selection operation of the first application identifier in the application identifiers.

5. The method of claim 1, wherein prior to the first proxy server receiving the first contract method and the second contract method sent by the first blockchain system, the method further comprises:

the first node equipment in the first blockchain system displays system identifiers corresponding to a plurality of third blockchain systems except the first blockchain system, which are registered on the manager blockchain system, based on an information input interface;

the first node device responds to the selected operation of the system identification corresponding to the second blockchain system in the system identifications, and a second contract method list is displayed, wherein the second contract method list comprises a plurality of contract methods registered by the second blockchain system in the management side blockchain system;

the first node device determining the selected second contract method from a plurality of contract methods and transmitting the second contract method to the first proxy server;

the process of the first proxy server receiving the second contract method sent by the first blockchain system includes:

the first proxy server receives the second contract method sent by the first node device.

6. The method of claim 5, wherein the first node device displaying a second list of contract methods in response to a selected operation on a system identification corresponding to the second blockchain system among the plurality of system identifications, comprises:

the first node device displaying a plurality of application identifications registered by the second blockchain system in the manager blockchain system in response to a selected operation of a system identification corresponding to the second blockchain system among the plurality of system identifications, each application indicated by the application identification being served by the second blockchain system;

the first node device displays, in response to a selection operation of a second application identifier of the plurality of application identifiers, the second contract method list in the information entry interface, the second contract method list including a plurality of contract methods registered by the second blockchain system in the manager blockchain system and corresponding to the second application identifier.

7. The method of claim 5, wherein the first node device in the first blockchain system displays system identifications corresponding to a plurality of third blockchain systems other than the first blockchain system registered on the manager blockchain system based on an information entry interface, comprising:

The first node device displays a plurality of system identifications in a second display area of the information input interface;

the first node device responds to the selected operation of the system identifier corresponding to the second blockchain system in the system identifiers, and displays a second contract method list, which comprises the following steps:

and the first node equipment responds to the selected operation of the system identification corresponding to the second blockchain system in the system identifications, and displays the system identification corresponding to the second blockchain system and the second contract method list in the second display area.

8. The method of claim 1, wherein the first proxy server receives a first contract method and a second contract method sent by the first blockchain system, comprising:

a first node device in the first blockchain system determining a first smart contract registered by the first blockchain system in the manager blockchain system, the first smart contract including at least one third contract method, and a second smart contract registered by the second blockchain system in the manager blockchain system, the second smart contract including at least one fourth contract method;

The first node device determining a plurality of contract method combinations based on at least one of the third contract method and at least one of the fourth contract method, each contract method combination including one of the third contract method and one of the fourth contract method;

the first node device determines a selected target contract method combination from a plurality of contract method combinations, wherein the target contract method combination comprises the first contract method and the second contract method, and sends the target contract method combination to the first proxy server;

the first proxy server receives the target contract method combination sent by the first node device.

9. The method of claim 1, wherein prior to the first proxy server receiving the first contract method and the second contract method sent by the first blockchain system, the method further comprises:

a first node device in the first blockchain system displays an information registration interface; acquiring registration information of the first blockchain system based on the information registration interface, wherein the registration information at least comprises the first contract method; sending an information registration request to the first proxy server, wherein the information registration request carries the registration information;

The first proxy server receives the information registration request sent by the first node device and sends the information registration request to the management side blockchain system;

the manager blockchain system receives the information registration request and stores the registration information.

10. The method according to any of claims 1-9, wherein the cross-chain protocol comprises a server address of the second proxy server corresponding to the second contract method; the sending, in response to a first cross-chain operation request by the first blockchain system to the second blockchain system, a second cross-chain operation request to the second proxy server based on the cross-chain protocol and the first contract method, including:

and the first proxy server responds to a first cross-link operation request of the first block chain system to the second block chain system, and sends a second cross-link operation request to the second proxy server indicated by the server address according to the server address contained in the cross-link protocol.

11. The method of claim 10, wherein the cross-link protocol further comprises a method identification of the second contract method; the second proxy server receives the second cross-link operation request, invokes the second contract method based on the cross-link protocol indicated by the cross-link protocol identification, and executes the cross-link operation based on the second contract method, including:

The second proxy server receives the second cross-link operation request, calls the second contract method based on the method identification in the cross-link protocol indicated by the cross-link protocol identification, and executes the cross-link operation based on the second contract method.

12. The method of any of claims 1-9, wherein the generating a cross-chain protocol based on the cross-chain protocol generation request comprises:

the manager blockchain system sends the cross-chain protocol generation request to the second blockchain system;

the second blockchain system receives the cross-link protocol generation request and sends an agreement notification to the manager blockchain system under the condition that the cross-link protocol generation request is agreed;

the manager blockchain system generates the cross-chain protocol based on the cross-chain protocol generation request in response to receiving the consent notification sent by the second blockchain system.

13. The method of claim 11, wherein the second blockchain system receiving the cross-chain protocol generation request, in the event that the cross-chain protocol generation request is granted, sending a grant notification to the manager blockchain system, comprising:

A second node device in the second blockchain system receives the request for generating the cross-link protocol, generates a request based on the cross-link protocol, and displays prompt information, wherein the prompt information is used for prompting the first blockchain system to request to generate the cross-link protocol for calling the second contract method based on the first contract method;

and the second node equipment responds to the confirmation operation of the prompt information and sends the consent notification to the management side blockchain system.

14. A network system, which comprises a first blockchain system, a second blockchain system, a first proxy server corresponding to the first blockchain system, a second proxy server corresponding to the second blockchain system and a management side blockchain system;

15. The system of any of claims 14, wherein the cross-chain protocol includes a server address of the second proxy server corresponding to the second contract method;

the first proxy server is configured to respond to a first cross-link operation request of the first blockchain system to the second blockchain system, and send a second cross-link operation request to the second proxy server indicated by the server address according to the server address included in the cross-link protocol.