Data processing method and device for block chain framework and program product

Abstract

The invention discloses a data processing method and device for a block chain framework and a program product. Relates to the field of block chains, and the method comprises the steps that a management demand of to-be-managed data is acquired, a target management demand is obtained, the to-be-managed data comprises to-be-managed data in a block chain bottom chain framework, the block chain bottom chain framework is a multi-layer framework, and the multi-layer framework comprises a data layer, a network layer, a consensus layer, an excitation layer, a contract layer and an application layer; the data layer comprises a zero-knowledge proof strategy and a homomorphic encryption strategy, the consensus layer comprises a hybrid consensus mechanism, and the excitation layer comprises a consensus node reward mechanism; based on the target management demand, a to-be-managed layer is determined, and the to-be-managed layer comprises at least one layer of architecture in the multi-layer architecture; and processing the to-be-managed data by using the to-be-managed layer based on the target management demand. Through the method and the device, the problems that data management of a block chain bottom chain framework depends on manual intervention and the data management complexity is high in the prior art are solved.

Description

Technical Field

[0001] This application relates to the field of blockchain, and more specifically, to a data processing method, apparatus, and program product for a blockchain framework. Background Technology

[0002] With the rapid development of blockchain technology, its application in finance, government affairs, supply chain and other fields is becoming increasingly in-depth, which puts forward higher requirements for the regulatory compliance, controllability and security of the underlying blockchain architecture.

[0003] Currently, while the blockchain underlying framework has gradually formed some conventional methods in terms of regulatory technology, there are still many technical defects in key layers such as the data layer, network layer, consensus layer, incentive layer, contract layer, and application layer, making it difficult to meet the needs of high security, high reliability, and automated regulation.

[0004] In related technologies, the basic blockchain architecture only provides basic functional descriptions for each layer. Each layer operates independently and lacks a unified anomaly detection and automatic response mechanism. If a problem occurs, manual troubleshooting is required layer by layer, resulting in extremely low anomaly response efficiency. In other words, the blockchain architecture in related technologies suffers from a lack of coordination mechanisms between layers, and the process of supervising data at each layer of the blockchain relies heavily on manual intervention, making it difficult to achieve efficient, intelligent, and reliable blockchain supervision.

[0005] There is currently no effective solution to the problem that data management in the underlying blockchain framework relies on manual intervention and is highly complex. Summary of the Invention

[0006] The main purpose of this application is to provide a data processing method, device, and program product for a blockchain framework, so as to solve the problem that data management of the blockchain bottom chain framework relies on manual intervention and has high data management complexity in related technologies.

[0007] To achieve the above objectives, according to one aspect of this application, a data processing method for a blockchain framework is provided. The method includes: obtaining management requirements for data to be managed, thus obtaining target management requirements, wherein the data to be managed includes data to be managed within a blockchain bottom-chain framework, the blockchain bottom-chain framework being a multi-layered architecture, the multi-layered architecture including: a data layer, a network layer, a consensus layer, an incentive layer, a contract layer, and an application layer, the data layer including: a zero-knowledge proof strategy and a homomorphic encryption strategy, the consensus layer including: a hybrid consensus mechanism, the incentive layer including: a reward mechanism for consensus nodes, and the contract layer including: smart contracts; determining a management layer to be managed based on the target management requirements, wherein the management layer to be managed includes: at least one layer of the multi-layered architecture; and processing the data to be managed using the management layer to be managed based on the target management requirements.

[0008] Further, the target management requirements include at least one of the following: data encryption and storage requirements, data verification and security analysis requirements, and data traceability requirements. The layer to be managed is the data layer. Based on the target management requirements, the data to be managed is processed using the layer to be managed, including: when the target management requirements include the data encryption and storage requirements, encrypting the data to be managed using the zero-knowledge proof strategy and the homomorphic encryption strategy to obtain encrypted data to be managed, and storing the encrypted data to be managed; when the target management requirements include the data verification and security analysis requirements, verifying and performing security analysis on the target encrypted data based on the zero-knowledge proof strategy, wherein the target encrypted data includes at least one of the following: encrypted data already stored in the data layer, and the encrypted data to be managed; when the target management requirements include the data traceability requirements, adding an identifier and a timestamp to the data to be managed, and recording the data flow of the data to be managed based on the identifier and the timestamp.

[0009] Furthermore, the target management requirements include: the data management requirements of the network layer; the management layer to be managed includes: the network layer; the data to be managed includes: preset parameters of the network layer; based on the target management requirements, the management layer to be managed processes the data to be managed, including: obtaining parameter values ​​of the preset parameters of the network layer to obtain a parameter set, wherein the preset parameters include at least one of the following: network traffic, connection status of nodes in the network layer, and communication latency; determining whether the parameter values ​​in the parameter set meet preset adjustment conditions to obtain a determination result; and adjusting the network protocol and communication mechanism used by the network layer when the determination result indicates that the parameter values ​​in the parameter set meet the preset adjustment conditions.

[0010] Further, the target management requirements include: the consensus processing requirements of the consensus layer, which include at least one of the following: consensus strategy selection requirements, data acquisition requirements, consensus node evaluation requirements, and consensus strategy adjustment requirements. The management layer includes: the consensus layer, which, based on the target management requirements, processes the data to be managed using the management layer, including: when the target management requirements include the consensus strategy selection requirements, selecting a consensus strategy in the hybrid consensus mechanism based on the target management requirements; when the target management requirements include the data acquisition requirements, determining the consensus nodes for the data to be acquired based on the data to be managed, obtaining multiple first consensus nodes, and acquiring the consensus nodes for each... The document describes the node consensus results of the first consensus nodes and the voting data of each first consensus node; when the target management requirement includes the evaluation requirement, based on the data to be managed, consensus nodes whose credibility needs to be evaluated are determined, resulting in multiple second consensus nodes. Based on the behavioral data of each second consensus node, a preset evaluation model is used to evaluate the credibility of the second consensus node, and an evaluation result is obtained. The behavioral data includes at least one of the following: node consensus results and voting data; when the target management requirement includes the consensus strategy adjustment requirement, based on the data to be managed, consensus nodes whose consensus strategies need to be adjusted are determined, resulting in multiple third consensus nodes, and the consensus strategy of each third consensus node is adjusted.

[0011] Furthermore, the target management requirements include: the management requirements of the incentive layer, and the management layer to be managed includes: the incentive layer. Based on the target management requirements, the management layer to be managed processes the data to be managed, including: based on the data to be managed, determining the consensus nodes to be managed by the incentive layer to obtain multiple fourth consensus nodes; obtaining the credibility assessment result of each fourth consensus node; based on the credibility assessment result of each fourth consensus node, scoring the behavioral data of each fourth consensus node to obtain a score value for each fourth consensus node; and based on the score value of each fourth consensus node, distributing a reward to each fourth consensus node using the reward mechanism.

[0012] Furthermore, the target management requirements include: the lifecycle management requirements of the contract layer and the application layer; the data to be managed includes: the smart contract; the management layer includes: the contract layer and the application layer; based on the target management requirements, the management layer processes the data to be managed, including: if the blockchain underlying framework reaches a first preset period at the current moment, then the smart contract is tested; if the blockchain underlying framework reaches a second preset period at the current moment, then the smart contract is upgraded.

[0013] Furthermore, the target management requirement includes the requirement for cross-layer management of the multi-layer architecture, and the data to be managed includes the operational status data of the multi-layer architecture. Based on the target management requirement, the data to be managed is processed by the management layer, including: collecting operational status data of each layer in the multi-layer architecture; performing anomaly detection on the operational status data to obtain detection results, and adjusting the multi-layer architecture based on the detection results.

[0014] To achieve the above objectives, according to another aspect of this application, a data processing apparatus for a blockchain framework is provided. The apparatus includes: an acquisition unit, configured to acquire management requirements for data to be managed, thereby obtaining target management requirements, wherein the data to be managed includes data to be managed within a blockchain underlying framework, the blockchain underlying framework being a multi-layered architecture, the multi-layered architecture including: a data layer, a network layer, a consensus layer, an incentive layer, a contract layer, and an application layer, the data layer including: a zero-knowledge proof strategy and a homomorphic encryption strategy, the consensus layer including: a hybrid consensus mechanism, the incentive layer including: a reward mechanism for consensus nodes, and the contract layer including: smart contracts; a determination unit, configured to determine a management layer to be managed based on the target management requirements, wherein the management layer to be managed includes: at least one layer of the multi-layered architecture; and a processing unit, configured to process the data to be managed using the management layer to be managed based on the target management requirements.

[0015] Further, the target management requirements include at least one of the following: data encryption and storage requirements, data verification and security analysis requirements, and data traceability requirements. The management layer to be managed is the data layer. The processing unit includes: a first processing subunit, used to encrypt the data to be managed using the zero-knowledge proof strategy and homomorphic encryption strategy when the target management requirements include the data encryption and storage requirements, to obtain encrypted data to be managed, and to store the encrypted data to be managed; a second processing subunit, used to verify and perform security analysis on the target encrypted data based on the zero-knowledge proof strategy when the target management requirements include the data verification and security analysis requirements, wherein the target encrypted data includes at least one of the following: encrypted data already stored in the data layer, and the encrypted data to be managed; a third processing subunit, used to add an identifier and a timestamp to the data to be managed when the target management requirements include the data traceability requirements, and to record the data flow of the data to be managed based on the identifier and the timestamp.

