A loosely coupled unified cross-chain supervision method and device supporting multi-dimensional expansion

Abstract

The present invention proposes a loosely coupled unified cross-chain supervision method and device that supports multi-dimensional expansion. This method and device are characterized by decoupling cross-chain message processing and cross-chain supervision processes, migrating the main cross-chain supervision processes off-chain, thereby minimizing the docking interaction between the blockchain system and the supervision system, and thus reducing the degree of coupling between the two processes. On this basis, the present invention proposes a full-chain supervision mechanism: Ex ante supervision of cross-chain transactions is achieved through a supervision contract deployed on the chain. As a member of the cross-chain system, the supervision system participates in the cross-chain message verification process to achieve in-process and post-process supervision of cross-chain transactions. Furthermore, supervision instructions can be constructed based on the designed unified cross-chain supervision data package that supports multi-dimensional expansion, and issued to the supervision contract of a specific blockchain to update the supervision rules of ex ante supervision.

Description

Technical Field

[0001] The present invention relates to the field of blockchain technology, and in particular to a loosely coupled unified cross-chain supervision method, device, electronic device, computer-readable storage medium and computer program product that supports multi-dimensional expansion. Background Art

[0002] As a distributed ledger technology, blockchain boasts core characteristics such as decentralization, immutability, and trusted traceability. It is the next-generation information infrastructure for building a trusted digital world. Since the official release of Ethereum in 2014, blockchain applications have rapidly expanded to encompass numerous industries, including cross-border payments, supply chain financing, and data copyright storage. However, due to differing needs and characteristics across industries, blockchains inevitably exhibit heterogeneity. Heterogeneous blockchain systems exhibit significant differences in underlying design, such as consensus mechanisms and block structures. This makes it difficult for blockchain data to interoperate and for trust to be transferred, resulting in a pronounced silo effect. Consequently, cross-chain technologies have emerged to enable data interoperability and trust transfer between chains.

[0003] However, to meet the regulatory needs of different countries and regions, cross-chain supervision has become an indispensable factor in ensuring the blockchain industry's continued scale, interoperability, and healthy development. This is because, on the one hand, implementing cross-chain supervision within the blockchain helps ensure the legality, transparency, and security of cross-chain transactions; on the other hand, cross-chain supervision can also help regulators better understand the flow of blockchain transaction data, thereby more effectively tracking and managing potential financial risks.

[0004] As the need for cross-chain supervision becomes increasingly prominent, research teams both domestically and internationally have proposed a number of solutions. For example, a distributed notary public cross-chain supervision mechanism for consortium chains employs a notary public chain as a cross-chain relay, connecting the supervision chain and various consortium chains. A set of supervision protocols is designed to ensure the security of the cross-chain supervision process. Furthermore, the cross-chain exchange protocol (PCP) was designed to balance privacy and regulatory traceability, leveraging cryptographic principles such as signatures of knowledge (SoKs) to ensure the correctness and privacy of cross-chain transactions. Finally, a chain-governing-chain supervision framework for multi-chain collaborative governance utilizes the blockchain itself as the regulatory infrastructure. Heterogeneous chains access this cross-chain supervision system through off-chain supervisory nodes, while a front-end engine is deployed on these supervisory nodes to load and execute supervisory instructions issued by the supervisory chain.

[0005] The distributed notary public cross-chain oversight mechanism only applies to consortium chains. Cross-chain oversight requests are initiated by the overseeing chain. A supervisory contract deployed on the supervised consortium chain randomly collects and packages partial transaction data, which is then transmitted back to the overseeing chain for verification. If any verification errors occur, the administrator of the supervised chain is notified. This supervisory process cannot provide real-time oversight of cross-chain transactions. Due to the random packaging of transaction data and the fact that supervisory operations are performed on the overseeing chain, the supervisory operation becomes very limited in scope while maintaining efficiency, and is often limited to simple verification.

[0006] The Cross-Chain Exchange Protocol (PCP) prioritizes privacy and traceability in cross-chain oversight. However, it is built solely on a sidechain-based cross-chain system and targets token swaps, resulting in a single regulatory dimension. While the protocol uses cryptography to ensure the accuracy and privacy of individual transactions, it lacks the ability to comprehensively analyze and monitor multiple transactions already occurring on the blockchain.

[0007] The chain-governing-chain regulatory framework of multi-chain collaborative governance uses off-chain regulatory nodes as the connection points between blockchains and cross-chain systems, which can support different heterogeneous links to access the system. However, blockchains are forced to build regulatory nodes before they can access and use this cross-chain system, which leads to the tight coupling of regulatory operations with basic cross-chain processes. If the system wants to supervise ongoing cross-chain transactions, the transactions on the chain need to be directed to the regulatory nodes, and after performing regulatory operations off-chain, they need to return to the chain for operations, and finally call the cross-chain related process interface to forward it to the destination blockchain. The regulatory process is relatively cumbersome.

[0008] Problem 1 of the above existing technologies: How to decouple the cross-chain supervision process from the basic cross-chain process. Cross-chain supervision and cross-chain transactions are independent of each other. Decoupling the two frameworks can make the cross-chain supervision architecture relatively easy to directly adapt to the existing cross-chain system.

[0009] The second problem with the existing technologies mentioned above is how to design a comprehensive cross-chain regulatory mechanism for the entire process. Most existing regulatory processes do not fully cover the entire cross-chain transaction process. For example, they only focus on a single transaction in progress or only conduct post-analysis of cross-chain transactions that have already been uploaded to the blockchain. Therefore, it is essential to design a regulatory mechanism that can cover all aspects of cross-chain transactions.

[0010] Problem 3 of the aforementioned existing technologies: How to support multi-dimensional cross-chain regulatory operations. Existing cross-chain regulatory mechanisms either offer a single regulatory operation (simple verification of cross-chain transactions) or downplay this issue, focusing more on implementing the specific cross-chain regulatory process without providing sufficient information on the specific regulatory operations that can be performed. Therefore, it is essential to design a protocol that clearly defines and expresses various regulatory operations.

[0011] To sum up, the above-mentioned existing technologies have problems such as high difficulty in unified supervision, difficulty in implementing cross-chain full-process supervision, tight coupling of the supervision process with the basic cross-chain process, single supervision dimension, and difficulty in expanding customized supervision models. As a result, after the cross-chain supervision process is added, the cross-chain supervision functionality is weak and the efficiency of cross-chain transaction processing is reduced. Summary of the Invention

