Project whole-process collaborative management system based on block chain technology

Abstract

The invention belongs to the technical field of block chains, and particularly relates to a block chain technology-based project full-process collaborative management system, which comprises a client module, a node server module and a block chain server, the client module comprises an information receiving unit and a first information transceiving unit; the node server module comprises a second information transceiving unit, a hash encryption unit and a packaging unit; the information receiving unit is used for receiving project data and project files uploaded by participants; the hash encryption unit is used for calculating a hash value of the project file; when the method is used, the distributed storage technology of the block chain, which adopts multi-party distributed collaboration of the block chain, real-time progress synchronization of all parties, non-tampering of data, transparent sharing of information and the block chain, enables all participants of the project to share various data in the project, eliminates information asymmetry, reduces communication cost, and depends on the advantages of the block chain, so that the method is easy to implement. Once the data is linked, the data is solidified through an encryption algorithm and is difficult to tamper.

Description

Technical Field

[0001] This invention relates to the field of blockchain technology, specifically to a project end-to-end collaborative management system based on blockchain technology. Background Technology

[0002] Blockchain is a distributed ledger technology that uses a chain-like data structure, cryptography, and consensus mechanisms to achieve immutable, transparent, and decentralized data storage. Its core value lies in building a trustless trust mechanism, solving the problems of single point of failure, data monopoly, and high trust costs in traditional centralized systems.

[0003] Project-wide collaborative management refers to a systematic management model that uses the project lifecycle as its axis and leverages standardized mechanisms, digital tools, and cross-role collaboration to achieve goal alignment, information synchronization, resource coordination, and joint risk prevention. Its core is breaking down departmental barriers and information silos to build a management ecosystem characterized by full participation, end-to-end visibility, and comprehensive collaboration.

[0004] However, in traditional project management, information transmission relies on centralized platforms, which can easily lead to tampering or loss and low collaboration efficiency. Existing systems are also unable to achieve full-process traceability and real-time risk warning, especially in multi-party collaboration scenarios, where the cost of establishing trust is high and dispute tracing is difficult. Therefore, a project full-process collaborative management system based on blockchain technology is proposed to address the above problems. Summary of the Invention

[0005] To overcome the shortcomings of existing technologies and solve at least one of the technical problems mentioned in the background, this invention proposes a project end-to-end collaborative management system based on blockchain technology.

[0006] The technical solution adopted by this invention to solve its technical problem is as follows: the project full-process collaborative management system based on blockchain technology described in this invention includes a client module, a node server module, and a blockchain server; the client module includes an information receiving unit and a first information sending and receiving unit; the node server module includes a second information sending and receiving unit, a hash encryption unit, and a packaging unit; The information receiving unit is used to receive project data and project files uploaded by the participants; The first information transceiver unit is used to transmit and receive data transmitted with the node server module; The hash encryption unit is used to calculate the hash value of the project file; The packaging unit is used to package project data and project file hash values ​​into a project data package, which, after consensus by the node server module, generates an on-chain credential. The second information transceiver unit is used to download project data packages from the data blockchain server, transmit and receive data with the client, and upload the packaged project data packages and on-chain credentials to the blockchain server. A blockchain server is a distributed blockchain network composed of node server modules from all participating parties. During use, the blockchain enables multi-party distributed collaboration, with all parties synchronizing progress in real time and ensuring data immutability and transparent information sharing. The distributed storage technology of blockchain allows all project participants to share data, including task progress, fund flows, and quality inspection results, all of which are synchronized to the chain in real time. This eliminates information asymmetry and reduces communication costs. Leveraging the advantages of blockchain, once data is on the chain, it is solidified through encryption algorithms, making it difficult to tamper with and ensuring the authenticity and integrity of project data. This also provides a reliable basis for project auditing, supervision, and dispute resolution. Furthermore, blockchain breaks the traditional centralized management model, placing all participants on an equal footing within the blockchain network, allowing for direct data interaction and collaborative work.

