A cross-chain decentralized approach based on contract management

Abstract

The present invention discloses a cross-chain decentralization method based on contract management, in which the cross-chain communication part includes three links: communication between source chain nodes and proxy nodes, communication between proxy nodes, and communication between proxy nodes and destination chain nodes; cross-chain proxy nodes are responsible for cross-chain registration, cross-chain identity management, cross-chain verification, cross-chain routing, cross-chain decentralized strategy management, etc.; cross-chain management contracts are deployed on blockchain nodes, responsible for consensus verification of decentralized strategies for communication between proxy nodes and blockchain nodes; decentralized strategies are included during cross-chain registration, and when cross-chain transactions are sent, decentralized strategies need to be met before the next transaction can be carried out; communication between proxy nodes and between proxy nodes and blockchain nodes all need to meet decentralized strategies. The method of the present invention can realize the decentralization of cross-chain transactions, prevent the risk of single-point evil, ensure the high availability and high security of cross-chain, and is of great significance to the construction of blockchain ecology.

Description

Technical Field

[0001] The present invention relates to the field of blockchain technology, and in particular to a cross-chain decentralization method based on contract management. Background Art

[0002] The greatest value of blockchain is to realize the transmission of information value, but most blockchain platforms are highly exclusive, resulting in many value islands in today's blockchain network, and blockchains cannot be interconnected in value. Cross-chain technology can break through the barriers between blockchains, but the existing cross-chain technologies, such as relay chains, notaries and other technical solutions, have centralization risks. When the relay chain solution is adopted, when the source chain conducts cross-chain transactions to the destination chain, generally a node in the source chain sends a cross-chain message to the relay chain, the relay chain does identity authentication, cross-chain routing, and sends the cross-chain transaction to the destination chain. In this process, the cross-chain transaction is sent from the source chain to the relay chain, which has a centralization problem such as single-node communication. Similarly, the communication link from the relay chain to the destination chain also has a centralization problem of single-point communication. This will lead to the possibility of communication nodes attacking maliciously and causing asset losses during cross-chain value exchange, and the entire cross-chain solution will lose the characteristics of high availability, high security, and anti-malice. A solution that can achieve cross-chain decentralization of blockchain is of great significance to cross-chain. Summary of the invention

[0003] In response to the above technical problems, the present invention proposes a blockchain cross-chain decentralization method based on contract management, which can realize the decentralization of cross-chain transactions, prevent the risk of single point evil, ensure the high availability and high security of the cross-chain, and is of great significance to the construction of the blockchain ecology.

[0004] The object of the present invention is achieved through the following technical solution: a cross-chain decentralized method based on contract management, the method comprising:

[0005] Blockchain cross-chain communication includes three links: communication between source chain nodes and proxy nodes, communication between source chain proxy nodes and destination chain proxy nodes, and communication between proxy nodes and destination chain nodes. Each cross-chain link can be configured with multiple communication connections according to the decentralization strategy.

[0006] The cross-chain proxy node is responsible for cross-chain registration, cross-chain identity management, cross-chain verification, cross-chain routing, cross-chain standardized communication, and cross-chain decentralized strategy management;

[0007] The cross-chain management contract is deployed on the blockchain node and is used for cross-chain communication between the blockchain node and the proxy node, cross-chain transaction verification, decentralized strategy verification, submission of cross-chain transactions to the destination chain business contract, receiving the execution results of the cross-chain transaction business contract, and sending the execution results to the proxy node;

[0008] The cross-chain management contract is responsible for the consensus verification of the decentralized strategy for communication between proxy nodes and blockchain nodes; the decentralized strategy is included in the cross-chain registration, and when sending a cross-chain transaction, the decentralized strategy needs to be met before the next transaction can be carried out; the communication between proxy nodes and between proxy nodes and blockchain nodes must meet the decentralized strategy.

[0009] Furthermore, the cross-chain process includes the following steps:

[0010] (1) The source chain initiates cross-chain registration: Sign according to the cross-chain certificate issued by the peer, register the identity information, verification rules, and decentralization strategy to the destination chain, the source chain proxy node verifies the signature, and sends the signature to the destination chain proxy node for verification and signature, and verifies according to the cross-chain certificate. After verification, cross-chain authorization is performed, and the registration information is stored on the chain and locally on the proxy node;

