Message pushing method and device

Abstract

The embodiment of the application provides a message pushing method and device, relates to the field of blockchains, and can also be applied to the financial field, and the method comprises the following steps: pushing a transaction message received by a consensus node to a backing node, so that the backing node performs backing filtering on the transaction message; pushing a backing filtering result of the backing node to a security node and the consensus node in parallel to perform security checking, and making the consensus node receive the backing filtering result; pushing the backing filtering result of the consensus node to an execution node, and pushing an execution result to the security node and a storage node in parallel, so that the security node performs security checking on the execution result, and the storage node performs on-chain storage on the execution result. The application can realize parallel acceleration of message pushing between module nodes under one blockchain transaction or multiple blockchain transactions.

Description

Technical Field

[0001] This application relates to the field of blockchain, and can also be applied to the financial field, specifically to a message push method and device. Background Technology

[0002] In traditional blockchain architectures, a single node typically handles multiple functions, including consensus, storage, communication, execution, and security. However, as transaction volume increases, node hardware configuration becomes a bottleneck limiting performance improvements. To improve overall efficiency, traditional blockchains have begun to adopt modular designs, breaking down different functions into independent modules. This modular decoupling improves overall efficiency to some extent, allowing nodes to select the necessary functional modules as needed, thereby enhancing performance.

[0003] However, after the modular decoupling of the blockchain, the interaction between the modules is usually synchronous. This means that messages between modules need to be transmitted synchronously in sequence, which reduces the transmission efficiency within the blockchain network nodes. When processing a large number of transactions, the synchronous push method further slows down the processing speed, limiting the processing performance of the entire blockchain network. Summary of the Invention

[0004] To address the problems in the existing technology, this application provides a message push method and apparatus that can achieve parallel acceleration of message push between module nodes under one or multiple blockchain transactions.

[0005] To solve at least one of the above problems, this application provides the following technical solution:

[0006] According to a first aspect of the embodiments of this application, this application provides a message push method applied to a message push node in a blockchain network, wherein the message push node is connected to a consensus node, an endorsement node, an execution node, a security node, and a storage node, and the method includes:

[0007] The transaction message received by the consensus node is pushed to the endorsement node so that the endorsement node can perform endorsement filtering on the transaction message;

[0008] The endorsement filtering results of the endorsing node are pushed in parallel to the security node and the consensus node, so that the security node performs security verification on the endorsement filtering results and the consensus node receives the endorsement filtering results.

[0009] The endorsement filtering result of the consensus node is pushed to the execution node to obtain the execution result, and the execution result is pushed in parallel to the storage node and the security node, so that the security node performs security verification on the execution result and the storage node stores the execution result on the chain.

[0010] According to any embodiment of this application, it further includes:

[0011] During the process of pushing the transaction message of the consensus node to the endorsing node, the transaction message is also pushed to other consensus nodes in the blockchain network in parallel.

[0012] During the process of pushing the execution results to the storage node and the security node in parallel, the execution results are also pushed to other consensus nodes of the blockchain network in parallel.

[0013] After the storage node stores the execution result on the blockchain, the stored result is pushed in parallel to other consensus nodes of the blockchain network.

[0014] According to any embodiment of this application, the message push node is connected to the verification node, and the step of pushing the execution result to the storage node and the security node in parallel includes:

[0015] The execution result is pushed to the verification node so that the verification node can verify the validity of the execution result.

[0016] If the verification passes, the execution result of the verification node is pushed in parallel to the storage node and the security node, so that the security node performs security verification on the execution result and the storage node stores the execution result on the blockchain.

[0017] According to any embodiment of this application, the process of pushing the execution result to the verification node further includes:

[0018] The consensus parameters of the consensus node are pushed in parallel to the storage node and the security node, so that the security node performs security verification on the consensus parameters and the storage node determines the corresponding block information based on the consensus parameters.

[0019] According to any embodiment of this application, before pushing the transaction message received by the consensus node to the endorsing node, the method further includes:

[0020] In response to receiving a storage resource contribution instruction from a user, the storage node is configured in the client corresponding to the user;

[0021] In response to receiving a computing resource contribution instruction from a user, the consensus node and the execution node are set up in the client corresponding to the user;

[0022] In response to receiving a bandwidth resource contribution instruction sent by a user, the endorsement node and the message push node are set for the client corresponding to the user;

[0023] The transaction message is received by at least one client that includes the storage node, consensus node, execution node, endorsement node, and message push node.

[0024] According to any embodiment of this application, it further includes:

[0025] In response to receiving a user's distrust instruction regarding the setting results, the client corresponding to the user is associated with the security node;

[0026] In response to receiving a user's trust instruction on the setting result, the security nodes in the setting result are pruned to obtain a setting result that deletes the security nodes.

[0027] According to a second aspect of the embodiments of this application, this application provides a message push device applied to a message push node in a blockchain network, wherein the message push node is connected to a consensus node, an endorsement node, an execution node, a security node, and a storage node, and the device includes:

[0028] The transaction task delivery module is used to: push the transaction message received by the consensus node to the endorsement node, so that the endorsement node can perform endorsement filtering on the transaction message;

[0029] The parallel push module for filtering results is used to: push the endorsement filtering results of the endorsement node in parallel to the security node and the consensus node, so that the security node performs security verification on the endorsement filtering results and the consensus node receives the endorsement filtering results;

[0030] The parallel push module for execution results is used to: push the endorsement filtering result of the consensus node to the execution node to obtain the execution result, and push the execution result in parallel to the storage node and the security node, so that the security node performs security verification on the execution result and the storage node stores the execution result on the blockchain.

[0031] According to any embodiment of this application, a consensus node synchronization module is further included, used for:

[0032] During the process of pushing the transaction message of the consensus node to the endorsing node, the transaction message is also pushed to other consensus nodes in the blockchain network in parallel.

[0033] During the process of pushing the execution results to the storage node and the security node in parallel, the execution results are also pushed to other consensus nodes of the blockchain network in parallel.

[0034] After the storage node stores the execution result on the blockchain, the stored result is pushed in parallel to other consensus nodes of the blockchain network.

[0035] According to any embodiment of this application, the message push node is connected to the verification node, and the parallel push module for execution results, when pushing the execution results to the storage node and the security node in parallel, is specifically used for:

[0036] The execution result is pushed to the verification node so that the verification node can verify the validity of the execution result.

[0037] If the verification passes, the execution result of the verification node is pushed in parallel to the storage node and the security node, so that the security node performs security verification on the execution result and the storage node stores the execution result on the blockchain.

[0038] According to any embodiment of this application, during the process of pushing the execution result to the verification node, a block parameter parallel push module is further included, used for:

[0039] The consensus parameters of the consensus node are pushed in parallel to the storage node and the security node, so that the security node performs security verification on the consensus parameters and the storage node determines the corresponding block information based on the consensus parameters.

[0040] According to any embodiment of this application, before pushing the transaction message received by the consensus node to the endorsing node, a node configuration module is further included, used for:

[0041] In response to receiving a storage resource contribution instruction from a user, the storage node is configured in the client corresponding to the user;

[0042] In response to receiving a computing resource contribution instruction from a user, the consensus node and the execution node are set up in the client corresponding to the user;

[0043] In response to receiving a bandwidth resource contribution instruction sent by a user, the endorsement node and the message push node are set for the client corresponding to the user;

[0044] The transaction message is received by at least one client that includes the storage node, consensus node, execution node, endorsement node, and message push node.

[0045] According to any embodiment of this application, a security node configuration module is further included, used for:

[0046] In response to receiving a user's distrust instruction regarding the setting results, the client corresponding to the user is associated with the security node;

[0047] In response to receiving a user's trust instruction on the setting result, the security nodes in the setting result are pruned to obtain a setting result that deletes the security nodes.

[0048] According to a third aspect of the embodiments of this application, this application provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the program to implement the steps of the message push method.

[0049] According to a fourth aspect of the embodiments of this application, this application provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps of the message push method described above.

[0050] According to a fifth aspect of the embodiments of this application, this application provides a computer program product, including a computer program / instructions, which, when executed by a processor, implement the steps of the message push method described above.

[0051] As can be seen from the above technical solution, this application provides a message push method and apparatus, which pushes the transaction message received by the consensus node to the endorsement node so that the endorsement node can perform endorsement filtering on the transaction message; pushes the endorsement filtering result of the endorsement node to the security node and the consensus node in parallel so that the security node can perform security verification on the endorsement filtering result and the consensus node can receive the endorsement filtering result; pushes the endorsement filtering result of the consensus node to the execution node to obtain the execution result, and pushes the execution result to the storage node and the security node in parallel so that the security node can perform security verification on the execution result and the storage node can store the execution result on the chain, which can realize parallel acceleration of message push between module nodes under one blockchain transaction or multiple blockchain transactions. Attached Figure Description

[0052] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0053] Figure 1 This is one of the schematic diagrams of the message push method in the embodiments of this application;

[0054] Figure 2 This is one of the flowcharts illustrating the message push method in this application embodiment;

[0055] Figure 3 This is a second flowchart illustrating the message push method in this application embodiment;

[0056] Figure 4 This is the third flowchart illustrating the message push method in this application embodiment;

[0057] Figure 5 This is a second schematic diagram of the message push method in the embodiments of this application;

[0058] Figure 6 This is the fourth flowchart illustrating the message push method in the embodiments of this application;

[0059] Figure 7 This is the fifth flowchart illustrating the message push method in the embodiments of this application;

[0060] Figure 8 This is the sixth flowchart illustrating the message push method in this application embodiment;

[0061] Figure 9 This is the seventh flowchart illustrating the message push method in this application embodiment;

[0062] Figure 10 This is one of the structural diagrams of the message push device in the embodiments of this application;

[0063] Figure 11 This is a schematic diagram of the structure of the electronic device in the embodiments of this application. Detailed Implementation

[0064] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0065] The acquisition, storage, use, and processing of data in this application all comply with the relevant provisions of national laws and regulations.

[0066] Considering that after the blockchain module completes modular decoupling, synchronous push leads to a reduction in the transmission efficiency within the blockchain network nodes, and when processing a large number of transactions, synchronous push further slows down the processing speed, limiting the processing performance of the entire blockchain network, this application provides a message push method and apparatus.

[0067] In order to achieve parallel acceleration of message push between module nodes under a single blockchain transaction or multiple blockchain transactions, this application provides an embodiment of a message push method, wherein the embodiment is applied to a message push node in a blockchain network, and the message push node is connected to a consensus node, an endorsement node, an execution node, a security node, and a storage node.

[0068] For example, this application discloses a modular architecture design for a blockchain system. Following the complete blockchain processing flow, the functions of blockchain nodes are modularized, proposing a design for modular blockchain nodes, such as... Figure 1 As shown, this application breaks down the complete blockchain node function into endorsement node 11, consensus node 12, verification node 13, execution node 14, message push node 15, storage module 16, security node 17, etc.

[0069] Specifically, the message push node is a key node proposed in this application, possessing several crucial functions for enabling parallel message transmission between blockchain nodes. The functions of the message push node are explained in detail below:

[0070] First, the message push node can construct a directed acyclic graph (DAG) for cross-module transaction execution. That is, the message push node can sort multiple transactions according to their dependencies and determine the execution order. By constructing the DAG, the message push node can accelerate the parallel execution of transactions, improving the overall system performance and throughput.

[0071] In addition, the message push node can also push the transaction execution results to external clients or cross-chain transaction initiators and perform corresponding callback processing to promptly transmit the transaction execution results to relevant parties so that they can obtain the execution status and results of the transaction in a timely manner.

[0072] Finally, the message push node integrates multiple communication protocols, such as HTTP, HTTPS, and gRPC, to communicate with other nodes. It can select the appropriate communication protocol for message delivery as needed. It also supports message subscription and push functions, enabling efficient transmission of intermediate state messages to ensure coordination and synchronization between nodes, allowing nodes to receive and process critical messages in real time.

[0073] The endorsing nodes can reject transactions that are non-compliant, cannot be verified, or are accessed due to network overload, based on pre-set transaction filtering rules. They assess the compliance of transactions and process those that meet the criteria. After accepting a transaction, the endorsing node can endorse and sign the transaction execution result to confirm its credibility. According to privacy requirements, the endorsing node can also perform zero-knowledge proofs to prove that the transaction execution result complies with the rules while protecting transaction privacy. Finally, the endorsing node returns the processed transaction execution result to the blockchain client for subsequent verification and use.

[0074] The consensus nodes are crucial nodes in a distributed blockchain network. After a series of transactions, different consensus nodes can negotiate transaction results through multiple rounds of consensus message interaction to achieve eventual consistency. The task of the consensus nodes is to ensure that transactions are not duplicated, missing, or out of order during the consensus process. Through consensus algorithms and rules, different blockchain nodes can reach a consensus and confirm the validity of transactions. Message push nodes are responsible for synchronizing data to other blockchain nodes to facilitate collaborative work in the consensus process.