[0007] Preferably, the node server module further includes a digital signature unit. The digital signature unit is used to encrypt the packaged project data packet using a private key to generate a digital signature. When the second information sending and receiving unit uploads, it uploads the digital signature and the project data packet together to the blockchain server. When in use, the uploader encrypts the project data packet using its own private key to generate a digital signature, and then sends the project data packet and digital signature together to the blockchain network. Other participants, such as the supervisor, receive the data, first obtain the public key, and then use the public key to decrypt the digital signature to obtain the decrypted hash value. At the same time, they recalculate the hash value of the received original data and compare the two hash values. If they do not match, the data has been tampered with, or the signature comes from a forged private key. The digital signature serves as an identity authentication tool to prevent impersonation and provides evidence for subsequent auditing and dispute resolution. It can be verified in a distributed manner, allowing multiple participants to verify the signature simultaneously without relying on a single central institution, thus improving the credibility of the verification.

[0008] Preferably, the blockchain server includes a synchronization node unit and a sharded storage unit, and the node server module further includes a file splitting unit. The synchronization node unit is used to store project data packets, and each node server module synchronously downloads project data packets in real time and maintains the consistency of project data packets. The file splitting unit is used to split large files stored in the project files into several data blocks. The sharded storage unit is used to store data blocks in shards and Merkle tree information formed by several data blocks. Through the above steps, a complete Merkle tree is generated. The hash value of the root node uniquely identifies the entire file. As long as the file content is modified, the root hash will be completely different. Users can confirm the authenticity of the file by querying the blockchain. During data verification, the root hash and a small number of intermediate node hashes can be used to verify whether any shard has been tampered with, without loading the entire file, which is more efficient. Shards with the same content have the same hash, so the corresponding data block can be stored only once, avoiding duplicate storage.

[0009] Preferably, the blockchain server has multiple channels, which are isolated according to business processes. Each project's node server module only synchronizes the project data of its own channel and downloads the project files of its own channel. When in use, the core purpose of setting up the channels is to build a private communication and data isolation space for different business processes, ensuring that different participants can only access the data within their own process, thus building a private communication and data isolation space for different project processes.

[0010] Preferably, the client module further includes a data preprocessing unit, which can standardize the format of the received raw data, unify the file encoding format, and perform data preprocessing before encrypting the file using a hash algorithm to avoid changes in hash value due to format differences.

[0011] Preferably, the node server module further includes a local storage unit. Sensitive privacy data in the project data is encrypted using a hash algorithm. The calculated hash value is packaged and sent to the blockchain server. Sensitive privacy data in the project data is stored in the local storage unit. By uploading the hash value of sensitive information to the blockchain, when verification is required, the original data is provided through the off-chain local storage unit. After calculating the hash, it is compared with the data on the blockchain to confirm that the data has not been tampered with and to avoid the problem of sensitive information leakage.

[0012] Preferably, the blockchain server further includes a smart contract unit. The smart contract unit can automatically trigger execution when preset conditions are met according to pre-established business rules. The execution process and results are recorded on the blockchain server and synchronized on the blockchain. By setting up the smart contract unit, the pre-established business rules are solidified in the form of code and automatically enforced after the conditions are met, thereby improving the efficiency of project business processes. The rules are open and transparent, and the execution results are tamper-proof.

[0013] Preferably, the blockchain server also includes an AI monitoring unit capable of real-time risk identification of project data. The AI ​​monitoring unit includes a rule interception component for real-time identification. The rule interception component can examine and identify uploaded project data according to pre-set anomaly types, distinguish abnormal data, write the identification results into the blockchain, and automatically send on-chain warnings to other participants. By setting up an AI monitoring unit for real-time risk identification, abnormal fund flow in project data can be identified, solving the problems of lagging and large errors in manual monitoring in traditional project management.

[0014] Preferably, the AI ​​monitoring unit further includes an intelligent algorithm component. The intelligent algorithm component runs an artificial intelligence learning model, which can analyze and identify fund flows, identify potential risks that are difficult for the rule-based interception component to cover, and supplement the identification by using the intelligent algorithm component. The intelligent algorithm component constructs behavioral profiles and correlation networks by training abnormal transaction patterns in historical project data, and identifies hidden risks that deviate from the normal pattern.