[0012] In order to solve the above problems, the present invention proposes a loosely coupled multi-dimensional unified cross-chain supervision protocol. The protocol is based on the principle of minimal intrusion and aims to connect and adapt to more blockchain systems with as little modification as possible, thereby building a unified cross-chain supervision framework. Specifically, the present invention decouples cross-chain message processing and cross-chain supervision processes, and migrates the main cross-chain supervision processes to the off-chain, thereby minimizing the docking interaction between the blockchain system and the supervision system, and further reducing the degree of coupling between the two processes. On this basis, the present invention proposes a full-chain supervision mechanism: through the supervision contract deployed on the chain, the pre-emptive supervision of cross-chain transactions is realized. As a member of the cross-chain system, the supervision system participates in the cross-chain message verification process to realize the in-process and post-process supervision of cross-chain transactions. It can also construct supervision instructions based on the designed unified cross-chain supervision data package that supports multi-dimensional expansion, and send them to the supervision contract of a specific blockchain to update the supervision rules of pre-emptive supervision.

[0013] Specifically, in view of the shortcomings of existing technologies, such as Figure 7 As shown, the present invention proposes a loosely coupled unified cross-chain supervision method that supports multi-dimensional expansion, which includes:

[0014] The initial step is to obtain registration and access to a cross-chain system of multiple blockchains, at least one of which has a regulatory contract deployed;

[0015] In a judgment step, an application contract of one blockchain A among the multiple blockchains initiates a cross-chain transaction to another blockchain B; a judgment is made as to whether blockchain A has the supervision contract and has enabled cross-chain supervision; if so, a supervision step is executed;

[0016] In the self-check step, the application contract calls the regulatory contract to determine whether the current cross-chain transaction complies with the regulatory contract. If so, a regulatory event indicating review passed is thrown and step 3 is executed. Otherwise, a regulatory event indicating review failed is thrown and the cross-chain transaction is terminated.

[0017] Verification step: The cross-chain transaction is executed to the cross-chain contract through a cross-contract call, and the cross-chain contract processes and encapsulates it to obtain a cross-chain event. After the relay node of the cross-chain system captures the cross-chain transaction, it checks whether blockchain A has enabled cross-chain supervision. If not, it sends a verification request to the node in the committee to obtain the verification result. The relay node of the cross-chain system decides whether to construct an endorsement and forward it to blockchain B together with the cross-chain transaction based on the verification request, completing the cross-chain process. If it is enabled, it sends a verification request to the node in the committee and a supervision request to the supervision node to obtain the verification and supervision results respectively. The relay node of the cross-chain system decides whether to construct an endorsement and forward it to blockchain B together with the cross-chain transaction based on the verification request and the supervision request, completing the cross-chain process.

[0018] The loosely coupled unified cross-chain regulatory approach supporting multi-dimensional expansion includes:

[0019] In the update step, the regulatory system sends the regulatory instructions to the regulatory nodes in the committee. The regulatory nodes store and forward the regulatory instructions to the cross-chain system. The cross-chain system delivers the regulatory instructions to the regulatory contract. The regulatory contract updates the stored regulatory rules according to the regulatory instructions and throws a rule update event. After the cross-chain system captures the rule update event, it returns a regulatory receipt to the regulatory node.

[0020] The loosely coupled unified cross-chain supervision method supporting multi-dimensional extension, wherein the supervision instruction includes: supervision type, and / or sending chain domain name, and / or receiving chain domain name, and / or sender contract address, and / or receiver contract address, and / or transaction content, and / or custom extension fields;

[0021] Among them, the field of this regulatory type adopts a hierarchical coding design, each main type identifies a regulatory dimension, and each main type is divided into multiple subtypes.

[0022] The loosely coupled unified cross-chain supervision method that supports multi-dimensional expansion,

[0023] The supervision contract and supervision system are added to the cross-chain system in the form of plug-ins. A designated flag is set in the supervision contract, and whether to enable cross-chain supervision is determined according to the content of the flag, thereby decoupling the cross-chain supervision process from the basic cross-chain process. When cross-chain supervision is enabled, cross-chain transactions issued by the application contract must be reviewed by the supervision contract before the supervision contract can continue to pass the transaction to the cross-chain contract. When cross-chain supervision is turned off, any application contract on the blockchain can call the cross-chain contract.

[0024] like Figure 8 As shown, the present invention also proposes a loosely coupled unified cross-chain supervision device that supports multi-dimensional expansion, including:

[0025] The initial module obtains registration and accesses a cross-chain system of multiple blockchains, at least one of which has a regulatory contract deployed;

[0026] The judgment module is used to determine whether the application contract of one blockchain A among the multiple blockchains initiates a cross-chain transaction to another blockchain B; and whether blockchain A has the supervision contract and has enabled cross-chain supervision. If so, the supervision module is executed;

[0027] In the self-check module, the application contract calls the regulatory contract to determine whether the current cross-chain transaction complies with the regulatory contract. If so, a regulatory event indicating that the review has passed is thrown and module 3 is executed. Otherwise, a regulatory event indicating that the review has failed is thrown and the cross-chain transaction is terminated.

[0028] Verification module: The cross-chain transaction is executed to the cross-chain contract through a cross-contract call, and the cross-chain contract processes and encapsulates it to obtain a cross-chain event. After the relay node of the cross-chain system captures the cross-chain transaction, it checks whether blockchain A has enabled cross-chain supervision. If not, it sends a verification request to the node in the committee to obtain a verification result. The relay node of the cross-chain system decides whether to construct an endorsement and forward it to blockchain B together with the cross-chain transaction based on the verification request to complete the cross-chain process; if it is enabled, it sends a verification request to the node in the committee and a supervision request to the supervision node to obtain verification and supervision results respectively. The relay node of the cross-chain system decides whether to construct an endorsement and forward it to blockchain B together with the cross-chain transaction based on the verification request and the supervision request to complete the cross-chain process.

[0029] The loosely coupled unified cross-chain supervision device supporting multi-dimensional expansion includes:

[0030] In the update module, the regulatory system sends the regulatory instructions to the regulatory nodes in the committee. The regulatory nodes store and forward the regulatory instructions to the cross-chain system. The cross-chain system delivers the regulatory instructions to the regulatory contract. The regulatory contract updates the stored regulatory rules according to the regulatory instructions and throws a rule update event. After the cross-chain system captures the rule update event, it returns a regulatory receipt to the regulatory node.

[0031] The loosely coupled unified cross-chain supervision device supporting multi-dimensional extension, wherein the supervision instruction includes: supervision type, and / or sending chain domain name, and / or receiving chain domain name, and / or sender contract address, and / or receiver contract address, and / or transaction content, and / or custom extension fields;