[0075] The verification nodes are primarily responsible for verifying the identity and validity of received blockchain transactions. Identity verification includes verifying the identities of the transaction initiator and endorser. The underlying verification technology can utilize services provided by secure nodes, employing techniques such as hashing, signature verification, and decryption to verify the legitimacy of identities. The validity verification of transaction results includes fee verification, plaintext result verification of the read / write set, and zero-knowledge proof verification of the read / write set. The underlying verification technology can be implemented using services provided by secure nodes.

[0076] The execution node is a node that executes pre-agreed processing logic according to the smart contract specified in the transaction. It is responsible for processing the transaction based on the code logic in the smart contract and generating a transaction result read / write set. This transaction result read / write set can be in plaintext or processed using privacy computing techniques to protect transaction privacy. The task of the execution node is to execute the transaction logic according to the contract rules and generate valid transaction results for subsequent verification and storage.

[0077] The storage nodes integrate various database and caching technologies, including relational databases, key-value databases, unstructured databases, stand-alone databases, embedded databases, and multi-level caching. They are responsible for the persistent storage of file-type and relational data in the blockchain, or for managing multi-level caching. Storage nodes play a crucial role in the blockchain system by storing and managing data, ensuring data security and reliability.

[0078] The secure node incorporates a range of cryptography-related processing technologies and facilities, including hashing, signature verification, encryption / decryption, trusted execution environments, hardware encryption / decryption, and privacy computing techniques (such as secure multi-party computation, zero-knowledge proofs, and differential privacy). The secure node's task is to provide cryptography-related functions and services to protect the security of the blockchain system, managing keys, certificates, and other cryptographic files to ensure the confidentiality, integrity, and trustworthiness of transactions and data. The secure node plays a crucial role in the entire scheme, providing security guarantees for the blockchain system.

[0079] The message push node, security node, and storage node are scalable, capable of fully utilizing computer resources to expand to multiple replicas, thereby improving the overall efficiency of the blockchain node. When the security processing efficiency of the blockchain node reaches a bottleneck, multiple security nodes can be added to process security-related functions in parallel. When the message push of the blockchain node is lagging, multiple message push nodes can be added to process message transmission in parallel. When the storage of blockchain messages reaches a bottleneck, multiple storage nodes can be added to process security-related functions in parallel.

[0080] See Figure 2 The message push method described in this application is applied to message push nodes in a blockchain network, and specifically includes the following:

[0081] Step S101: Push the transaction message received by the consensus node to the endorsement node so that the endorsement node can perform endorsement filtering on the transaction message.

[0082] The transaction message, transmitted within the blockchain network, contains data including transaction information. This transaction message includes the transaction request initiated by the participants and related parameters. By pushing the transaction messages received by the consensus node to the endorsing node, the endorsing node can perform endorsement filtering on these transaction messages. It filters according to pre-set rules, rejecting non-compliant, unverifiable, or network-overloaded transaction messages, ensuring that only qualified transaction messages are further processed, thus improving the security and efficiency of the entire blockchain system.

[0083] Step S102: Push the endorsement filtering result of the endorsement node to the security node and the consensus node in parallel, so that the security node performs security verification on the endorsement filtering result and the consensus node receives the endorsement filtering result.

[0084] The endorsement filtering result represents the filtering result of the transaction messages obtained after processing by the endorsement node. The result includes accepted transaction messages, transaction messages that meet the rules, and other relevant information.

[0085] The endorsement filtering results from the endorsing node are pushed to the security node and the consensus node in parallel. That is, the endorsing node will transmit the filtering results to both the security node and the consensus node simultaneously so that they can perform subsequent processing at the same time.

[0086] Specifically, the security node can perform security verification and validation on the endorsement filtering results, such as using cryptographic techniques to perform hashing, signature verification, and decryption operations on the data to ensure the integrity, authenticity, and trustworthiness of the data. The consensus node receives the endorsement filtering results from the endorsing nodes to obtain the latest endorsement information and uses this information to negotiate transaction results during the consensus process.

[0087] By pushing the endorsement filtering results from endorsing nodes to security nodes and consensus nodes in parallel, security nodes can perform security verification on the filtering results to ensure the trustworthiness and integrity of the data. Simultaneously, consensus nodes can receive the endorsement filtering results and use them in the consensus process to negotiate the final transaction outcome.

[0088] Step S103: Push the endorsement filtering result of the consensus node to the execution node to obtain the execution result, and push the execution result in parallel to the storage node and the security node, so that the security node performs security verification on the execution result and the storage node stores the execution result on the chain.

[0089] The endorsement filtering results of the consensus node will be pushed to the execution node to obtain the execution results. At the same time, the execution results will be pushed to the storage node and the security node in parallel, so that the security node can perform security verification on the execution results and the storage node can store the execution results on the chain.

[0090] The execution result refers to the transaction result obtained after the operation is executed through the smart contract, including the read / write set and other related information obtained after processing the transaction.

[0091] By pushing the endorsement filtering results from consensus nodes to execution nodes, the execution results of transactions can be obtained. Simultaneously, the execution results are pushed to storage and security nodes in parallel. Storage nodes can store the execution results on the blockchain, ensuring persistent data storage and blockchain data integrity, while security nodes can perform security verification on the execution results, ensuring data trustworthiness. This improves the security and reliability of transactions and the overall stability of the blockchain system.

[0092] As can be seen from the above description, the message push method provided in this application embodiment realizes the synchronous to asynchronous process of transaction flow in the blockchain network through message push nodes, and promotes the parallel and rapid advancement of transaction flow among multiple modular nodes, thereby improving the data processing efficiency of the blockchain network.

[0093] Specifically, firstly, the message push node acts as an intermediary for message transmission, receiving messages from various modular nodes such as consensus nodes and endorsing nodes, and asynchronously pushing these messages to the relevant receiving nodes. This allows the sending node to immediately continue executing subsequent operations without waiting for a response from the receiving node. With the assistance of the message push node, the transaction process is transformed from synchronous to asynchronous.

[0094] Furthermore, the asynchronous transaction process allows modular nodes to process transactions in parallel without waiting for other nodes to complete. For example, after the endorsing node endorses and filters a transaction, the result can be pushed in parallel to the security and consensus nodes for security verification and consensus reaching. Simultaneously, the execution node can immediately begin executing the smart contract and providing the execution result upon receiving the endorsement filtering result from the consensus node. This parallel processing method accelerates the transaction process and improves the data processing efficiency of the blockchain network.

[0095] Finally, by implementing asynchronous processing and parallel execution of the transaction process, this application effectively improves the data processing efficiency of the blockchain network. Each modular node can perform its own tasks simultaneously without waiting for other nodes to complete, thus fully utilizing system resources and parallel computing capabilities. This accelerates transaction confirmation and processing, reduces transaction latency, and improves the overall network throughput and responsiveness.

