A method for managing multiple blockchain underlying platforms

Abstract

A method for managing multiple blockchain underlying platforms, including analyzing the common functions of the external interfaces of different blockchain underlying platform software development kits (SDKs), determining the key points of managing multiple blockchain underlying platforms from the aspects of data reading and writing, application deployment, smart contract calls, and on-chain event monitoring; from the interface specifications that the blockchain underlying platforms need to follow, forming the standards for the management and intercommunication of multiple blockchain underlying platforms; for the data reading and writing, application deployment, smart contract calls, and on-chain event monitoring external interaction interfaces of the blockchain underlying platforms to be managed, modifying them according to the determined interface specifications; testing the connectivity of the interface adaptation and modification of the blockchain underlying platforms to be managed, and becoming one of the underlying platforms of the blockchain management platform; for other blockchain underlying platforms that need to be managed, realizing the adaptation and management of multiple blockchain underlying platforms. This method meets the flexible selection needs of multiple blockchain underlying platforms for blockchain applications in various regions and fields.

Description

Technical Field

[0001] The present invention belongs to the field of computer technology and relates to blockchain technology, and specifically is a method for managing multiple blockchain underlying platforms. Background Art

[0002] Blockchain technology is considered to be the cornerstone of the development of the digital economy. It has been widely used in digital finance, the Internet of Things, intelligent manufacturing, supply chain management, charitable donations, government services, social governance, item traceability, digital asset transactions and other fields, and has become an important tool for promoting high-quality development in various places. The underlying blockchain platform is regarded as the "operating system" of blockchain applications, providing basic environmental support such as encryption algorithms and consensus mechanisms for specific blockchain applications. Relevant domestic and foreign institutions have launched a number of underlying blockchain platforms. The underlying blockchain platforms have great differences in encryption algorithms, consensus mechanisms, and data structures, and their performance and efficiency have their own advantages, providing flexible and diverse choices for blockchain applications in various fields. At present, when promoting blockchain applications, various places generally adopt two ways to choose the underlying blockchain platform. One way is "one chain for multiple uses", that is, choosing a single underlying blockchain platform, and various fields build various "business chains" based on this platform; the other way is "multi-chain coexistence", allowing various fields to choose different underlying blockchain platforms to build their own "business chains". The problem with "one chain for multiple uses" is that blockchain technology has not yet converged, and no single underlying blockchain platform can cover everything, making it difficult to meet diverse business needs. Users are easily "technologically kidnapped" and "service monopolized" by a single technology service provider. The problem with "multiple chains coexisting" is that different underlying blockchain platform technologies are heterogeneous, and different blockchain applications are independent of each other and lack interoperability, which restricts large-scale cross-platform applications. In addition, the maintenance costs of multiple underlying blockchain platform technologies are high.

[0003] At present, the industry is mainly concerned about how to effectively exchange cross-chain data. Duan Tiantian et al. (Duan Tiantian, Zhang Hanwen, Li Bo, et al. A review of blockchain interoperability technology. Journal of Software, 2024, 35(02):800-827) comprehensively analyzed the progress of blockchain interoperability technology and summarized it into three key issues: cross-chain information transmission, cross-chain trust transfer, and cross-chain operation atomicity guarantee; Li Fang et al. (Li Fang, Li Zhuoran, Zhao He. Research on the progress of blockchain cross-chain technology. Journal of Software, 2019, 30(6):1649−1660) systematically summarized the research progress of 24 blockchain cross-chain technologies and pointed out that notary mechanism, side chain / relay, and hash lock are the main cross-chain interoperability technologies. The current cross-chain interoperability technology is mainly aimed at the needs of business application data intercommunication and trust transfer. It lacks standardized data interface communication technology similar to the current Internet, and then abstracts typical interoperability services to realize the management of different blockchain underlying platforms, providing a unified basic environment support for blockchain applications in different fields in various places. Summary of the invention

[0004] The purpose of the present invention is to provide a method for managing multiple blockchain underlying platforms to solve the problems faced by the existing promotion of blockchain applications in various places, such as insufficient diversity of "one chain for multiple uses" and insufficient compatibility of "multiple chains coexisting".

[0005] The technical problem to be solved by the present invention is: how to formulate the adaptation interface requirements of the blockchain underlying platform without changing the technical architecture of each blockchain underlying platform, provide a data, application, event and other interaction method common to multiple blockchain underlying platforms, and realize unified management of multiple blockchain underlying platforms.