[0015] Preferably, the intelligent algorithm component can perform integrated analysis of project data and project issues based on the project data and project files uploaded by each participant, and identify potential factors that may lead to delays in the project schedule in advance.

[0016] The advantages of this invention are: 1. This invention, by setting up client, node server modules, and a blockchain server, allows each project participant to have both a client module and a node server module. The node server module acts as a node in the blockchain, participating in block consensus. This multi-party distributed collaboration ensures real-time progress synchronization and immutable data, enabling transparent information sharing. The distributed storage technology of blockchain allows all project participants to share data, including task progress, fund flows, and quality inspection results, all of which are synchronized to the chain in real time. This eliminates information asymmetry and reduces communication costs. Furthermore, leveraging the advantages of blockchain, once data is on the chain, it is solidified through encryption algorithms, making it difficult to tamper with and ensuring the authenticity and integrity of project data. This also provides a reliable basis for project auditing, supervision, and dispute resolution. Moreover, blockchain breaks the traditional centralized management model, placing all participants on an equal footing within the blockchain network, allowing for direct data interaction and collaborative work.

[0017] 2. This invention solves the problems of lagging and large errors in traditional project management by setting up an AI monitoring unit to identify risks in real time and detect abnormalities in the flow of funds in project data. Attached Figure Description

[0018] To more clearly illustrate the technical solutions in the embodiments of the present invention 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 only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0019] Figure 1 This is a schematic diagram of the full-process collaborative management system structure of the present invention; Figure 2 This is a schematic diagram of the blockchain server structure of the present invention. Detailed Implementation

[0020] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0021] Specific implementation examples are given below.

[0022] Please see Figure 1As shown, the project end-to-end collaborative management system based on blockchain technology includes a client module, a node server module, and a blockchain server; the client module includes an information receiving unit and a first information sending and receiving unit; the node server module includes a second information sending and receiving unit, a hash encryption unit, and a packaging unit. The information receiving unit is used to receive project data and project files uploaded by the participants; The first information transceiver unit is used to transmit and receive data transmitted with the node server module; The hash encryption unit is used to calculate the hash value of the project file; The packaging unit is used to package project data and project file hash values ​​into a project data package, which, after consensus by the node server module, generates an on-chain credential. The second information transceiver unit is used to download project data packages from the data blockchain server, transmit and receive data with the client, and upload the packaged project data packages and on-chain credentials to the blockchain server. A blockchain server is a distributed blockchain network composed of node server modules from all participating parties. In use, each participant in the project possesses a client module and a node server module. The node server module acts as a node in the blockchain, participating in block consensus. The client module includes mobile terminals and PCs. Before the project begins, tasks and resources are allocated, and task allocation records are uploaded to the blockchain, linked to the digital identities of participants, clarifying responsibility. Each participant's node synchronizes plan data to avoid information asymmetry. During the execution process, project data from each participant is uploaded to the node server module via the client. The hash encryption unit calculates the hash value of the project file, packages the project data and the project file hash value into a project data package, and then the second information transceiver unit uploads it to the blockchain server. Each participant's node server module synchronously downloads the project data package, synchronizing the project progress. Each participant can adjust the project data as needed. By unpacking the data packets, project data can be obtained. The aforementioned multi-party distributed collaboration ensures that all parties synchronize progress in real time, and the data is tamper-proof, with transparent information sharing. Blockchain's distributed storage technology enables all project participants to share data. Various data in the project, such as task progress, fund flow, and quality inspection results, can be synchronized to the chain in real time, eliminating information asymmetry and reducing communication costs. Relying on the advantages of blockchain, once data is on the chain, it is solidified through encryption algorithms, making it difficult to tamper with and ensuring the authenticity and integrity of project data. It also provides a reliable basis for project auditing, supervision, and dispute resolution. At the same time, the advantages of blockchain break the traditional centralized management model, with all participants on an equal footing in the blockchain network, allowing them to directly interact with data and collaborate.