[0016] Furthermore, the target management requirements include: the data management requirements of the network layer; the management layer to be managed includes: the network layer; the data to be managed includes: preset parameters of the network layer; the processing unit further includes: a first acquisition subunit, used to acquire the parameter values ​​of the preset parameters of the network layer to obtain a parameter set, wherein the preset parameters include at least one of the following: network traffic, connection status of nodes in the network layer, and communication latency; a judgment subunit, used to judge whether the parameter values ​​in the parameter set meet preset adjustment conditions to obtain a judgment result; and an adjustment subunit, used to adjust the network protocol and communication mechanism used by the network layer when the judgment result indicates that the parameter values ​​in the parameter set meet the preset adjustment conditions.

[0017] Further, the target management requirements include: the consensus processing requirements of the consensus layer, the consensus processing requirements including at least one of the following: consensus strategy selection requirements, data acquisition requirements, consensus node evaluation requirements, and consensus strategy adjustment requirements. The management layer to be managed includes: the consensus layer. The processing unit further includes: a selection subunit, used to select a consensus strategy in the hybrid consensus mechanism based on the target management requirements when the target management requirements include the consensus strategy selection requirements; and a fourth processing subunit, used to determine the consensus nodes for the data to be acquired based on the data to be managed when the target management requirements include the data acquisition requirements, thereby obtaining multiple first consensus nodes and acquiring the node consensus result of each first consensus node. The fifth processing subunit is configured to, when the target management requirement includes the evaluation requirement, determine the consensus nodes whose credibility needs to be evaluated based on the data to be managed, obtain multiple second consensus nodes, and evaluate the credibility of each second consensus node using a preset evaluation model based on the behavioral data of each second consensus node, thereby obtaining an evaluation result, wherein the behavioral data includes at least one of the following: node consensus result, voting data; the sixth processing subunit is configured to, when the target management requirement includes the consensus strategy adjustment requirement, determine the consensus nodes whose consensus strategy needs to be adjusted based on the data to be managed, obtain multiple third consensus nodes, and adjust the consensus strategy of each third consensus node.

[0018] Furthermore, the target management requirements include the management requirements of the incentive layer, the management layer to be managed includes the incentive layer, and the processing unit further includes: a determining subunit, used to determine the consensus nodes to be managed in the incentive layer based on the data to be managed, thereby obtaining multiple fourth consensus nodes; a second obtaining subunit, used to obtain the credibility assessment result of each fourth consensus node; a scoring subunit, used to score the behavioral data of each fourth consensus node based on the credibility assessment result of each fourth consensus node, thereby obtaining a score value for each fourth consensus node; and a disbursement subunit, used to disburse a reward to each fourth consensus node based on its score value using the reward mechanism.

[0019] Furthermore, the target management requirements include: the lifecycle management requirements of the contract layer and the application layer; the data to be managed includes: the smart contract; the management layer to be managed includes: the contract layer and the application layer; the processing unit further includes: a testing subunit, used to test the smart contract if the blockchain underlying framework reaches a first preset period at the current moment; and an upgrade subunit, used to upgrade the smart contract if the blockchain underlying framework reaches a second preset period at the current moment.

[0020] Furthermore, the target management requirements include: the requirement for cross-layer management of the multi-layer architecture; the data to be managed includes: the operational status data of the multi-layer architecture; and the processing unit includes: a collection subunit for collecting operational status data of each layer of the multi-layer architecture; and a seventh processing subunit for performing anomaly detection on the operational status data, obtaining detection results, and adjusting the multi-layer architecture based on the detection results.

[0021] According to another aspect of this application, a computer-readable storage medium is provided, the computer-readable storage medium including a stored executable program, wherein, when the executable program is executed, it controls the device where the computer-readable storage medium is located to perform the data processing method for a blockchain framework.

[0022] According to another aspect of this application, an electronic device is provided, comprising: a memory storing an executable program; and a processor for running the program, wherein the program, when running, executes the data processing method for a blockchain framework.

[0023] According to another aspect of this application, a computer program product is provided, including computer instructions that, when executed by a processor, implement the steps of the data processing method for a blockchain framework.

[0024] This application employs the following approach: First, it obtains the management requirements for the data to be managed, resulting in target management requirements. The data to be managed includes data within the blockchain's underlying framework, which is a multi-layered architecture comprising: a data layer, a network layer, a consensus layer, an incentive layer, a contract layer, and an application layer. The data layer includes zero-knowledge proof and homomorphic encryption strategies; the consensus layer includes a hybrid consensus mechanism; the incentive layer includes a reward mechanism for consensus nodes; and the contract layer includes smart contracts. Based on the target management requirements, a management layer is determined, comprising at least one layer of the multi-layered architecture. Then, based on the target management requirements, the management layer is used to process the data to be managed, thereby solving the technical problem of data management in related technologies relying on manual intervention and exhibiting high complexity. In this application, the combination of zero-knowledge proof, homomorphic encryption, and a hybrid consensus mechanism for multi-layered management of the blockchain's underlying framework avoids the reliance on manual intervention and high complexity in data management of related technologies, thus achieving the technical effect of reducing the complexity of data management in the blockchain's underlying framework and improving its security. Attached Figure Description

[0025] The accompanying drawings, which form part of this application, are used to provide a further understanding of this application. The illustrative embodiments and descriptions of this application are used to explain this application and do not constitute an undue limitation of this application. In the drawings:

[0026] Figure 1 A hardware structure block diagram of a computer terminal for implementing a data processing method for a blockchain framework is shown.

[0027] Figure 2 This is a flowchart of a data processing method for a blockchain framework provided according to an embodiment of this application;

[0028] Figure 3 This is a schematic diagram of a data processing system for a blockchain framework provided according to an embodiment of this application;

[0029] Figure 4 This is a flowchart of data processing for a blockchain framework provided according to an embodiment of this application;

[0030] Figure 5 This is a schematic diagram of a data processing apparatus for a blockchain framework provided according to an embodiment of this application;

[0031] Figure 6 This is a structural block diagram of an electronic device according to an embodiment of this application. Detailed Implementation

[0032] To enable those skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present application, and not all embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative effort should fall within the scope of protection of the present application.

[0033] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this application described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0034] It should be noted that the information collected in this application (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for display, data used for analysis, etc.) are information and data authorized by the user or fully authorized by all parties. Furthermore, the collection, storage, use, processing, transmission, provision, disclosure, and application of this data all comply with relevant laws, regulations, and standards, necessary confidentiality measures have been taken, and they do not violate public order and good morals. Corresponding access points are provided for users to choose to authorize or refuse. For example, interfaces are set up between this system and relevant users or organizations, providing users with corresponding access points to choose to agree to or refuse automated decision-making results; if the user chooses to refuse, the process proceeds to the expert decision-making stage.

[0035] Example 1

[0036] According to an embodiment of this application, a method embodiment for a data processing method for a blockchain framework is also provided. It should be noted that the steps shown in the flowchart in the accompanying drawings can be executed in a computer system such as a set of computer-executable instructions. Furthermore, although a logical order is shown in the flowchart, in some cases, the steps shown or described may be executed in a different order than that shown here.

[0037] The method embodiment provided in Embodiment 1 of this application can be executed on a mobile terminal, computer terminal, or similar computing device. Figure 1A hardware structure block diagram of a computer terminal (or mobile device) for implementing a data processing method for a blockchain framework is shown. Figure 1 As shown, the computer terminal 10 (or mobile device) may include one or more processors 102 (shown as 102a, 102b, ..., 102n in the figure) 102 (processor 102 may include, but is not limited to, a microprocessor MCU or a programmable logic device FPGA, etc.), a memory 104 for storing data, and a transmission device 106 for communication functions. In addition, it may also include: a display, an input / output interface (I / O interface), a universal serial bus (USB) port (which may be included as one of the ports of a BUS bus), a network interface, a power supply, and / or a camera. Those skilled in the art will understand that... Figure 1 The structure shown is for illustrative purposes only and does not limit the structure of the aforementioned electronic device. For example, computer terminal 10 may also include... Figure 1 The more or fewer components shown, or having the same Figure 1 The different configurations shown.

[0038] It should be noted that the aforementioned one or more processors 102 and / or other data processing circuits are generally referred to herein as "data processing circuits". These data processing circuits may be embodied, in whole or in part, in software, hardware, firmware, or any other combination thereof. Furthermore, the data processing circuits may be a single, independent processing module, or may be integrated, in whole or in part, into any other element within the computer terminal 10 (or mobile device). As involved in the embodiments of this application, the data processing circuits serve as a processor control mechanism (e.g., selection of a variable resistor termination path connected to an interface).

[0039] The memory 104 can be used to store software programs and modules of application software, such as the program instructions / data storage device corresponding to the data processing method for the blockchain framework in this embodiment of the application. The processor 102 executes various functional applications and data processing by running the software programs and modules stored in the memory 104, thereby realizing the aforementioned data processing method for the blockchain framework. The memory 104 may include high-speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory 104 may further include memory remotely located relative to the processor 102, and these remote memories can be connected to the computer terminal 10 via a network. Examples of such networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.

[0040] The transmission device 106 is used to receive or send data via a network. Specific examples of the network described above may include a wireless network provided by the communication provider of the computer terminal 10. In one example, the transmission device 106 includes a Network Interface Controller (NIC), which can connect to other network devices via a base station to communicate with the Internet. In another example, the transmission device 106 may be a Radio Frequency (RF) module, used for wireless communication with the Internet.

[0041] The display can be, for example, a touchscreen liquid crystal display (LCD), which allows the user to interact with the user interface of the computer terminal 10 (or mobile device).

[0042] Under the aforementioned operating environment, this application provides the following: Figure 2 The data processing method shown is used in the blockchain framework. Figure 2 This is a flowchart of a data processing method for a blockchain framework according to Embodiment 1 of this application.