[0006] The following technical solution implements: a method for managing multiple blockchain underlying platforms, including the following steps:

[0007] Step 1: Determine the key points of blockchain underlying platform management. Analyze the common functions of the external interfaces of different blockchain underlying platform software development kits (SDKs), combine the management requirements of multiple blockchain underlying platforms, and determine the key points of multiple blockchain underlying platform management from four aspects: data reading and writing, application deployment, smart contract calling, and on-chain event monitoring;

[0008] Step 2: Formulate the interface requirements for the underlying blockchain platform. Formulate the interface specifications that the underlying blockchain platform needs to follow from four aspects: data reading and writing, application deployment, smart contract calling, and on-chain event monitoring. Clarify the corresponding interface functions, input parameters, and output parameter requirements, and form a standard for the management and interoperability of multiple underlying blockchain platforms.

[0009] Step 3: Adapt and transform the external interface of the blockchain underlying platform. For the data reading and writing, application deployment, smart contract calling, and on-chain event monitoring external interaction interfaces of the blockchain underlying platform to be managed, adapt and transform them according to the interface specifications determined in step 2;

[0010] Step 4: Management, review and deployment of the blockchain underlying platform. Test the connectivity of the interface adaptation and transformation of the proposed blockchain underlying platform. After passing the test, it will be deployed online and become one of the underlying platforms of the blockchain management platform;

[0011] Step 5: Adapt and manage multiple blockchain underlying platforms. Repeat steps 3 and 4 for other blockchain underlying platforms that need to be managed to achieve the adaptation and management of multiple blockchain underlying platforms.

[0012] As a preferred embodiment of the present invention, the data read and write interface specification interface function includes a block acquisition interface and a transaction acquisition interface. The input parameter of the block acquisition interface is the block number, and the output parameter is the block information; the input parameter of the transaction acquisition interface is the transaction number, and the output parameter is the transaction information.

[0013] As a preferred embodiment of the present invention, the application deployment interface specification interface functions include creating an application chain interface, joining an application chain interface, and exiting an application chain interface. The input parameter for creating an application chain interface is the application chain configuration file, which is used to request the blockchain node to create an application chain, and there is no output parameter; the input parameter for joining the application chain interface is the application chain name, which is used for the blockchain node to join the application chain, and there is no output parameter; the input parameter for exiting the application chain interface is the application chain name, which is used for the blockchain node to exit the application chain, and there is no output parameter.

[0014] As a preferred embodiment of the present invention, the smart contract call interface specification interface functions include smart contract initialization, smart contract deployment, smart contract upgrade, and smart contract deletion. The input parameters of the smart contract initialization interface are the smart contract name and smart contract parameters, which are mainly used to initialize the deployed smart contract, and there are no output parameters; the input parameters of the smart contract deployment interface are the smart contract name and smart contract parameters, which are mainly used to deploy the smart contract to the blockchain node, and there are no output parameters; the input parameters of the smart contract upgrade interface are the smart contract name and smart contract parameters, which are mainly used to upgrade the smart contract on the blockchain node, and there are no output parameters; the input parameters of the smart contract deletion interface are the smart contract name, which are mainly used to delete the smart contract on the blockchain node, and there are no output parameters.

[0015] As a preferred embodiment of the present invention, the on-chain event monitoring interface specification interface functions include event registration, event query, and event deletion. The input parameter of the event registration interface is the event key, and the output parameter is the event code, which is used to register event callbacks and receive event notifications; the input parameter of the event query interface is the event code, which is used to query the registered chain code event monitoring list, and there is no output parameter; the input parameter of the event deletion interface is the event code, which is used to cancel the registered chain code event monitoring, and there is no output parameter.

[0016] The present invention has the following beneficial effects:

[0017] 1. By formulating the requirements for the adaptation interface of the underlying blockchain platform, a data interface communication standard for the management and intercommunication of multiple underlying blockchain platforms is established. Different underlying blockchain platforms can be uniformly managed after being adapted and transformed according to the interface requirements, meeting the flexible selection needs of multiple underlying blockchain platforms for blockchain applications in various regions and fields;

[0018] 2. For the adaptation and transformation of the underlying blockchain platform under management, it is only necessary to implement the core interface encapsulation such as data reading and writing, application deployment, smart contract calling, and on-chain event monitoring based on its original SDK. There is no need to make penetration modifications to the original underlying blockchain platform, and it does not change the upper-layer application service mode and user chain usage habits. It supports the smooth migration of independent "business chains" developed using the original underlying blockchain platform;