[0023] Project files include: project documents, design drawings, photos, and videos; project data includes: project progress, fund flow, change records, and project-related information, such as the project ID, uploader (digital identity), upload time, and associated tasks; on-chain credentials include the uploader's ID and timestamp.

[0024] Furthermore, such as Figure 1 As shown, the node server module also includes a digital signature unit, which is used to encrypt the packaged project data packet using a private key to generate a digital signature. When the second information sending and receiving unit uploads, it uploads the digital signature and the project data packet together to the blockchain server.

[0025] The uploader encrypts the project data packet using their private key, generates a digital signature, and then sends the project data packet and digital signature together to the blockchain network. Other participants, such as the supervisor, receive the data, first obtain the public key, and then use the public key to decrypt the digital signature to obtain the decrypted hash value. At the same time, they recalculate the hash value of the received original data and compare the two hash values. If they do not match, the data has been tampered with, or the signature comes from a forged private key. The digital signature serves as identity authentication, preventing impersonation and tampering, ensuring that the data has not been modified during transmission or storage, and preventing repudiation. The uploader cannot deny their operation, and the private key is kept by the uploader. All subsequent operations (such as task allocation and progress reporting) must be signed with the private key. On the blockchain, the identity is verified through the public key, ensuring that whoever operates is responsible. During verification, both "file hash matching" and "signature from the uploader" must be verified simultaneously, providing double assurance of credibility. Relying on the advantages of blockchain, once uploaded to the chain, it cannot be modified, providing evidence for subsequent auditing and dispute resolution. Distributed verification is possible, with multiple participants verifying the signature simultaneously, without relying on a single central institution, thus improving the credibility of the verification.

[0026] Furthermore, such as Figure 1 As shown, the blockchain server includes a synchronization node unit and a sharded storage unit. The node server module also includes a file splitting unit. The synchronization node unit is used to store project data packets, and each node server module synchronously downloads project data packets in real time and maintains the consistency of project data packets. The file splitting unit is used to split large files stored in the project files into several data blocks. The sharded storage unit is used to store data blocks in shards and Merkle tree information formed by several data blocks. The distributed storage process for large files is as follows: Step 1: Split large files into contiguous data blocks of fixed size (e.g., 256KB, 1MB); Step 2: The hash encryption unit calculates the hash value for each data block individually, and the resulting hash value is used as the leaf node of the Merkle tree; Step 3: Following the rule of "merging in pairs", calculate the hash of the intermediate nodes layer by layer from the leaf nodes upwards to finally generate the root node (Merkle root). The above steps generate a complete Merkle tree. The hash value of the root node uniquely identifies the entire file. As long as the file content is modified, the root hash will be completely different. Users can verify the authenticity of the file by querying the blockchain. During data verification, any shard can be verified to see if it has been tampered with by using the root hash and a small number of intermediate node hashes without loading the entire file, which is more efficient. Shards with the same content have the same hash, so the corresponding data block can be stored only once, avoiding duplicate storage. The Merkle tree information includes the root hash, the list of leaf node hashes, and optional intermediate node hashes.

[0027] Furthermore, the blockchain server is equipped with multiple channels, which are isolated according to business processes. Each project's node server module only synchronizes the project data of its own channel and downloads the project files of its own channel.

[0028] When using this channel, the core purpose of its establishment is to create private communication and data isolation spaces for different business processes, ensuring that different participants can only access data within their own process. The process of establishing a channel to create private communication and data isolation spaces for different project processes includes the following steps: Step 1: Generate a channel configuration file, which specifies the channel name, participant permissions, and core rules of the consensus mechanism. Step 2: Initiate a channel creation request. The channel initiator submits the configuration transaction file generated in Step 1 to the sorting node, which then creates the channel and generates the channel genesis block file. Step 3: Invite participating nodes to join the channel. The initiator distributes the channel genesis block file to other participants. Each participant adds its own peer node to the channel. The node will synchronize the channel genesis block from the sorting node, initialize the local ledger, and the sorting node will update the channel member list. Step 4: Configure channel permissions and chaincodes, bind business logic through chaincodes, and configure access permissions for participating nodes to ensure data isolation is effective.

