Intelligent contract-driven distributed collaborative office system

Abstract

The invention relates to the technical field of data processing, in particular to a distributed collaborative office system driven by an intelligent contract. Comprising a distributed account book module used for persistently storing key data of collaborative office and a smart contract state; the intelligent contract module is deployed on the distributed account book, comprises an intelligent contract of a plurality of precoding business logics and is used for automatically executing processing of a collaborative office task according to a preset rule; and the collaborative application module is used for enabling a user to interact with the intelligent contract layer, initiating collaborative office operation and feeding back an execution result of the intelligent contract to the user. According to the system and the method, the intelligent contract and the distributed account book technology are combined and applied, so that the transparency and the credibility of cooperative work can be remarkably enhanced, the data security and the non-tampering property are improved, and the automation level and the overall efficiency of a cooperative process are improved; and communication cost and potential disputes caused by information asymmetry and manual intervention are effectively reduced.

Description

Technical Field

[0001] The present invention relates to the technical field of data processing, and specifically to a distributed collaborative office system driven by smart contracts. Background Art

[0002] Current collaborative office systems have played an important role in improving organizational work efficiency and information sharing. However, most of these systems are built on a centralized server architecture. Although this centralized architecture has its convenience in deployment and management, it also brings inherent risks and limitations. First, the risk of single-point failure is significant. Any hardware failure, software crash, or cyber attack on the central server may cause the entire collaborative office system to collapse, seriously affecting work continuity. Second, the issues of data sovereignty and security are prominent. All data is centrally stored and managed, making it easy for data to be stolen, tampered with, or misused by central administrators with access rights or malicious attackers. This risk is particularly fatal in collaborations involving sensitive business information or intellectual property. Third, the lack of transparency is obvious. The execution of collaboration processes, the modification history of data, and the allocation of permissions often rely on the internal records of the central system, and it is difficult for external participants to effectively supervise and verify, which easily leads to trust issues.

[0003] In practical applications, existing systems have shown many deficiencies in handling cross-organizational collaborations, clearly defining task responsibilities, fairly distributing benefits, ensuring the security of data sharing, and automatically executing protocols. For example, in a project involving multiple parties, determining whether a task is completed, the attribution of work results, and the incentive distribution based on contribution often require a large amount of manual communication, coordination, and intervention. These processes are not only inefficient, but also extremely prone to disputes and disputes due to information asymmetry or subjective judgment due to the lack of objective and immutable records and automated execution mechanisms. Even if advanced project management tools are introduced or partial cloud-based solutions are adopted, these attempts are usually just improvements within the existing centralized framework and fail to fundamentally solve the core problems of trust deficiency, lack of transparency, and difficulty in automatically enforcing protocols brought about by centralization. Summary of the Invention

[0004] The present invention provides a distributed collaborative office system driven by smart contracts, which can significantly enhance the transparency of the collaboration process, ensure the security and immutability of data, realize the automated execution of task management and collaboration protocols, and on this basis, build an efficient collaborative working environment that can be trusted by all participating parties.

[0005] The distributed collaborative office system driven by smart contracts includes:

[0006] A distributed ledger module: used to store key data related to collaborative office and the status information of smart contracts;

[0007] Smart contract module: Deployed on top of the distributed ledger module, the smart contract module contains multiple smart contracts, and the multiple smart contracts contain preset business logic rules for automatically executing the processing of at least one collaborative office task. The processing of the collaborative office task includes, but is not limited to, task life cycle management and data access permission control.

[0008] Collaborative application module: Connected to the smart contract module, it is used to receive the collaborative office operation instructions of the user, convert the operation instructions into call requests for the corresponding smart contracts in the smart contract module, and present the results of the execution of the smart contracts to the user.

[0009] Preferably, the underlying layer of the distributed ledger is implemented based on blockchain technology. The key data and smart contract status information are recorded in the blocks of the blockchain in the form of transactions, and the blockchain technology implementation includes a Layer-2 scaling solution for improving transaction throughput and reducing transaction costs.

[0010] Preferably, the smart contract module also includes using zero-knowledge proofs to verify specific claims of task completion or the compliance of data access permissions without revealing the specific content.

[0011] Preferably, the smart contract module includes:

[0012] Identity authentication and permission management contract: Used to manage user identity information, roles, and the operation permissions of users to resources within the system. It further uses decentralized identifiers and verifiable credentials for self-management of user identities and fine-grained, verifiable permission declarations and grants.