[0011] (2) The destination chain registers with the source chain;

[0012] (3) The source chain sends a cross-chain transaction, standardizes the communication message through the proxy node, and signs and sends it to the peer proxy node;

[0013] (4) The destination chain proxy node receives the cross-chain transaction, performs signature verification, identity verification, permission verification, and decentralization strategy verification. After the verification is passed, the standard message is converted into the destination chain message format and the cross-chain transaction is submitted to the destination chain;

[0014] (5) The destination chain cross-chain management contract processes cross-chain transactions, verifies the identity and decentralization strategy of the transaction, and submits the cross-chain transaction to the destination chain business contract after verification;

[0015] (6) The destination chain returns the cross-chain transaction results of the business contract execution.

[0016] Furthermore, the decentralization strategies include: ANY, MAJORITY, ALL, NOUTOF;

[0017] ANY: Verification is passed upon receiving a message from any proxy node;

[0018] MAJORITY: Verification is successful only when messages sent by most proxy nodes are received;

[0019] ALL: Verification can only be passed after receiving messages sent by all proxy nodes;

[0020] NOUTOF: Verification can only be passed after receiving messages sent by the specified N proxy nodes.

[0021] Furthermore, the registration information structure when the source chain performs cross-chain registration with the destination chain is as follows:

[0022] Fields meaning Version Chain registration information version ChainID The ID of the source chain P2CPolicy Decentralization strategy between blockchain nodes and proxy nodes C2CPolicy Decentralization strategy between proxy nodes Validators Validation rule information ConsensuType Consensus type of source chain Status Status Information ChainType Types of source chains PublicKey Public key information Description Description Extra Custom extension fields

[0023] Furthermore, during cross-chain registration, the decentralized strategies of the two links are obtained and persistently stored in the cross-chain management contract ledger and the proxy node; the strategy between the blockchain node and the proxy node is obtained through the cross-chain management contract in the registration message and the decentralized strategy between the blockchain node and the proxy node is recorded in the blockchain ledger; the strategy between the proxy nodes is obtained through the registration message and recorded in the proxy node.

[0024] Furthermore, the source chain performs cross-chain registration with the destination chain, which mainly includes the identity information, verification rules, and decentralization strategy of the source chain. After successful registration, the verification engine of the destination chain generates verification rules for the chain, and subsequently verifies the legitimacy of cross-chain transactions and the decentralization strategy according to this verification rule; generates different verification rules for blockchains with different architectures, and generates different decentralization strategies according to different registration information; stores the identity information and registration information of the source chain persistently; the verification engine of the destination chain proxy node checks the registration information of the source chain, verifies the transaction according to the generated verification rules, and ensures the correctness of the transaction according to the decentralization strategy.

[0025] Furthermore, when conducting a cross-chain transaction, the proxy node first receives the cross-chain transaction sent by the peer proxy node. The destination chain proxy node verifies the transaction according to the decentralized strategy at the time of registration. If the strategy is met, the cross-chain transaction is submitted to the destination chain cross-chain management contract. The cross-chain management contract verifies the transaction according to the decentralized strategy at the time of registration. If the strategy is met, the verification is passed and the cross-chain transaction consensus is conducted within the chain. After the consensus is completed, the transaction is written into the ledger. The destination chain executes the cross-chain transaction and returns the result, which is sent to the destination chain proxy node through the cross-chain management contract and then to the source chain proxy node.

[0026] Furthermore, the decentralized strategy verification between the proxy nodes is specifically as follows: the destination chain proxy node collects cross-chain transactions sent from the peer chain; verifies the cross-chain message digest and signature information, and if the message digest is the same and the signature verification passes, it is considered that messages endorsed by different proxy nodes are received; within a limited time T, for the same cross-chain transaction, the endorsement messages of different proxy nodes are verified with the decentralized strategy, and if the verification passes, it is submitted to the cross-chain management contract of the destination chain.

[0027] Furthermore, the decentralized strategy verification between the proxy node and the blockchain node is specifically as follows: the cross-chain management contract receives the cross-chain transaction sent by the proxy node; verifies the cross-chain message digest and signature information, if the message digest is the same and the signature verification passes, it is considered that messages endorsed by different proxy nodes are received; within the limited time T, for the same cross-chain transaction, the endorsement messages of different proxy nodes are verified with the decentralized strategy, and if the verification passes, consensus execution is performed.