[0019] 3. By managing multiple blockchain underlying platforms and unifying interface standards, developers do not need to write specific logic for each different blockchain underlying platform, which reduces development duplication and effectively reduces the technical difficulty and cost of maintaining multiple blockchain underlying platforms. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] Figure 1 It is a flow chart of the method for managing multiple blockchain underlying platforms in the present invention;

[0021] Figure 2 It is a schematic diagram of the connection relationship of applications enabled by the blockchain management platform according to an embodiment of the present invention. DETAILED DESCRIPTION

[0022] The following takes the management of the two blockchain underlying platforms FISCO BCOS and XuperChain as examples to further explain the technical solution in the embodiments of the present invention in detail.

[0023] FISCO BCOS is a stable, efficient and secure blockchain underlying platform, developed by the Golden Chain Alliance led by WeBank. It adopts the technical architecture of the alliance chain, integrates and absorbs distributed architecture, distributed storage, peer-to-peer network protocol, encryption algorithm, consensus algorithm, smart contract and virtual machine and other technologies, with the advantages of high performance, security and controllability, and rich functions. It has been widely used in finance, medical care, education, culture, social governance and other fields, and has become an important blockchain underlying framework for promoting blockchain applications in various fields. XuperChain is a blockchain underlying platform independently developed by Baidu, providing multi-component and customized development services, supporting global deployment and intra-chain parallelism, providing users with an environment for rapid deployment and operation of blockchain applications, and flexible payment capabilities for computing and storage resources. It has been applied to multiple fields such as justice, government affairs, education, and traceability. It is a blockchain operating system for enterprise development and user use.

[0024] This embodiment will use the present invention to manage the two blockchain underlying platforms FISCO BCOS and XuperChain. The specific workflow is as follows: Figure 1 As shown:

[0025] Step 1: Determine the key points of blockchain underlying platform management. Analyze the common functions of the external interfaces of different blockchain underlying platform software development kits (SDKs), combine the management requirements of multiple blockchain underlying platforms, and determine the key points of multiple blockchain underlying platform management from four aspects: data reading and writing, application deployment, smart contract calling, and on-chain event monitoring.

[0026] The present invention provides a method for managing multiple blockchain underlying platforms. The compatibility and diversity of technology are the primary considerations, and the mainstream blockchain underlying platform should be adapted and managed. Here, the main external interface functions of the SDK of mainstream blockchain underlying platforms such as FISCO BCOS, XuperChain, Fabric, CITA, Wutong Chain, Brochain, etc. are analyzed, as shown in Table 1. Among them, data reading and writing, application deployment, smart contract calling, and on-chain event monitoring are SDK external interface functions supported by all the listed mainstream blockchain underlying platforms, while channels, side chains, and groups are only provided by some blockchain underlying platform SDK external interface functions. From the perspective of the management requirements of multiple blockchain underlying platforms, data reading and writing, application deployment, and smart contract calling are conventional operations of the blockchain underlying platform, which are core requirements. On-chain event monitoring allows applications to respond accordingly when specific events occur on the blockchain, which can improve the flexibility of blockchain underlying platform management. Therefore, the four functions of data reading and writing, application deployment, smart contract calling, and on-chain event monitoring can meet the management requirements of multiple blockchain underlying platforms, and are determined to be the key points of the management of the blockchain underlying platform of the present invention.

[0027] Table 1

[0028]

[0029] Step 2: Formulate the interface requirements for the underlying blockchain platform. Formulate the interface specifications that the underlying blockchain platform needs to follow from four aspects: data reading and writing, application deployment, smart contract calling, and on-chain event monitoring. Clarify the corresponding interface functions, input parameters, and output parameter requirements to form a standard for the management and interoperability of multiple underlying blockchain platforms.

[0030] As a preferred implementation of the present invention, the data reading and writing, application deployment, smart contract calling, and on-chain event monitoring interface methods are clarified, including interface functions, input parameters, output parameters, interface functions, and parameter descriptions, as shown in Table 2.

[0031] Table 2

[0032]

[0033]