[0013] Task life cycle management contract: Used to define and execute the logic of task creation, assignment, acceptance, submission, acceptance, and status change. It further integrates a zero-knowledge proof mechanism, allowing task executors to prove certain aspects of the task being completed according to preset standards without revealing the details of the task results.

[0014] Document and data management contract: Used to record the metadata and version history of documents, and manage access credentials or permission logic for off-chain stored data associated with documents. It further supports performing homomorphic encryption operations on encrypted documents stored in the data storage and management module, allowing collaborative editing or data analysis in the ciphertext state, or using zero-knowledge proofs to verify the access permissions of users to specific encrypted document fragments without decrypting the entire document.

[0015] Preferably, the smart contract module further includes a collaboration protocol and an incentive contract, which are used to encode collaboration rules and milestones, and automatically execute the distribution of rewards according to preset conditions. It is further integrated with a decentralized oracle to obtain verification data related to the quality of collaboration results or external conditions from external trusted data sources to trigger the distribution of the rewards.

[0016] Preferably, the smart contract-driven distributed collaborative office system further includes:

[0017] A data storage and management module, connected to the smart contract module, for storing large file data generated during collaborative office work;

[0018] The document and data management contract is also used to store the hash value or content identifier of the large file data, and controls access to the large file data through the permission rules defined in the identity authentication and permission management contract and combined with zero-knowledge proof for privacy protection verification.

[0019] Preferably, the data storage and management module adopts distributed storage technologies such as IPFS or Swarm.

[0020] A smart contract-driven distributed collaborative office method includes:

[0021] Receiving a collaborative office operation instruction initiated by a user through the collaborative application module;

[0022] The collaborative application module calls the corresponding smart contract in the smart contract module according to the operation instruction to process the operation instruction;

[0023] The called smart contract executes corresponding operations according to the business logic rules preset inside it, which include privacy protection calculations, and records the results of the operations or the information on state changes caused in the distributed ledger module.

[0024] Preferably, when the collaborative office operation instruction is a task creation instruction, it further includes:

[0025] The task lifecycle management contract records task information in the distributed ledger module, including task description, designated executor, and initial state of the task.

[0026] Preferably, when the collaborative office operation instruction is a result submission instruction, it further includes:

[0027] The user submits proof of results related to the task through the collaborative application module, such as the hash value of the results, or a zero-knowledge proof for proving that the results meet specific standards;

[0028] The task lifecycle management contract records the proof of achievement in the distributed ledger module and updates the task status to pending acceptance.

[0029] Preferably, after the task is confirmed to be completed, it further includes:

[0030] The collaboration agreement and the incentive contract automatically determine whether the incentive conditions are met according to the preset incentive rules and the task completion situation obtained through the decentralized oracle;

[0031] If the incentive conditions are met, the collaboration agreement and the incentive contract automatically execute the operation of allocating the preset rewards to the executor of the task and record the allocation result in the distributed ledger module.

[0032] Preferably, when the collaborative office operation instruction is a document access request, it further includes:

[0033] The identity authentication and permission management contract verifies the access permission of the requesting user by verifying the attributes declared in the verifiable credentials submitted by the user or by verifying that the user meets the pre-stored permission rules through zero-knowledge proof;

[0034] If the verification passes, the user is allowed to access the corresponding document data stored in the data storage and management module or perform authorized calculation operations on the homomorphically encrypted document data.

[0035] Compared with the prior art, the advantages of the present invention are as follows:

[0036] Enhanced transparency and credibility: All core rules of collaborative office, the real-time status of tasks, every important change of data and its historical records are securely recorded on the distributed ledger. These records are publicly transparent to all authorized participants and cannot be unilaterally tampered with due to the characteristics of the distributed ledger. This high degree of transparency and the immutability of data greatly reduce information asymmetry, significantly enhance the mutual trust foundation among participants, and lay a solid foundation for smooth collaboration.

[0037] Improved security: The distributed architecture of the system fundamentally avoids the single point of failure risk faced by traditional centralized systems. Even if some nodes fail, the entire system can still operate and the data will not be lost. At the same time, combined with cryptographic techniques and the data access permission logic strictly controlled by smart contracts, it ensures the confidentiality, integrity and availability of collaborative data, effectively preventing unauthorized access and malicious tampering.