[0028] Furthermore, the method supports decentralized strategy upgrades, sends decentralized strategy upgrade transactions on the premise of satisfying the current decentralized strategy, and then upgrades and updates the decentralized strategy and performs persistent storage.

[0029] The beneficial effects of the present invention are as follows: the present invention designs a cross-chain management contract and a decentralized strategy, the cross-chain management contract is deployed on the blockchain node, and is responsible for the decentralized strategy of communication between the consensus verification agent node and the blockchain node; the decentralized strategy is included in the cross-chain registration, and when sending a cross-chain transaction, the decentralized strategy needs to be satisfied before the next transaction can be carried out; the entire cross-chain communication link: the communication between the crossagent and the crossagent and the blockchain node all needs to satisfy the decentralized strategy. The method of the present invention can realize the decentralization of cross-chain transactions, prevent the risk of single-point evil, ensure the high availability and high security of the cross-chain, and is of great significance to the construction of the blockchain ecology. BRIEF DESCRIPTION OF THE DRAWINGS

[0030] Figure 1 This is an overall architecture diagram of the blockchain cross-chain decentralization method provided by an embodiment of the present invention;

[0031] Figure 2 is a cross-chain flow chart provided by an embodiment of the present invention;

[0032] Figure 3 It is a flow chart of decentralized strategy verification between crossagents provided by an embodiment of the present invention;

[0033] Figure 4 It is a flow chart of decentralized strategy verification between a crossagent and a blockchain node provided by an embodiment of the present invention;

[0034] Figure 5 is a cross-chain registration flow chart provided by an embodiment of the present invention;

[0035] Figure 6 is a cross-chain transaction flow chart provided by an embodiment of the present invention;

[0036] Figure 7 is a policy upgrade flow chart provided by an embodiment of the present invention;

[0037] Figure 8 It is a flow chart of the cross-chain management contract design provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0038] In order to better understand the technical solution of the present application, the embodiments of the present application are described in detail below with reference to the accompanying drawings.

[0039] It should be clear that the described embodiments are only part of the embodiments of the present application, rather than all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in the field without creative work are within the scope of protection of the present application.

[0040] The terms used in the embodiments of the present application are only for the purpose of describing specific embodiments, and are not intended to limit the present application. The singular forms "a", "said" and "the" used in the embodiments of the present application and the appended claims are also intended to include plural forms, unless the context clearly indicates other meanings.

[0041] The overall architecture of the cross-chain decentralized method based on contract management provided by the present invention is as follows: Figure 1 shown.

[0042] The cross-chain communication part includes three links: cross-chain link 1, i.e. the communication between the source chain blockchain node and the proxy node, cross-chain link 2, i.e. the communication between the source chain proxy node and the destination chain proxy node, and cross-chain link 3, i.e. the communication between the proxy node and the destination chain blockchain node. Each cross-chain link can be configured with multiple communication connections according to the decentralization strategy.

[0043] The cross-chain proxy node crossagent is responsible for cross-chain registration, cross-chain identity management, cross-chain verification, cross-chain routing, cross-chain standardized communication, cross-chain decentralized strategy management, etc.

[0044] The cross-chain management contract is deployed on the blockchain node and is mainly used for cross-chain communication between the blockchain node and the cross-chain proxy node, cross-chain transaction verification, decentralized strategy verification, submission of cross-chain transactions to the destination chain business contract, receiving the execution results of the business contract of the cross-chain transaction, and sending the execution results to the cross-chain proxy node.

[0045] The cross-chain management contract is responsible for consensus verification of the decentralized strategy of communication between the crossagent and the blockchain node; the decentralized strategy is included in the cross-chain registration. When sending a cross-chain transaction, the decentralized strategy must be met before the next transaction can be carried out. For example, the source chain needs to meet the endorsement of two or more nodes for the cross-chain transaction to meet the decentralized strategy. The communication between crossagents also needs to meet the decentralized strategy, and the communication between the crossagent and the destination chain also needs to meet the decentralized strategy. According to the strategy at the time of registration, the crossagent will verify the number of messages sent by the crossagent of the opposite chain. For example, when the decentralized strategy is to meet the message of two or more crossagents, it is necessary to receive the same summary message endorsed by two or more crossagents of the opposite chain to consider the transaction valid. In this way, the entire cross-chain communication link: between crossagents, between crossagents and blockchain nodes, all implement the decentralized strategy, preventing the possibility of single-point evil, and improving the high availability and high security of the cross-chain.