[0032] The regulatory type field adopts a hierarchical coding design, where each main type identifies a regulatory dimension, and each main type is divided into multiple subtypes;

[0033] The supervision contract and supervision system are added to the cross-chain system in the form of plug-ins. A designated flag is set in the supervision contract, and whether to enable cross-chain supervision is determined according to the content of the flag, thereby decoupling the cross-chain supervision process from the basic cross-chain process. When cross-chain supervision is enabled, cross-chain transactions issued by the application contract must be reviewed by the supervision contract before the supervision contract can continue to pass the transaction to the cross-chain contract. When cross-chain supervision is turned off, any application contract on the blockchain can call the cross-chain contract.

[0034] The present invention also proposes an electronic device, which includes a loosely coupled unified cross-chain supervision device that supports multi-dimensional expansion. The electronic device may be connected to an information display device, which is used to display the verification and / or supervision results using display parameters and attributes set by the user or through an artificial intelligence model.

[0035] The present invention also proposes a computer-readable storage medium on which a computer program is stored. When the computer program is executed by a processor, the steps of the loosely coupled unified cross-chain supervision method that supports multi-dimensional expansion are implemented.

[0036] The present invention also proposes a computer program product, including a computer program, wherein when the computer program is executed by a processor, it implements the steps of the loosely coupled unified cross-chain supervision method that supports multi-dimensional expansion. BRIEF DESCRIPTION OF THE DRAWINGS

[0037] Figure 1 A loosely coupled cross-chain regulatory architecture;

[0038] Figure 2 A schematic diagram of the cross-chain supervision process before and during the event;

[0039] Figure 3 This is a diagram of the post-cross-chain supervision process;

[0040] Figure 4 This is the design of the supervision field supervisionType of the present invention;

[0041] Figure 5 This is a flow chart of cross-chain supervision before and during the present invention;

[0042] Figure 6 This is the post-cross-chain supervision flow chart of the present invention;

[0043] Figure 7 Flow chart of the method of the present invention;

[0044] Figure 8 This is a module diagram of the device of the present invention;

[0045] Figure 9 This is a schematic structural diagram of a first electronic device of the present invention;

[0046] Figure 10 This is a schematic diagram of the application environment structure of the first electronic device of the present invention;

[0047] Figure 11 This is a schematic structural diagram of a second electronic device according to the present invention.

[0048] Reference numerals:

[0049] A-First electronic device;

[0050] B- Loosely coupled unified cross-chain supervisory device supporting multi-dimensional expansion;

[0051] C-data acquisition equipment;

[0052] D-information display device;

[0053] 1000- second electronic device;

[0054] Ⅰ-computing unit;

[0055] II-ROM;

[0056] III-RAM;

[0057] IV-bus;

[0058] V-interface;

[0059] VI-input unit;

[0060] VII-output unit;

[0061] VIII-Storage medium;

[0062] IX-Communication unit. DETAILED DESCRIPTION

[0063] It should be noted that, in this application, relational terms such as first and second, etc., are used only to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any actual relationship or order between these entities or operations. Moreover, the terms "comprises," "comprising," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus comprising a series of elements includes not only those elements, but also other elements not explicitly listed, or elements inherent to such process, method, article, or apparatus.

[0064] Without further constraints, an element defined by the phrase "comprises a..." does not preclude the existence of additional identical elements in the process, method, article or apparatus that includes the element.

[0065] The processor described in the present invention is the control center of an electronic device and can be a single processor or a collective term for multiple processing elements. For example, it can be one or more central processing units (CPUs), an application-specific integrated circuit (ASIC), or one or more integrated circuits configured to implement embodiments of the present invention, such as one or more digital signal processors (DSPs) or one or more field programmable gate arrays (FPGAs).

[0066] Optionally, the processor can perform various functions of the electronic device by running or executing a software program stored in the memory, and calling data stored in the memory.

[0067] In a specific implementation, as an example, the processor may include one or more CPUs. Each of these processors may be a single-core processor (single-CPU) or a multi-core processor (multi-CPU). The processor herein may refer to one or more devices, circuits, and / or processing cores for processing data (e.g., computer program instructions). Electronic devices may include servers, desktop computers, laptop computers, smartphones, tablet computers, embedded computers, etc., where the embedded computers include vehicles and robots, etc.

[0068] The memory is used to store the software program for executing the solution of the present invention, and the execution is controlled by the processor. The specific implementation method can refer to the above method embodiment and will not be repeated here.

[0069] It should be noted that the structure of the electronic device shown in the drawings of the present invention does not constitute a limitation thereto, and the actual knowledge structure recognition device may include more or fewer components than shown in the drawings, or a combination of certain components, or a different arrangement of components.

[0070] The above embodiments can be implemented in whole or in part via software, hardware (e.g., circuits), firmware, or any other combination thereof. When implemented using software, the above embodiments can be implemented in whole or in part in the form of a computer program product. The computer program product comprises one or more computer instructions or computer programs. When loaded or executed on a computer, the processes or functions described in accordance with the embodiments of the present invention are fully or partially performed. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired means (e.g., infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium accessible by a computer or a data storage device such as a server or data center that contains a collection of one or more available media. The available medium can be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., DVDs), or semiconductor media. The semiconductor media can be a solid-state drive.

[0071] It should also be understood that the term "and / or" in this document simply describes an association between related objects, indicating that three possible relationships exist. For example, "A and / or B" can represent: A alone, A and B together, or B alone. A and B can be singular or plural. Furthermore, the character " / " in this document generally indicates an "or" relationship between the related objects, but it may also indicate an "and / or" relationship. For specific understanding, please refer to the context.

[0072] In this disclosure, "at least one" means one or more, and "plurality" means two or more. "At least one of the following" or similar expressions refers to any combination of these items, including any combination of single or plural items. For example, "at least one of a, b, or c" can mean: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or plural.

[0073] It should also be understood that in various embodiments of the present invention, the size of the serial numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present invention.

[0074] In the several embodiments provided by the present invention, it should be understood that the disclosed devices, apparatuses, and methods can be implemented in other ways. For example, the device embodiments described above are merely illustrative. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another device, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interface, indirect coupling or communication connection of the device or unit, which can be electrical, mechanical or other forms.

[0075] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected to achieve the purpose of this embodiment according to actual needs.

