WO2022057106A1

WO2022057106A1 - Credibility verification system for digital asset data packet

Info

Publication number: WO2022057106A1
Application number: PCT/CN2020/134330
Authority: WO
Inventors: 白杰
Original assignee: 江苏傲为控股有限公司
Priority date: 2020-09-21
Filing date: 2020-12-07
Publication date: 2022-03-24
Also published as: JP6911231B1; GB202108535D0; CN111833062A; JP2022051652A; GB2593109A; CN111833062B

Abstract

A credibility verification system for a digital asset data packet, comprising a plurality of execution terminal nodes, a plurality of collection nodes, and a plurality of verification nodes. The execution terminal nodes comprise a plurality of nodes, on different main chains or sub-chains, for performing digital asset data packet operations; the collection nodes are nodes pre-assigned with a corresponding collection function role; and the verification nodes are nodes pre-assigned a corresponding verification function role. First, the verification nodes first send to the execution terminal nodes a credibility verification request for a digital asset data packet; the execution terminal nodes receive the verification request and perform digital signing on the data packet by using respective private keys of the execution terminal nodes; the verification nodes verify the digital signatures, and if each digital signature passes the verification, trigger the collection nodes to collect the digital signature; the collection nodes perform a collection operation on the digital signatures to generate a collection signature; the verification nodes verify the collection signature result; and if the collection signature result passes the verification, the data packet is credible.

Description

Credibility verification system of digital asset data package

technical field

The present application relates to the field of internet data processing, in particular to a trustworthiness verification system for digital asset data packets based on a blockchain network.

Background technique

Digital asset financial systems usually use blockchain as the bearer network to solve problems such as the credibility of digital assets. The realization of each function of the system, such as the generation and transaction of digital assets, is usually completed by different nodes or sub-chains of the public chain. For the simple blockchain network diagram shown in Figure 1, different nodes are used to implement different functions or operations. The network P shown in Figure 1 can be regarded as a simple public chain, in which node 1 is used to realize the generation of digital assets, and node 2 is used to realize the transaction of digital assets. For the typical block chain network schematic diagram shown in Figure 2, different functions or operations are implemented by different sub-chains, or nodes of sub-chains. As shown in Figure 2, the public chain P connects four sub-chains, wherein, sub-chain 3 is a digital asset generation sub-chain, referred to as a sub-chain of generation; sub-chain 4 is a digital asset transaction sub-chain, referred to as a transaction sub-chain; 5 is the digital asset storage sub-chain, referred to as the storage sub-chain; sub-chain 6 is the digital asset verification sub-chain, referred to as the verification sub-chain. In Figure 1 or Figure 2, the nodes used to implement different functions or operations are usually determined by the traditional technical mechanisms of the blockchain network, such as election or competition mechanisms. In addition, the cross-chain operation between the sub-chains shown in Figure 2 through the public chain is not discussed here.

The blockchain network shown in Figure 2 is a typical bearer network of a digital asset financial system, in which the functions and operations of sub-chains are related to each other. The data structures and mechanisms used by the functions implemented by the sub-chain 6 are relevant, otherwise the corresponding functions or operations cannot be implemented. The relationship between each sub-chain in FIG. 2 is described in conjunction with FIG. 3 .

The sub-chain 3 shown in FIG. 2 is an example of the digital asset generation sub-chain, including the digital asset generation node 31, which is used to carry the digital asset generation platform, and the

other nodes

32, 33, 34, and 35 are used to carry justice, evaluation, due diligence Platforms for surveys, guarantees, etc., where each platform in turn links one or more sub-chains consisting of terminal nodes formed by multiple nodes. Referring to FIG. 3, FIG. 3 is a relationship diagram between the sub-chains of the digital asset financial system carried by the blockchain network shown in FIG. 2, the digital asset data packet A generated by the digital asset generation node 31 is transmitted to the

nodes