[0043] Step S201: Obtain the management requirements for the data to be managed, and obtain the target management requirements. The data to be managed includes: the data to be managed in the blockchain bottom chain framework. The blockchain bottom chain framework is a multi-layer architecture, which includes: data layer, network layer, consensus layer, incentive layer, contract layer and application layer. The data layer includes: zero-knowledge proof strategy and homomorphic encryption strategy. The consensus layer includes: hybrid consensus mechanism. The incentive layer includes: reward mechanism for consensus nodes. The contract layer includes: smart contract.

[0044] The aforementioned target management requirements may include: control instructions, which may be manually triggered instructions or system-triggered instructions based on actual needs. For example, manually triggered instructions may include instructions obtained by parsing user-triggered operation instructions at different layers, while system-triggered instructions may include instructions triggered by system-set periodic check mechanisms, etc.

[0045] In this embodiment, before obtaining the management requirements of the data to be managed and the target management requirements, initialization and configuration operations can be performed on each layer included in the blockchain underlying framework, as follows:

[0046] Step 1.1: For the data layer, generate a basic encryption key pair based on zero-knowledge proof and homomorphic encryption technology.

[0047] Step 1.2: For the consensus layer, configure and integrate the Proof-of-Work (PoW), Proof-of-Stake (PoS), and Delegated Proof-of-Stake (DPoS) algorithms, and set the initial weights and parameters.

[0048] Step 1.3: For the incentive layer, set the incentive points calculation rules, redemption period, and reward types (such as digital assets and computing resources).

[0049] Step 1.4: For the contract layer and application layer, develop and deploy automated testing, verification tools and upgrade mechanisms for smart contracts.

[0050] Step 1.5: Optionally, for the overall blockchain underlying framework, establish a data collection, state indicator threshold setting, and linkage adjustment strategy.

[0051] Step S202: Based on the target management requirements, determine the management layer to be managed, wherein the management layer to be managed includes at least one layer of the multi-layer architecture.

[0052] In this embodiment, the management layer to be managed can be determined based on which layer of the architecture the target management requirements include. For example, if the target management requirements include data encryption and storage operations, data verification and security analysis operations, and data traceability management operations for the data to be managed at the data layer, the management layer to be managed can include the data layer; if the target related requirements include network supervision requirements for the network layer, the management layer to be managed can include the network layer; if the target management requirements include consensus processing requirements for the consensus layer, the management layer to be managed can include the consensus layer; if the target management requirements include node supervision requirements for the incentive layer, the management layer to be managed can include the incentive layer; if the target management requirements include lifecycle management requirements for the contract layer and application layer, the management layer to be managed can include both the contract layer and the application layer; if the current target management requirements include cross-layer management requirements for the overall blockchain bottom chain framework, then the management layer to be managed can include all layers of the blockchain bottom chain architecture.

[0053] Step S203: Based on the target management requirements, process the data to be managed by the management team.

[0054] In this embodiment, the data to be managed in the management layer can be associated based on the target management requirements, so as to achieve the purpose of collaborative management of the blockchain underlying architecture.

[0055] This solves the technical problem of high complexity and reliance on manual intervention in data management of blockchain underlying frameworks in related technologies. In this application, a multi-layered management system for the blockchain underlying framework is implemented by combining zero-knowledge proof strategies, homomorphic encryption strategies, and hybrid consensus mechanisms. This avoids the high complexity and reliance on manual intervention in data management of blockchain underlying frameworks in related technologies, thereby reducing the complexity of data management and improving the security of the blockchain underlying framework.

[0056] Optionally, in the data processing method for a blockchain framework provided in this application embodiment, the target management requirements include at least one of the following: data encryption and storage requirements, data verification and security analysis requirements, and data traceability requirements. The management layer to be managed is the data layer. Based on the target management requirements, the management layer to be managed processes the data to be managed, including: when the target management requirements include data encryption and storage requirements, encrypting the data to be managed using a zero-knowledge proof strategy and a homomorphic encryption strategy to obtain encrypted data to be managed, and storing the encrypted data to be managed; when the target management requirements include data verification and security analysis requirements, verifying and performing security analysis on the target encrypted data based on a zero-knowledge proof strategy, wherein the target encrypted data includes at least one of the following: encrypted data already stored in the data layer, and encrypted data to be managed; when the target management requirements include data traceability requirements, adding an identifier and a timestamp to the data to be managed, and recording the data flow of the data to be managed based on the identifier and timestamp.

[0057] For example, for the data to be managed in the input data layer, the target management requirements for the data to be managed can be determined, and at least one of the following operations can be performed on the data to be managed according to the target management requirements: data encryption and storage operation, data verification and security analysis operation, and data traceability management operation, to obtain the data layer supervision results for the data to be managed, as follows:

[0058] Step 2.1: When the target management requirements include data encryption and storage requirements, the input data to be managed can be encrypted based on zero-knowledge proof and homomorphic encryption technology (corresponding to zero-knowledge proof strategy and homomorphic encryption strategy) to obtain encrypted data for the data to be managed, and the encrypted data can also be stored in a distributed storage environment.

[0059] For example, firstly, homomorphic encryption algorithms can be used to encrypt the data to be managed, generating ciphertext data. This ensures data privacy is protected even if the data is transmitted over the network or stored in the blockchain. Then, zero-knowledge proofs are used to prove that the encrypted data possesses certain specific properties, such as data integrity or conformity to predefined rules. Verifiers can be certain that the data satisfies these properties but cannot know the specific content of the data. In this encrypted state, smart contracts or other components of the blockchain network can use the properties of homomorphic encryption to process the data, while using zero-knowledge proofs to verify the correctness of the processing results, ensuring data privacy and the accuracy of the processing.

[0060] Step 2.2: When the target management requirements include data verification and security analysis requirements, the encrypted data can be periodically verified based on zero-knowledge proofs to verify the authenticity of the encrypted data. The encrypted data can be the data encrypted in real time in step 2.1, or it can be the encrypted data stored historically in the database of the data layer.

[0061] In this embodiment, the integrity of the encrypted data can be checked based on knowledge proof, and the integrity check result of the encrypted data can be obtained.

[0062] Based on pre-set machine learning algorithms and historical security data associated with encrypted data, security early warning analysis is performed on the encrypted data to be analyzed, and security early warning analysis results are obtained for the encrypted data, so as to realize regular security early warning for encrypted data.

[0063] Step 2.3: When the target management requirements include data traceability management, a unique identifier and timestamp can be added to the data to be managed. Simultaneously, the transmission and flow information of the data to be managed can be recorded and updated in real time. Furthermore, a data traceability query interface can be set up for the data to be managed. Here, the data to be managed refers to the data prior to the data encryption operation.

[0064] It should be noted that the data to be managed generally refers to independent data from each layer, such as the data layer, network layer, and consensus layer. Furthermore, once the layers are interconnected, data that interacts or is related between different layers can be updated adaptively. For example, the data layer uses data A, and the network layer uses data B; data A and data B are related, so if data A is updated, data B can be updated adaptively. This correlation and adaptive updating of data across different layers is part of the cross-layer data management function.

[0065] To avoid relying on single, fixed encryption algorithms (such as AES and RSA) for on-chain data encryption and integrity verification through hash verification or digital signatures, and to address the limitations of centralized storage structures where trusted third parties maintain and verify data, this approach addresses the issue of data leakage risks. Single encryption algorithms have limited encryption strength, leading to low data security. Furthermore, data verification depends on trusted third parties, increasing trust costs and reducing system decentralization. Additionally, once data is on the chain, it is publicly accessible, lacking access control and privacy isolation mechanisms for sensitive information, resulting in weak data privacy protection. This embodiment combines Zero-Knowledge Proof (ZKP) with Homomorphic Encryption (HE) to achieve the core concept of "data usable but invisible." This allows for data authenticity verification and integrity checks without decryption, significantly reducing the risk of data leakage during the verification process.

[0066] Optionally, in the data processing method for a blockchain framework provided in this application embodiment, the target management requirements include: data management requirements of the network layer; the management layer to be managed includes: the network layer; the data to be managed includes: preset parameters of the network layer; based on the target management requirements, the management layer to be managed processes the data to be managed, including: obtaining parameter values ​​of the preset parameters of the network layer to obtain a parameter set, wherein the preset parameters include at least one of the following: network traffic, connection status of nodes in the network layer, and communication latency; determining whether the parameter values ​​in the parameter set meet preset adjustment conditions to obtain a determination result; and adjusting the network protocol and communication mechanism used by the network layer when the determination result indicates that the parameter values ​​in the parameter set meet the preset adjustment conditions.

[0067] When the target management requirements for the data to be managed include network surveillance requirements at the network layer, real-time network surveillance operations and network adjustment operations based on real-time network status can be performed on the data to be managed at the network layer according to these network surveillance requirements, as follows:

[0068] Step 3.1: Determine the network monitoring parameters for the network layer (corresponding to preset parameters). These network monitoring parameters may include, but are not limited to, network traffic, node connection status, and communication latency. In this embodiment, real-time network monitoring operations can be performed on the network layer according to the network monitoring parameters to obtain real-time network monitoring results for the network layer.

[0069] Step 3.2: Based on the real-time network monitoring results, it can be determined whether the network layer meets the network adjustment conditions (e.g., whether the parameter values ​​meet the preset adjustment conditions, such as whether the parameter values ​​of the network monitoring parameters exceed the preset range). If so, based on the real-time network monitoring results, the network layer performs dynamic adjustment operations on the network protocol parameters and communication mechanisms.