[0096] In one embodiment of the message push method of this application, see [link to relevant documentation]. Figure 3 It can also specifically include the following:

[0097] Step S104: During the process of pushing the transaction message of the consensus node to the endorsement node, the transaction message is pushed to other consensus nodes of the blockchain network in parallel.

[0098] Step S105: During the process of pushing the execution result to the storage node and the security node in parallel, the execution result is also pushed to other consensus nodes of the blockchain network in parallel;

[0099] Step S106: After the storage node stores the execution result on the blockchain, the storage result is pushed to other consensus nodes of the blockchain network in parallel.

[0100] First, in the process of pushing the transaction message of the consensus node to the endorsing node, this application simultaneously pushes the transaction message to other consensus nodes in the blockchain network. That is, in addition to the endorsing node, other consensus nodes will also receive the transaction message at the same time, so that other consensus nodes can learn about the new transaction and participate in the subsequent consensus process, ensuring that the transaction can be widely verified and confirmed, and completing the update of the consensus node list, activation and maintenance of communication connections.

[0101] After the execution node receives the transaction execution result, it can simultaneously push the result to the storage node and the security node to ensure persistent storage of the result, and the security node can perform security verification on the result. At the same time, the execution result is also pushed to other consensus nodes in the blockchain network so that they can obtain the execution result information and participate in the subsequent consensus process.

[0102] After the storage node stores the execution result on the blockchain, the stored result needs to be pushed in parallel to other consensus nodes in the blockchain network. This allows other consensus nodes to obtain the stored result and proceed with the subsequent consensus process accordingly. By pushing the stored result to other consensus nodes, the storage result can be broadcast, ensuring that each consensus node in the network receives a copy of the stored result.

[0103] In the scheme described in this application, transaction messages, execution results, and storage results are pushed in parallel to other consensus nodes in the blockchain network to ensure transaction verification, security checks of execution results, and broadcasting of storage results. This increases node participation and data reliability in the network, further improving the security and efficiency of the entire blockchain network.

[0104] In one embodiment of the message push method of this application, see [link to relevant documentation]. Figure 4 The message push node is connected to the verification node, and the parallel push of the execution result to the storage node and the security node may further include the following:

[0105] Step S103A: Push the execution result to the verification node so that the verification node can verify the validity of the execution result.

[0106] Step S103B: If the verification passes, the execution result of the verification node is pushed to the storage node and the security node in parallel, so that the security node performs security verification on the execution result and the storage node stores the execution result on the blockchain.

[0107] The message push node and the verification node establish a connection for information transmission and verification. After the execution node receives the execution result, the result is pushed to the verification node in parallel, allowing the verification node to validate the result and ensure it conforms to predetermined rules and standards. The verification node checks whether the execution result is legal and complete, and verifies the correctness of various information and data involved.

[0108] Once verification is successful, the verification node pushes the execution result to both the storage node and the security node in parallel. This allows the storage node to store the execution result on the blockchain, permanently preserving it for future retrieval and auditing. Simultaneously, the security node performs security checks on the execution result to ensure it is not subject to tampering or forgery. The security node uses cryptographic techniques and facilities, such as hashing, signature verification, and encryption / decryption, to perform security checks and verifications on the execution result.

[0109] Preferably, the process of pushing the execution result to the verification node further includes:

[0110] The consensus parameters of the consensus node are pushed in parallel to the storage node and the security node, so that the security node performs security verification on the consensus parameters and the storage node determines the corresponding block information based on the consensus parameters.

[0111] The consensus parameters represent various information parameters related to consensus, such as transaction results, consensus state, signature of the target consensus node, encryption and privacy computation parameters, etc. These parameters are used to ensure the security and correctness of the consensus process.

[0112] The purpose of pushing consensus parameters to secure nodes is to verify the security of these parameters. Secure nodes use cryptographic techniques and facilities, such as hashing, signature verification, and encryption / decryption, to verify the consensus parameters, ensuring they have not been tampered with, forged, or maliciously modified. The security verification by secure nodes ensures the integrity and credibility of the consensus parameters, providing a reliable reference and basis for subsequent consensus processes.

[0113] Simultaneously, the purpose of pushing consensus parameters to storage nodes in parallel is to determine the corresponding block information based on these parameters. Storage nodes, based on relevant information in the consensus parameters, such as the requested latest block height and block-related information like hash values, determine the location and content of the block to be stored. This allows storage nodes to subsequently assemble the execution results and related consensus parameters into a block according to the blockchain's structure and rules, and store it in the blockchain network, achieving permanent data preservation and immutability.

[0114] In summary, this application establishes a connection between the message push node and the verification node, allowing the execution result to be pushed in parallel to the storage node and the security node, and then validated by the verification node. This ensures the security, integrity, and reliability of the execution result, and enables on-chain storage of the execution result, providing reliable data storage and security guarantees.

[0115] To further illustrate this application, this application also provides a specific application example of using the aforementioned message push device to implement the message push method. After a transaction is connected to the blockchain system, a cross-module execution flowchart is generated via the message push node, as shown below. Figure 5 As shown, specifically:

[0116] Message A indicates that the message push node pushes the transaction message in parallel to other consensus nodes in the blockchain network, completing the update of the consensus node list and the maintenance of communication connections.

[0117] Message B indicates that the message push node pushes the transaction message received by the consensus node to the endorsement node, thus completing the consensus node status notification.

[0118] Message C indicates that the message push node pushes the endorsement filtering result of the endorsement node to the security node to complete the legitimate authentication of the request.

[0119] Message D indicates that the message push node pushes the endorsement filtering result of the endorsement node to the consensus node, thus completing the push of the filtered transaction.

[0120] Message E indicates that the message push node pushes the endorsement filtering result of the consensus node to the execution node to obtain the transaction execution result.

[0121] Message F indicates that the message push node pushes the consensus parameters of the consensus node to the security node, including the reading of information such as transaction results, consensus-related status, signature of the target consensus node, encryption and privacy calculation parameters.

[0122] Message G represents that the message push node pushes the execution result in parallel to other consensus nodes in the blockchain network, completing the transmission of consensus intermediate messages and aligning the states of each stage of consensus.

[0123] Message H indicates that the message push node pushes the consensus parameters of the consensus node to the storage node, requesting the latest block height, hash and other block-related information.

[0124] Message I indicates that after the storage node stores the execution result on the chain, the message push node pushes the stored result in parallel to other consensus nodes in the blockchain network to complete the transmission of consensus block messages.

[0125] Message J indicates that the message push node pushes the execution result of the consensus node to the verification node and reads the verification result.

[0126] Message K indicates that the message push node pushes the execution result of the verification node to the storage node and reads the state data that the verification depends on, such as block height, previous block hash and other information.