[0029] Furthermore, such as Figure 1 As shown, the client module also includes a data preprocessing unit, which can standardize the format of the received raw data and unify the file encoding format; before encrypting the file using a hash algorithm, the data preprocessing unit performs data preprocessing to avoid changes in hash value due to format differences.

[0030] Furthermore, such as Figure 1As shown, the node server module also includes a local storage unit. Sensitive privacy data in the project data is encrypted using a hash algorithm. The calculated hash value is packaged and sent to the blockchain server, while the sensitive privacy data in the project data is stored in the local storage unit. When in use, the blockchain data is visible to all participants. Sensitive privacy data in the project data, such as project budget details, contact information of core participants, and internal approval opinions, cannot be directly uploaded to the chain, as direct storage of sensitive information would lead to leakage. Therefore, it is necessary to upload the hash value of sensitive information to the chain. When verification is required, the original data is provided through the off-chain local storage unit. After calculating the hash, it is compared with the on-chain data to confirm that the data has not been tampered with and to avoid the problem of sensitive information leakage. When verification is required, the decrypted original project data + encrypted ciphertext is provided. The hash is calculated and compared with the hash value on the chain. If they match, it proves that the data is genuine. The immutability of the blockchain ensures the credibility of the project information, while the off-chain storage protects privacy, achieving trust and security.

[0031] Furthermore, such as Figure 2 As shown, the blockchain server also includes a smart contract unit. The smart contract unit can automatically trigger execution when preset conditions are met according to pre-established business rules. The execution process and results are recorded on the blockchain server and synchronized on the blockchain. In practice, to address the issues of low efficiency, opaque rule execution, and high trust costs associated with traditional project management, smart contract units are used. These units solidify pre-defined business rules into code, automatically enforcing them when conditions are met. This improves the efficiency of project business processes, ensuring transparency and immutability of execution results. Before a project begins, all participants jointly define business rules, triggering conditions, and execution actions (e.g., when the executor reports progress, the smart contract verifies whether the reported data conforms to the format, timestamp, and digital signature, updating the on-chain progress upon successful verification). Contract code is written in a programming language and sent to the blockchain network. After node consensus, the contract is deployed on the chain, automatically executing preset actions when conditions are met.