[0070] Optionally, in the data processing method for a blockchain framework provided in this application embodiment, the target management requirements include: consensus processing requirements of the consensus layer, which include at least one of the following: consensus strategy selection requirements, data acquisition requirements, consensus node evaluation requirements, and consensus strategy adjustment requirements. The management layer includes: a consensus layer. Based on the target management requirements, the management layer processes the data to be managed, including: when the target management requirements include consensus strategy selection requirements, selecting a consensus strategy in a hybrid consensus mechanism based on the target management requirements; when the target management requirements include data acquisition requirements, determining the consensus nodes for the data to be acquired based on the data to be managed, and obtaining multiple first consensuses. The system identifies nodes and obtains the consensus results and voting data of each first consensus node. When the target management requirements include evaluation requirements, it determines the consensus nodes whose credibility needs to be evaluated based on the data to be managed, obtaining multiple second consensus nodes. Based on the behavioral data of each second consensus node, it uses a preset evaluation model to evaluate the credibility of that second consensus node, obtaining the evaluation result. The behavioral data includes at least one of the following: node consensus results and voting data. When the target management requirements include consensus strategy adjustment requirements, it determines the consensus nodes whose consensus strategies need to be adjusted based on the data to be managed, obtaining multiple third consensus nodes, and adjusts the consensus strategy of each third consensus node.

[0071] When the target management requirements for the data to be managed include consensus processing requirements for the consensus layer, the target consensus operation to be executed corresponding to the consensus processing requirements can be determined, and the target consensus operation can be executed on the consensus layer to obtain the target consensus result for the consensus layer. These consensus requirements may include at least one requirement corresponding to consensus algorithm selection (corresponding to consensus strategy options), data acquisition requirements (e.g., obtaining node consensus calculation results and voting information), node behavior evaluation (corresponding to the evaluation requirements of consensus nodes), and consensus mechanism adjustment (corresponding to consensus strategy adjustment requirements). The specific processing is as follows:

[0072] Step 4.1: When the consensus processing requirement includes the requirement to select the corresponding consensus algorithm, obtain the current task to be processed (i.e., the data to be managed) in the consensus layer, and select the target consensus algorithm that matches the task to be processed from the pre-configured hybrid consensus mechanism (including: PoW / PoS / DPoS, three mechanisms. In actual application, one or more of the appropriate mechanisms can be selected to execute the task to be processed as needed).

[0073] In an alternative example, a hybrid consensus engine can be used to select a consensus strategy (i.e., a target consensus algorithm). The hybrid consensus engine can include a three-layer consensus coordination architecture, such as a mechanism selection layer, a consensus execution layer, and a result verification layer.

[0074] The hybrid consensus engine can establish a consensus mechanism registry, supporting dynamic registration and management of PoW, PoS, and DPoS mechanisms.

[0075] A hybrid consensus engine may also include a consensus context manager that maintains the running state and history of each mechanism.

[0076] The initial parameter configuration of the hybrid consensus engine includes: setting the initial weight allocation ratio: PoW 40%, PoS 30%, DPoS 30%; defining consensus switching trigger conditions: block height threshold, network status indicators, security event trigger; and configuring minimum security parameters: minimum PoW difficulty value, minimum PoS staking amount, and minimum number of delegated nodes for DPoS.

[0077] Step 4.2: When the consensus processing requirements include the requirements for obtaining node consensus calculation results and voting information (corresponding to data acquisition requirements), all first consensus nodes currently under supervision in the consensus layer can be identified, all first consensus nodes can be located, and the node consensus calculation results and voting information calculated for each first consensus node can be collected.

[0078] In one alternative example, the first consensus node can be determined based on the node classification according to the consensus mechanism type, as shown in the following example:

[0079] Category 1: Currently active nodes participating in consensus: (1) PoW mechanism: miner nodes that have successfully produced blocks in the past 24 hours; (2) PoS mechanism: validator nodes and candidate nodes in the current round; (3) DPoS mechanism: currently active delegate nodes and backup nodes.

[0080] Category 2: Nodes with special privileges or importance: (1) Nodes ranked in the top N for staking (e.g., the top 50); (3) Nodes with a historical block production success rate exceeding the threshold (e.g., 95%); (4) Hub nodes with high network connectivity (top 20% of the number of connections).

[0081] Category 3: Nodes exhibiting signs of abnormal behavior: (1) Nodes with recent abnormal voting records; (2) Nodes with significantly abnormal block production times; (3) Nodes with abrupt changes in network behavior patterns.

[0082] In an optional example, the first consensus node can also be determined based on dynamically determined rules of the regulatory policy. These dynamically determined rules include:

[0083] Rule 1: Layered sampling strategy: (1) Layer by node type: full node, verification node, miner node, etc.; (2) Sampling by proportion of each layer: such as sampling 20% ​​of the nodes in each layer as the monitoring object; (3) Dynamically adjust the sampling rate: adjust according to the network size and security status.

[0084] Rule 2: Risk-oriented strategy: (1) High-risk nodes must be selected: historical violation nodes and newly added high-staking nodes; (2) Randomly select low-risk nodes: randomly select some normal nodes as a control; (3) Related node expansion: related nodes that have high-frequency interaction with abnormal nodes.

[0085] Rule 3: Performance monitoring strategy: (1) Select nodes with high network latency for key monitoring; (2) Select nodes with high block failure rate; (3) Select nodes with slow transaction verification speed.

[0086] In an alternative example, the first consensus node can also be determined based on a fixed regulatory group, for example, (1) a core node designated by a designated institution; (2) a node that provides critical infrastructure services (such as a cross-chain bridge node); (3) a large node whose pledged amount exceeds 1% of the entire network.

[0087] In an alternative example, the first consensus node can also be determined based on a rotating oversight group, which may include: (1) a random group of nodes rotating in a time period; (2) nodes selected by community governance voting; and (3) nodes that voluntarily join the oversight plan, or a fixed set of nodes based on governance requirements.

[0088] Methods for locating the first consensus node can include: network layer location methods, consensus layer internal location mechanisms, and hybrid location strategies, for example:

[0089] (I) Network Layer Localization Method:

[0090] Method 1: Node identification location, for example, (1) Public key address location: uniquely identified by the encrypted public key address of the node; (2) Node ID location: node ID assigned by the P2P network; (3) IP address and port combination: record the network access point of the node.

[0091] Method 2: Network topology discovery: (1) Neighbor node list query: Obtain the list of nodes connected to a known node; (2) Web crawler scan: Actively scan the active nodes in the blockchain network; (3) DHT network query: Locate the node location through a distributed hash table.

[0092] Method 3: Blockchain ledger record location: (1) Block record tracing: locate from the miner / validator field in the block header; (2) Transaction signature analysis: associate with specific nodes through transaction signatures; (3) Smart contract event log: record node registration and activity events.

[0093] (II) Internal Positioning Mechanism of the Consensus Layer:

[0094] Location Mechanism 1: Consensus Participation Record Location: (1) Validator Set Record: The current list of validators maintained in the consensus contract; (2) Voting History Record: The history of all node addresses that participated in voting; (3) Block Round Record: The information of the block producing node corresponding to each block.

[0095] Location Mechanism 2: State Synchronization Protocol Location: (1) Consensus State Subscription: Nodes subscribe to consensus state change events; (2) Heartbeat Monitoring: Confirm the online status of nodes through periodic heartbeats; (3) Consensus Message Tracking: Track the source node of consensus messages.

[0096] Location Mechanism 3: Reputation System Related Location: (1) Reputation Score Mapping: Mapping the node ID in the reputation system to the actual network address; (2) Behavior Record Association: Association of abnormal behavior records with node identity; (3) Historical Performance Database: Maintaining the historical consensus performance records of nodes.

[0097] (III) Implementation steps of the hybrid positioning strategy:

[0098] Step a: Identity verification stage: (1) Read the list of currently active validators from the consensus contract; (2) Verify the online status of these nodes through the P2P network; (3) Confirm the consistency of the nodes' multiple identities.

[0099] Step b: Network reachability verification: (1) Send a test message to confirm the node's response capability; (2) Verify the stability of the node's network connection; (3) Test the node's data transmission delay.

[0100] Step c: Establishment of regulatory access point: (1) Establish a dedicated regulatory connection channel with the target node; (2) Negotiate the data collection protocol and frequency; (3) Set up an encrypted transmission mechanism for regulatory data;

[0101] Step d: Dynamic tracking and maintenance: (1) Regularly update the network location information of the nodes; (2) Monitor changes in node identity (such as public key rotation); (3) Handle situations where nodes are offline or migrated.

[0102] Step 4.3: When the consensus processing requirements include the requirements corresponding to node behavior evaluation operations, all second consensus nodes to be evaluated can be determined based on the data to be monitored. Then, based on the preset reputation evaluation model (corresponding to the preset evaluation model) and the node behavior data of the second consensus node, an evaluation operation is performed on the second consensus node to obtain the node evaluation result for that second consensus node. The node behavior data of each second consensus node may include the node consensus calculation result obtained in Step 4.2 (corresponding to the node consensus result) and node voting information (corresponding to voting data).

[0103] Step 4.4: When the consensus processing requirements include the requirements corresponding to the consensus mechanism adjustment operation (corresponding to the consensus strategy adjustment requirements), the consensus results of all third consensus nodes and the overall network operation status can be determined within the preset monitoring period; the consensus results of all third consensus nodes and the overall network operation status are analyzed to obtain the analysis results for all third consensus nodes. The analysis results can be used to identify malicious nodes and / or inefficient nodes that meet the preset node adjustment requirements.

[0104] Step 4.5: Based on the analysis results (corresponding to the analysis results obtained in Step 4.4), dynamically adjust the weight ratio of each algorithm in the hybrid consensus algorithm and dynamically optimize the corresponding model parameters of the reputation evaluation model; at the same time, perform duty and permission adjustment operations on malicious nodes and / or inefficient nodes.