[0127] Message L indicates that the message push node pushes the execution result of the verification node to the security node to complete functions such as decryption, signature verification, and privacy calculation parameter verification.

[0128] Message M indicates that the message push node pushes the execution result of the verification node to the storage node, completes the block submission, reads the result after the state change, and advances the consensus to the next stage.

[0129] Finally, the message push node pushes the transaction results, which have completed all stages of processing, to the relevant subscribers.

[0130] Among them, message types A and B are messages from the modular blockchain node initialization phase (such as...). Figure 5 (As shown by the dotted line), the remaining message types are messages triggered by blockchain transaction access (such as...). Figure 5 (Solid lines indicate this). Message types A and B receive special handling; the remaining message types are handled as usual. Figure 5 The DAG structure shown.

[0131] Furthermore, this application also provides a specific flowchart of a message push method applied to the aforementioned message push node, such as... Figure 6 As shown, specifically:

[0132] Step S601: The message push node first processes the concurrent delivery of messages A and B, constructing a cross-module execution flow DAG (e.g., ...). Figure 5 (As shown by the solid line).

[0133] Step S602: The message push node processes the concurrent delivery of messages C and D.

[0134] Step S603: The message push node processes the concurrent delivery of messages E, F, G, H, I, and J.

[0135] Step S604: The message push node processes the concurrent delivery of messages K, L, and M.

[0136] Step S605: The message push node repeats the processing steps 601-604 to advance the transaction process.

[0137] As can be seen from the above description, the message push method provided in this application embodiment realizes the synchronous to asynchronous process of transaction flow in the blockchain network through message push nodes, and promotes the parallel and rapid advancement of transaction flow among multiple modular nodes, thereby improving the data processing efficiency of the blockchain network.

[0138] Specifically, firstly, the message push node acts as an intermediary for message transmission, receiving messages from various modular nodes such as consensus nodes and endorsing nodes, and asynchronously pushing these messages to the relevant receiving nodes. This allows the sending node to immediately continue executing subsequent operations without waiting for a response from the receiving node. With the assistance of the message push node, the transaction process is transformed from synchronous to asynchronous.

[0139] Furthermore, the asynchronous transaction process allows modular nodes to process transactions in parallel without waiting for other nodes to complete. For example, after the endorsing node endorses and filters a transaction, the result can be pushed in parallel to the security and consensus nodes for security verification and consensus reaching. Simultaneously, the execution node can immediately begin executing the smart contract and providing the execution result upon receiving the endorsement filtering result from the consensus node. This parallel processing method accelerates the transaction process and improves the data processing efficiency of the blockchain network.

[0140] Finally, by implementing asynchronous processing and parallel execution of the transaction process, this application effectively improves the data processing efficiency of the blockchain network. Each modular node can perform its own tasks simultaneously without waiting for other nodes to complete, thus fully utilizing system resources and parallel computing capabilities. This accelerates transaction confirmation and processing, reduces transaction latency, and improves the overall network throughput and responsiveness.

[0141] In one embodiment of the message push method of this application, see [link to relevant documentation]. Figure 7 Before pushing the transaction message received by the consensus node to the endorsing node, it may specifically include the following:

[0142] Step S107: In response to receiving a storage resource contribution instruction sent by a user, set the storage node in the client corresponding to the user;

[0143] Step S108: In response to receiving a computing resource contribution instruction sent by a user, set the consensus node and the execution node in the client corresponding to the user;

[0144] Step S109: In response to receiving a bandwidth resource contribution instruction sent by a user, set the endorsement node and the message push node for the client corresponding to the user;

[0145] Step S110: Receive the transaction message through at least one client that includes the storage node, consensus node, execution node, endorsement node, and message push node.

[0146] When the full functionality of a blockchain node is limited by the hardware of a single device, the blockchain functionality can be distributed across multiple devices for processing, thereby utilizing the idle resources of multiple devices to achieve distributed deployment and collaboration of the blockchain network.

[0147] In one exemplary embodiment, when the full functionality of a blockchain node cannot be deployed on a single device, different functions can be distributed across multiple devices for processing. For example, a device with available storage resources can function as a storage node to store blockchain data; a device with available computing resources can function as an execution node to execute smart contracts and process transactions; and a device with specialized encryption hardware can function as a security node to perform cryptographic processing and verification.

[0148] In this distributed deployment, when a user sends a storage resource contribution instruction, the system responds and sets up a storage node for the user's corresponding client. That is, idle devices will be designated as storage nodes to store blockchain data.

[0149] Similarly, when a user sends a command to contribute computing resources, the system responds and sets up consensus and execution nodes for the user's corresponding client. Idle devices will be designated as consensus and execution nodes to assist in the blockchain's consensus process and execute smart contracts.

[0150] Additionally, when a user sends a bandwidth resource contribution instruction, the system responds and sets up an endorsement node and a message push node for the user's corresponding client. Devices with available bandwidth resources will be designated as endorsement nodes and message push nodes for filtering transactions and pushing messages.

[0151] This application enables a client, comprising a storage node, a consensus node, an execution node, an endorsement node, and a message push node, to receive and process transaction messages. This allows different devices in the blockchain network to work collaboratively to complete transaction processing and fulfill network functional requirements. Furthermore, blockchain nodes can be customized according to actual needs and hardware configurations, flexibly deploying various modules on different hardware devices and making full use of idle equipment to build the blockchain network.

[0152] In one embodiment of the message push method of this application, see [link to relevant documentation]. Figure 8 It can also specifically include the following:

[0153] Step S111: In response to receiving a user's distrust instruction regarding the setting result, associate the client corresponding to the user with the security node;

[0154] Step S112: In response to receiving a user's trust instruction on the setting result, the security nodes in the setting result are pruned to obtain a setting result that deletes the security nodes.

[0155] Specifically, when the system receives a user's distrust command, indicating that the user has doubts or distrust regarding the settings, it can take corresponding measures to meet the user's security needs. Specifically, the system will associate the client associated with that user to a security node, enabling the user to access the functions associated with that security node, thereby strengthening the protection of their data and transactions.

[0156] When a user expresses trust in the settings, the system can trim the security nodes in the settings according to the user's requirements. That is, based on the user's trust, the system can delete the security nodes in the settings to achieve a more streamlined configuration.

[0157] Because users have a high level of trust in other parts of the network, believing that these parts already provide sufficient security, the complexity and resource consumption of the blockchain network can be reduced while meeting users' trust requirements by pruning redundant nodes.

[0158] To further illustrate this application, this application also provides a specific application example of implementing a message push method using the aforementioned message push device, as shown in the following flowchart for the modular customization of a blockchain node. Figure 9 As shown, specifically:

[0159] Step S901: The user's deployment environment has passed the storage idle assessment. Ask the user if they are willing to contribute storage resources. If yes, add storage nodes, update the routing of related modules on other nodes, and execute S902; if no, synchronize the storage node routing on other nodes, and the functions involving storage nodes will be completed by other blockchain nodes, and execute S903.

[0160] Step S902: Ask the user whether they trust the local storage environment. If yes, the storage node removes the security node; if no, the storage node is associated with the security node. The storage node can provide storage proof based on the security node's ZKP or OP security technology, while the verification node verifies the storage proof.

[0161] Step S903: The user's deployment environment has passed the computing idle assessment. Ask the user if they are willing to contribute computing resources. If yes, add an execution node, update the execution node routes of other nodes, and proceed to S904; if no, synchronize the execution node routes of other nodes and proceed to S905.

[0162] Step S904: Ask the user if they trust the local execution environment. If yes, the execution node trims the security node; if no, the execution node associates with the security node. The execution node can provide proof of the relationship between the state before and after computation and the relevant business parameters based on the various types of ZKP security technologies of the security node, while the consensus node realizes rapid verification of the numerical relationship between the state and the relevant business parameters.

[0163] Step S905: The user's deployment environment has passed the bandwidth availability assessment. Ask the user if they are willing to act as a transaction entry point. If yes, add an endorsement node, update the endorsement node routes of other nodes, and execute S906; if no, synchronize the endorsement node routes of other nodes and execute S907.

[0164] Step S906: Ask the user if they trust the local network environment. If yes, the endorsement node removes the security node; if no, the endorsement node is associated with the security node to achieve transaction initiator identity authentication and communication protocol encryption.

[0165] Step S907: Determine the modules of the blockchain modular node, trim the message types, generate a customized message push node DAG graph, and complete the creation of the blockchain node.

[0166] Step S908: If the preceding steps involve updating the routing of other nodes in the network, package the update information into a transaction and publish it on the blockchain network.

[0167] This application enables a client, comprising a storage node, a consensus node, an execution node, an endorsement node, and a message push node, to receive and process transaction messages. This allows different devices in the blockchain network to work collaboratively to complete transaction processing and fulfill network functional requirements. Furthermore, blockchain nodes can be customized according to actual needs and hardware configurations, flexibly deploying various modules on different hardware devices and making full use of idle equipment to build the blockchain network.

[0168] When the system receives a user's distrust command, indicating that the user has doubts or distrust regarding the settings, it can take corresponding measures to meet the user's security needs. Specifically, the system will associate the client associated with that user to a security node, enabling the user to access the functions associated with the security node, thereby strengthening the protection of their data and transactions.

[0169] When a user expresses trust in the settings, the system can trim the security nodes in the settings according to the user's requirements. That is, based on the user's trust, the system can delete the security nodes in the settings to achieve a more streamlined configuration.

[0170] To achieve parallel acceleration of message pushing between module nodes under one or multiple blockchain transactions, this application provides an embodiment of a message pushing device for implementing all or part of the aforementioned message pushing method. See [link to embodiment]. Figure 10 A message push node applied to a blockchain network, wherein the message push node is connected to consensus nodes, endorsement nodes, execution nodes, security nodes, and storage nodes, the device comprising:

[0171] The transaction task delivery module 1101 is used to: push the transaction message received by the consensus node to the endorsement node so that the endorsement node can perform endorsement filtering on the transaction message;

[0172] The parallel push module 1102 for filtering results is used to: push the endorsement filtering results of the endorsement node in parallel to the security node and the consensus node, so that the security node performs security verification on the endorsement filtering results and the consensus node receives the endorsement filtering results.

[0173] The parallel push module 1103 for execution results is used to: push the endorsement filtering result of the consensus node to the execution node to obtain the execution result, and push the execution result in parallel to the storage node and the security node, so that the security node performs security verification on the execution result and the storage node stores the execution result on the chain.

[0174] According to any embodiment of this application, a consensus node synchronization module is further included, used for:

[0175] During the process of pushing the transaction message of the consensus node to the endorsing node, the transaction message is also pushed to other consensus nodes in the blockchain network in parallel.

[0176] During the process of pushing the execution results to the storage node and the security node in parallel, the execution results are also pushed to other consensus nodes of the blockchain network in parallel.

[0177] After the storage node stores the execution result on the blockchain, the stored result is pushed in parallel to other consensus nodes of the blockchain network.

[0178] According to any embodiment of this application, the message push node is connected to the verification node, and the parallel push module for execution results, when pushing the execution results to the storage node and the security node in parallel, is specifically used for:

[0179] The execution result is pushed to the verification node so that the verification node can verify the validity of the execution result.

[0180] If the verification passes, the execution result of the verification node is pushed in parallel to the storage node and the security node, so that the security node performs security verification on the execution result and the storage node stores the execution result on the blockchain.

[0181] According to any embodiment of this application, during the process of pushing the execution result to the verification node, a block parameter parallel push module is further included, used for:

[0182] The consensus parameters of the consensus node are pushed in parallel to the storage node and the security node, so that the security node performs security verification on the consensus parameters and the storage node determines the corresponding block information based on the consensus parameters.

[0183] According to any embodiment of this application, before pushing the transaction message received by the consensus node to the endorsing node, a node configuration module is further included, used for:

[0184] In response to receiving a storage resource contribution instruction from a user, the storage node is configured in the client corresponding to the user;

[0185] In response to receiving a computing resource contribution instruction from a user, the consensus node and the execution node are set up in the client corresponding to the user;

[0186] In response to receiving a bandwidth resource contribution instruction sent by a user, the endorsement node and the message push node are set for the client corresponding to the user;

[0187] The transaction message is received by at least one client that includes the storage node, consensus node, execution node, endorsement node, and message push node.

[0188] According to any embodiment of this application, a security node configuration module is further included, used for:

[0189] In response to receiving a user's distrust instruction regarding the setting results, the client corresponding to the user is associated with the security node;

[0190] In response to receiving a user's trust instruction on the setting result, the security nodes in the setting result are pruned to obtain a setting result that deletes the security nodes.

[0191] As can be seen from the above description, the message push device provided in this application embodiment can realize the synchronous to asynchronous process of transaction process in blockchain network through message push node, and promote the parallel and rapid advancement of transaction process among multiple modular nodes, thereby improving the data processing efficiency of blockchain network.

[0192] From a hardware perspective, in order to achieve parallel acceleration of message pushing between module nodes under one or more blockchain transactions, this application provides an embodiment of an electronic device for implementing all or part of the message pushing method, wherein the electronic device specifically includes the following:

[0193] The system comprises a processor, memory, a communications interface, and a bus; wherein the processor, memory, and communications interface communicate with each other via the bus; the communications interface is used to transmit messages between the message push device and core business systems, user terminals, and related databases and other related devices; the logic controller can be a desktop computer, tablet computer, or mobile terminal, etc., and this embodiment is not limited to these. In this embodiment, the logic controller can be implemented with reference to the embodiments of the message push method and the message push device in the embodiments, the content of which is incorporated herein, and repeated details will not be described again.

[0194] It is understood that the user terminal may include smartphones, tablet computers, network set-top boxes, portable computers, desktop computers, personal digital assistants (PDAs), in-vehicle devices, smart wearable devices, etc. Among these, the smart wearable devices may include smart glasses, smartwatches, smart bracelets, etc.

[0195] In practical applications, the message push method can be partially executed on the electronic device side as described above, or all operations can be completed on the client device. The choice can be made based on the processing power of the client device and the limitations of the user's usage scenario. This application does not impose any limitations on this. If all operations are completed on the client device, the client device may further include a processor.

[0196] The aforementioned client device may have a communication module (i.e., a communication unit) that can communicate with a remote server to achieve data transmission. The server may include a server on the task scheduling center side; in other implementation scenarios, it may also include a server on an intermediate platform, such as a server on a third-party server platform that has a communication link with the task scheduling center server. The server may include a single computer device, a server cluster consisting of multiple servers, or a distributed server structure.

[0197] Figure 11 This is a schematic block diagram illustrating the system configuration of the electronic device 9600 according to an embodiment of this application. Figure 11As shown, the electronic device 9600 may include a central processing unit 9100 and a memory 9140; the memory 9140 is coupled to the central processing unit 9100. It is worth noting that... Figure 11 This is an example; other types of structures can also be used to supplement or replace this structure to achieve telecommunications functions or other functions.

[0198] In one embodiment, the message push method functionality can be integrated into the central processing unit 9100. The central processing unit 9100 can be configured to perform the following control:

[0199] Step S101: Push the transaction message received by the consensus node to the endorsement node so that the endorsement node can perform endorsement filtering on the transaction message.

[0200] Step S102: Push the endorsement filtering result of the endorsement node to the security node and the consensus node in parallel, so that the security node performs security verification on the endorsement filtering result and the consensus node receives the endorsement filtering result.

[0201] Step S103: Push the endorsement filtering result of the consensus node to the execution node to obtain the execution result, and push the execution result in parallel to the storage node and the security node, so that the security node performs security verification on the execution result and the storage node stores the execution result on the chain.

[0202] As can be seen from the above description, the electronic device provided in this application embodiment realizes the synchronous to asynchronous process of transaction flow in the blockchain network through message push nodes, and promotes the parallel and rapid advancement of transaction flow among multiple modular nodes, thereby improving the data processing efficiency of the blockchain network.

[0203] In another embodiment, the message push device can be configured separately from the central processing unit 9100. For example, the message push device can be configured as a chip connected to the central processing unit 9100, and the message push method function can be implemented through the control of the central processing unit.

[0204] like Figure 11 As shown, the electronic device 9600 may further include: a communication module 9110, an input unit 9120, an audio processor 9130, a display 9160, and a power supply 9170. It is worth noting that the electronic device 9600 does not necessarily need to include these components. Figure 11 All components shown; in addition, the electronic device 9600 may also include Figure 11 For components not shown, please refer to existing technology.

[0205] like Figure 11As shown, the central processing unit 9100, sometimes also referred to as a controller or operating control, may include a microprocessor or other processor device and / or logic device, which receives inputs and controls the operation of various components of the electronic device 9600.

[0206] The memory 9140 may be, for example, one or more of a cache, flash memory, hard drive, removable media, volatile memory, non-volatile memory, or other suitable devices. It may store the aforementioned failure-related messages, and also store programs for executing those messages. The central processing unit 9100 may execute the program stored in the memory 9140 to perform message storage or processing, etc.

[0207] Input unit 9120 provides input to central processing unit 9100. Input unit 9120 may be, for example, a keypad or touch input device. Power supply 9170 provides power to electronic device 9600. Display 9160 displays images and text. Display may be, for example, an LCD display, but is not limited thereto.

[0208] The memory 9140 can be a solid-state memory, such as a read-only memory (ROM), random access memory (RAM), a SIM card, etc. It can also be a memory that retains messages even when power is off, can be selectively erased, and contains more data; examples of this type of memory are sometimes referred to as EPROMs. The memory 9140 can also be some other type of device. The memory 9140 includes a buffer memory 9141 (sometimes referred to as a buffer). The memory 9140 may include an application / function storage unit 9142 for storing application programs and function programs or processes for executing the operation of the electronic device 9600 via the central processing unit 9100.

[0209] The memory 9140 may also include a data storage unit 9143 for storing data, such as contacts, digital data, pictures, sounds, and / or any other data used by the electronic device. The driver storage unit 9144 of the memory 9140 may include various drivers for the electronic device's communication functions and / or for performing other functions of the electronic device (such as messaging applications, address book applications, etc.).

[0210] The communication module 9110 is a transmitter / receiver 9110 that transmits and receives signals via the antenna 9111. The communication module (transmitter / receiver) 9110 is coupled to the central processing unit 9100 to provide input signals and receive output signals, which can be the same as in a conventional mobile communication terminal.

[0211] Based on different communication technologies, multiple communication modules 9110 can be configured in the same electronic device, such as cellular network modules, Bluetooth modules, and / or wireless LAN modules. The communication module (transmitter / receiver) 9110 is also coupled to a speaker 9131 and a microphone 9132 via an audio processor 9130 to provide audio output via the speaker 9131 and receive audio input from the microphone 9132, thereby realizing typical telecommunications functions. The audio processor 9130 may include any suitable buffer, decoder, amplifier, etc. Additionally, the audio processor 9130 is coupled to a central processing unit 9100, enabling on-device recording via the microphone 9132 and on-device playback of stored sound via the speaker 9131.

[0212] Embodiments of this application also provide a computer-readable storage medium capable of implementing all steps of the message push method with the execution subject being a server or client in the above embodiments. The computer-readable storage medium stores a computer program that, when executed by a processor, implements all steps of the message push method with the execution subject being a server or client in the above embodiments. For example, when the processor executes the computer program, it implements the following steps:

[0213] Step S101: Push the transaction message received by the consensus node to the endorsement node so that the endorsement node can perform endorsement filtering on the transaction message.

[0214] Step S102: Push the endorsement filtering result of the endorsement node to the security node and the consensus node in parallel, so that the security node performs security verification on the endorsement filtering result and the consensus node receives the endorsement filtering result.