[0076] In addition, each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0077] If the functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, or the portion that contributes to the prior art, or the portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in various embodiments of the present invention. The aforementioned storage media include various media that can store program code, such as USB flash drives, mobile hard drives, read-only memories (ROM), random access memories (RAM), magnetic disks, or optical disks.

[0078] In order to make the above features and effects of the present invention more clear and understandable, the following examples are given and explained in detail with reference to the accompanying drawings. This specification discloses one or more embodiments that include the features of the present invention. The disclosed embodiments are for illustration only. The scope of protection of the present invention is not limited to the disclosed embodiments, and the present invention is defined by the appended claims. In response to the defects of the existing cross-chain solutions described above, the present invention is designed mainly based on the following key technical points:

[0079] Key Technical Point 1: Loosely Coupled Cross-Chain Supervision Architecture. To overcome the drawback of the prior art of tightly coupling the cross-chain supervision process with the basic cross-chain process, this invention proposes a loosely coupled cross-chain supervision architecture that minimizes the interaction between the blockchain system and the supervision system, thereby reducing the degree of coupling between the two processes.

[0080] The architecture mainly includes blockchain, regulatory contracts, cross-chain systems and regulatory systems, such as Figure 1 As shown, in the architecture of the present invention, the supervisory contract, as a system-provided application contract, intervenes in the cross-chain process. The cross-chain system deploys it alongside the cross-chain contract when a blockchain is connected to the system. Specifically, the present invention and the cross-chain supervisory function are closely related to the supervisory contract deployed on each blockchain and the independent supervisory system. The supervisory contract receives supervisory instructions from the supervisory system and supports simple supervisory operations on the chain. The supervisory system receives cross-chain transactions pushed by the cross-chain system and issues supervisory instructions after comprehensive analysis. In this architecture, the supervisory contract and supervisory system are added to the existing cross-chain system in a plug-in-like manner to perform supervisory functions. Each blockchain can independently select or suspend the cross-chain supervisory function by modifying the SUPERVISOR_BUTTION parameter defined in the supervisory contract, thereby decoupling the cross-chain supervisory process from the basic cross-chain process. Under this architecture, the cross-chain system can be designed independently by developers. For example, a cross-chain system can be designed to support cross-chain transactions between different heterogeneous chains. In this way, the integration of the cross-chain supervisory function also enables unified supervision of these heterogeneous chains. Since the implementation of loose coupling is closely related to the design of the cross-chain supervision mechanism, the present invention and its specific implementation methods form the following key technical point 2;

[0081] Key Technical Point 2: A unified cross-chain supervision mechanism for the entire chain. To overcome the shortcomings of the existing technologies, which suffer from limited regulatory coverage, this invention proposes a unified cross-chain supervision mechanism for the entire chain, enabling cross-chain supervision to cover all aspects of cross-chain transactions. This unified cross-chain supervision mechanism aims to provide pre-, in-, and post-process supervision of cross-chain transactions.

[0082] First, we introduce the design of cross-chain supervision mechanism before and during the event, such as Figure 2As shown. Although there are many options for cross-chain systems, for ease of description, this invention uses the form of relay node + committee PTC for introduction. The relay node is responsible for connecting various entities in the cross-chain process, such as blockchain #1, blockchain #2, committee PTC and other relay nodes in the figure. Each committee node in the committee PTC is responsible for providing endorsements for cross-chain transactions. The regulatory system also acts as an entity, providing regulatory nodes to participate in the committee PTC. In a basic cross-chain process, the cross-chain contract in the source blockchain processes the cross-chain transaction initiated by the application contract and throws a cross-chain event. After being captured by the relay node, it sends a verification request to the committee PTC. After obtaining the endorsement, the cross-chain transaction is forwarded to the destination blockchain. During the cross-chain process, the cross-chain transaction is encapsulated as a universal cross-chain data packet and transmitted in the cross-chain system in a unified message format.

[0083] The supervisory contract is deployed between the application contract and the cross-chain system contract and can be considered a system-deployed application contract. Unlike the basic cross-chain process, cross-chain transactions initiated by the application contract are not directly transmitted through the cross-chain contract. Instead, they are first reviewed by the supervisory contract based on the supervisory rules stored in the contract, completing a pre-emptive oversight process. If the review passes, the supervisory contract forwards the original transaction to the cross-chain contract via a cross-contract call, and the cross-chain contract proceeds with the normal cross-chain process. If the review fails, the supervisory contract no longer forwards the original transaction, and the cross-chain process terminates. After completing its pre-emptive oversight function, the supervisory contract returns a result (e.g., a simple and effective True or False variable) to the application contract regarding the success or failure of the transaction forwarding. This allows the application contract to quickly roll back the result in the event of a transaction failure. It also throws an event recording the supervisory result and its cause, which is stored on the blockchain. Blockchain administrators can use this supervisory event to further analyze the application contract involved. For example, if the supervisory event is related to preventing replay attacks, administrators can analyze where the application contract contains replay attack vulnerabilities and implement code corrections and other related measures.

[0084] When a cross-chain transaction reaches a relay node during the process, it is sent to various committee nodes for voting according to the corresponding strategy. Committee nodes include both normal nodes and supervisory nodes connected to the supervisory system. In this cross-chain mechanism, the supervisory system participates in the cross-chain oversight process as a member of the PTC (Proactive Committee Committee). Unlike the majority-rule voting mechanism of standard committee voting, supervisory nodes are responsible for conducting ongoing oversight, specifically analyzing the legality of the cross-chain transaction. Therefore, their votes carry a veto power. If a supervisory node deems the cross-chain transaction unverified, it will vote against it, preventing the relay node from generating the PTC endorsement for the cross-chain transaction, and the cross-chain process will terminate. If a cross-chain transaction is reversed due to a supervisory node's negative vote, the handling of this abnormal transaction can replicate the same handling procedures used for cross-chain transactions reversed by the PTC in the basic cross-chain process. The specific procedures will be defined by the cross-chain system developer to implement cross-chain asset rollback and on-chain state synchronization. If the cross-chain transaction passes the PTC's verification strategy, the relay node will construct an endorsement for the cross-chain transaction and forward the endorsement and cross-chain message together. The relay node can send it directly to the destination blockchain or, if necessary, forward it through multiple relay nodes before finally sending it to the destination blockchain.