[0105] To avoid relying on a single consensus algorithm in related technologies, node admission and behavior monitoring often depend on manual configuration or simple voting mechanisms. However, a single consensus mechanism is difficult to handle dynamic network environments (such as frequent node joining / leaving, network latency fluctuations, etc.), which can easily lead to forks, consensus failures, or performance degradation. In other words, a single consensus mechanism has poor applicability. In this embodiment, a dynamic weighted hybrid consensus mechanism (PoW / PoS / DPoS) is adopted. By analyzing the network state and node behavior in real time, the weights of each algorithm and the reputation model parameters are dynamically adjusted, which improves the overall security of the blockchain system (against malicious nodes), data response efficiency (low latency and high throughput), and decentralization.

[0106] Optionally, in the data processing method for a blockchain framework provided in this application embodiment, the target management requirements include: the management requirements of the incentive layer, and the management layer to be managed includes: the incentive layer. Based on the target management requirements, the management layer to be managed processes the data to be managed, including: based on the data to be managed, determining the consensus nodes to be managed by the incentive layer to obtain multiple fourth consensus nodes; obtaining the credibility assessment result of each fourth consensus node; based on the credibility assessment result of each fourth consensus node, scoring the behavioral data of each fourth consensus node to obtain the score value of each fourth consensus node; and based on the score value of each fourth consensus node, distributing rewards to each fourth consensus node using a reward mechanism.

[0107] When the target management requirements for the data to be managed include node supervision requirements for the incentive layer, for the incentive layer, the node evaluation results calculated for each consensus node can be obtained. For each consensus node (corresponding to the fourth consensus node), at least one of the following operations can be performed on the consensus node based on the node evaluation results: node behavior score calculation operation, incentive points and reward conversion operation based on the calculated node behavior score, reward redemption operation, and reward distribution operation.

[0108] Step 5.1: For the incentive layer, the node evaluation results of its supervisory nodes can be obtained in real time. The node evaluation results include the reputation evaluation results of the supervisory node by the consensus layer (corresponding to the credibility evaluation). Based on the node evaluation results of the supervisory node, the behavior score corresponding to the supervisory node is calculated.

[0109] For example, the behavior score = consensus performance score × 40% + security contribution score × 30% + governance participation score × 20% - violation penalty score × 10%, where the weights of each dimension (e.g., 40%, 30%, 20% and 10%) can be dynamically adjusted according to the network status.

[0110] Step 5.2: According to the preset incentive mechanism, convert the behavior score of the regulatory node into incentive points and / or preset incentive rewards; at the same time, according to the preset exchange cycle, convert the incentive points into preset incentive rewards and distribute the preset incentive rewards to encourage participants (nodes) in the blockchain network to actively, honestly and efficiently execute network rules and tasks.

[0111] Optionally, in the data processing method for a blockchain framework provided in this application embodiment, the target management requirements include: lifecycle management requirements of the contract layer and the application layer, the data to be managed includes: smart contracts, the management layer to be managed includes: the contract layer and the application layer, and based on the target management requirements, the management layer to be managed processes the data to be managed, including: if the blockchain underlying framework reaches a first preset period at the current moment, then the smart contract is tested; if the blockchain underlying framework reaches a second preset period at the current moment, then the smart contract is upgraded.

[0112] When the target management requirements for the data to be managed include lifecycle management requirements for both the contract layer and the application layer, for the contract layer and the application layer, at least one of the following operations can be performed periodically on the configured smart contracts according to a preset management cycle and in conjunction with preset automation tools: testing and verification operations, contract upgrade and deployment operations, as follows:

[0113] Step 6.1: For the contract layer, when it is detected that the current first management cycle (corresponding to the first preset cycle) has been reached, the configured smart contract can be tested and verified according to the preset automated tools to obtain the test and verification results for the smart contract.

[0114] For example, smart contracts can be tested using a multi-level testing framework architecture. This framework can include: a basic testing layer (unit testing), an integration testing layer (interaction testing), and a security testing layer (vulnerability scanning). The basic testing layer can include testing functions for correctness, state variable changes, access control verification, and boundary conditions and exception handling. The integration testing layer (interaction testing) can include testing inter-contract calls and dependencies, cross-contract state consistency verification, and event triggering and listening mechanisms. The security testing layer can include detecting reentrancy vulnerabilities, integer overflow / underflow checks, missing access control detection, and identifying logical vulnerabilities and business risks. The test execution workflow is as follows:

[0115] 1. Pre-inspection stage:

[0116] Step (1): Contract compliance verification: coding style check (Solidity style guide), license and copyright statement verification, and dependency library version compatibility check.

[0117] Step (2): Environment preparation: test network configuration (Ganache / Hardhat Network), test account and initial funding settings, and creation of external dependency objects.

[0118] 2. Core Test Execution:

[0119] Step (3): Unit test execution: Execute predefined test case sets, coverage analysis (target ≥95%), and Gas (resource consumption, such as computing power (CPU time), storage space (memory and hard disk space), and network bandwidth) consumption benchmark tests.

[0120] Step (4): Integration test execution: Deploy dependent contracts and main contract, execute cross-contract scenario tests, and front-end and back-end interaction simulation tests.

[0121] Step (5): Stress testing: high-concurrency transaction load testing, large data volume state operation testing, and extreme boundary condition testing.

[0122] 3. Security verification execution:

[0123] Step (6): Static analysis scan: Perform parallel scanning with multiple tools, generate security vulnerability reports, and classify risk levels (high risk, medium risk, low risk).

[0124] Step (7): Dynamic analysis testing: fuzzing, symbolic execution analysis, and formal verification (for key contracts).

[0125] The verification results are generated and analyzed as follows:

[0126] Standardized output of test results: Output format: structured JSON test report, visual HTML coverage report, and security scan risk matrix, including: test pass rate, code coverage (line coverage, branch coverage, function coverage), gas consumption analysis table, and security vulnerability list and remediation suggestions.

[0127] Automated quality access control: Quality threshold settings: Unit test pass rate: must be 100%; Code coverage: must be ≥85% (critical contracts ≥95%); Security vulnerabilities: zero high-risk vulnerabilities, medium-risk vulnerabilities ≤3; Gas optimization: not exceeding the preset gas limit.

[0128] Step 6.2: According to the preset second management cycle (corresponding to the second preset cycle), obtain the update and deployment information for the smart contract, and perform contract upgrade and deployment operations on the configured smart contract based on the update and deployment information to obtain the contract upgrade and deployment results for the smart contract.

[0129] Step 6.3: For the application layer, it provides application functions such as transaction matching, digital asset ownership confirmation, and transaction flow. Simultaneously, this application layer has multiple standard interfaces to provide interfaces for external application access and local application invocation.

[0130] Optionally, in the data processing method for a blockchain framework provided in this application embodiment, the target management requirement includes: the requirement for cross-layer management of a multi-layer architecture, and the data to be managed includes: the operational status data of the multi-layer architecture. Based on the target management requirement, the data to be managed is processed by the management layer, including: collecting the operational status data of each layer in the multi-layer architecture; performing anomaly detection on the operational status data to obtain the detection results, and adjusting the multi-layer architecture based on the detection results.

[0131] The aforementioned operational status data refers to information reflecting the current operational status of each layer of the blockchain system, including but not limited to network traffic, node status, transaction rate, gas consumption, smart contract execution status, data storage capacity, and consensus algorithm execution. This data forms the basis for cross-layer management; by collecting it in real-time or periodically, a comprehensive understanding of the system status can be achieved, providing a basis for subsequent anomaly detection and system adjustments.

[0132] When the target management requirements for the data to be managed include cross-layer management requirements for the overall blockchain underlying framework, the overall blockchain underlying framework can continuously collect the operating status and performance indicators of the data layer, network layer, consensus layer, incentive layer, contract layer, and application layer according to the preset cross-layer monitoring mechanism; and perform anomaly diagnosis operations, anomaly warning operations based on anomaly diagnosis results (corresponding to detection results), and cross-layer optimization operations based on anomaly diagnosis results on the operating status and performance indicators respectively.

[0133] For example, anomaly detection of operational status data can identify events that deviate from normal or expected behavior. In blockchain systems, this can detect network congestion, malicious attacks (such as 51% attacks), smart contract vulnerabilities, and data breach risks. Statistical analysis and machine learning algorithms can be used to establish a baseline of normal behavior based on historical data, which can then be compared with current operational status data to identify any anomalies.

[0134] Once an anomaly is detected, adjustments can be made to the multi-layered architecture based on the detection results. These adjustments can include optimizing network routing, adjusting consensus parameters (such as PoW difficulty and PoS stake weights), updating smart contract code, and reallocating incentives among nodes. This dynamic cross-layer adjustment can fix system problems, improve overall performance, prevent potential security risks, and respond to changes in network environment or business needs.

[0135] In this embodiment, the core concept of "data usable but not visible" is achieved through the combined application of zero-knowledge proof (ZKP) and homomorphic encryption (HE). This enables data authenticity verification and integrity checks to be completed without decryption, reducing the risk of data leakage during the verification process and improving data privacy and security.

[0136] Unlike the single consensus algorithm commonly used in blockchain underlying frameworks in related technologies, this embodiment adopts a dynamic weighted hybrid consensus mechanism (PoW / PoS / DPoS). By analyzing network status and node behavior in real time, it dynamically adjusts the weights of each algorithm and reputation model parameters, thereby improving the overall security of the blockchain system (against malicious nodes), data response efficiency (low latency and high throughput), and decentralization, and enhancing the applicability and practicality of the consensus algorithm.

[0137] Establish a real-time monitoring mechanism for each layer in the blockchain base chain. When a certain layer (such as network layer congestion or malicious nodes in the consensus layer) experiences performance bottlenecks or security threats, it can trigger cross-layer linkage (such as adjusting consensus parameters, network routing, and node incentives) to achieve intelligent self-healing and automatic optimization of the system. This is beneficial to improving the robustness of the overall system and realizing cross-layer monitoring and intelligent dynamic adjustment.