[0215] Step S103: Push the endorsement filtering result of the consensus node to the execution node to obtain the execution result, and push the execution result in parallel to the storage node and the security node, so that the security node performs security verification on the execution result and the storage node stores the execution result on the chain.

[0216] As can be seen from the above description, the computer-readable storage medium provided in this application embodiment realizes the synchronous to asynchronous process of transaction flow in the blockchain network through message push nodes, and promotes the parallel and rapid advancement of transaction flow among multiple modular nodes, thereby improving the data processing efficiency of the blockchain network.

[0217] Embodiments of this application also provide a computer program product capable of implementing all steps of the message push method in the above embodiments, where the execution subject is a server or a client. When this computer program / instruction is executed by a processor, it implements the steps of the message push method. For example, the computer program / instruction implements the following steps:

[0218] Step S101: Push the transaction message received by the consensus node to the endorsement node so that the endorsement node can perform endorsement filtering on the transaction message.

[0219] Step S102: Push the endorsement filtering result of the endorsement node to the security node and the consensus node in parallel, so that the security node performs security verification on the endorsement filtering result and the consensus node receives the endorsement filtering result.

[0220] Step S103: Push the endorsement filtering result of the consensus node to the execution node to obtain the execution result, and push the execution result in parallel to the storage node and the security node, so that the security node performs security verification on the execution result and the storage node stores the execution result on the chain.

[0221] As can be seen from the above description, the computer program product provided in this application embodiment realizes the synchronous to asynchronous process of transaction flow in the blockchain network through message push nodes, and promotes the parallel and rapid advancement of transaction flow among multiple modular nodes, thereby improving the data processing efficiency of the blockchain network.

[0222] Those skilled in the art will understand that embodiments of the present invention can be provided as methods, apparatus, or computer program products. Therefore, the present invention can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present invention can take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0223] This invention is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (devices), and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart illustrations and / or block diagrams. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0224] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0225] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0226] Specific embodiments have been used to illustrate the principles and implementation methods of this invention. The descriptions of the embodiments above are only for the purpose of helping to understand the method and core ideas of this invention. At the same time, for those skilled in the art, there will be changes in the specific implementation methods and application scope based on the ideas of this invention. Therefore, the content of this specification should not be construed as a limitation of this invention.

Claims

1. A message push method, characterized in that, A message push node applied to a blockchain network, wherein the message push node is connected to consensus nodes, endorsement nodes, execution nodes, security nodes, and storage nodes, the method comprising: The transaction message received by the consensus node is pushed to the endorsement node so that the endorsement node can perform endorsement filtering on the transaction message; The endorsement filtering results of the endorsing node are pushed in parallel to the security node and the consensus node so that they can perform subsequent processing at the same time. The security node performs security verification on the endorsement filtering results, and the consensus node receives the endorsement filtering results. The endorsement filtering result of the consensus node is pushed to the execution node to obtain the execution result, and the execution result is pushed to the storage node and the security node in parallel, so that the security node performs security verification on the execution result and the storage node stores the execution result on the chain. Wherein, the message push node is connected to the verification node, and the step of pushing the execution result to the storage node and the security node in parallel includes: The execution result is pushed to the verification node so that the verification node can verify the validity of the execution result. If the verification passes, the execution result of the verification node is pushed in parallel to the storage node and the security node, so that the security node performs security verification on the execution result and the storage node stores the execution result on the blockchain.

2. The method according to claim 1, characterized in that, Also includes: During the process of pushing the transaction message of the consensus node to the endorsing node, the transaction message is also pushed to other consensus nodes in the blockchain network in parallel. During the process of pushing the execution results to the storage node and the security node in parallel, the execution results are also pushed to other consensus nodes of the blockchain network in parallel. After the storage node stores the execution result on the blockchain, the stored result is pushed in parallel to other consensus nodes of the blockchain network.

3. The method according to claim 1, characterized in that, The process of pushing the execution result to the verification node also includes: The consensus parameters of the consensus node are pushed in parallel to the storage node and the security node, so that the security node performs security verification on the consensus parameters and the storage node determines the corresponding block information based on the consensus parameters.

4. The method according to claim 1, characterized in that, Before pushing the transaction message received by the consensus node to the endorsing node, the process also includes: In response to receiving a storage resource contribution instruction from a user, the storage node is configured in the client corresponding to the user; In response to receiving a computing resource contribution instruction from a user, the consensus node and the execution node are set up in the client corresponding to the user; In response to receiving a bandwidth resource contribution instruction sent by a user, the endorsement node and the message push node are set for the client corresponding to the user; The transaction message is received by at least one client that includes the storage node, consensus node, execution node, endorsement node, and message push node.

5. The method according to claim 4, characterized in that, Also includes: In response to receiving a user's distrust instruction regarding the setting results, the client corresponding to the user is associated with the security node; In response to receiving a user's trust instruction on the setting result, the security nodes in the setting result are pruned to obtain a setting result that deletes the security nodes.

6. A message push device, characterized in that, A message push node applied to a blockchain network, wherein the message push node is connected to consensus nodes, endorsement nodes, execution nodes, security nodes, and storage nodes, the device comprising: The transaction task delivery module is used to: push the transaction message received by the consensus node to the endorsement node, so that the endorsement node can perform endorsement filtering on the transaction message; The parallel push module for filtering results is used to: push the endorsement filtering results of the endorsement node to the security node and the consensus node in parallel, so that they can perform subsequent processing at the same time, so that the security node can perform security verification on the endorsement filtering results, and so that the consensus node can receive the endorsement filtering results. The parallel push module for execution results is used to: push the endorsement filtering result of the consensus node to the execution node to obtain the execution result, and simultaneously push the execution result to the storage node and the security node in parallel, so that the security node performs security verification on the execution result and the storage node stores the execution result on the blockchain; Wherein, the message push node is connected to the verification node, and the step of pushing the execution result to the storage node and the security node in parallel includes: The execution result is pushed to the verification node so that the verification node can verify the validity of the execution result. If the verification passes, the execution result of the verification node is pushed in parallel to the storage node and the security node, so that the security node performs security verification on the execution result and the storage node stores the execution result on the blockchain.

7. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the program, it implements the steps of the message push method according to any one of claims 1 to 5.

8. A computer-readable storage medium having a computer program stored thereon, characterized in that, When executed by a processor, the computer program implements the steps of the message push method according to any one of claims 1 to 5.

9. A computer program product, comprising a computer program / instructions, characterized in that, When the computer program / instruction is executed by the processor, it implements the steps of the message push method according to any one of claims 1 to 5.

Images