[0046] The cross-chain process of the present invention is as follows Figure 2 As shown, the following steps are included:

[0047] 1. The source chain initiates cross-chain registration, signs the cross-chain certificates issued by the certificate management module, registers identity information, verification rules, decentralization strategies and other information to the destination chain, and the crossagent of the source chain verifies the signature and sends the signature to the crossagent of the destination chain to verify the signature and sign it, and verify it according to the cross-chain certificate. After the verification is passed, cross-chain authorization is performed, and the registration information is stored on the chain and in the crossagent local database.

[0048] 2. The destination chain is registered with the source chain, and the process is the same as the forward process.

[0049] 3. Send cross-chain transactions, standardize communication messages through crossagent, and sign and send them to the peer crossagent.

[0050] 4. The destination chain crossagent receives the cross-chain transaction and performs signature verification, identity verification, permission verification, and decentralized strategy verification. That is, it receives cross-chain transactions sent by multiple peer crossagents. If the strategy is met within the threshold time, the verification is passed, otherwise the verification fails. After the verification is passed, the standard message is converted into the destination chain message format and the cross-chain transaction is submitted to the destination chain. The specific decentralized strategy verification process includes: verification between crossagents and verification between crossagents and blockchain nodes.

[0051] The verification process between crossagents is as follows Figure 3 As shown, it includes: the destination chain crossagent collects cross-chain transactions sent by the peer chain; verifies the cross-chain message digest and signature information. If the message digest is the same and the signature verification is passed, it is considered that messages endorsed by different crossagents are received; within the limited time T, for the same cross-chain transaction, different crossagent endorsement messages and decentralized strategies are verified. If the verification is passed, it is submitted to the cross-chain management contract of the destination chain. Otherwise, it is determined whether it has timed out. If it has timed out, it returns the timeout information. Otherwise, the destination chain crossagent continues to collect cross-chain transactions sent by the peer chain.

[0052] The verification process between crossagent and blockchain nodes is as follows Figure 4 As shown, it includes: the cross-chain management contract receives the cross-chain transaction sent by the crossagent; verifies the cross-chain message digest and signature information. If the message digest is the same and the signature verification passes, it is considered that the message endorsed by different crossagents is received; within the limited time T, for the same cross-chain transaction, the endorsed messages of different crossagents are verified with the decentralization strategy. If the verification passes, consensus execution is performed, otherwise it is determined whether it has timed out. If it has timed out, the timeout information is returned, otherwise the cross-chain management contract continues to receive the cross-chain transaction sent by the crossagent.

[0053] 5. The destination chain cross-chain management contract processes cross-chain transactions, verifies the identity and decentralization strategy of the transaction, and submits the cross-chain transaction to the destination chain business contract if the verification passes.

[0054] 6. The destination chain returns the cross-chain transaction results of the business contract execution, and the return process is consistent with the forward process.

[0055] The following is a detailed introduction to the implementation process of each part of the cross-chain.

[0056] (1) Certificate issuance

[0057] The certificate management module issues a cross-chain root certificate and a public-private key pair to the cross-chain proxy node. The specific issuance rules are as follows: Assuming that chain A and chain B communicate with each other, the root certificate of chain A will use the public key of chain B to issue a cross-chain certificate to chain B; the root certificate of chain B will use the public key of chain A to issue a cross-chain certificate to chain A, and deploy the certificate and the public-private key pair on the cross-chain proxy node crossagent. Then chain B can use the root certificate to verify the cross-chain certificate of the message sent by chain A, and chain A can also use the root certificate to verify the cross-chain certificate of the message sent by chain B; at the same time, the message digest signature will also be verified to achieve identity authentication and ensure communication security.

[0058] (2) Cross-chain registration