[0034] ·Data read and write interface specification interface functions include block acquisition interface and transaction acquisition interface. The input parameter of the block acquisition interface is the block number, and the output parameter is the block information; the input parameter of the transaction acquisition interface is the transaction number, and the output parameter is the transaction information. Taking the acquisition of XuperChain block interface as an example, the blockchain management platform sends a communication request to the XuperChain blockchain node by calling the getBlockInfo function and carrying the block number as a parameter. After receiving the request, the XuperChain blockchain node searches for the locally stored blockchain data and locates the specified block number; if the corresponding block is found, all the information of the block is returned; if not found, an error message is returned.

[0035] ·Application deployment interface specification interface functions include generating application chain creation interface, application chain joining interface and application chain exit interface. The input parameter of application chain creation interface is the application chain configuration file, which is used to request the blockchain node to create an application chain, and there is no output parameter; the input parameter of application chain joining interface is the application chain name, which is used for the blockchain node to join the application chain, and there is no output parameter; the input parameter of application chain exit interface is the application chain name, which is used for the blockchain node to exit the application chain, and there is no output parameter. Taking the creation of XuperChain application chain interface as an example, the blockchain management platform sends a communication request containing the application chain configuration file to the XuperChain blockchain node by calling the newAppChain function. After receiving the request, the XuperChain blockchain node parses the configuration file and creates a new application chain according to the configuration. After successful creation, the node updates the internal status and broadcasts this event to other nodes.

[0036] ·Smart contract call interface specification interface functions include smart contract initialization, smart contract deployment, smart contract upgrade, and smart contract deletion. The input parameters of the smart contract initialization interface are the smart contract name and smart contract parameters, which are mainly used to initialize the deployed smart contract, and there are no output parameters; the input parameters of the smart contract deployment interface are the smart contract name and smart contract parameters, which are mainly used to deploy the smart contract to the blockchain node, and there are no output parameters; the input parameters of the smart contract upgrade interface are the smart contract name and smart contract parameters, which are mainly used to upgrade the smart contract on the blockchain node, and there are no output parameters; the input parameters of the smart contract deletion interface are the smart contract name, which are mainly used to delete the smart contract on the blockchain node, and there are no output parameters. Taking XuperChain smart contract deployment as an example, the blockchain management platform sends a communication request containing the smart contract name and smart contract information to the XuperChain blockchain node by calling the InstallChaincode function. After receiving the request, the XuperChain blockchain node checks whether the smart contract chain code is initialized, adds the smart contract chain code to the specified channel, and instantiates the smart contract chain code.

[0037] ·On-chain event listening interface specification interface functions include event registration, event query, and event deletion. The input parameter of the event registration interface is the event key, and the output parameter is the event code, which is used to register event callbacks and receive event notifications; the input parameter of the event query interface is the event code, which is used to query the registered chain code event listening list, and there is no output parameter; the input parameter of the event deletion interface is the event code, which is used to cancel the registered chain code event listening, and there is no output parameter. Taking the XuperChain event registration interface as an example, the blockchain management platform sends a communication request containing the event key to the XuperChain blockchain node by calling the eventRegister function. After receiving the request, the XuperChain blockchain node registers an event listener and returns a unique event code. When an event occurs, the blockchain node will use the event code to send a notification to the caller.

[0038] Step 3: Adapt and transform the external interface of the underlying blockchain platform. The data reading and writing, application deployment, smart contract calling, and on-chain event monitoring external interaction interfaces of the underlying blockchain platform to be managed are adapted and transformed according to the interface specifications determined in step 2.

[0039] For this embodiment, the underlying blockchain platforms to be managed include FISCO BCOS and XuperChain. Here we focus on the adaptation and transformation process of FISCO BCOS's data reading and writing, application deployment, smart contract calling, and on-chain event monitoring external interaction interfaces according to the interface standards specified in Table 2.

[0040] In terms of data read and write interface adaptation, it is necessary to make corresponding modifications to the differences between the original interface design of FISCO BCOS and the interface specification proposed by the present invention. The original interface of FISCO BCOS provides the function of reading blocks and transaction information, but there are inconsistencies between its interface design and the interface specification required by the embodiment of the present invention. Taking the block information interface modification as an example, the original interface of FISCO BCOS only accepts one block height parameter, and the block interface specification of this embodiment requires the return of the block hash value. In order to enable FISCO BCOS to be managed, the incoming block hash is converted to the block height, and the original interface function GetBolckInfoByBlockHeight() of FISCO BCOS is called to obtain the block height data, and then the returned result is converted into the correct format output according to the data read and write interface specification. Similarly, the acquisition transaction interface is further adapted and modified. Through the above modification, the data read and write interface of FISCO BCOS can be smoothly connected to the blockchain management platform to achieve unified management and access of data reading and writing.