[0085] When a supervisory node obtains a cross-chain transaction, in addition to performing corresponding supervisory operations, it also needs to push it to the supervisory system. The supervisory system can collect as many cross-chain transactions as possible, analyze them, generate supervisory instructions based on the analysis results, and complete the issuance of supervisory instructions, which is the function of post-supervision. Figure 3As shown in the figure, the content of regulatory instructions is encapsulated in the cross-chain system's universal cross-chain message format, reusing the system's cross-chain processes. Regulatory instructions are issued via relay nodes to the cross-chain contract on the corresponding blockchain, ultimately passing them to the regulatory contract. The regulatory contract updates and saves the regulatory rules, generating an event indicating the updated regulatory rules. After capturing the event, the relay node returns a regulatory receipt to the regulatory node, which confirms the proper issuance of the regulatory instructions. This reuse eliminates the need for the regulatory system to adapt to each blockchain type to issue regulatory instructions, further decoupling and reducing the burden on the regulatory system. Furthermore, when necessary, the regulatory system can choose to directly issue regulatory instructions to the blockchain or perform other post-event regulatory actions to update the regulatory contract and modify account status stored within the contract. Upon issuing regulatory instructions, the regulatory system can notify the administrator of the corresponding blockchain, who can then further manage the blockchain based on the results of the cross-chain regulatory analysis. For example, if a regulatory directive is related to a certain user address, the administrator can proactively query and analyze the historical transactions of the user address. If necessary, the user's assets can be frozen through smart contracts and other means, and relevant announcements can be issued in the community.

[0086] The full-chain cross-chain supervision mechanism designed in this key technical point is based on a loosely coupled cross-chain supervision architecture, leveraging its loosely coupled nature. In the basic cross-chain process, there is no supervisory contract. Application contracts on the blockchain interact directly with the cross-chain contract to complete the transfer of cross-chain transactions to the off-chain layer. In this framework, the supervisory contract, a special application contract provided by the system, intervenes between the application contract and the cross-chain contract, providing pre-emptive supervision at the start of cross-chain transactions. When a blockchain registers and uses the cross-chain system, both the supervisory contract and the cross-chain contract are deployed on the blockchain. To achieve this loose coupling, a SUPERVISOR_BUTTON value is set in the cross-chain contract. When the SUPERVISOR_BUTTON value is True, only the supervisory contract can call the cross-chain contract. This means that cross-chain transactions initiated by the application contract must be reviewed by the supervisory contract before the supervisory contract can pass the transaction on to the cross-chain contract. When the value is False, any application contract on the blockchain can call the cross-chain contract, bypassing the supervisory function of the supervisory contract and proceeding with the basic cross-chain process. The blockchain can apply to the relay node to use or suspend the cross-chain supervision function for this chain. The relay node modifies the SUPERVISOR_BUTTON value of the cross-chain contract of the chain based on the application result, thereby controlling whether the supervision contract is effective.

[0087] When a blockchain requests to a relay node to enable or suspend cross-chain supervision, the relay node also records the results of each connected blockchain's request. In this cross-chain supervision architecture, the supervisory system participates in the cross-chain process by voting as a member of the PTC committee. When a relay node receives a cross-chain transaction from a source chain and forwards it to a committee node, it determines whether the chain is using cross-chain supervision. If not, the cross-chain transaction is forwarded to the relevant committee node for verification according to the verification policy provided during the chain's registration. Otherwise, the transaction is additionally forwarded to the supervisory node. The supervisory node pushes the cross-chain transaction to the balancing system, completes the in-process supervision function, and returns the voting results. The relay node collects all voting results and continues the cross-chain process.

[0088] Therefore, the cross-chain supervision architecture and the corresponding cross-chain full-process supervision mechanism proposed in this invention can enable the cross-chain supervision function to reuse the basic cross-chain process in a convenient way while achieving full coverage of the cross-chain transaction links and minimizing the intrusion into the normal cross-chain process.

[0089] Key Technology Point 3: A unified cross-chain regulatory data package supporting multi-dimensional expansion. To overcome the drawbacks of the existing technologies, which focus on single regulatory operations, this key technology design incorporates a unified cross-chain regulatory data package supporting multi-dimensional expansion. This package clarifies the various regulatory operations of the regulatory system on the cross-chain system and supports the multi-dimensional expansion of on-chain regulatory rules, enabling the issuance of targeted regulatory instructions based on the characteristics of different business types and participating entities.

[0090]

[0091] Table 1 Definition of unified cross-chain regulatory data packet format

[0092] The format of the unified cross-chain supervision data packet is shown in Table 1 above. This data packet format, also known as the supervision instruction format, occurs during the post-supervision phase of cross-chain supervision. This data packet is encapsulated in a universal cross-chain data packet and sent by the supervision system, reusing the cross-chain system's cross-chain process. It is then sent via relay nodes to the cross-chain contract on the corresponding blockchain, and ultimately delivered to the supervision contract. The domain name is a unique field identifier assigned by the cross-chain system when a blockchain is connected to the cross-chain system. The cross-chain system uses the domain name to locate the sender and receiver of cross-chain transactions and forward transactions. The most important parameter in the protocol is supervisionType, which indicates the supervision type specified by the supervision instruction, thereby defining multi-dimensional supervision rules. Other parameters serve this purpose. Figure 4This section describes the specific design of the supervisionType parameter. This field uses a hierarchical coding design, where each main type identifies a supervision dimension, and each main type is divided into multiple subtypes. The length of the subtype field can be determined by the supervision system itself and the supervision contract before use. Assuming that the subtype occupies n bits, each main type has a total of 2 n Seed type. The specific meaning of the main type is defined by the regulatory system. For example, "blacklist" as a main type means that certain senders or receivers are not allowed to participate in cross-chain transactions initiated by a certain blockchain. Subtypes of this main type can include "prohibit a certain application contract of the sender from sending cross-chain transactions," "prohibit a certain application contract of the receiver from receiving cross-chain transactions sent by the current chain," "prohibit the sender from sending any cross-chain transactions to a certain receiver," etc. The main type can also be "transaction content review," etc., which can also be subdivided into multiple subtypes.

[0093] The hierarchical design of supervisionType maintains a small field length while enabling the definition of multi-dimensional supervision rules. The message design of the multi-dimensional supervision protocol also includes an Extra parameter. This parameter is not a specific parameter, but rather allows the supervision system to negotiate with the supervision contract before use to determine whether new parameters are required to complete supervision operations in the supervision rules, thereby extending the protocol.

[0094] like Figure 5 As shown, it shows the cross-chain supervision flow chart before and during the event. Figure 6 A flowchart of post-cross-chain supervision is shown.

[0095] The steps of the pre- and in-process cross-chain supervision process are described below. It is important to note that the present invention can monitor both blockchains involved in a cross-chain transaction simultaneously, or it can monitor only one of them. The following examples only use the example of monitoring two blockchains involved in a cross-chain transaction, but the present invention does not require that a supervision contract be deployed on both blockchains involved in a cross-chain transaction.