32, 33, 34, 35, used to generate some attributes b1, b2, b3, b4 of the digital asset data package A, for example, used to express data such as evaluation value, justice matters, due diligence data, guarantee matters, etc. These attributes b1, b2, b3 , b4 is processed by the node 31 to form the attribute B of the digital asset data package A. The digital asset data package A and the attribute B together constitute a tradable digital asset data package D, and the digital asset data package D is sent by the node 31 to the transaction sub-chain 4 and the storage sub-chain 5 for transactions. Subchain 4 verifies the transaction or stores subchain 5 storage. Alternatively, the digital asset data package D is sent to the storage sub-chain 5 by the node 31 , and the transaction sub-chain 4 obtains the tradable digital asset data package D from the sub-chain 5 . Obviously, the digital asset data package D should have credibility before it can be stored by the sub-chain 5 or traded by the transaction sub-chain 4 .

However, due to various reasons, such as node failure, node attack, etc., the blockchain network cannot guarantee the credibility of the digital asset data package, that is, it cannot guarantee that the digital asset data package stored in the storage sub-chain 5 has complete credibility. sex. The way to ensure trustworthiness is that the digital asset data package can withstand verification. The usual practice is that any platform or any blockchain node initiates a verification request for a digital asset data package through a trusted node to further verify each verification sub-item of the digital asset data package. For example, in FIG. 2,

nodes

32, 33, 34, and 35 may all be provided with differential services by many terminals in the same or different time periods. That is to say, some attributes b1, b2, b3 or b4 of the digital asset data package A may all be the product of the cooperative operation of multiple terminals. Therefore, the credibility of the digital asset data package is realized by the credibility of each terminal operation, and verifying the credibility of the digital asset data package is to verify the credibility of each terminal operation. The usual practice is to perform hash signatures on the operation results of all terminals, that is, for the final formation of attribute B or digital asset data packet D, so that the node performing the verification will pass the hash calculation for attribute B or digital asset data packet D. , to get the conclusion of the credibility of attribute B or digital asset data package D. Obviously, this cannot guarantee the credibility of the formation process and source of attribute B or digital asset data package D.

An improved method is to perform a verification operation on the operator of the attribute B or the digital asset data package D. Since the verification operation usually generates verification requirements at an uncertain time after the attribute B or the digital asset data package D is generated, so , using this method to trace the source and verify the operators one by one requires complex retrieval and deletion operations, involving many blockchain service nodes and a large amount of data, resulting in high resource consumption and low efficiency.

SUMMARY OF THE INVENTION

Based on the above technical problems, the present application provides a reliability verification system for digital asset data packets. The problem to be solved by this application is to provide a reliability verification system for digital asset data packets that consumes less resources and is efficient.

A credibility verification system for digital asset data packets, comprising: several execution terminal nodes, several aggregation nodes, and several verification nodes, the execution terminal nodes include a plurality of different main chains or sub-chains that perform operations on the digital asset data packets , the collection node is a node that is pre-assigned a corresponding collection function role, and the verification node is a node that is pre-assigned a corresponding verification function role, wherein:

The verification node is configured with:

Verification request step: send a credibility verification request for the digital asset data package to the execution terminal node;

The execution terminal node is configured with:

The step of receiving verification: receiving the verification request sent by the verification node;

Digital signature step: digitally sign the data packet by using the respective private keys of the execution terminal nodes, and the digital signature is at least one;

The verification node is further configured with:

Digital signature verification step: verifying the digital signature;

Aggregation triggering step: if each of the digital signatures passes the verification, trigger the aggregation node to aggregate the digital signatures;

The collection node is configured with:

The collective signature step: performing a collective operation on the digital signature to generate a collective signature;

The verification node is further configured with:

The collective signature verification step: verifying the collective signature, if the verification is passed, the data packet is credible.