[0041] In terms of application deployment interface adaptation, the goal is to ensure that different blockchain underlying platforms can deploy and manage applications through a unified interface. This process involves converting the application deployment interface specification of this embodiment with the interface specific to each blockchain underlying platform in order to achieve a standardized deployment process. For FISCO BCOS, the application deployment interface adaptation converts the application deployment information into the group information of the FISCO BCOS underlying chain to ensure that the application can run on the nodes of FISCO BCOS.

[0042] Specifically, the FISCO BCOS application deployment interface adaptation is achieved through the following methods:

[0043] 1. Create an application chain interface: Enter the application chain configuration file and convert the request into a FISCO BCOS creation command to create an application chain on the blockchain. First, create a new application chain on all nodes of each participating organization by calling the underlying new application chain interface; second, use the underlying control application chain status interface and set the type=start parameter to start the application chain of each node under each organization to ensure its normal operation; finally, add at least one administrator user to each organization by calling the underlying new application chain administrator user interface to grant them the authority to manage the application chain. This series of operations ensures the successful establishment and effective management of the application chain.

[0044] 2. Join the application chain interface: Enter the application chain name and convert this information into a FISCO BCOS join command so that the blockchain node can join the application chain. First, create a new node by calling the new application chain interface and filling in the new node information in the nodeId field; secondly, use the control application chain status interface and set the type=start parameter and nodeId to the new node information to start the application chain state of the new node; finally, call the node consensus state management interface twice to set the consensus state of the new node. In the first call, nodeId is set to the new node, reqNodeId is set to the consensus node of the application chain, and nodeType is set to observer. In the second call, nodeId is also set to the new node, reqNodeId is set to the consensus node of the application chain, and nodeType is changed to sealer. This series of operations ensures that the new node can successfully join the application chain and participate in the consensus process.

[0045] 3. Exit application chain interface: Enter the application chain name, convert the request into an exit command, and allow the blockchain node to exit the application chain. First, stop the application chain status of all nodes under each organization by calling the underlying control application chain status interface and setting the type=stop parameter; secondly, call the underlying control application chain status interface again and set the type=remove parameter to remove the application chain; finally, notify the deletion of the group ledger file under each relevant node. These steps ensure a thorough cleanup from the application layer to the data layer, so that the exit or deletion operation of the group can be completed smoothly.

[0046] In terms of smart contract call interface adaptation, the goal is to ensure that smart contracts on different blockchain underlying platforms can be called and managed through the same interface, while supporting flexible parameter configuration. The smart contract call interface adaptation content of FISCO BCOS is as follows:

[0047] 1. Smart contract initialization interface: call the underlying initialization interface, pass in the smart contract name and smart contract parameters to initialize the contract. The initialization of the smart contract only needs to be executed once and can be executed on any node.

[0048] 2. Smart contract deployment interface, first, compile the contract by calling the underlying contract compilation interface to ensure that the contract code is correct and converted into an executable format; second, use the underlying contract saving interface to save or update the compiled contract so that the organization of the newly added user can call it; finally, call the underlying contract deployment interface to deploy the contract, package the smart contract name, smart contract parameters and related codes into the standard format of the FISCO BCOS underlying contract deployment package, and then request to efficiently deploy the smart contract to the FISCO BCOS node.

[0049] 3. The smart contract upgrade interface is similar to the deployment process. First, the contract is compiled by calling the underlying contract compilation interface to ensure that the contract code is correct and converted into an executable format; second, the underlying contract saving interface is used to save or update the compiled contract so that the organization of the newly added user can call it; finally, the underlying contract deployment interface is called to deploy the contract, and the smart contract name, parameters and related codes are packaged into a deployment package format that complies with the FISCO BCOS standard, so as to efficiently deploy the smart contract to the FISCO BCOS node. This process ensures the smooth progress of smart contracts from development to launch, so that the organization of the newly added user can effectively use and manage these contracts.

[0050] 4. Smart contract deletion interface, calling the self-destruction contract on the chain is implemented by calling the selfdestruct function, which deletes the contract code and storage, releases network resources, and removes the smart contract on the blockchain node.