[0096] Step 1: Blockchain A and Blockchain B register and connect to the cross-chain system, obtain their own domain names, and relay nodes (such as servers, desktops, or other mobile terminals) deploy corresponding regulatory contracts and cross-chain contracts on both Blockchain A and Blockchain B.

[0097] The present invention has no restrictions on the type of blockchain being regulated. It can be a public blockchain like Ethereum, or a consortium blockchain like Ant Chain, Changan Chain, or FISCO BCOS. Therefore, the present invention is highly scalable and applicable.

[0098] The cross-chain system is designed to solve the problem that data and assets cannot directly interact between different blockchains. It uses protocols or tools to achieve information sharing and interoperability between chains. Examples include Cosmos and Polkadot, Ant Chain's Antchain Bridge, and WeBank's cross-chain platform WeCross.

[0099] The regulatory contract primarily consists of regulatory rules and corresponding review logic code. The regulatory contract receives and executes regulatory instructions issued by the regulatory system, which are embodied as regulatory rules stored in the regulatory contract. The review logic code, upon receiving the sender's cross-chain transaction, traverses the regulatory rules to conduct a transaction review. Together, these two functions fulfill the function of pre-emptive regulation.

[0100] Step 2: The application contract on blockchain A initiates a cross-chain transaction with another application contract on blockchain B. If blockchain A does not have cross-chain supervision enabled, proceed directly to step 3. Otherwise, the application contract calls the supervision contract to complete the pre-regulatory process. If the review passes, a supervision event is thrown indicating that the review has passed, and step 3 is executed. Otherwise, a supervision event indicating that the review has failed is thrown, and the cross-chain process terminates.

[0101] The specific review process must be based on regulatory instructions. For example, after the regulatory contract on A obtains the cross-chain transaction initiated by A, if the included regulatory rules include "prohibiting an application contract on a certain receiving blockchain from receiving cross-chain transactions sent by the current chain", the regulatory contract obtains the recipient blockchain domain name and recipient application contract address of the cross-chain transaction, and reviews them against the rule table. If the review is correct, the rule is passed. If all rules are reviewed and passed, the cross-chain transaction is qualified in terms of prior supervision; otherwise, it fails.

[0102] Step 3: The cross-chain transaction is executed via a cross-contract call to the cross-chain contract. The cross-chain contract processes and encapsulates the transaction and then throws a cross-chain event. After the relay node captures the cross-chain transaction, it determines whether cross-chain supervision is enabled based on the value of the SUPERVISOR_BUTTON parameter of the supervisory contract on each blockchain. It checks whether the initiator has enabled cross-chain supervision. If not, a verification request is sent to each ordinary node of the committee according to the verification strategy. If enabled, a supervision request is also sent to the supervisory node.

[0103] Among them, the committee in the cross-chain field is a group of nodes or entities responsible for coordinating cross-chain operations. They are usually given the power to verify, sign and execute cross-chain transactions to ensure that the exchange of data or assets between different blockchains is secure and effective.

[0104] Step 4: The relay node collects the signatures of the committee nodes that sent the verification or supervision request and verifies whether the valid signatures comply with the verification policy. If so, it constructs an endorsement and forwards it to blockchain B along with the cross-chain transaction, completing the cross-chain process. Otherwise, the cross-chain process terminates and the abnormal transaction is handled according to the cross-chain system's abnormal transaction handling mechanism. This concludes the pre- and in-process cross-chain supervision process.

[0105] The steps of the post-cross-chain supervision process are described below.

[0106] Step S1: After analyzing a large number of stored cross-chain transactions based on its own logic, the regulatory system examines the transactions and finds problems. It then generates regulatory instructions for these problems and sends them to the regulatory nodes. It also notifies the corresponding blockchain managers of the relevant regulatory results to facilitate further management.

[0107] Among them, there are problems with transactions such as replay attacks (the attacker repeatedly submits the cross-chain transaction message or proof, causing the target chain to release assets multiple times or perform repeated operations); a specific sender initiates a large number of small cross-chain transactions to the target chain in a short period of time, etc.

[0108] Step S2: After storing the supervision instruction, the supervision node transmits the message to the relay node.

[0109] Step S3: The relay node forwards the message to the chain by calling the cross-chain contract of the corresponding blockchain. The cross-chain contract continues to call the supervision contract and delivers the supervision instructions to the supervision contract.

[0110] Step S4: The regulatory contract updates the stored regulatory rules based on the regulatory instructions and throws a rule update event. The specific meaning of the regulatory rules is defined by the regulatory system. For example, the main type of "blacklist" can include subtypes such as "prohibit a certain application contract of the sender from sending cross-chain transactions." The main type can also be "transaction content review," and the corresponding subtype can be "prohibit sending cross-chain transactions containing a specific field in the transaction content."

[0111] Step S5: After the relay node captures the rule update event, it returns a supervision receipt to the supervision node. After this event, the cross-chain supervision process ends.

[0112] The following is a system embodiment corresponding to the above method embodiment. This embodiment can be implemented in conjunction with the above embodiment. The relevant technical details mentioned in the above embodiment are still valid in this embodiment and will not be repeated here to reduce repetition. Accordingly, the relevant technical details mentioned in this embodiment can also be applied to the above embodiment.

[0113] like Figure 8 As shown, the present invention also proposes a loosely coupled unified cross-chain supervision device that supports multi-dimensional expansion, including:

[0114] The initial module obtains registration and accesses a cross-chain system of multiple blockchains, at least one of which has a regulatory contract deployed;

[0115] The judgment module is used to determine whether the application contract of one blockchain A among the multiple blockchains initiates a cross-chain transaction to another blockchain B; and whether blockchain A has the supervision contract and has enabled cross-chain supervision. If so, the supervision module is executed;

[0116] Self-check module: The application contract calls the regulatory contract to determine whether the current cross-chain transaction complies with the regulatory contract. If so, a regulatory event indicating that the review is passed is thrown and the verification module is called. Otherwise, a regulatory event indicating that the review failed is thrown and the cross-chain transaction is terminated.