[0032] Furthermore, such as Figure 2 As shown, the blockchain server also includes an AI monitoring unit capable of real-time risk identification of project data. The AI ​​monitoring unit includes a rule-based interception component for real-time identification. The rule-based interception component can examine and identify uploaded project data according to pre-defined anomaly types, distinguish abnormal data, write the identification results into the blockchain, and automatically send on-chain warnings to other participants. The AI ​​monitoring unit also includes an intelligent algorithm component, which runs a machine learning model and can analyze and identify project data, identifying potential risks that the rule-based interception component cannot cover. In order to solve the problems of lag and large errors in manual monitoring in traditional project management, an AI monitoring unit is set up for real-time risk identification. When identifying abnormal fund flow in project data, the following types of abnormal fund flow are identified: 1. Unrelated transactions: Payments are not supported by corresponding project tasks, acceptance records, or contracts (e.g., the executor suddenly transfers 1 million to an unfamiliar account, with no related procurement contract hash on the blockchain). 2. Overpayment: The amount of a single payment or cumulative payment exceeds the corresponding contract / budget limit; 3. Splitting to circumvent: Split large sums of money into multiple smaller transactions (e.g., splitting 500,000 into 5 transactions of 100,000 each) to circumvent large payment review rules; 4. Abnormal timing: Payment is made before the acceptance date or after the payment period stipulated in the contract (e.g., deliberately delaying payment to the supplier, suspected of misappropriation). 5. Abnormal transaction network: Frequent transfers to the same non-partner account (e.g., the executor makes monthly transfers to a personal account that is unrelated to the project). 6. Missing vouchers: The payment was not associated with the hash of the necessary vouchers (such as invoices and acceptance slips) (there is no corresponding evidence record on the chain); The rule-based interception component performs hard checks on each transaction by pre-defining specific anomaly types, such as: Association verification: The transaction must be associated with a project task, acceptance record, or contract; if any element is missing, it is marked as a missing document anomaly; Amount verification: The transaction amount must be ≤ the associated contract / budget amount (read from the on-chain budget data); if it exceeds, it is marked as an over-amount anomaly; Time verification: The payment time must be ≥ the acceptance time of the associated task (read from the on-chain acceptance time); otherwise, it is marked as a time anomaly; Account verification: The payee must be on the on-chain whitelist; payments to accounts outside the whitelist are marked as unfamiliar account anomalies. When an anomaly occurs, the rule-based interception component automatically sends on-chain alerts to other participants, and the identified results are written to the blockchain. Since the rule-based interception component can only identify pre-defined explicit anomalies, it may miss potential risks that are highly concealed and have complex patterns. Therefore, an intelligent algorithm component is used for supplementary identification. The intelligent algorithm component constructs behavioral profiles and correlation networks by training on abnormal transaction patterns in historical project data, and identifies hidden risks that deviate from normal patterns, such as disguised related transactions, closed-loop fund flows, and multi-account coordinated cash-out. The machine learning model selected is XGBoost / LightGBM.

[0033] Furthermore, the intelligent algorithm component can integrate and analyze project data and project issues based on the project data and project files uploaded by each participant, and identify potential factors that may lead to delays in the project schedule in advance.

[0034] When in use, the intelligent algorithm component can analyze multi-source data based on the data provided by each participant. Project data from all participants is uploaded to the blockchain to ensure data immutability. Relying on the comprehensiveness and authenticity of the data, it performs multi-source data fusion analysis to identify potential factors that may cause delays in advance. By quantifying risk levels and issuing early warning signals, it facilitates timely intervention by the project team. Potential factors include: schedule delays, resource shortages, quality rework, and external interference. For example, construction progress uploaded by the contractor may be lower than expected; discrepancies may exist between the supplier's delivery plan and actual deliveries, low attendance rates among construction teams, and high equipment failure rates, leading to resource shortages and potential delays in subsequent processes; multiple quality-related rectifications exceeding deadlines may also cause delays; and external interference such as high rainfall probability or high temperature warnings may also cause delays. In practice, project data from each participant is uploaded to the blockchain server. The data preprocessing unit standardizes the project data format and unifies data standards. The intelligent algorithm component aligns the data streams from each source using timestamps to form a planned progress curve and an actual progress curve. Features reflecting risk trends are extracted from the raw data, such as: progress-related features: progress deviation rate, progress acceleration, and key node completion rate; resource-related features: resource load rate (e.g., personnel attendance rate, construction equipment load rate), material delivery delay rate, and equipment availability; quality-related features: quality defect density, rework frequency, and first-time acceptance pass rate; and environmental features: number of days of adverse weather. Based on these multi-dimensional features, the data is input into a graph neural network (GNN) and a time series model (e.g., LSTM). The time series model predicts future progress curves based on historical progress data and compares them with the planned curve to calculate the expected lag days. The graph neural network models the transmission relationship between risk factors (e.g., material delay → worker idleness → progress delay → quality rework) to quantify the impact of a certain risk on the final cycle, combining the risk propagation path and impact weights. Then, by combining the results of the above models, a cycle risk index (0-100 points) is calculated through weighted scoring (e.g., schedule delays account for 40%, resource shortages account for 30%, quality problems account for 20%, and external risks account for 10%), and corresponding to pre-established early warning levels (e.g., low risk 0-30 points, medium risk 31-60 points, and high risk 61-100 points). The early warning information is distributed to all relevant participants so that they can take timely intervention and coordination measures to reduce the risk of project delays.