[0051] Through these adaptation measures, the smart contract call interface adaptation ensures that smart contracts can maintain consistent behavior on the FISCO BCOS blockchain underlying platform, while also simplifying the work of developers and improving the interoperability and portability of cross-chain smart contracts.

[0052] In terms of on-chain event monitoring interface adaptation, the native event monitoring mechanism of FISCO BCOS needs to be adapted to comply with the interface specifications defined in this embodiment. This adaptation process is intended to ensure that the on-chain event monitoring function of the underlying platform of the FISCO BCOS blockchain can interact under a unified interface specification, thereby achieving cross-chain event monitoring and management. FISCO BCOS natively supports on-chain event monitoring, but its interface design differs from the interface specifications of this embodiment. The adaptation work mainly includes:

[0053] 1. Interface naming and parameter adjustment: Adjust the naming of the on-chain event monitoring interface of FISCO BCOS to make it conform to the interface specification of Table 2. At the same time, adjust the parameter structure to match the definition of parameter type in the interface specification of this embodiment.

[0054] 2. Event registration: The event registration interface of FISCO BCOS needs to be able to receive the event key as input and return the event code. The adaptation work needs to ensure that the mapping relationship between the event key and the event code is correct, and that the event registration can be completed through the interface of FISCOBCOS. When the event is triggered, the system will send the event content to the registered notification address. The user needs to provide the event type (eventType), the value of 1 indicates a block event, and the value of 2 indicates a contract event. When a block event is selected, the contract address (contractAddress) and the contract name (contractName) can be empty; if a contract event is selected, the contract address and contract name cannot be empty at the same time. In addition, the user must provide a notification address (notifyUrl) to receive event notifications.

[0055] 3. Event query and deletion: Ensure that the event query and deletion interface of FISCO BCOS can be executed according to the interface specification of this embodiment, that is, query or delete the corresponding on-chain event listener through event coding.

[0056] Similarly, the same method is used to adapt and transform XuperChain's data reading and writing, application deployment, smart contract calling, and on-chain event monitoring external interfaces, which will not be repeated here.

[0057] Step 4: Management, review and deployment of the blockchain underlying platform. Test the connectivity of the interface adaptation and transformation of the proposed blockchain underlying platform, and deploy it online after passing the test, becoming one of the underlying platforms of the blockchain management platform.

[0058] For this embodiment, it is necessary to test the connectivity of the interface adaptation and transformation of the two blockchain underlying platforms FISCO BCOS and XuperChain in turn according to the interface standards specified in Table 2. In terms of data reading and writing interface testing, the focus is on testing the functions of obtaining block and transaction information, including normal acquisition, error handling and timeout. In terms of application deployment interface testing, the focus is on testing the creation, joining and exit processes of the application chain, including the flexibility and security of parameter configuration. In terms of smart contract call interface testing, the focus is on testing the deployment, initialization, upgrade and deletion of smart contracts to ensure that all operations are executed as expected. In terms of on-chain event monitoring interface testing, the focus is on testing the registration, query and deletion functions of events to ensure the accuracy and timeliness of event notifications. If the above tests are successfully passed, that is, all interface functions can work normally according to the interface specification description, the input parameters are correctly processed, and the output parameters are consistent with the interface specification, then FISCO BCOS and XuperChain can be deployed online to the blockchain management platform.

[0059] Step 5: Adaptation and management of multiple blockchain underlying platforms. In this embodiment, the adaptation and management of the two blockchain underlying platforms FISCO BCOS and XuperChain were carried out. For other blockchain underlying platforms that need to be managed, repeat steps 3 and 4 to achieve the adaptation and management of multiple blockchain underlying platforms. The blockchain underlying platforms after adaptation and management are uniformly managed and monitored by the blockchain management platform, and the blockchain management platform is used to empower blockchain applications in government affairs, finance, traceability, medical care, and evidence storage. The connection relationship is as follows: Figure 2 shown.