[0138] By comprehensively applying the incentive layer, consensus layer, and reputation assessment model, the behavior of each consensus node can be quantified and evaluated in a timely manner. Simultaneously, it enables timely and accurate rewards for effective nodes and prompt penalties for malicious or negative nodes, achieving precise and dynamic evaluation of node consensus behavior.

[0139] Adding a unique identifier and timestamp before data encryption ensures the immutability and plaintext queryability of traceability metadata. It provides transparent and efficient trusted traceability capabilities across the entire data chain, from generation and encryption to storage and circulation, meeting the auditing needs of high-value data assets and compliance scenarios, and achieving full lifecycle governance and trusted traceability of data.

[0140] By introducing automated testing and verification tools and standardized upgrade mechanisms, the security risks of smart contracts caused by code vulnerabilities (such as asset theft) are significantly reduced. At the same time, contract iteration and updates are made smoother and more secure, enhancing the stability and credibility of the contract layer and improving the reliability and maintainability of smart contracts.

[0141] It should be noted that the steps shown in the flowchart in the accompanying drawings can be executed in a computer system such as a set of computer-executable instructions, and although a logical order is shown in the flowchart, in some cases the steps shown or described may be executed in a different order than that shown here.

[0142] Example 2

[0143] Embodiment 2 of this application provides an optional data processing system for a blockchain framework, which can be used to execute the data processing method for a blockchain framework provided in Embodiment 1 of this application.

[0144] Figure 3 This is a schematic diagram of a data processing system for a blockchain framework provided according to an embodiment of this application, such as... Figure 3 As shown, it includes:

[0145] The initial configuration module 301 is used to perform initialization and configuration operations on each layer included in the blockchain bottom chain framework.

[0146] The requirement determination module 302 is used to determine the target management requirements for the data to be managed for the input data layer after the initialization and configuration module has completed the initialization and configuration operations for each layer included in the blockchain bottom chain framework.

[0147] The security control module 303 is used to perform at least one of the following operations on the data to be managed according to the target management requirements: data encryption and storage operation, data verification and security analysis operation, and data traceability management operation, so as to obtain the data layer supervision result for the data to be managed.

[0148] The network management module 304 is used to perform real-time network monitoring operations and network adjustment operations based on real-time network status on the network layer when the target management requirements for the data to be managed include network monitoring requirements for the network layer.

[0149] The consensus control module 305 is used to determine the target consensus operation to be executed corresponding to the consensus processing requirement when the target management requirements for the data to be managed include consensus processing requirements for the consensus layer, and to execute the target consensus operation on the consensus layer to obtain the target consensus result for the consensus layer.

[0150] The node evaluation and control module 306 is used to, when the target management requirements for the data to be managed include the node supervision requirements for the incentive layer, obtain the node evaluation results calculated for each consensus node for the incentive layer, and for each consensus node, perform at least one of the following operations based on the node evaluation results corresponding to that consensus node: calculating node behavior score, converting incentive points and rewards based on the calculated node behavior score, redeeming rewards, and distributing rewards.

[0151] The cycle management module 307, when the target management requirements for the data to be managed include lifecycle management requirements for the contract layer and the application layer, performs at least one of the following operations on the configured smart contracts periodically, according to the preset management cycle and in combination with preset automation tools: test and verification operations, contract upgrade and deployment operations.

[0152] The cross-layer monitoring module 308 is used to continuously collect the operating status and performance indicators of the data layer, network layer, consensus layer, incentive layer, contract layer, and application layer of the overall blockchain bottom chain framework when the target management requirements for the data to be managed include the cross-layer management requirements for the overall blockchain bottom chain framework, according to the preset cross-layer monitoring mechanism; and to perform anomaly diagnosis operations, anomaly warning operations based on anomaly diagnosis results, and cross-layer optimization operations based on anomaly diagnosis results on the operating status and performance indicators respectively.

[0153] Figure 4 This is a flowchart of data processing for a blockchain framework provided according to embodiments of this application, such as... Figure 4 As shown, it includes:

[0154] Step S401: Perform initialization and configuration operations on each layer included in the blockchain bottom chain framework.

[0155] Step S402: For the data to be managed in the input data layer, determine the target management requirements for the data to be managed, and perform at least one of the following operations on the data to be managed according to the target management requirements: data encryption and storage operation, data verification and security analysis operation, and data traceability management operation, to obtain the data layer supervision results for the data to be managed.

[0156] Step S403: Perform real-time network monitoring operations and network adjustment operations based on real-time network status on the network layer.

[0157] Step S404: Determine the consensus processing requirements for the consensus layer, identify the target consensus operation to be executed corresponding to the consensus processing requirements, and execute the target consensus operation on the consensus layer to obtain the target consensus result for the consensus layer. These consensus requirements include at least one requirement corresponding to consensus algorithm selection, acquisition of node consensus calculation results and voting information, node behavior evaluation, and consensus mechanism adjustment.

[0158] Step S405: For the incentive layer, obtain the node evaluation result calculated for each consensus node. For each consensus node, based on the node evaluation result corresponding to the consensus node, perform at least one of the following operations for the consensus node: node behavior score calculation operation, node behavior based on calculation, incentive points and reward conversion operation for score, reward exchange operation, and reward distribution operation.

[0159] Step S406: For the contract layer and application layer, according to the preset management cycle and in combination with the preset automation tools, perform at least one of the following operations on the configured smart contracts periodically: test and verification operation, contract upgrade and deployment operation.

[0160] Step S407: According to the preset cross-layer monitoring mechanism, continuously collect the operating status and performance indicators of the data layer, network layer, consensus layer, incentive layer, contract layer, and application layer; and perform anomaly diagnosis operation, anomaly warning operation based on anomaly diagnosis results, and cross-layer optimization operation based on anomaly diagnosis results on the operating status and performance indicators respectively.

[0161] In this embodiment, a cryptographic data verification and security analysis method based on the fusion of ZKP and HE can be set up at the data layer. For the consensus layer, dynamic analysis and dynamic adjustment mechanisms for hybrid consensus algorithms can be set up. For the blockchain base layer, cross-layer monitoring, cross-layer collaboration, and optimization mechanisms can be set up. A joint intelligent incentive processing mechanism can be implemented for the consensus layer and incentive layer. For smart contracts, automated testing, verification, and upgrade mechanisms can be set up, improving the regulatory reliability of the blockchain base layer architecture.

[0162] Example 3

[0163] This application also provides a data processing apparatus for a blockchain framework. It should be noted that the data processing apparatus for a blockchain framework provided in this application can be used to execute the data processing method for a blockchain framework provided in this application. The following describes the data processing apparatus for a blockchain framework provided in this application.

[0164] According to embodiments of this application, an apparatus for implementing the above-described data processing method for a blockchain framework is also provided, such as... Figure 5 As shown, the device includes: an acquisition unit 51, a determination unit 52, and a processing unit 53.

[0165] The acquisition unit 51 is used to acquire the management requirements of the data to be managed and obtain the target management requirements. The data to be managed includes the data to be managed in the blockchain bottom chain framework. The blockchain bottom chain framework is a multi-layer architecture, which includes: data layer, network layer, consensus layer, incentive layer, contract layer and application layer. The data layer includes: zero-knowledge proof strategy and homomorphic encryption strategy. The consensus layer includes: hybrid consensus mechanism. The incentive layer includes: reward mechanism for consensus nodes. The contract layer includes: smart contract.

[0166] The determination unit 52 is used to determine the management layer to be managed based on the target management requirements, wherein the management layer to be managed includes at least one layer of the multi-layer architecture;

[0167] Processing unit 53 is used to process the data to be managed by the management layer based on the target management requirements.

[0168] In the data processing apparatus for a blockchain framework provided in this application embodiment, the acquisition unit 51 is used to acquire the management requirements of the data to be managed, thereby obtaining the target management requirements. The data to be managed includes the data to be managed within the blockchain's underlying blockchain framework, which is a multi-layered architecture including a data layer, a network layer, a consensus layer, an incentive layer, a contract layer, and an application layer. The data layer includes zero-knowledge proof strategies and homomorphic encryption strategies; the consensus layer includes a hybrid consensus mechanism; the incentive layer includes a reward mechanism for consensus nodes; and the contract layer includes smart contracts. The determination unit 52 is used to determine the management layer to be managed based on the target management requirements. The management layer to be managed includes at least one layer of the multi-layered architecture. The processing unit 53 is used to process the data to be managed using the management layer to be managed based on the target management requirements. This solves the technical problem in related technologies where data management of the blockchain's underlying blockchain framework relies on manual intervention and has high data management complexity. In this embodiment, a multi-layered management of the blockchain underlying framework is achieved by combining zero-knowledge proof strategy, homomorphic encryption strategy and hybrid consensus mechanism. This avoids the situation in related technologies where the data management of the blockchain underlying framework relies on manual intervention and has high data management complexity. As a result, the technical effect of reducing the complexity of data management of the blockchain underlying framework and improving the security of the blockchain underlying framework is achieved.

[0169] Optionally, the target management requirements include at least one of the following: data encryption and storage requirements, data verification and security analysis requirements, and data traceability requirements. The layer to be managed is the data layer, and the processing unit includes: a first processing subunit, used to encrypt the data to be managed using a zero-knowledge proof strategy and a homomorphic encryption strategy when the target management requirements include data encryption and storage requirements, to obtain encrypted data to be managed, and to store the encrypted data to be managed; a second processing subunit, used to verify and perform security analysis on the target encrypted data based on a zero-knowledge proof strategy when the target management requirements include data verification and security analysis requirements, wherein the target encrypted data includes at least one of the following: encrypted data already stored in the data layer, and encrypted data to be managed; and a third processing subunit, used to add an identifier and a timestamp to the data to be managed when the target management requirements include data traceability requirements, and to record the data flow of the data to be managed based on the identifier and timestamp.