[0117] Verification module: The cross-chain transaction is executed to the cross-chain contract through a cross-contract call, and the cross-chain contract processes and encapsulates it to obtain a cross-chain event. After the relay node of the cross-chain system captures the cross-chain transaction, it checks whether blockchain A has enabled cross-chain supervision. If not, it sends a verification request to the node in the committee to obtain a verification result. The relay node of the cross-chain system decides whether to construct an endorsement and forward it to blockchain B together with the cross-chain transaction based on the verification request to complete the cross-chain process; if it is enabled, it sends a verification request to the node in the committee and a supervision request to the supervision node to obtain verification and supervision results respectively. The relay node of the cross-chain system decides whether to construct an endorsement and forward it to blockchain B together with the cross-chain transaction based on the verification request and the supervision request to complete the cross-chain process.

[0118] The loosely coupled unified cross-chain supervision device supporting multi-dimensional expansion includes:

[0119] In the update module, the regulatory system sends the regulatory instructions to the regulatory nodes in the committee. The regulatory nodes store and forward the regulatory instructions to the cross-chain system. The cross-chain system delivers the regulatory instructions to the regulatory contract. The regulatory contract updates the stored regulatory rules according to the regulatory instructions and throws a rule update event. After the cross-chain system captures the rule update event, it returns a regulatory receipt to the regulatory node.

[0120] The loosely coupled unified cross-chain supervision device supporting multi-dimensional extension, wherein the supervision instruction includes: supervision type, and / or sending chain domain name, and / or receiving chain domain name, and / or sender contract address, and / or receiver contract address, and / or transaction content, and / or custom extension fields;

[0121] The regulatory type field adopts a hierarchical coding design, where each main type identifies a regulatory dimension, and each main type is divided into multiple subtypes;

[0122] The supervision contract and supervision system are added to the cross-chain system in the form of plug-ins. A designated flag is set in the supervision contract, and whether to enable cross-chain supervision is determined according to the content of the flag, thereby decoupling the cross-chain supervision process from the basic cross-chain process. When cross-chain supervision is enabled, cross-chain transactions issued by the application contract must be reviewed by the supervision contract before the supervision contract can continue to pass the transaction to the cross-chain contract. When cross-chain supervision is turned off, any application contract on the blockchain can call the cross-chain contract.

[0123] like Figure 9 As shown, the present invention further proposes a first electronic device A in another embodiment, which includes the loosely coupled unified cross-chain supervision device that supports multi-dimensional expansion.

[0124] like Figure 10 As shown, the first electronic device A can also be connected to the data acquisition device C and the information display device D through a wired or wireless information transmission scheme. The data acquisition device C is used to collect and obtain cross-chain transactions, and the information display device D is used to display the verification and supervision results analyzed by the present invention.

[0125] The information display device D can organize and process the data output by the first electronic device A based on the information display mechanism to improve the readability of the data output by the first electronic device A. The information display mechanism can be manually preset, for example, the data output by the first electronic device A is visually displayed, which can be based on the display parameters and / or attributes set by the user. The display parameters can be, for example, the display data range, and the display attributes can be, for example, the display font, color, whether to scroll, etc. The user is presented with the key information specified by the user, and the user can understand this information more promptly without having to access the secondary page or scroll the page, saving the user's operation. Or the information display mechanism can be an artificial intelligence AI display model, which can learn the user's key information based on the user's previous usage habits, such as viewing time, number of clicks, number of edits, etc., and then automatically present the user with rich and necessary key information.

[0126] The present invention also provides a computer program product, which includes a computer program. The computer program can be stored on a readable storage medium. When the computer program is executed by a processor, the computer can execute the loosely coupled unified cross-chain supervision method that supports multi-dimensional expansion provided by the above methods.