It can be seen from the above technical solutions that the present application provides a credibility verification system for digital asset data packets, including several execution terminal nodes, several aggregation nodes and several verification nodes, and the execution terminal nodes include a plurality of different types of performing digital asset data packet operations. Nodes on the main chain or sub-chain, the collection node is the node that is pre-assigned the corresponding collection function role, and the verification node is the node that is pre-assigned the corresponding verification function role. First, the verification node sends the trustworthiness of the digital asset data package to the execution terminal node. To verify the request, the execution terminal node receives the verification request, uses the private key of the execution terminal node to digitally sign the data packet, and the verification node verifies the digital signature. If each digital signature passes the verification, trigger the collection node to collect the digital signatures , the collection node performs a collection operation on the digital signature, generates a collection signature, and the verification node verifies the collection signature result. If the verification is passed, the data packet is credible. The collective signature can be verified once, which greatly reduces the cost of verifying the signature and saves the storage space of the execution terminal node.

Description of drawings

In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the accompanying drawings required in the embodiments will be briefly introduced below. Obviously, the drawings in the following description are only some of the present application. In the embodiments, for those of ordinary skill in the art, other drawings can also be obtained according to these drawings without any creative effort.

Figure 1 is an example diagram of a simple blockchain network;

Figure 2 is an example diagram of a typical blockchain network;

Fig. 3 is a relationship diagram between sub-chains of the digital asset financial system carried by the blockchain network shown in Fig. 2;

Figure 4 is a schematic diagram of the reliability verification flow of the digital asset data package;

FIG. 5 is a schematic diagram of forming a trustworthy tree during a transaction operation process of a data packet.

detailed description

In order to make the objectives, technical solutions and advantages of the present application clearer, the technical solutions of the present application will be clearly and completely described below with reference to the specific embodiments of the present application and the corresponding drawings. Obviously, the described embodiments are only a part of the embodiments of the present application, but not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative efforts shall fall within the protection scope of the present application. The technical solutions provided by the embodiments of the present application will be described in detail below with reference to the accompanying drawings.

With the development and application of Internet technology, digital assets, such as electronic money, Q coins, online games and some application software, are constantly being integrated into people's production and life, becoming an indispensable part of the Internet era. These various resources that are owned or controlled by enterprises or individuals, exist in the form of electronic data, have certain value or are expected to bring economic benefits are collectively referred to as digital assets. Digital assets can be seen everywhere in daily life. For example, the common manifestations of digital assets include movie tickets, game equipment, paid courseware, paid music, star voting, virtual points, etc. The main areas involved in digital assets are literature, film and television, Games, animation, finance and other fields.

Packet is a data unit in TCP/IP protocol communication transmission, generally also called "data packet". Digital asset data packet means that digital assets exist in the Internet in the form of data packets. In order to ensure the credibility of digital asset data packets, blockchain is usually used as the bearer network, but digital asset data packets will generate a lot of intermediate process data during the transaction process. A certain node of the node initiates a transaction on the digital asset data package. The transaction operation process passes through several sub-chains on the main chain, and passes through the next-level nodes of some nodes on the sub-chain, that is, the digital asset data package. In the entire transaction process, many terminal nodes will pass through, and a lot of process data will be generated. In order to ensure the credibility of the entire digital asset data package, all process data must be verified. The commonly used method is the traceability verification method, but verification In the process, due to the large number of blockchain service nodes involved in the transaction process and the large amount of data, many resources are consumed and the efficiency is low.