[0038] Improving Collaboration Efficiency: Smart contracts can automatically execute a large number of repetitive and procedural tasks according to preset logic. For example, once a task meets specific conditions, it can be automatically assigned to the next process handler; the approval process can automatically flow according to rules; once the results meeting the delivery standards are accepted, the corresponding payments or incentives can be automatically triggered and executed by the smart contract. This automation significantly reduces the need for manual intervention, shortens waiting times and communication costs, and thus significantly accelerates the overall collaboration process. BRIEF DESCRIPTION OF THE DRAWINGS

[0039] Figure 1 It is a schematic diagram of the architecture of the distributed collaborative office system driven by the smart contract proposed by the present invention. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0040] Next, the technical solutions in the embodiments of the present invention will be clearly and completely described in conjunction with the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are only a part of the embodiments of the present invention, rather than all the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those of ordinary skill in the art without creative efforts shall fall within the protection scope of the present invention.

[0041] Embodiment 1: Referring to Figure 1 , an embodiment of the present invention provides a system architecture of a distributed collaborative office system driven by a smart contract, including:

[0042] Distributed ledger module: This module is the infrastructure for the operation of smart contracts and the trusted storage of data. It can select existing public blockchains, consortium blockchains or private blockchains, or other types of distributed ledger technologies for implementation. Its key features include:

[0043] Consensus mechanism: Ensure that all network nodes reach an agreement on the ledger state, such as proof of work, proof of stake, practical Byzantine fault tolerance, etc.

[0044] Node types: May include verification nodes (participating in consensus and transaction packaging), light nodes (only synchronizing part of the data), etc.

[0045] Transaction processing process: Operations that need to change the ledger state initiated by users through the collaborative application module (such as creating tasks, updating permissions) will be packaged into transactions, broadcast to the network, and recorded in the block after verification and consensus. This layer ensures the immutability of transactions, the transparency of data, and the complete traceability through cryptography, providing guarantees for the reliable execution of the upper-layer smart contracts.

[0046] Smart Contract Module: This module is the core module of the present invention and is deployed on the underlying distributed ledger network. This module contains a series of specially designed smart contracts, which solidify various core rules and processes of collaborative work in the form of code. The main types of smart contracts may include:

[0047] Identity Authentication and Permission Management Contract: Responsible for managing the digital identities of system users (e.g., through public-private key pairs or decentralized identity identifiers DID). This contract records the roles of users and, based on roles or specific authorizations, finely manages users' access and operation permissions to different collaboration spaces, specific documents, and functional modules (such as read, write, modify, approve, etc.).

[0048] Task Lifecycle Management Contract: This contract defines the complete process and state transition logic of a task from creation to end. For example, task creation, assignment, acceptance or rejection by the assignee, status updates during execution, result submission, acceptance or rejection by relevant parties, until the task is finally closed or archived. Each status change will be recorded on the distributed ledger.

[0049] Document and Data Management Contract: This contract mainly manages the metadata and control logic related to collaborative work documents and data. It records key information such as the document creator, creation time, version number, modification history summary, access logs, etc. For large files stored in an off-chain distributed storage system, this contract will store their content hashes and access credentials to ensure that access to this off-chain data is strictly controlled by the smart contract.

[0050] Collaboration Agreement and Incentive Contract: This contract is used to encode complex collaboration agreement terms (such as project milestones, deliverable standards, quality requirements, reward and punishment rules). When preset conditions are met, this contract can automatically execute corresponding incentive distributions (such as issuing project tokens, points, or triggering payment processes) or punishment measures.

[0051] There are interactions and dependencies among these smart contracts. For example, the task management contract may trigger the execution of the incentive contract after task acceptance. Smart contracts achieve this interaction by listening to on-chain events or directly calling the functions of other contracts.

[0052] Collaborative Application Module: This module includes a suite of collaborative work functions that users can directly perceive and use. For example:

[0053] Document Collaborative Editing Unit: Supports multiple people to edit the same document in real-time or asynchronously online and records the version history.

[0054] Project Management Unit: Supports project creation, task decomposition, progress planning, resource allocation, etc.

[0055] Task Assignment and Tracking Unit: It realizes the assignment, reception, status update, reminder, etc. of tasks.

[0056] Approval Workflow Unit: It defines and executes various approval processes, such as document approval, expense approval, etc.

[0057] This module receives requests from users, parses and converts them into calls to the smart contract layer, or directly interacts with the data storage and management module. At the same time, it formats the results of smart contract execution or the data read from the distributed ledger and presents them to users.