[0059] The source chain will register with the destination chain across chains, mainly including the identity information, verification rules, and decentralization strategies of the source chain. After successful registration, the verification engine of the destination chain will generate verification rules for the chain, and then verify the legitimacy of cross-chain transactions and the decentralization strategy according to the verification rules. Different verification rules will be generated for blockchains with different architectures, and different decentralization strategies will be generated according to different registration information. The identity information and registration information of the source chain are stored persistently. The verification engine of the destination chain crossagent will check the registration information of the source chain, verify the transaction according to the generated verification rules, and ensure the correctness of the transaction according to the decentralization strategy.

[0060] (3) Identity and authority management

[0061] The permission control module provides functions such as certificate issuance, multi-chain registration, and permission control. Specifically, when the source chain and the destination chain need to communicate with each other, they need to issue cross-chain certificates to each other, and then register according to permission management requirements, such as chain access rights, smart contract access rights, contract method rights, related field access rights, and data read and write rights. The other party will then review it. If the registration is successful, the communication information will be verified during communication. Access to other chains requires authorization verification from other chains to meet the isolation and protection of data.

[0062] (4) Cross-chain standardized communication

[0063] The cross-chain communication standard bus mainly includes the cross-chain communication interface and the cross-chain standard communication protocol. The communication protocol is CSCP (crosschain standard communication protocol), which is mainly used for cross-chain network communication between blockchains. It standardizes messages from different blockchain platforms and can realize the communication of the underlying blockchains of heterogeneous platforms. The bus defines standard interfaces for information exchange between blockchains, mainly:

[0064] The transaction conversion interface can convert transaction messages to and from the bus standard protocol CSCP, and can use the unified standard interface on the bus during the communication process;

[0065] Transaction sending interface, used by the source chain to send information to the destination chain;

[0066] Transaction receiving interface, used by the destination chain to receive cross-chain transactions;

[0067] Transaction verification interface, used to verify transaction information;

[0068] Registration link interface, used for identity registration;

[0069] Update chain interface, used to update chain identity information;

[0070] Logout link interface, used to log out link identity information.

[0071] (5) Decentralized strategy management

[0072] (a) Cross-chain registration: Obtain the decentralization strategies of the two links and store them persistently in the cross-chain management contract ledger and crossagent.

[0073] Decentralization strategies mainly include: ANY, MAJORITY, ALL, NOUTOF;

[0074] ANY: Verification is successful upon receiving a message from any crossagent;

[0075] MAJORITY: Verification is successful only when messages sent by most crossagents are received;

[0076] ALL: Verification is passed only after receiving messages sent by all crossagents;

[0077] NOUTOF: Verification can only be passed after receiving messages sent by the specified N crossagents.

[0078] The decentralization strategy includes the entire cross-chain link: blockchain node to crossagent, crossagent to crossagent. The strategy between blockchain node and crossagnet obtains the node to crossagent strategy in the registration message through the cross-chain management contract and records it in the ledger; the strategy between crossagent and crossagent is obtained through the registration message and recorded in the crossagent. The cross-chain registration process is as follows: Figure 5 shown.

[0079] When a chain initiates a cross-chain transaction, it is necessary to construct the chain registration information. Its structure is shown in the following table. This information is used for the information structure when the source chain registers the destination chain across chains:

[0080] Fields meaning Version Chain registration information version ChainID The ID of the source chain P2CPolicy Decentralization strategy between blockchain nodes and crossagents C2CPolicy Decentralization strategy between crossagents Validators Validation rule information ConsensuType Consensus type of source chain Status Status Information ChainType Types of source chains PublicKey Public key information Description Description Extra Custom extension fields

[0081] (b) Cross-chain transactions

[0082] When conducting a cross-chain transaction, the crossagent first receives the cross-chain transaction sent by the peer crossagent. The crossagnet of the destination chain verifies the number of cross-chain transactions according to the decentralization strategy at the time of registration. If the strategy is met, the cross-chain transaction is submitted to the cross-chain management contract of the destination chain. The cross-chain transaction verified by the crossagent will be sent to the blockchain node. At this time, the cross-chain management contract will receive the cross-chain transaction sent by the crossagent. The cross-chain management contract verifies it according to the registered decentralization strategy. When enough cross-chain transactions with the same summary endorsed by the crossagen are received, the verification is passed, and the cross-chain transaction consensus within the chain is performed. After the consensus is completed, it is written into the ledger. The destination chain executes the cross-chain transaction and returns the result, which is sent to the crossagent through the cross-chain management contract and then to the crossagent of the source chain. Its decentralization strategy is consistent with the forward process. The cross-chain transaction process is as follows: Figure 6 shown.