The present application provides a credibility verification system for digital asset data packets, including: several execution terminal nodes, several aggregation nodes, and several verification nodes, and the execution terminal nodes include multiple different main chains or sub-chains that perform operations on digital asset data packets When a node in the blockchain performs a transaction operation on a digital asset data packet (hereinafter referred to as a data packet), this node is the execution terminal node. Usually, the transaction operation of a data packet will pass through many nodes. , so the number of execution terminal nodes corresponds to a lot. A collection node is a node that is pre-assigned the corresponding collection function role. The collection node mainly collects each discrete signature, and collects multiple signatures into one collection signature. It can combine multiple signatures of a transaction or multi-signature transactions. The public keys and signatures of each participant are set as a public key and signature, and the entire set process is invisible, and only needs to be verified once. The verification node is the node that is pre-assigned the corresponding verification function role, mainly to verify the credibility of the node and the credibility of the signature in the process of the data packet transaction. Functional role, a node is an execution terminal node, and can also be a collection node and a verification node. The number of execution terminal nodes, verification nodes and collection nodes is not limited, but multiple verification nodes include at least one trusted node. The foundation initiates a credibility verification request for the digital asset data package.

Referring to Fig. 4, Fig. 4 is a schematic diagram of the credibility verification process of the digital asset data package, the credibility verification system of the digital asset data packet of the present application, wherein:

Verify that the node is configured with the following steps:

Verification request step: send a credibility verification request for the digital asset data package to the execution terminal node.

It should be noted that, before the verification node initiates a credibility verification request to the execution terminal node, the execution terminal node also needs to perform the node trustworthiness judgment step, that is, the execution terminal node judges whether the verification node is a trusted node, and the specific judgment method is this application. Without specific limitations, if the verification node is credible and receives a credibility verification request, that is, the verification node can verify the credibility of the digital asset data package. Or maliciously pretend to be a node, etc., and the execution terminal node rejects the credibility verification request of the verification node, that is, the verification node cannot perform the credibility verification process of the digital asset data package.

The execution endpoint configuration is:

The step of receiving verification: receiving the verification request sent by the verification node, and if the execution terminal node determines that the verification node is a trusted node, then receives the verification request sent by the verification node.

Digital signature step: digitally sign the data package with the private key of the execution terminal node, and the number of digital signatures must be at least one. The initial data packet may be allocated to one or more execution terminal nodes at the beginning of the transaction, or the data packet may be split and allocated to different execution terminal nodes. In order to ensure the credibility of the execution terminal node and each transaction and each link, the blockchain mainly uses digital signatures to realize permission control, and the private key of each execution terminal node is used for digital data packet transactions of each execution terminal node. Signature, the public key corresponding to the private key is disclosed, and the digital signature using the private key has an anti-tampering mechanism, which can identify the legal identity of the transaction initiator, prevent the identity of malicious nodes from impersonating, and thus prevent transactions from being tampered with by third parties.

Digital signatures, also known as electronic signatures, use certain algorithms to achieve effects similar to traditional physical signatures. A digital signature is to process the signature content through algorithms in the field of cryptography to obtain a segment of characters used to represent the signature. In the field of cryptography, a set of digital signature algorithms generally includes two operations: signature and signature verification. After the data is signed, it only needs to be verified by the matching verification signature method, and it does not require professional means to identify it like traditional physical signatures.

Digital signature usually adopts asymmetric encryption algorithm, that is, each node needs a pair of private key and public key. The signatures of different private keys to the same piece of data are completely different, similar to the handwriting of physical signatures. The digital signature is usually attached to the original message as additional information to prove the identity of the message sender. The public key is the key that everyone can obtain. The public key is required to verify the signature. Because the public key can be obtained by everyone, all nodes can verify the legitimacy of the identity.

The specific steps of digital signature are as follows:

The step of generating the digest: generating a digital digest by hashing the original data of the data packet, and in this application, hashing the initial data of the digital asset data packet to generate a digital digest;

The step of encrypting the digest: encrypting the digital digest with the private key of the node where the data packet is located to obtain a digital signature. In this application, the generated digital digest is encrypted with the private key of the execution terminal node where the data packet is located;

Digital signature sending step: Send the digital signature and the original data of the data packet to the verification node.

The verification node is further configured with:

The digital signature verification step: verifying the digital signature result of the execution terminal node. The digital signature verification method can be determined through pre-negotiation between the verification node and the execution terminal node, which is not specifically limited in this application.