[0035] The foregoing has shown and described the basic principles, main features, and advantages of the present invention. Those skilled in the art should understand that the present invention is not limited to the above embodiments. The embodiments and descriptions in the specification are merely illustrative of the principles of the invention. Various changes and modifications can be made to the invention without departing from its spirit and scope, and all such changes and modifications fall within the scope of the claimed invention.

Claims

1. A project end-to-end collaborative management system based on blockchain technology, characterized by: It includes a client module, a node server module, and a blockchain server; the client module includes an information receiving unit and a first information sending and receiving unit; the node server module includes a second information sending and receiving unit, a hash encryption unit, and a packaging unit; The information receiving unit is used to receive project data and project files uploaded by the participants; The first information transceiver unit is used to transmit and receive data transmitted with the node server module; The hash encryption unit is used to calculate the hash value of the project file; The packaging unit is used to package project data and project file hash values ​​into a project data package, which, after consensus by the node server module, generates an on-chain credential. The second information transceiver unit is used to download project data packages from the data blockchain server, transmit and receive data with the client, and upload the packaged project data packages and on-chain credentials to the blockchain server. A blockchain server is a distributed blockchain network composed of node server modules from all participating parties.

2. The project end-to-end collaborative management system based on blockchain technology according to claim 1, characterized in that: The node server module also includes a digital signature unit, which is used to encrypt the packaged project data packet using a private key to generate a digital signature. When the second information sending and receiving unit uploads the digital signature and the project data packet together, it uploads them to the blockchain server.

3. The project end-to-end collaborative management system based on blockchain technology according to claim 2, characterized in that: The blockchain server includes a synchronization node unit and a sharded storage unit, and the node server module further includes a file splitting unit; The synchronization node unit is used to store project data packets, and each node server module downloads project data packets in real time and maintains the consistency of project data packets. The file splitting unit is used to split large files stored in the project files into several data blocks; The segmented storage unit is used to store data blocks in segments and Merkle tree information formed by several data blocks.

4. The project end-to-end collaborative management system based on blockchain technology according to claim 3, characterized in that: The blockchain server has multiple channels, which are isolated according to business processes. Each project's node server module only synchronizes the project data of its own channel and downloads the project files of its own channel.

5. The project end-to-end collaborative management system based on blockchain technology according to claim 1, characterized in that: The client module also includes a data preprocessing unit, which can standardize the format of the received raw data and unify the file encoding format.

6. The project end-to-end collaborative management system based on blockchain technology according to claim 1, characterized in that: The node server module also includes a local storage unit. Sensitive privacy data in the project data is encrypted using a hash algorithm. The calculated hash value is packaged and sent to the blockchain server. Sensitive privacy data in the project data is stored in the local storage unit.

7. The project end-to-end collaborative management system based on blockchain technology according to claim 3, characterized in that: The blockchain server also includes a smart contract unit, which can automatically trigger execution when preset conditions are met according to pre-established business rules. The execution process and results are recorded on the blockchain server and synchronized on the blockchain.

8. The project end-to-end collaborative management system based on blockchain technology according to claim 3, characterized in that: The blockchain server also includes an AI monitoring unit capable of real-time risk identification of project data. The AI ​​monitoring unit includes a rule interception component for real-time identification. The rule interception component can examine and identify uploaded project data according to pre-set anomaly types, distinguish abnormal data, write the identification results into the blockchain, and automatically send on-chain warnings to other participants.

9. The project end-to-end collaborative management system based on blockchain technology according to claim 8, characterized in that: The AI ​​monitoring unit also includes an intelligent algorithm component, which runs an artificial intelligence learning model that can analyze and identify fund flows and detect potential risks that are difficult for the rule-based interception component to cover.

10. The project end-to-end collaborative management system based on blockchain technology according to claim 9, characterized in that: The intelligent algorithm component can integrate and analyze project data and project issues based on the project data and project files uploaded by each participant, and identify potential factors that may lead to delays in advance.

Images