[0083] (c) Strategy Upgrade

[0084] Supports decentralized strategy upgrades. The upgrade process is to send a decentralized strategy upgrade transaction under the premise of satisfying the current decentralized strategy, and then upgrade and update the decentralized strategy. For example, to upgrade the strategy between crossagents, the strategy upgrade transaction is sent to the crossagent on the other end. When the decentralized strategy between crossagents is satisfied, the decentralized strategy of the crossagent is updated and persistently stored. The strategy upgrade process is as follows: Figure 7 shown.

[0085] (6) Cross-chain management contract design

[0086] It is mainly used for cross-chain communication between blockchain nodes and cross-chain proxy nodes, cross-chain transaction verification, decentralized strategy verification, submitting cross-chain transactions to the destination chain business contract, receiving the execution results of the cross-chain transaction business contract, and sending the execution results to the cross-chain proxy node. The cross-chain management contract design process is as follows Figure 8 shown.

[0087] The cross-chain management contract interface design mainly includes:

[0088] Init: used for cross-chain management contract initialization;

[0089] recvCrossTx: used to receive cross-chain transactions;

[0090] verifyCrossTx: used to verify cross-chain transactions;

[0091] CommitCrossTx: used to submit cross-chain transactions to the destination chain;

[0092] RecvCrossTxResponse: used to receive cross-chain transaction execution results;

[0093] SendCrossTxResponse: used to send cross-chain transaction receipts;

[0094] Query: used to query cross-chain transactions.

[0095] The above description is merely a preferred embodiment of one or more embodiments of the present specification and is not intended to limit one or more embodiments of the present specification. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of one or more embodiments of the present specification shall be included in the scope of protection of one or more embodiments of the present specification.

Claims