Collection triggering step: If each digital signature passes the verification, trigger the collection node to collect the digital signatures to generate a collection signature. Collective signature collects multiple digital signature data of one execution terminal node or multiple execution terminal nodes to generate collective signature data corresponding to the execution terminal node, that is, multiple signatures signed by multiple users on multiple messages respectively, can be collected. Synthesize a short signature.

The collection node configuration has:

Collection signature step: perform collection operations on digital signatures to generate collection signatures. Collection signatures are digital signatures with additional properties, which have compression and batch processing properties. In practice, the more favorable factor is that collection signatures are verifiable , and only one verification is required, that is, when multiple digital signatures are assembled to generate a collective signature for the first time, all digital signatures involved and the collective signature after the collection of digital signatures need to be verified. Once the initial verification is passed, There is no need to verify the digital signature in the verification in the future, only the final generated set signature result is verified. The rule of the collective signature is that as long as the collective signature result passes the verification, it means that each digital signature that generates the collective signature has passed the verification.

The verification node is further configured with:

Collection signature verification step: Verify the collection signature, if it passes the verification, the data package is trusted.

The verification of the collective signature includes two cases. One is to verify all digital signatures involved in the collective signature when the collective signature is performed for the first time; the other is to verify the collective signature when the collective signature is initialized. The details are as follows:

Initial verification step: When the collective node performs collective signature on the digital signature for the first time, all digital signatures need to be verified. The verification method of the digital signature can be predetermined. For example, a verification method of the digital signature data can be: encrypt the digest information with the sender's private key, transmit it to the receiver together with the original text, and decrypt the receiver with his own public key The encrypted summary information, and then use the HASH function to generate a summary information for the received original text, and compare it with the decrypted summary information. If they are the same, it means that the received information is complete and has not been modified during the transmission process; otherwise, it means that the information has been modified, so the digital signature can verify the integrity of the information. It should be noted that it is only necessary to verify all the digital signature data during the initial collective signature. After the initial verification is passed, there is no need to verify all the digital signature data in the future. It is only necessary to verify the result of the collective signature. Can.

Set result verification step: In the initial set signature, if all the digital signatures pass the verification, verify the initial set signature result, or, in practical applications, when the set signature is initialized, initialization certification is required. The initialization referred to here includes, for example, When the system carried by the data packet exchange is started every day or the system is restarted, the verification method of the collective signature result can be pre-determined by the verification node. For example, the collective signature result can be the product of each digital signature data, and the verification node only needs to verify the collective signature once to be sure whether the digital signature involved in the collective signature comes from the specified execution terminal node. Attributes and links are signed separately, which greatly improves the efficiency of signature verification and transmission. The collective signature result may also be other algorithms customized by the user according to actual needs, which is not specifically limited in this application.

Compared with the traceability verification of digital signatures one by one, the collective signature can be verified only once, so the cost of verifying the signature can be greatly reduced. Moreover, since multiple signatures are aggregated into one signature, the storage of the execution terminal node can be greatly saved. The purpose of collectively signing digital signatures is to provide a reliability verification system for digital asset data packets with less resource consumption and high efficiency.

In order to record the transaction process of data packets more clearly, the execution terminal node is further configured with the following steps:

Steps of generating a trusted tree: According to the transaction operation process of the terminal node to the data packet, the trusted tree of the processing process of the data packet is generated according to the node level. The trusted tree here refers to the operation process of all the execution terminal nodes that the data packet passes through. Referring to FIG. 5, FIG. 5 is a schematic diagram of a trusted tree formed by a transaction operation process of a data packet. In this embodiment, the node-level confirmation method is to first confirm the root node, and take the execution terminal node of the initial operation data packet as the root Next, confirm the child nodes. The confirmation method is that the root node is the first level node, and the next level node of the root node is the second level node. With reference to Figure 5, the execution terminal node of the initial data packet is the root node. In this embodiment, the initial data packet is divided into data packet 0 and data packet 1, then the second-level node has two execution terminal nodes to operate the two packet data packets respectively. The next-level node of the node is the third-level node, and the third-level node splits the data packet 0 into three data packets, namely data packet 01, data packet 02 and data packet 03, and splits the data packet 1 again. There are two data packets, namely data packet 11 and data packet 12, that is, there are 5 third-level nodes in FIG. 5, and the division continues until all execution terminal nodes passed by the data packet are recorded.