[0170] Optionally, the target management requirements include: data management requirements of the network layer; the management layer to be managed includes: the network layer; the data to be managed includes: preset parameters of the network layer; the processing unit further includes: a first acquisition subunit, used to acquire the parameter values ​​of the preset parameters of the network layer to obtain a parameter set, wherein the preset parameters include at least one of the following: network traffic, connection status of nodes in the network layer, and communication latency; a judgment subunit, used to judge whether the parameter values ​​in the parameter set meet the preset adjustment conditions and obtain a judgment result; and an adjustment subunit, used to adjust the network protocol and communication mechanism used by the network layer when the judgment result indicates that the parameter values ​​in the parameter set meet the preset adjustment conditions.

[0171] Optionally, the target management requirements include: consensus processing requirements of the consensus layer, which include at least one of the following: consensus strategy selection requirements, data acquisition requirements, consensus node evaluation requirements, and consensus strategy adjustment requirements. The management layer includes: the consensus layer. The processing unit further includes: a selection subunit, used to select a consensus strategy in the hybrid consensus mechanism based on the target management requirements when the target management requirements include consensus strategy selection requirements; and a fourth processing subunit, used to determine the consensus nodes for the data to be acquired based on the data to be managed when the target management requirements include data acquisition requirements, obtaining multiple first consensus nodes, and acquiring the node consensus result of each first consensus node and the consensus result of each first consensus node. The fifth processing subunit is used to determine the consensus nodes whose credibility needs to be evaluated based on the data to be managed, when the target management requirements include evaluation requirements, to obtain multiple second consensus nodes, and to evaluate the credibility of each second consensus node using a preset evaluation model based on the behavioral data of each second consensus node, thereby obtaining an evaluation result. The behavioral data includes at least one of the following: node consensus results and voting data. The sixth processing subunit is used to determine the consensus nodes whose consensus strategies need to be adjusted based on the data to be managed, when the target management requirements include consensus strategy adjustment requirements, to obtain multiple third consensus nodes, and to adjust the consensus strategy of each third consensus node.

[0172] Optionally, the target management requirements include: the management requirements of the incentive layer; the management layer to be managed includes: the incentive layer; and the processing unit further includes: a determination subunit, used to determine the consensus nodes to be managed in the incentive layer based on the data to be managed, thereby obtaining multiple fourth consensus nodes; a second acquisition subunit, used to acquire the credibility assessment results of each fourth consensus node; a scoring subunit, used to score the behavioral data of each fourth consensus node based on the credibility assessment results of each fourth consensus node, thereby obtaining the score value of each fourth consensus node; and a distribution subunit, used to distribute rewards to each fourth consensus node based on the score value of each fourth consensus node using a reward mechanism.

[0173] Optionally, the target management requirements include: lifecycle management requirements of the contract layer and application layer; the data to be managed includes: smart contracts; the management layer to be managed includes: the contract layer and the application layer; and the processing unit further includes: a testing subunit, used to test the smart contract if the blockchain underlying framework reaches the first preset period at the current moment; and an upgrade subunit, used to upgrade the smart contract if the blockchain underlying framework reaches the second preset period at the current moment.

[0174] Optionally, the target management requirements include: the need for cross-layer management of the multi-layer architecture; the data to be managed includes: the operational status data of the multi-layer architecture; and the processing units include: a collection subunit, used to collect the operational status data of each layer in the multi-layer architecture; and a seventh processing subunit, used to perform anomaly detection on the operational status data, obtain the detection results, and adjust the multi-layer architecture based on the detection results.

[0175] It should be noted that the acquisition unit 51, determination unit 52, and processing unit 53 mentioned above correspond to steps S201 to S203 in Embodiment 1. Each unit and its corresponding step implement the same instance and application scenario, but are not limited to the content disclosed in Embodiment 1. It should be noted that the above modules or units can be hardware or software components stored in memory (e.g., memory 104) and processed by one or more processors (e.g., processors 102a, 102b, ..., 102n). The above modules can also be part of a device and run in the computer terminal 10 provided in Embodiment 1.

[0176] Example 4

[0177] Embodiments of this application may provide an electronic device. Figure 6 This is a structural block diagram of an electronic device according to an embodiment of this application. Figure 6 As shown, the electronic device may include: one or more ( Figure 6 (Only one is shown) Processor 602, memory 604, memory controller, and peripheral interface, wherein the peripheral interface is connected to the radio frequency module, audio module and display.

[0178] The memory can be used to store software programs and modules, such as the program instructions / modules corresponding to the methods and apparatus in the embodiments of this application. The processor executes various functional applications and data processing by running the software programs and modules stored in the memory, thereby implementing the above-described methods. The memory may include high-speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory may further include memory remotely located relative to the processor, and these remote memories can be connected to the terminal via a network. Examples of such networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.

[0179] The processor can invoke information and applications stored in the memory via a transmission device to perform the following steps: Obtaining the management requirements of the data to be managed, thus obtaining the target management requirements. The data to be managed includes: data to be managed within the blockchain's underlying framework. The blockchain's underlying framework is a multi-layered architecture, including: a data layer, a network layer, a consensus layer, an incentive layer, a contract layer, and an application layer. The data layer includes: zero-knowledge proof strategies and homomorphic encryption strategies; the consensus layer includes: a hybrid consensus mechanism; the incentive layer includes: a reward mechanism for consensus nodes; and the contract layer includes: smart contracts. Based on the target management requirements, determining the management layer to be managed, wherein the management layer to be managed includes: at least one layer of the multi-layered architecture; and processing the data to be managed using the management layer to be managed, based on the target management requirements.

[0180] The processor can also invoke information and applications stored in the memory via a transmission device to perform the following steps: The target management requirements include at least one of the following: data encryption and storage requirements, data verification and security analysis requirements, and data traceability requirements. The layer to be managed is the data layer. Based on the target management requirements, the data to be managed is processed using the layer to be managed, including: when the target management requirements include data encryption and storage requirements, the data to be managed is encrypted using a zero-knowledge proof strategy and a homomorphic encryption strategy to obtain encrypted data to be managed, and the encrypted data to be managed is stored; when the target management requirements include data verification and security analysis requirements, the target encrypted data is verified and security analyzed based on a zero-knowledge proof strategy, wherein the target encrypted data includes at least one of the following: encrypted data already stored in the data layer, and encrypted data to be managed; when the target management requirements include data traceability requirements, an identifier and a timestamp are added to the data to be managed, and the data flow of the data to be managed is recorded based on the identifier and timestamp.

[0181] The processor can also invoke information and applications stored in the memory via a transmission device to perform the following steps: Target management requirements include: data management requirements of the network layer; the management layer to be managed includes: the network layer; the data to be managed includes: preset parameters of the network layer; based on the target management requirements, the management layer to be managed processes the data to be managed, including: obtaining the parameter values ​​of the preset parameters of the network layer to obtain a parameter set, wherein the preset parameters include at least one of the following: network traffic, connection status of nodes in the network layer, and communication latency; determining whether the parameter values ​​in the parameter set meet preset adjustment conditions to obtain a judgment result; and adjusting the network protocol and communication mechanism used by the network layer if the judgment result indicates that the parameter values ​​in the parameter set meet the preset adjustment conditions.

[0182] The processor can also invoke information and applications stored in the memory via a transmission device to perform the following steps: The target management requirements include: consensus processing requirements of the consensus layer, which include at least one of the following: consensus strategy selection requirements, data acquisition requirements, consensus node evaluation requirements, and consensus strategy adjustment requirements. The management layer includes: the consensus layer, which, based on the target management requirements, processes the data to be managed using the management layer, including: when the target management requirements include consensus strategy selection requirements, selecting a consensus strategy in a hybrid consensus mechanism based on the target management requirements; when the target management requirements include data acquisition requirements, determining the consensus nodes for acquiring data based on the data to be managed, and obtaining multiple... A consensus node is established, and the node consensus result and voting data of each first consensus node are obtained. When the target management requirements include evaluation requirements, based on the data to be managed, consensus nodes whose credibility needs to be evaluated are determined, resulting in multiple second consensus nodes. Based on the behavioral data of each second consensus node, a preset evaluation model is used to evaluate the credibility of the second consensus node and obtain the evaluation result. The behavioral data includes at least one of the following: node consensus result and voting data. When the target management requirements include consensus strategy adjustment requirements, based on the data to be managed, consensus nodes whose consensus strategy needs to be adjusted are determined, resulting in multiple third consensus nodes. The consensus strategy of each third consensus node is then adjusted.

[0183] The processor can also invoke information and applications stored in the memory via a transmission device to perform the following steps: Target management requirements include: management requirements of the incentive layer; the management layer to be managed includes: the incentive layer; based on the target management requirements, the management layer to be managed processes the data to be managed, including: based on the data to be managed, determining the consensus nodes to be managed by the incentive layer, obtaining multiple fourth consensus nodes; obtaining the credibility assessment result of each fourth consensus node; based on the credibility assessment result of each fourth consensus node, scoring the behavioral data of each fourth consensus node to obtain a score value for each fourth consensus node; based on the score value of each fourth consensus node, distributing rewards to each fourth consensus node using a reward mechanism.

[0184] The processor can also call the information and applications stored in the memory through the transmission device to perform the following steps: the target management requirements include: the lifecycle management requirements of the contract layer and the application layer; the data to be managed includes: smart contracts; the management layer includes: the contract layer and the application layer; based on the target management requirements, the management layer processes the data to be managed, including: if the blockchain underlying framework reaches the first preset period at the current moment, then test the smart contract; if the blockchain underlying framework reaches the second preset period at the current moment, then upgrade the smart contract.

[0185] The processor can also call the information and application programs stored in the memory through the transmission device to perform the following steps: The target management requirements include: the need for cross-layer management of the multi-layer architecture; the data to be managed includes: the operating status data of the multi-layer architecture; based on the target management requirements, the data to be managed is processed by the management layer, including: collecting the operating status data of each layer in the multi-layer architecture; performing anomaly detection on the operating status data, obtaining the detection results, and adjusting the multi-layer architecture based on the detection results.

[0186] By employing the embodiments of this application, a multi-layered management of the blockchain underlying framework is achieved by combining zero-knowledge proof strategies, homomorphic encryption strategies, and hybrid consensus mechanisms. This avoids the situation in related technologies where data management of the blockchain underlying framework relies on manual intervention and has high data management complexity, thereby achieving the technical effect of reducing the complexity of data management of the blockchain underlying framework and improving the security of the blockchain underlying framework.

[0187] Those skilled in the art will understand that Figure 6 The structure shown is for illustrative purposes only. Electronic devices can also be smartphones, tablets, handheld computers, mobile internet devices (MIDs), PADs, and other terminal devices. Figure 6 This does not limit the structure of the aforementioned electronic device. For example, electronic devices may also include components that are more... Figure 6The more or fewer components shown (such as network interfaces, display devices, etc.), or having the same Figure 6 The different configurations shown.

[0188] Those skilled in the art will understand that all or part of the steps in the various methods of the above embodiments can be implemented by a program instructing the hardware related to the terminal device. The program can be stored in a computer-readable storage medium, which may include: flash drive, read-only memory (ROM), random access memory (RAM), disk or optical disk, etc.

[0189] Example 5

[0190] Embodiments of this application also provide a storage medium. Optionally, in this embodiment, the storage medium can be used to store the program code executed by the data processing method for the blockchain framework provided in Embodiment 1.

[0191] Optionally, in this embodiment, the storage medium may be located in any computer terminal in a group of computer terminals in a computer network, or in any mobile terminal in a group of mobile terminals.

[0192] This application also provides a computer program product that, when executed on a data processing device, is adapted to perform data processing method steps for a blockchain framework.

[0193] The sequence numbers of the embodiments in this application are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.

[0194] In the above embodiments of this application, the descriptions of each embodiment have different focuses. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions of other embodiments.

[0195] In the several embodiments provided in this application, it should be understood that the disclosed technical content can be implemented in other ways. The device embodiments described above are merely illustrative; for example, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the displayed or discussed mutual coupling, direct coupling, or communication connection may be through some interfaces; the indirect coupling or communication connection between units or modules may be electrical or other forms.

[0196] The units described as separate components may or may not be physically separate. 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 the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0197] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0198] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part 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 to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as a USB flash drive, read-only memory (ROM), random access memory (RAM), portable hard drive, magnetic disk, or optical disk.