[0058] API Interface: This module also provides a set of well-defined API interfaces. These APIs allow third-party applications or services to integrate with this collaborative office system, or are used for secondary development of customized functions by enterprises with special needs, thus enhancing the openness and scalability of the system.

[0059] Data Storage and Management Module: This module is used to store large files generated in collaborative office to avoid the high costs and low efficiency problems brought about by directly storing these files on the distributed ledger. Optional technical solutions include:

[0060] IPFS or Swarm: Such peer-to-peer distributed storage networks provide high availability and censorship resistance through content addressing (using the hash value of the file as its address) and redundant data sharding storage.

[0061] Traditional distributed file systems or object storage services: Such as HDFS or cloud storage services, combined with permission management.

[0062] Regardless of the storage solution adopted, the hash value (or unique identifier) of the file and related metadata (such as file name, size, uploader) will be recorded in the "Document and Data Management Contract" on the chain. The smart contract will control the access rights to these off-chain actual data. For example, only contract calls that meet specific conditions can obtain valid links or keys to access or decrypt off-chain files. This "on-chain anchor + off-chain storage + smart contract control" model is one of the important technical means to balance data storage efficiency, cost, and security controllability.

[0063] This modular system architecture design clearly defines the functional responsibilities of each part. For example, subdividing smart contracts into different modules such as identity, task, document, incentive, and governance not only makes the system logic clearer, easier to develop and maintain, but also provides great flexibility for the future evolution and customization of the system. Different organizations or projects can selectively deploy or replace certain smart contract modules according to their own needs without making subversive transformations to the entire system.

[0064] Moreover, the detailed division of on-chain data and off-chain data, and the design of securely associating the two through smart contracts solve the inherent bottleneck of distributed ledger technology in dealing with large-scale data storage. Place the key metadata and control logic with high-frequency changes and strict consensus requirements on the chain, leveraging its immutable and transparent characteristics; while place the bulky file content in an off-chain efficient storage system, and then manage its hash and access rights through smart contracts. This reflects the comprehensive consideration of technical feasibility, economy, and security in practical applications, greatly enhancing the practicality of the present invention.

[0065] Embodiment 2: Another embodiment of the present invention provides a smart contract-driven distributed collaborative office method, which specifically includes:

[0066] User registration and identity authentication: New users access the system application interface and initiate a registration request. Users may need to provide some basic information and generate or associate a digital identity. The system submits the registration information to the "Identity Authentication and Permission Management Contract". This contract verifies the validity of the information, records the user's identity, and may grant the user an initial role and permissions according to preset rules or administrator configurations. The result of this process is recorded on the distributed ledger.

[0067] Create or join a collaboration space / project: Registered users can create a new collaboration space or be invited to join an existing one. When creating a collaboration space, users can configure the name, description, member management rules, etc. of the space through the application interface, and this information may be recorded and managed by a specific "Space Management Contract" or through the "Identity Authentication and Permission Management Contract". Joining an existing space requires meeting the access conditions of that space, and relevant permission changes are handled by smart contracts.

[0068] Initiate / assign collaborative tasks: Within a collaboration space, users with corresponding permissions can initiate a new collaborative task through the application interface. After the user fills in the task details, the collaborative application module packages this information and calls the create task function of the "Task Lifecycle Management Contract". The smart contract verifies the initiator's permissions, records the task information in the distributed ledger, and notifies the designated task executor.

[0069] Accept / Execute / Submit tasks: After receiving the task notification, the task executor views the task details through the application interface and selects to accept or reject the task. This operation is achieved by calling the corresponding function of the "Task Lifecycle Management Contract", and the task status is updated on the chain accordingly. During the task execution, the executor can update the task progress. After the task is completed, the executor submits the work result through the application interface (for example, uploads the result file to the data storage and management module and submits the file hash to the smart contract). The smart contract records the result submission information and updates the task status to "pending acceptance".

[0070] Sharing / Collaborative Editing of Documents: In task execution or daily collaboration, users may need to share or collaboratively edit documents. When a user uploads a document, the document content is stored off-chain, and its hash and metadata are recorded on-chain by the "Document and Data Management Contract". Users can set access and editing permissions for the document, and these permission rules are managed by the "Identity Authentication and Permission Management Contract" or a dedicated document permission contract. When other users access or edit the document, the system will verify their permissions through smart contracts. Modifications to the document will result in new versions, and the version history is recorded by smart contracts.