The trusted tree encryption step: encrypting each transaction operation in the trusted tree, and the specific encryption method is not specifically limited in this application.

Trust tree verification step: verify the transaction operation of each execution terminal node to determine whether there is any malicious operation.

Trust tree storage steps: If there is a malicious operation, record the execution terminal node corresponding to the malicious operation, indicating that the operation of the execution terminal node is untrustworthy. If the set signature verification fails later, it is likely that the malicious node failed. Verify, record the encryption and verification process of each execution terminal node, and store the trust tree periodically according to the preset time. For example, the trust tree can be stored after the data packet transaction is completed, or it can be stored in stages during the data packet transaction process. , which can be preset according to the transaction complexity of the data package.

Based on the above embodiment of generating a trusted tree, the present application can also perform collective signatures on digital signatures according to the trusted tree. It should be noted that the collective signature can perform collective signatures on multiple digital signatures of a user, that is, an execution terminal node, It is also possible to collectively sign multiple digital signatures of multiple users, that is, multiple execution terminal nodes. In the trusted tree storage step, the execution terminal nodes corresponding to malicious operations have been recorded, and the collective signature is constructed on the basis of the trusted tree. Once the set signature verification fails, the first search should be the execution terminal node with malicious operation records, which saves the work of checking and tracing the source one by one, greatly improving the efficiency. The processing flow of the entire data packet can be clearly displayed.

After the trust tree records the transaction process of the entire data packet, the verification node is further configured with the following steps:

Data packet storage step: If the data packet is credible, that is, the verification result of the verification node on the set signature is verified, the data packet is stored in the verification node, and the data packet at this time is a trusted data packet, in which the stored data The operation of digital signature and collective signature is included in the package. Specifically, the data package storage step specifically includes the following steps:

The data packet splitting step: splitting the trusted data packet to obtain a plurality of grouped data packets.

Packet data packet encryption step: encrypt each packet data packet.

Encrypted data packet storage step: store each encrypted packet data packet to the verification node for later use.

It can be seen from the above technical solutions that the present application provides a credibility verification system for digital asset data packets, including several execution terminal nodes, several aggregation nodes and several verification nodes, and the execution terminal nodes include a plurality of different types of performing digital asset data packet operations. Nodes on the main chain or sub-chain, the collection node is the node that is pre-assigned the corresponding collection function role, and the verification node is the node that is pre-assigned the corresponding verification function role. First, the verification node sends the trustworthiness of the digital asset data package to the execution terminal node. To verify the request, the execution terminal node receives the verification request, uses the private key of the execution terminal node to digitally sign the data packet, and the verification node verifies the digital signature. If each digital signature passes the verification, trigger the collection node to collect the digital signatures , the collection node performs a collection operation on the digital signature, generates a collection signature, and the verification node verifies the collection signature result. If the verification is passed, the data packet is credible. The collective signature does not need to verify all digital signatures every time. It can be verified by one time, which greatly reduces the cost of verifying signatures. Moreover, because multiple signatures are aggregated into one signature, the storage space of the execution terminal node can be greatly saved. , which provides a low-resource consumption and efficient digital asset data package credibility verification system. At the same time, the execution terminal node is also configured with the step of generating a trusted tree. Once the collective signature verification fails, the first search should be the execution terminal node with malicious operation records, which eliminates the need for one-by-one investigation and traceability. It greatly improves the efficiency, and at the same time, the processing flow of the entire data packet can be clearly displayed through the trusted tree.