[0127] In another embodiment, the present invention further proposes a storage medium VIII for storing a computer program for executing the loosely coupled unified cross-chain supervision method supporting multi-dimensional expansion. It should be understood that the storage medium in the embodiment of the present invention can be a volatile memory or a non-volatile memory, or can include both volatile and non-volatile memories. Among them, the non-volatile memory can be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory can be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of random access memory (RAM) are available, such as static RAM (SRAM), dynamic random access memory (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchronous link DRAM (SLDRAM), and direct RAM bus RAM (DR RAM).

[0128] Figure 11 A schematic block diagram of a second electronic device 1000 that can be used to implement an embodiment of the present invention is shown. The second electronic device 1000 electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The second electronic device 1000 can also represent various forms of mobile devices, such as personal digital assistants, cellular phones, smart phones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely examples and are not intended to limit the implementation of the present invention described and / or required herein. The second electronic device 1000 may be the same as or different from the first electronic device A.

[0129] Second electronic device 1000 includes a computing unit I, which can perform various appropriate actions and processes based on a computer program stored in a read-only memory (ROM) II or loaded from a storage medium VIII into a random access memory (RAM) III. RAM III may also store various programs and data required for the operation of device 1000. Computing unit I, ROM II, and RAM III are interconnected via a bus IV. An input / output (I / O) interface V is also connected to bus IV.

[0130] Multiple components in the second electronic device 1000 are connected to the I / O interface V, including: an input unit VI, such as a keyboard and mouse; an output unit VII, such as various types of displays and speakers; a storage medium VIII, such as a magnetic disk and optical disk; and a communication unit IX, such as a network card, a modem, a wireless communication transceiver, etc. The communication unit IX allows the second electronic device 1000 to exchange information / data with other devices via a computer network such as the Internet and / or various telecommunication networks.

[0131] Computing unit I can be various general-purpose and / or specialized processing components with processing and computing capabilities. Some examples of computing unit I include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various specialized artificial intelligence (AI) computing chips, various computing units running machine learning model algorithms, a digital signal processor (DSP), and any suitable processor, controller, microcontroller, etc. Computing unit I performs the various methods and processes described above, such as method steps S1-S4. For example, in some embodiments, the method can be implemented as a computer software program tangibly embodied on a machine-readable medium, such as storage medium VIII. In some embodiments, part or all of the computer program can be loaded and / or installed onto device 1000 via ROM II and / or communication unit IX. When the computer program is loaded into RAM III and executed by computing unit I, one or more steps of the method described above can be performed. Alternatively, in other embodiments, computing unit I can be configured to perform the method by any other suitable means (e.g., via firmware).

[0132] Although the embodiments of the present invention have been disclosed above, they are not limited to the applications listed in the description and implementation methods. They can be fully applied to various fields suitable for the present invention. For those familiar with the art, additional modifications can be easily implemented. Therefore, without departing from the general concept defined by the claims and the scope of equivalents, the present invention is not limited to the specific details and illustrations shown and described herein.

Claims

1. A loosely coupled unified cross-chain supervision method that supports multi-dimensional expansion, characterized by: include: The initial step is to obtain registration and access to a cross-chain system of multiple blockchains, at least one of which has a regulatory contract deployed; In a judgment step, an application contract of one blockchain A among the multiple blockchains initiates a cross-chain transaction to another blockchain B; a judgment is made as to whether blockchain A has the supervision contract and has enabled cross-chain supervision; if so, a supervision step is executed; In the self-check step, the application contract calls the regulatory contract to determine whether the current cross-chain transaction complies with the regulatory contract. If so, a regulatory event indicating that the review has passed is thrown and the verification step is executed. Otherwise, a regulatory event indicating that the review has failed is thrown and the cross-chain transaction is terminated. Verification step: The cross-chain transaction is executed to the cross-chain contract through a cross-contract call. The cross-chain contract processes and encapsulates the cross-chain event. After the relay node of the cross-chain system captures the cross-chain transaction, it checks whether blockchain A has enabled cross-chain supervision. If not, it sends a verification request to the node in the committee to obtain the verification result. The relay node of the cross-chain system decides whether to construct an endorsement and forward it to blockchain B together with the cross-chain transaction based on the verification request, completing the cross-chain process. If it is enabled, it sends a verification request to the node in the committee and a supervision request to the supervision node to obtain the verification and supervision results respectively. The relay node of the cross-chain system decides whether to construct an endorsement and forward it to blockchain B together with the cross-chain transaction based on the verification request and the supervision request, completing the cross-chain process. The supervision contract and supervision system are added to the cross-chain system in the form of plug-ins. A designated flag is set in the supervision contract, and whether to enable cross-chain supervision is determined according to the content of the flag, so as to decouple the cross-chain supervision process from the basic cross-chain process. When cross-chain supervision is enabled, cross-chain transactions issued by the application contract must be reviewed by the supervision contract before the supervision contract can continue to pass the transaction to the cross-chain contract. When cross-chain supervision is turned off, any application contract on the blockchain can call the cross-chain contract.

2. The loosely coupled unified cross-chain supervision method supporting multi-dimensional expansion according to claim 1 is characterized in that: include: In the update step, the regulatory system sends the regulatory instructions to the regulatory nodes in the committee. The regulatory nodes store and forward the regulatory instructions to the cross-chain system. The cross-chain system delivers the regulatory instructions to the regulatory contract. The regulatory contract updates the stored regulatory rules according to the regulatory instructions and throws a rule update event. After the cross-chain system captures the rule update event, it returns a regulatory receipt to the regulatory node.

3. The loosely coupled unified cross-chain supervision method supporting multi-dimensional expansion according to claim 2 is characterized in that: The supervision instruction includes: supervision type, and / or sending chain domain name, and / or receiving chain domain name, and / or sender contract address, and / or receiver contract address, and / or transaction content, and / or custom extension fields; Among them, the field of this regulatory type adopts a hierarchical coding design, each main type identifies a regulatory dimension, and each main type is divided into multiple subtypes.

4. A loosely coupled unified cross-chain supervision device supporting multi-dimensional expansion, characterized in that: include: The initial module obtains registration and accesses a cross-chain system of multiple blockchains, at least one of which has a regulatory contract deployed; The judgment module is used to determine whether the application contract of one blockchain A among the multiple blockchains initiates a cross-chain transaction to another blockchain B; and whether blockchain A has the supervision contract and has enabled cross-chain supervision. If so, the supervision module is executed; Self-check module: The application contract calls the regulatory contract to determine whether the current cross-chain transaction complies with the regulatory contract. If so, a regulatory event indicating that the review is passed is thrown and the verification module is called. Otherwise, a regulatory event indicating that the review failed is thrown and the cross-chain transaction is terminated. Verification module: The cross-chain transaction is executed to the cross-chain contract through a cross-contract call. The cross-chain contract processes and encapsulates the cross-chain event. After the relay node of the cross-chain system captures the cross-chain transaction, it checks whether blockchain A has enabled cross-chain supervision. If not, it sends a verification request to the committee node to obtain the verification result. The relay node of the cross-chain system decides whether to construct an endorsement and forward it to blockchain B together with the cross-chain transaction based on the verification request, completing the cross-chain process. If it is enabled, it sends a verification request to the committee node and a supervision request to the supervision node to obtain the verification and supervision results respectively. The relay node of the cross-chain system decides whether to construct an endorsement and forward it to blockchain B together with the cross-chain transaction based on the verification request and the supervision request, completing the cross-chain process. The supervision contract and supervision system are added to the cross-chain system in the form of plug-ins. A designated flag is set in the supervision contract, and whether to enable cross-chain supervision is determined according to the content of the flag, so as to decouple the cross-chain supervision process from the basic cross-chain process. When cross-chain supervision is enabled, cross-chain transactions issued by the application contract must be reviewed by the supervision contract before the supervision contract can continue to pass the transaction to the cross-chain contract. When cross-chain supervision is turned off, any application contract on the blockchain can call the cross-chain contract.

5. The loosely coupled unified cross-chain supervision device supporting multi-dimensional expansion according to claim 4, characterized in that: include: In the update module, the regulatory system sends the regulatory instructions to the regulatory nodes in the committee. The regulatory nodes store and forward the regulatory instructions to the cross-chain system. The cross-chain system delivers the regulatory instructions to the regulatory contract. The regulatory contract updates the stored regulatory rules according to the regulatory instructions and throws a rule update event. After the cross-chain system captures the rule update event, it returns a regulatory receipt to the regulatory node.

6. The loosely coupled unified cross-chain supervision device supporting multi-dimensional expansion according to claim 5, characterized in that: The supervision instruction includes: supervision type, and / or sending chain domain name, and / or receiving chain domain name, and / or sender contract address, and / or receiver contract address, and / or transaction content, and / or custom extension fields; Among them, the field of this regulatory type adopts a hierarchical coding design, each main type identifies a regulatory dimension, and each main type is divided into multiple subtypes.

7. An electronic device, characterized in that: It includes a loosely coupled unified cross-chain supervision device that supports multi-dimensional expansion as described in any one of claims 4-6, and the electronic device is connected to an information display device, which is used to display the verification and / or supervision results with display parameters and attributes set by the user or through an artificial intelligence model.

8. A computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps of the loosely coupled unified cross-chain supervision method supporting multi-dimensional expansion as described in any one of claims 1-3.

9. A computer program product comprising a computer program, characterized in that When the computer program is executed by a processor, the steps of the loosely coupled unified cross-chain supervision method supporting multi-dimensional expansion described in any one of claims 1-3 are implemented.

Images