[0071] Task Acceptance and Result Confirmation: After the task result is submitted, the designated acceptor will receive a notification. The acceptor reviews the result and approves or rejects the result by invoking the functions of the "Task Lifecycle Management Contract" through the application interface. The smart contract updates the final status of the task (such as "completed" or "rejected") according to the acceptor's operation and records the result on the distributed ledger.

[0072] Automated Incentive Allocation: If the task is successfully completed and passes the acceptance, and the task is associated with an incentive mechanism (defined in the "Collaboration Agreement and Incentive Contract"), the incentive contract will automatically determine whether to trigger the incentive according to the preset conditions. If the conditions are met, the incentive contract will automatically execute the incentive allocation operation (such as transferring tokens or points to the executor's account). This allocation process is completely automated by the smart contract and recorded on-chain.

[0073] Completion and Archiving of Collaboration: After the task is completed, relevant task records, document versions, communication histories, etc. are securely stored in the distributed ledger and distributed storage system for ready reference and auditing. After the project or collaboration cycle ends, the relevant data can be archived.

[0074] In this method process, each key operation involves interaction with smart contracts. Smart contracts not only record the results and state transitions of the operations but also automatically execute the process flow, permission verification, and condition judgment according to the preset rules, thus ensuring the transparency, efficiency, credibility, and automation of the collaborative office process. This method fundamentally changes the dependence of traditional collaborative office on centralized servers and manual intervention.

[0075] Embodiment 3: Another embodiment of the present invention shows the implementation of secure sharing and version control of documents by combining on-chain smart contracts and off-chain distributed storage, including:

[0076] Document Upload and On-chain Anchoring: Users upload a document through the application interface. The actual content of the document is sent to the system's data storage and management module. The system generates a unique hash value (content identifier) for the document. Subsequently, the collaborative application module calls the "Document and Data Management Contract" to record the metadata of the document (such as file name, creator ID, upload timestamp, initial version number) along with its hash value in the distributed storage onto the distributed ledger.

[0077] Permission Setting and Management: The document uploader can set access permissions for the document through the application interface. For example, it can specify which users or user groups have read-only permissions and which have edit permissions. These permission rules are written into the "Identity Authentication and Permission Management Contract" or a dedicated "Document Permission Contract" and are associated with the unique ID (or hash) of the document recorded in the "Document and Data Management Contract".

[0078] Document Access and Permission Verification: When other users attempt to access the document, the system first sends a query request to the relevant permission management smart contract, passing in the ID of the requesting user, the document ID, and the type of operation requested. The smart contract verifies based on the permission rules recorded on the chain. If the verification passes, it provides the user with a way to access the actual off-chain document (for example, returns the hash of the document in the distributed storage, and the user client then retrieves the file from a network such as IPFS using this hash; or, if the file is encrypted, the smart contract may also participate in the decryption key distribution or authorization process). All successful access attempts and failed unauthorized access attempts will be recorded by the smart contract to form an audit log.

[0079] Document Editing and Version Control: If a user has edit permissions and modifies the document, when saving the new version, the content of the new version of the document is also uploaded to the distributed storage and a new hash value is generated. At this time, the system calls the "Document and Data Management Contract" to record the hash value of the new version, the modifier ID, the modification timestamp, and the new version number onto the chain and associates them with the original document ID. The hash and metadata of the old version of the document still remain on the chain, forming an immutable version history record. Users can trace and view any historical version of the document at any time.

[0080] In this way, the large document content itself does not occupy on-chain storage space, but its existence, integrity (through hash verification), version evolution history, and access permissions are strictly and transparently managed by the on-chain smart contract, thus achieving secure, controllable, and traceable document collaboration.

[0081] In the description of this specification, the descriptions referring to terms such as "one embodiment", "example", "specific example", etc. mean that the specific features, structures, materials or characteristics described in connection with the embodiment or example are included in at least one embodiment or example of the present invention. In this specification, the schematic representations of the above terms do not necessarily refer to the same embodiment or example. Moreover, the specific features, structures, materials or characteristics described may be combined in any one or more embodiments or examples in a suitable manner.

[0082] The preferred embodiments of the present invention disclosed above are only used to help illustrate the present invention. The preferred embodiments do not describe all the details in detail, nor do they limit the invention to the specific embodiments described. Obviously, many modifications and variations can be made according to the content of this specification. These embodiments are selected and specifically described in this specification in order to better explain the principles and practical applications of the present invention, so that those skilled in the art can well understand and utilize the present invention. The present invention is only limited by the claims and their full scope and equivalents.

Claims

1. A distributed collaborative office system driven by smart contracts, characterized in that, Comprising: A distributed ledger module: used to store key data related to collaborative office work and the status information of smart contracts; A smart contract module: deployed on top of the distributed ledger module, the smart contract module contains multiple smart contracts, the multiple smart contracts contain preset business logic rules, and are used to automatically execute the processing of at least one collaborative office task according to the rules. The processing of the collaborative office task includes but is not limited to task life cycle management and data access permission control; A collaborative application module: connected to the smart contract module, used to receive the collaborative office operation instructions of the user, convert the operation instructions into call requests for the corresponding smart contracts in the smart contract module, and present the results of the execution of the smart contracts to the user; The smart contract module also includes using zero-knowledge proof to verify the compliance of specific declarations for task completion or data access permissions without revealing the specific content; The underlying of the distributed ledger is implemented based on blockchain technology. The key data and smart contract status information are recorded in the blocks of the blockchain in the form of transactions, and the blockchain technology implementation includes a Layer-2 scaling solution for improving transaction throughput and reducing transaction costs.

2. The distributed collaborative office system driven by smart contracts according to claim 1, characterized in that, The smart contract module includes: An identity authentication and permission management contract, used to manage user identity information, roles, and the operation permissions of users to resources within the system; A task life cycle management contract, used to define and execute the logic of task creation, assignment, acceptance, submission, acceptance, and status change; A document and data management contract, used to record the metadata and version history of documents, and manage access credentials or permission logic for off-chain stored data associated with documents.

3. The distributed collaborative office system driven by a smart contract according to claim 2, wherein, The smart contract module also contains a collaboration protocol and incentive contract, and the collaboration protocol and incentive contract are used to encode collaboration rules and milestones, and automatically execute the distribution of rewards according to preset conditions.

4. The distributed collaborative office system driven by a smart contract according to claim 1, characterized in that, Also including: A data storage and management module, connected to the smart contract module, used to store large file data generated during collaborative office work; The document and data management contract is also used to store the hash value or content identifier of the large file data, and control access to the large file data through the permission rules defined in the identity authentication and permission management contract and combined with zero-knowledge proof for privacy protection verification.

5. The distributed collaborative office system driven by smart contracts according to claim 4, wherein The data storage and management module adopts distributed storage technology, such as IPFS or Swarm.

6. The intelligent contract-driven distributed collaborative office method is applied to the intelligent contract-driven distributed collaborative office system according to any one of claims 1 to 5, and is characterized in that, Including: Receiving a collaborative office operation instruction initiated by the user through the collaborative application module; The collaborative application module calls the corresponding smart contract in the smart contract module according to the operation instruction to process the operation instruction; The smart contract executes the corresponding operation according to the preset business logic rules including privacy protection calculation inside it, and records the results of the operation or the state change information caused in the distributed ledger module.

7. The intelligent contract-driven distributed collaborative office method according to claim 6, wherein When the collaborative office operation instruction is a task creation instruction, it also includes: The task lifecycle management contract records task information in the distributed ledger module, including task description, designated executor, and the initial state of the task.

8. The intelligent contract-driven distributed collaborative office method according to claim 6, wherein When the collaborative office operation instruction is a result submission instruction, it further includes: The user submits proof of results related to the task through the collaborative application module, such as the hash value of the result, or a zero-knowledge proof for proving that the result meets specific criteria; The task lifecycle management contract records the result proof in the distributed ledger module and updates the task state to pending acceptance.

9. The intelligent contract-driven distributed collaborative office method according to claim 8, wherein After the task is confirmed as completed, it further includes: The collaboration protocol and incentive contract automatically determine whether the incentive conditions are met according to the preset incentive rules and the task completion status obtained through the decentralized oracle; If the incentive conditions are met, the collaboration protocol and incentive contract automatically execute the operation of distributing the preset rewards to the executor of the task and record the distribution result in the distributed ledger module.

10. The intelligent contract-driven distributed collaborative office method according to claim 6, wherein, When the collaborative office operation instruction is a document access request, it further includes: The identity authentication and permission management contract verifies the access permission of the requesting user by verifying the attributes declared in the verifiable credentials submitted by the user or by verifying that the user meets the pre-stored permission rules through zero-knowledge proof; If the verification passes, the user is allowed to access the corresponding document data stored in the data storage and management module, or perform authorized computational operations on the homomorphically encrypted document data.

Images