[0199] The above description is only a preferred embodiment of this application. It should be noted that for those skilled in the art, several improvements and modifications can be made without departing from the principle of this application, and these improvements and modifications should also be considered within the scope of protection of this application.

Claims

1. A data processing method for a blockchain framework, characterized in that, The method comprises the following steps: obtaining a management requirement of to-be-managed data to obtain a target management requirement, wherein the to-be-managed data comprises to-be-managed data in a blockchain bottom chain framework, the blockchain bottom chain framework is a multi-layer architecture, the multi-layer architecture comprises a data layer, a network layer, a consensus layer, an incentive layer, a contract layer and an application layer, the data layer comprises zero-knowledge proof strategy and homomorphic encryption strategy, the consensus layer comprises a hybrid consensus mechanism, and the incentive layer comprises a reward mechanism of a consensus node, and the contract layer comprises a smart contract; determining a to-be-managed layer based on the target management requirement, wherein the to-be-managed layer comprises at least one layer of the multi-layer architecture; processing the to-be-managed data by using the to-be-managed layer based on the target management requirement.

2. The data processing method according to claim 1, characterized in that, The target management requirement comprises at least one of data encryption and storage requirement, data verification and security analysis requirement, and data traceability requirement, the to-be-managed layer is the data layer, and processing the to-be-managed data by using the to-be-managed layer based on the target management requirement comprises: in a case where the target management requirement comprises the data encryption and storage requirement, performing encryption processing on the to-be-managed data by using the zero-knowledge proof strategy and the homomorphic encryption strategy to obtain encrypted to-be-managed data, and storing the encrypted to-be-managed data; in a case where the target management requirement comprises the data verification and security analysis requirement, verifying and performing security analysis on target encrypted data based on the zero-knowledge proof strategy, wherein the target encrypted data comprises at least one of the encrypted data stored in the data layer and the encrypted to-be-managed data; in a case where the target management requirement comprises the data traceability requirement, adding an identifier and a time stamp to the to-be-managed data, and recording data flow of the to-be-managed data based on the identifier and the time stamp.

3. The data processing method of claim 1, wherein, The target management requirement comprises a data management requirement of the network layer, the to-be-managed layer comprises the network layer, and the to-be-managed data comprises preset parameters of the network layer, and processing the to-be-managed data by using the to-be-managed layer based on the target management requirement comprises: obtaining parameter values of the preset parameters of the network layer to obtain a parameter set, wherein the preset parameters comprise at least one of network traffic, a connection state of a node in the network layer and communication delay; determining whether the parameter values in the parameter set meet a preset adjustment condition to obtain a determination result; in a case where the determination result indicates that the parameter values in the parameter set meet the preset adjustment condition, adjusting a network protocol and a communication mechanism used by the network layer.

4. The data processing method of claim 1, wherein, The target management requirement comprises a consensus processing requirement of the consensus layer, the consensus processing requirement comprises at least one of a consensus strategy selection requirement, a data acquisition requirement, an evaluation requirement of a consensus node and a consensus strategy adjustment requirement, the to-be-managed layer comprises the consensus layer, and processing the to-be-managed data by using the to-be-managed layer based on the target management requirement comprises: In a case where the target management requirement comprises the consensus strategy selection requirement, a consensus strategy is selected in the hybrid consensus mechanism based on the target management requirement; In a case where the target management requirement comprises the data acquisition requirement, consensus nodes for to-be-acquired data are determined based on the to-be-managed data, a plurality of first consensus nodes are obtained, and node consensus results of each first consensus node and voting data of each first consensus node are acquired; In a case where the target management requirement comprises the evaluation requirement, consensus nodes for to-be-evaluated credibility are determined based on the to-be-managed data, a plurality of second consensus nodes are obtained, and a preset evaluation model is used to evaluate the credibility of each second consensus node based on behavior data of the second consensus node to obtain an evaluation result, wherein the behavior data comprises at least one of the following: a node consensus result and voting data; In a case where the target management requirement comprises the consensus strategy adjustment requirement, consensus nodes for to-be-adjusted consensus strategies are determined based on the to-be-managed data, a plurality of third consensus nodes are obtained, and a consensus strategy of each third consensus node is adjusted.

5. The data processing method according to claim 4, characterized in that, The target management requirement comprises a management requirement of the incentive layer, the to-be-managed layer comprises the incentive layer, and the to-be-managed data is processed by using the to-be-managed layer based on the target management requirement, comprising: Consensus nodes to be managed by the incentive layer are determined based on the to-be-managed data, and a plurality of fourth consensus nodes are obtained; A credibility evaluation result of each fourth consensus node is acquired; Behavior data of each fourth consensus node is scored based on the credibility evaluation result of each fourth consensus node, and a score value of each fourth consensus node is obtained; Based on the score value of each fourth consensus node, a reward mechanism is used to issue a reward for each fourth consensus node.

6. The data processing method of claim 1, wherein, The target management requirement comprises a lifecycle management requirement of the contract layer and the application layer, and the to-be-managed data comprises the smart contract. The to-be-managed layer comprises the contract layer and the application layer, and the to-be-managed data is processed by using the to-be-managed layer based on the target management requirement, comprising: If the blockchain bottom chain framework reaches a first preset period at a current time, the smart contract is tested; If the blockchain bottom chain framework reaches a second preset period at the current time, the smart contract is upgraded.

7. The data processing method of claim 1, wherein, The target management requirement comprises a requirement for cross-layer management of the multi-layer architecture, and the to-be-managed data comprises running state data of the multi-layer architecture. The to-be-managed data is processed by using the to-be-managed layer based on the target management requirement, comprising: Running state data of each layer of the multi-layer architecture is collected; The running state data is subjected to abnormality detection to obtain a detection result, and the multi-layer architecture is adjusted based on the detection result.

8. A data processing apparatus for a blockchain framework, characterized in that, Comprising: An acquisition unit is configured to acquire a management requirement of to-be-managed data, and obtain a target management requirement. The to-be-managed data includes to-be-managed data in a blockchain bottom chain framework. The blockchain bottom chain framework is a multi-layer architecture, which includes a data layer, a network layer, a consensus layer, an incentive layer, a contract layer, and an application layer. The data layer includes zero-knowledge proof strategies and homomorphic encryption strategies. The consensus layer includes a hybrid consensus mechanism. The incentive layer includes a reward mechanism of a consensus node. The contract layer includes a smart contract. A determination unit is configured to determine a to-be-managed layer based on the target management requirement. The to-be-managed layer includes at least one layer in the multi-layer architecture. A processing unit is configured to process the to-be-managed data by using the to-be-managed layer based on the target management requirement.

9. A computer-readable storage medium, characterized in that, The computer readable storage medium includes a stored executable program. When the executable program is running, the computer readable storage medium controls a device where the computer readable storage medium is located to perform the data processing method for a blockchain framework in any one of claims 1 to 7.

10. A computer program product comprising computer instructions, characterized in that, The computer instructions are executed by a processor to implement the steps of the data processing method for the blockchain framework in any one of claims 1 to 7.

Images