[0060] In general, the present invention provides a method for managing multiple blockchain underlying platforms. By analyzing the common functions of the external interfaces of different blockchain underlying platform SDKs and combining the actual management needs, a unified interface specification is formulated from four aspects: data reading and writing, application deployment, smart contract calling, and on-chain event monitoring. The data interface requirements thus formed enable each blockchain underlying platform to be adapted and transformed without changing its own technical architecture, thereby achieving unified management and interconnection between different blockchain underlying platforms. This approach not only meets the needs of various regions and fields for flexible selection of blockchain underlying platforms, but also avoids the problems of "technical kidnapping" and service monopoly that may be brought about by a single technical service provider, and also overcomes the problems of poor cross-platform interoperability and high technical maintenance costs in the "multi-chain coexistence" mode. The technical means of the present invention ensure that applications developed based on the original blockchain underlying platform can be smoothly migrated, and significantly reduce the complexity and cost of development and maintenance, and improve the flexibility and interoperability of the blockchain ecosystem.

[0061] The above embodiments are only for illustrating the technical idea of ​​the present invention, and cannot be used to limit the protection scope of the present invention. Any changes made on the basis of the technical solution in accordance with the technical idea proposed by the present invention shall fall within the protection scope of the present invention.

Claims

1. A method for managing multiple blockchain underlying platforms, characterized in that: The steps include: Step 1: Determine the key points of blockchain underlying platform management: Analyze the common functions of the external interfaces of different blockchain underlying platform software development toolkits, combine the management requirements of multiple blockchain underlying platforms, and determine the key points of multiple blockchain underlying platform management from four aspects: data reading and writing, application deployment, smart contract calling, and on-chain event monitoring; Step 2: Formulate the interface requirements for the underlying blockchain platform: formulate the interface specifications that the underlying blockchain platform needs to follow from the above four aspects, clarify the corresponding interface functions, input parameters and output parameter requirements, and form the standards for the management and interoperability of multiple underlying blockchain platforms; Step 3: Adapt and transform the external interfaces of the underlying blockchain platform: Adapt and transform the external interaction interfaces of the four aspects of the underlying blockchain platform to be managed according to the interface specifications determined in step 2; Step 4: Management review and deployment of the blockchain underlying platform: Test the connectivity of the interface adaptation and transformation of the proposed blockchain underlying platform. After passing the test, it will be deployed online and become one of the underlying platforms of the blockchain management platform. Step 5: Adapt and manage multiple blockchain underlying platforms: For other blockchain underlying platforms that need to be managed, repeat steps 3 and 4 to achieve the adaptation and management of multiple blockchain underlying platforms.

2. The method for managing multiple blockchain underlying platforms as claimed in claim 1, characterized in that: The interface functions of the data reading and writing interface specifications include the block acquisition interface and the transaction acquisition interface: the block acquisition interface input parameter is the block number, and the output parameter is the block information; the transaction acquisition interface input parameter is the transaction number, and the output parameter is the transaction information.

3. The method for managing multiple blockchain underlying platforms as claimed in claim 1, characterized in that: Interface specification for application deployment. Interface functions include creating an application chain interface, joining an application chain interface, and exiting an application chain interface. The input parameter for creating an application chain interface is the application chain configuration file, which is used to request the blockchain node to create an application chain, and there is no output parameter. The input parameter for joining the application chain interface is the application chain name, which is used for the blockchain node to join the application chain, and there is no output parameter. The input parameter for exiting the application chain interface is the application chain name, which is used for the blockchain node to exit the application chain, and there is no output parameter.

4. The method for managing multiple blockchain underlying platforms as claimed in claim 1, characterized in that: The interface functions of smart contract calls include smart contract initialization, smart contract deployment, smart contract upgrade, and smart contract deletion; the input parameters of the smart contract initialization interface are the smart contract name and smart contract parameters, which are used to initialize the deployed smart contract, and there are no output parameters; the input parameters of the smart contract deployment interface are the smart contract name and smart contract parameters, which are used to deploy the smart contract to the blockchain node, and there are no output parameters; the input parameters of the smart contract upgrade interface are the smart contract name and smart contract parameters, which are used to upgrade the smart contract on the blockchain node, and there are no output parameters; The input parameter of the smart contract deletion interface is the smart contract name, which is used to delete the smart contract on the blockchain node. There is no output parameter.

5. The method for managing multiple blockchain underlying platforms as claimed in claim 1, characterized in that: Interface specification for on-chain event monitoring The interface functions include event registration, event query, and event deletion; the input parameter of the event registration interface is the event key, and the output parameter is the event code, which is used to register event callbacks and receive event notifications; The input parameter of the event query interface is the event code, which is used to query the list of registered chaincode event listeners and has no output parameters. The input parameter of the event deletion interface is the event code, which is used to cancel the registered chaincode event listener and has no output parameters.

Images