1. A cross-chain decentralized method based on contract management, characterized in that: The method includes: Blockchain cross-chain communication includes three links: communication between source chain nodes and proxy nodes, communication between source chain proxy nodes and destination chain proxy nodes, and communication between proxy nodes and destination chain nodes. Each cross-chain link is configured with multiple communication connections according to the decentralization strategy. The cross-chain proxy node is responsible for cross-chain registration, cross-chain identity management, cross-chain verification, cross-chain routing, cross-chain standardized communication and cross-chain decentralized strategy management; The cross-chain management contract is deployed on the blockchain node and is used for cross-chain communication between the blockchain node and the proxy node, cross-chain transaction verification, decentralized strategy verification, submission of cross-chain transactions to the destination chain business contract, receiving the execution results of the cross-chain transaction business contract, and sending the execution results to the proxy node; The cross-chain management contract is responsible for consensus verification of the decentralized strategy for communication between proxy nodes and blockchain nodes. The decentralized strategy is included in cross-chain registration. When sending cross-chain transactions, the decentralized strategy must be met before the next transaction can proceed. The communication between proxy nodes and between proxy nodes and blockchain nodes must meet the decentralized strategy. The cross-chain process includes the following steps: (1) The source chain initiates cross-chain registration: Sign according to the cross-chain certificate issued by the peer, register the identity information, verification rules and decentralization strategy to the destination chain, the source chain proxy node verifies the signature, and sends the signature to the destination chain proxy node for verification and signature, and verifies according to the cross-chain certificate. After verification, cross-chain authorization is performed, and the registration information is stored on the chain and locally on the proxy node; (2) The destination chain registers with the source chain; (3) The source chain sends a cross-chain transaction, standardizes the communication message through the proxy node, and signs and sends it to the peer proxy node; (4) The destination chain proxy node receives the cross-chain transaction and performs signature verification, identity verification, permission verification, and decentralized strategy verification. Decentralized strategy verification is to receive cross-chain transactions sent by multiple peer proxy nodes. If the strategy is met within the threshold time, the verification passes. Otherwise, the verification fails. After the verification passes, the standard message is converted into the destination chain message format and the cross-chain transaction is submitted to the destination chain; The decentralized strategy verification between proxy nodes is as follows: the proxy node of the destination chain collects cross-chain transactions sent by the peer chain; verifies the cross-chain message digest and signature information. If the message digest is the same and the signature verification passes, it is considered that messages endorsed by different proxy nodes have been received; within the limited time T, for the same cross-chain transaction, the endorsement messages of different proxy nodes are verified with the decentralized strategy. If the verification passes, it is submitted to the cross-chain management contract of the destination chain. Otherwise, it is determined whether it has timed out. If it has timed out, the timeout information is returned. Otherwise, the proxy node of the destination chain continues to collect cross-chain transactions sent by the peer chain. The decentralization strategy verification between the proxy node and the blockchain node is as follows: the cross-chain management contract receives the cross-chain transaction sent by the proxy node; verifies the cross-chain message digest and signature information. If the message digest is the same and the signature verification passes, it is considered that the message endorsed by different proxy nodes has been received; within the limited time T, for the same cross-chain transaction, the endorsement messages of different proxy nodes are verified with the decentralization strategy. If the verification passes, consensus execution is performed. Otherwise, it is determined whether it has timed out. If it has timed out, a timeout message is returned. Otherwise, the cross-chain management contract continues to receive cross-chain transactions sent by the proxy node. (5) The destination chain cross-chain management contract processes cross-chain transactions, verifies the identity and decentralization strategy of the transaction, and submits the cross-chain transaction to the destination chain business contract after verification; (6) The destination chain returns the cross-chain transaction results of the business contract execution; The cross-chain decentralized strategy management is specifically as follows: (a) Cross-chain registration: Obtain the decentralization strategies of the two links and store them persistently in the cross-chain management contract ledger and proxy nodes; The decentralization strategies include: ANY, MAJORITY, ALL and NOUTOF; ANY: verification is passed when a message is received from any proxy node; MAJORITY: verification is passed when a message is received from most proxy nodes; ALL: verification is passed when a message is received from all proxy nodes; NOUTOF: verification is passed when a message is received from the specified N proxy nodes; The decentralization strategy includes the entire cross-chain link: blockchain node to proxy node, proxy node to proxy node; the strategy between blockchain node and proxy node, the decentralization strategy between blockchain node and proxy node in the registration message is obtained through the cross-chain management contract and recorded in the blockchain ledger; the strategy between proxy node and proxy node is obtained through the registration message and recorded in the proxy node; When a chain initiates a cross-chain transaction, it needs to build the chain registration information. The registration information structure when the source chain registers cross-chain with the destination chain is as follows: Version: chain registration information version; ChainID: source chain ID; P2CPolicy: decentralization strategy between blockchain nodes and proxy nodes; C2CPolicy: decentralization strategy between proxy nodes; Validators: validation rule information; ConsensuType: chain consensus type; Status: status information; ChainType: source chain type; PublicKey: public key information; Description: description information; Extra: custom extension field; (b) Cross-chain transactions: When conducting cross-chain transactions, the proxy node first receives the cross-chain transaction sent by the peer proxy node. The destination chain proxy node verifies the transaction according to the decentralized strategy at the time of registration. If the strategy is met, the cross-chain transaction is submitted to the destination chain cross-chain management contract. The cross-chain management contract verifies the transaction according to the decentralized strategy at the time of registration. If the strategy is met, the transaction passes the verification and the cross-chain transaction consensus is conducted within the chain. After the consensus is reached, the transaction is written into the ledger. The destination chain executes the cross-chain transaction and returns the result, which is sent to the destination chain proxy node through the cross-chain management contract and then to the source chain proxy node. (c) Strategy upgrade: Supports the upgrade of decentralized strategies. The upgrade process is to send a decentralized strategy upgrade transaction on the premise of satisfying the current decentralized strategy, and then upgrade and update the decentralized strategy and perform persistent storage.

2. The method according to claim 1, characterized in that The source chain registers cross-chain with the destination chain, including the source chain's identity information, verification rules and decentralization strategy. After successful registration, the destination chain's verification engine generates verification rules for the source chain that performs cross-chain registration. Subsequently, the legitimacy of cross-chain transactions and the decentralization strategy are verified according to this verification rule. Different verification rules are generated for blockchains with different architectures, and different decentralization strategies are generated according to different registration information. The source chain's identity information and registration information are persistently stored. The verification engine of the destination chain proxy node verifies the source chain's registration information, verifies transactions according to the generated verification rules, and ensures the correctness of transactions according to the decentralization strategy.

Images