Claims

The reliability verification system of digital asset data package is characterized by comprising: several execution terminal nodes, several aggregation nodes and several verification nodes, and the execution terminal node includes a plurality of different main chains that perform operations on the digital asset data package. Or a node on a sub-chain, the collection node is a node that is pre-assigned a corresponding collection function role, and the verification node is a node that is pre-assigned a corresponding verification function role, wherein:

The verification node is configured with:

Verification request step: sending a credibility verification request to the digital asset data package to the execution terminal node;

The execution terminal node is configured with:

The step of receiving verification: receiving the verification request sent by the verification node;

Digital signature step: digitally sign the data packet by using the respective private keys of the execution terminal nodes, and the digital signature is at least one;

The verification node is further configured with:

Digital signature verification step: verifying the digital signature;

Aggregation triggering step: if each of the digital signatures passes the verification, triggering the aggregation node to aggregate the digital signatures;

The collection node is configured with:

The collective signature step: performing a collective operation on the digital signature to generate a collective signature;

The verification node is further configured with:

The collective signature verification step: verifying the collective signature, if the verification is passed, the data packet is credible.
The reliability verification system of the digital asset data package according to claim 1, wherein the execution terminal node is further configured with:

Node credibility judgment step: determine whether the verification node is a trusted node, if the verification node is trusted, receive the credibility verification request, and if the verification node is not trusted, reject the credibility verification request.
The reliability verification system of digital asset data package according to claim 1, is characterized in that, described collection node is further configured with:

The initial verification step: when the aggregation node assembles the digital signatures for the first time, it verifies all the digital signatures;

The step of verifying the collective result: if all the digital signatures pass the verification, the initial collective signature result is verified, and the verification method of the collective signature result is predetermined by the verification node.
The reliability verification system of the digital asset data package according to claim 1, wherein the execution terminal node is further configured with:

The step of generating a trustworthy tree: generating a trustworthy tree of the processing process of the data packet according to the node level according to the transaction operation process of the data packet by the execution terminal node;

Trusted tree encryption step: encrypting each transaction operation in the trusted tree;

Trust tree verification step: verifying each transaction operation to determine whether there is a malicious operation;

The step of storing the trusted tree: if there is a malicious operation, record the execution terminal node corresponding to the malicious operation, and periodically store the trusted tree according to a preset time.
The reliability verification system of the digital asset data package according to claim 4, wherein the collective signature is that the digital signature is collectively signed according to the trust tree.
The reliability verification system for digital asset data packets according to claim 4, wherein the step of confirming at the node level comprises:

Root node confirmation step: take the execution terminal node that operates the data packet for the first time as the root node;

Sub-node confirmation step: take the root node as a first-level node, the next-level node of the root node as a second-level node, and the next-level node of the second-level node as a third-level node, until All nodes that the data packet passes through are recorded.
The reliability verification system of a digital asset data package according to claim 1, wherein the digital signature step specifically comprises:

The step of generating a digest: generating a digital digest by hashing the original data of the data packet;

The step of encrypting the digest: encrypting the digital digest with the private key of the node where the data packet is located to obtain a digital signature;

The digital signature sending step: sending the digital signature together with the original data of the data packet to the verification node.
The reliability verification system for digital asset data packets according to claim 1, wherein the digital signature verification method is pre-negotiated and determined by the verification node and the execution terminal node.
The reliability verification system for digital asset data packages according to claim 1, wherein the plurality of verification nodes include at least one trusted node.
The reliability verification system of digital asset data package according to claim 1, is characterized in that, described verification node is further configured with:

The data packet storage step: if the data packet is credible, the data packet is stored in the verification node, and the data packet storage step specifically includes:

Data packet splitting step: splitting the trusted data packet to obtain a plurality of grouped data packets;

Packet data packet encryption step: encrypting each of the packet data packets;

The step of storing encrypted data packets: storing each encrypted packet data packet to the verification node.