Archive full-life-cycle tracing management method and system based on block chain

Abstract

The invention discloses an archive full-life-cycle tracing management method and system based on a block chain, and relates to the technical field of data processing, and the method comprises the steps: creating a digital archive, generating a unique archive identifier, and storing the unique archive identifier in the block chain; obtaining event related data of the archive; calling a block chain smart contract, associating event-related data with the archive identifier, and recording the event-related data as newly-added block data into a block chain; in response to the tracing request, retrieving and extracting all associated on-chain records from the block chain according to the target archive identifier; the method is based on chain records. Constructing and outputting at least one of the following traceability views: a circulation track and a state transition history of an archive entity, an association relationship graph between the archive and other associated archives, all operators related to the archive in a life cycle and operation records thereof, and change history and version comparison information of archive content or metadata; and based on the output tracing view, verifying the archive and triggering a predefined disposal rule or alarm.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of blockchain data processing, and in particular to a file full life cycle traceability management method and system based on a blockchain. BACKGROUND

[0002] Currently, the file management industry generally faces the core problems of difficult full life cycle information traceability and weak tamper resistance. The traditional management mode relies on manual recording and paper account books, which has the risk of low efficiency, loss or tampering of records, and is difficult to clearly and credibly restore the complete track of the file from generation, circulation, utilization to destruction.

[0003] Currently, the mainstream solution is to use a centralized database for electronic information management, which has improved efficiency but has inherent defects: centralized storage is vulnerable to single-point attacks or malicious tampering by internal personnel, and the data credibility and security are questionable; information systems at each link are often independently constructed, forming "information islands", and it is difficult to realize cross-system, full-chain data penetration and consistency verification.

[0004] Therefore, the industry urgently needs a new management solution that can ensure data tamper resistance, establish cross-entity trust, and support multi-dimensional, fine, and automated traceability and verification of file entity status, associated relationships, operation behavior, and content changes, to meet the increasingly stringent compliance audit and security control requirements. SUMMARY

[0005] The present application provides a file full life cycle traceability management method and system based on a blockchain to solve the above problems.

[0006] In one aspect, the present application provides a file full life cycle traceability management method based on a blockchain, the method comprising the following steps: step S1: creating a digital file and generating a unique file identifier; storing the on-chain summary information of the digital file and the file identifier in the blockchain; step S2: obtaining event-related data of the file; calling a blockchain smart contract, associating the event-related data with the file identifier, and recording the event-related data as new block data in the blockchain to update the on-chain state of the file; step S3: in response to a traceability request, retrieving and extracting all associated on-chain records from the blockchain according to the target file identifier; based on the on-chain records, constructing and outputting at least one of the following traceability views: the circulation track and state transition history of the file entity itself, the association relationship graph between the file and other associated files, all operators involved in the file in the life cycle and their operation records, and the change history and version comparison information of the file content or metadata; step S4: verifying the file based on the output traceability view; and triggering a predefined disposal rule or alarm according to the verification result.

[0007] In one implementation of this application, in step S1, the on-chain digest information includes at least the hash value of the digital file, the creation timestamp, the creator's digital identity certificate, and the file identifier.

[0008] In one implementation of this application, in step S2, the event-related data includes at least: event type, event timestamp, operator digital identity certificate, hash value of the snapshot of the state before and after the event, and evidence identification of the associated physical or electronic certificate.

[0009] In one implementation of this application, the construction and output of the archive entity's own flow trajectory and state change history specifically includes: parsing all on-chain records related to the target archive identifier in chronological order, extracting the event type, occurrence time, responsible party, and storage location information from each record, and generating a linear trajectory diagram with time as the axis that clearly shows all key nodes and location changes of the archive from its creation to the present.

[0010] In one implementation of this application, the construction and output of the relationship graph between the file and other related files specifically includes: parsing the related file identifier recorded in the on-chain record, querying the on-chain summary of the related file through a smart contract; and dynamically generating a network topology graph that displays the reference, composition, and reference relationships between the target file and its upstream and downstream files, reference files, or other files in the same case file, with the target file as the central node.

[0011] In one implementation of this application, the construction and output of all operators and their operation records involved in the lifecycle of the file specifically includes: summarizing the digital identity certificates of operators recorded in all on-chain records, querying a pre-set identity database to obtain operator entity information; generating a detailed operation log list sorted by time, with each item in the list clearly recording the operator, operation time, operation type, and a summary of the system environment at the time of operation.

[0012] In one implementation of this application, the construction and output of the change history and version comparison information of the file content or metadata specifically includes: extracting the file content hash value or metadata snapshot hash stored in each status change event record; locating the change point by comparing the hash values ​​of adjacent versions, and retrieving the full data of the corresponding version in the off-chain storage system for content comparison, and displaying the specific details of the added, deleted or modified content in a highlighted manner.

[0013] In one implementation of this application, the handling rules in step S4 include: if the verification finds that the file transfer chain is broken or the key node signature is missing, the subsequent transfer permission of the file is automatically frozen and an alarm is sent to the supervisory node; if the verification is successful, a trusted traceability report containing the hash value digest of all current on-chain records is generated for the file and attached to the digital copy of the file.

[0014] On the other hand, this application also provides a blockchain-based archive lifecycle traceability management system, the system comprising: an archive management client for initiating archive creation, lifecycle operations, and traceability query requests; a blockchain network composed of multiple consensus nodes for storing an immutable ledger of on-chain archive summaries and all lifecycle event records; a smart contract module deployed on the blockchain network, containing contract code for executing archive registration, event record writing, and traceability logic queries; an off-chain archive storage system for storing the full data files and metadata of digital archives, and anchored to the blockchain network via hash values; and a traceability service engine that communicates with the blockchain network and the off-chain archive storage system for parsing traceability requests, invoking smart contracts, integrating on-chain and off-chain data, and constructing multiple traceability views.

[0015] In one implementation of this application, the smart contract module includes at least: an archive registration contract for verifying and recording the initial on-chain information of the archive; an event processing contract for verifying operation permissions and structurally recording lifecycle events; an association management contract for maintaining and querying the association identifiers between archives; and a traceability query contract for efficiently retrieving and returning the required traceability data set from the blockchain ledger by combining query conditions according to predetermined logic.

[0016] This application provides a blockchain-based method and system for full lifecycle traceability management of archives, which has the following beneficial effects: 1. By leveraging the immutability and decentralization of blockchain, key events throughout the entire lifecycle of archives are anchored on the chain, forming a continuous and reliable data trajectory. This effectively prevents information tampering and loss, providing a reliable technical endorsement and auditing basis for the authenticity and integrity of archives.

[0017] 2. It supports the construction of traceability views from multiple perspectives, including entity flow, relationships, operation logs and content versions, breaking the traditional fragmented state of archival information, fully restoring the dynamic process of archives, and significantly improving the transparency, relevance and refinement of archive management.

[0018] 3. Based on on-chain records, the system automatically verifies the compliance and integrity of the document flow and has built-in intelligent handling rules to provide real-time alerts and permission intervention for abnormal situations, transforming passive verification into proactive control and significantly reducing the risks and management costs of manual review. Attached Figure Description

[0019] The accompanying drawings, which are included to provide a further understanding of this application and form part of this application, illustrate exemplary embodiments and are used to explain this application, but do not constitute an undue limitation of this application. In the drawings: Figure 1A flowchart of a blockchain-based method for full lifecycle traceability management of archives is provided for embodiments of this application; Figure 2 This is a diagram illustrating the composition of a blockchain-based archive lifecycle traceability management system, as provided in this application embodiment. Detailed Implementation

[0020] To make the objectives, technical solutions, and advantages of this application clearer, the technical solutions of this application will be clearly and completely described below in conjunction with specific embodiments and corresponding drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of them. Based on the embodiments in this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0021] This application provides a blockchain-based method and system for full lifecycle traceability management of archives. The technical solution proposed in this application will be described in detail below with reference to the accompanying drawings.

[0022] Figure 1 This application provides a flowchart of a blockchain-based method for full lifecycle traceability management of archives. Figure 1 As shown, the method mainly includes the following steps: Step S1: Create a digital archive and generate a unique archive identifier; store the on-chain summary information of the digital archive and the archive identifier in the blockchain.

[0023] In this application, a file creation request is received, a digital file containing the core attributes and initial state information of the file is generated, and a corresponding unique file identifier is generated; the on-chain summary information of the digital file and the file identifier are anchored and stored in the blockchain to form an immutable initial record.

[0024] Specifically, when the system receives a file creation request, it first parses and extracts the file's core attributes (such as title, document number, category, and security classification) and initial state (such as "new"), encapsulating them into a structured digital file object. Then, it generates a globally unique file identifier (ID) using a UUID algorithm or content-based hashing. The system calculates the cryptographic hash value of the complete content of the digital file and combines it with a creation timestamp accurate to milliseconds and the creator's digital identity signed with their private key to form an on-chain digest. By invoking the file registration smart contract deployed on the blockchain, the digest is bound to the file identifier and submitted to the blockchain network as a transaction. After verification by consensus nodes and packaging into a new block, this record is permanently and immutably stored in the distributed ledger, thus completing the initial anchoring of the file's trusted lifecycle.

[0025] Step S2: Obtain event-related data of the archive; invoke the blockchain smart contract to associate the event-related data with the archive identifier, and record it as new block data in the blockchain to update the on-chain state of the archive.

[0026] In this application, when any lifecycle event of a file occurs—its storage, borrowing, transfer, authentication, or destruction—event-related data is acquired. A blockchain smart contract is invoked to associate the event-related data with the file identifier and record it as new block data in the blockchain, updating the file's on-chain state. The on-chain summary information includes at least the hash value of the digital file, the creation timestamp, the creator's digital identity certificate, and the file identifier. The event-related data includes at least: the event type, the event timestamp, the operator's digital identity certificate, the hash value of the snapshot of the state before and after the event, and the evidence identifier of the associated physical or electronic certificate.

[0027] Step S3: In response to the traceability request, retrieve and extract all associated on-chain records from the blockchain based on the target archive identifier; based on the on-chain records, construct and output at least one of the following traceability views: the archive entity's own flow trajectory and status change history, the relationship graph between the archive and other related archives, all operators involved in the archive's life cycle and their operation records, and the change history and version comparison information of the archive content or metadata.

[0028] In this application, the flow trajectory and status change history of the archive entity itself are constructed and output, specifically including: parsing all on-chain records related to the target archive identifier in chronological order, extracting the event type, occurrence time, responsible party and storage location information in each record, and generating a linear trajectory diagram with time as the axis that clearly shows all key nodes and location changes of the archive from creation to the present.

[0029] Specifically, after receiving a traceability instruction for a specific archive identifier, the traceability service engine first calls the blockchain network's query interface to retrieve all block transaction records associated with that identifier through a smart contract. The system strictly sorts all records according to block timestamps and parses the transaction data payload one by one to accurately extract structured fields: event type (such as "transfer" or "loaned"), timestamp accurate to the second, operator ID verified by digital signature, and target location (such as warehouse number or system address). Subsequently, the engine uses these discrete event points as nodes and automatically draws a continuous trajectory line in the visualization engine with time as the horizontal axis, marking the key attributes of each node, and finally generating an interactive linear time series diagram that intuitively presents the movement path and status (such as "in storage" or "loaned") of the archive in physical or logical space, showing each change.

[0030] Furthermore, a relationship graph between the archive and other related archives is constructed and output, specifically including: parsing the related archive identifiers recorded in the on-chain records, querying the on-chain summary of the related archives through smart contracts; and dynamically generating a network topology graph that displays the reference, composition, and reference relationships between the target archive and its upstream and downstream archives, reference archives, or other archives in the same case file, with the target archive as the central node.

[0031] Specifically, the tracing engine first parses the predefined "related file identifier" field in the target file's on-chain record to obtain a list of one or more related file IDs. Then, it calls a dedicated "relationship query contract" on the blockchain, passing the ID list to the contract. The contract retrieves the initial registration digest (such as name, hash, and creation time) for each related ID in parallel from the on-chain ledger and returns the result set. After receiving the data, the engine constructs a graph data structure in memory: with the target file as the root node and each related file as a child node, and labels each edge with attributes based on the relationship type field of the on-chain record (such as "referenced," "belongs to file," and "referenced from"). Finally, the engine calls a graph layout algorithm (such as force-directed layout) to automatically calculate the node positions and dynamically draws an interactive network topology graph with clearly distinguishable nodes and edges, supporting click-to-view details, using a front-end rendering library.

[0032] Furthermore, the system constructs and outputs all operators and their operation records involved in the lifecycle of the file, specifically including: summarizing the digital identity certificates of operators recorded in all on-chain records, querying the pre-set identity database to obtain operator entity information; and generating a detailed operation log list sorted by time, with each item in the list clearly recording the operator, operation time, operation type, and a summary of the system environment at the time of the operation.

[0033] Specifically, the traceability service engine first calls the blockchain network's query interface to retrieve all on-chain records related to the target file identifier through the traceability query smart contract. The engine parses the transaction data payload of each record, extracting the operator's public key address or DID (Decentralized Identifier) ​​as proof of identity, which is digitally signed. Subsequently, the engine uses an internal security interface to query a pre-built authoritative identity database (such as an LDAP directory or CA authentication library), mapping the digital identity to specific operator entity information (such as name, department, and employee number). The system binds the event type, the blockchain timestamp accurate to milliseconds, and the hash digest of the system environment at the time of the operation extracted from the on-chain metadata (which can reflect information such as terminal, IP, and software version) in each record with the operator entity information, arranges them in strict ascending order according to the timestamp, and generates a structured JSON or XML format log list. Finally, it outputs a complete time-series list of operator behavior with legal evidentiary value, which can be audited and held accountable.

[0034] Furthermore, the system constructs and outputs the change history and version comparison information of the archive content or metadata, specifically including: extracting the archive content hash value or metadata snapshot hash stored in each status change event record; locating the change point by comparing the hash values ​​of adjacent versions, and retrieving the full data of the corresponding version in the off-chain storage system for content comparison, and displaying the details of the specific additions, deletions or modifications in a highlighted manner.

[0035] Specifically, the traceability service engine first invokes a smart contract to retrieve and extract events marked as "content change" or "metadata update" from all on-chain records of the target file. From specific fields of these events, the engine obtains the file content hash value or serialized metadata hash value corresponding to each change. The engine arranges these hash values ​​in chronological order and precisely locates the specific version node (adjacent version pairs with different hash values) where the content or metadata change occurred by comparing adjacent hash values ​​one by one. For each identified version pair of changes, the engine requests the full data file of that version from an off-chain object storage system (such as IPFS or secure cloud storage) based on its corresponding unique content hash. Subsequently, the engine uses text / data difference comparison algorithms (such as line-based diff algorithms or specialized document comparison libraries) to perform detailed analysis on the two versions of the file, calculating the specific content fragments added, deleted, or modified. Finally, through a front-end visualization component, the details, location, and type of the change are intuitively displayed to the user using methods such as highlighting, underlining, or sidebar comparison views.

[0036] Step S4: Verify the archive based on the output traceability view; trigger predefined disposal rules or alarms according to the verification results.

[0037] In this application, the authenticity, integrity, and compliance of the archives are verified based on the traceability view output in step S3; and predefined disposal rules or alarms are triggered according to the verification results.

[0038] Specifically, the handling rules include: if the verification finds that the file circulation chain is broken or the signature of a key node is missing, the subsequent circulation rights of the file will be automatically frozen and an alarm will be sent to the supervisory node; if the verification is successful, a trusted traceability report containing the hash value digest of all current on-chain records will be generated for the file and attached to the digital copy of the file.

[0039] The above is a blockchain-based method for full lifecycle traceability management of archives provided by embodiments of this application. Based on the same inventive concept, embodiments of this application also provide a blockchain-based full lifecycle traceability management system for archives. Figure 2 A diagram illustrating the composition of a blockchain-based archive lifecycle traceability management system provided in this application embodiment is shown below. Figure 2 As shown, the system mainly includes: The document management client 201 is used to initiate document creation, lifecycle operations, and traceability query requests. Blockchain network 202 consists of multiple consensus nodes and is used to store an immutable ledger of on-chain summaries of archives and records of all lifecycle events. The smart contract module 203, deployed on the blockchain network, contains contract code for performing file registration, event record writing, and traceability logic querying; The off-chain archive storage system 204 is used to store the full data files of digital archives and their metadata, and is anchored to the blockchain network through hash values; The traceability service engine 205 communicates with the blockchain network and the off-chain archive storage system to parse traceability requests, invoke smart contracts, integrate on-chain and off-chain data, and construct various traceability views.

[0040] The smart contract module 203 includes at least: an archive registration contract for verifying and recording the initial on-chain information of the archive; an event processing contract for verifying operation permissions and structurally recording lifecycle events; an association management contract for maintaining and querying the association identifiers between archives; and a traceability query contract for efficiently retrieving and returning the required traceability data set from the blockchain ledger by combining query conditions according to predetermined logic.

[0041] Below is an example of a specific application scenario for this application: Digital archive management of a large-scale inter-provincial water conservancy project. This project involves design institutes, multiple construction companies, supervision units, and a provincial archive. The specific process is as follows: 1. Archive Creation and Event Recording: The engineering design institute creates a core digital archive of the "Dam Structure Design Drawings" through the system. The system generates a unique ID "DAM-2023-001" and calculates the file hash value H0, which, along with the creator's digital signature and timestamp, is stored in the blockchain as an initial digest. Subsequently, all key events, such as each approval of the drawings, issuance to construction party A, design changes (from version V1.0 to V1.1), handover to the supervision party for verification, and final archiving to the provincial archives, are recorded permanently on the blockchain by calling smart contracts. The event type, operator signature, changed file hash (e.g., H1), and associated electronic approval document storage ID are recorded as on-chain records.

[0042] 2. Traceability Query Trigger: One year after the project was put into operation, during an internal quality audit, auditors discovered that the design drawings currently archived in the database (hash value H1) appeared to differ from the version of drawings initially received by contractor A, requiring tracing responsibility. Auditors submitted a traceability request for "DAM-2023-001" through the system.

[0043] 3. Multi-dimensional traceability view generation and verification: (1) Flow trajectory view: The system immediately generates a timeline view, clearly showing the complete path and time nodes of the drawing from the creation of the design institute → receipt by the construction party A → online submission of change application by the design institute → approval by the supervisor → receipt by the archives. (2) Operation log view: The list details all operators (real names), operation time (accurate to the second) and operation type. The auditors quickly discovered that after the design institute submitted the change application, there was only the approval record of the supervisor, but the "confirmation of receipt" record of the construction party A, which should have been there according to regulations, was missing. (3) Version comparison view: The system automatically locates the change point where the hash value changes from H0 to H1, and retrieves the full drawing files of V1.0 and V1.1 stored in the chain. After comparison, it highlights the modification details of a dam body parameter. (4) Association map view: The system displays the association relationship between the design drawing and multiple related archives such as "geological exploration report" and "construction log".

[0044] 4. Intelligent Verification and Handling: Based on the above view, the system automatically verifies that "the file transfer chain is broken at the confirmation stage of Construction Party A" and "the digital signature of the key node (Construction Party A) is missing." The smart contract then automatically triggers the handling rules: freezing the external sharing and borrowing permissions of the "DAM-2023-001" file and sending alarm notifications to the project director and file supervisor. At the same time, the system generates a trusted traceability report containing the hash digests of all on-chain records for auditors as audit evidence.

[0045] This system transforms tasks that would otherwise require days or even weeks of multi-party verification and paper document checks into precise problem identification and responsibility clarification within minutes. The blockchain-guaranteed immutable records prevent any party from shifting blame, the multi-dimensional view provides a comprehensive overview, and automated compliance verification and processing significantly improve management efficiency and response speed, effectively mitigating quality and legal risks that may result from incomplete document transfer.

[0046] The various embodiments in this application are described in a progressive manner. Similar or identical parts between embodiments can be referred to mutually. Each embodiment focuses on describing the differences from other embodiments. In particular, the device embodiments are basically similar to the method embodiments, so the description is relatively simple; relevant parts can be referred to the descriptions of the method embodiments.

[0047] It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0048] The above description is merely an embodiment of this application and is not intended to limit the scope of this application. Various modifications and variations can be made to this application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of the claims of this application.

Claims

1. A blockchain-based method for full lifecycle traceability management of archives, characterized in that, The method includes the following steps: Step S1: Create a digital archive and generate a unique archive identifier; store the on-chain summary information of the digital archive and the archive identifier in the blockchain; Step S2: Obtain event-related data of the archive; invoke the blockchain smart contract to associate the event-related data with the archive identifier, and record it as new block data in the blockchain to update the on-chain state of the archive; Step S3: In response to the traceability request, retrieve and extract all associated on-chain records from the blockchain based on the target archive identifier; based on the on-chain records, construct and output at least one of the following traceability views: the archive entity's own flow trajectory and status change history, the relationship graph between the archive and other related archives, all operators involved in the archive's life cycle and their operation records, and the change history and version comparison information of the archive content or metadata; Step S4: Verify the archive based on the output traceability view; trigger predefined disposal rules or alarms according to the verification results.

2. The method for full lifecycle traceability management of archives based on blockchain according to claim 1, characterized in that, In step S1, the on-chain digest information includes at least the hash value of the digital file, the creation timestamp, the creator's digital identity certificate, and the file identifier.

3. The method for full lifecycle traceability management of archives based on blockchain according to claim 1, characterized in that, In step S2, the event-related data includes at least: event type, event timestamp, operator digital identity certificate, hash value of the snapshot of the state before and after the event, and evidence identification of the associated physical or electronic credential.

4. The method for full lifecycle traceability management of archives based on blockchain according to claim 1, characterized in that, The construction and output of the archive entity's own flow trajectory and state change history specifically includes: parsing all chain records related to the target archive identifier in chronological order, extracting the event type, occurrence time, responsible party and storage location information from each record, and generating a linear trajectory diagram with time as the axis that clearly shows all key nodes and location changes of the archive from creation to the present.

5. The method for full lifecycle traceability management of archives based on blockchain according to claim 1, characterized in that, The construction and output of the relationship graph between the file and other related files specifically includes: parsing the related file identifiers recorded in the on-chain records, querying the on-chain summary of the related files through smart contracts; and dynamically generating a network topology graph that displays the reference, composition, and reference relationships between the target file and its upstream and downstream files, reference files, or other files in the same case file, with the target file as the central node.

6. The method for full lifecycle traceability management of archives based on blockchain according to claim 1, characterized in that, The process of constructing and outputting all operators and their operation records involved in the lifecycle of the archive specifically includes: summarizing the digital identity certificates of operators recorded in all on-chain records, querying a pre-set identity database to obtain operator entity information; and generating a detailed operation log list sorted by time, with each item in the list clearly recording the operator, operation time, operation type, and a summary of the system environment at the time of the operation.

7. The method for full lifecycle traceability management of archives based on blockchain according to claim 1, characterized in that, The process of constructing and outputting the change history and version comparison information of the archive content or metadata specifically includes: extracting the archive content hash value or metadata snapshot hash stored in each status change event record; locating the change point by comparing the hash values ​​of adjacent versions, and retrieving the full data of the corresponding version in the off-chain storage system for content comparison, and displaying the specific details of the added, deleted or modified content in a highlighted manner.

8. The method for full lifecycle traceability management of archives based on blockchain according to claim 1, characterized in that, The handling rules in step S4 include: if the verification finds that the file transfer chain is broken or the key node signature is missing, the subsequent transfer permission of the file is automatically frozen and an alarm is sent to the supervisory node; if the verification is successful, a trusted traceability report containing the hash value digest of all current on-chain records is generated for the file and attached to the digital copy of the file.

9. A blockchain-based archive lifecycle traceability management system, characterized in that, The system includes: an archive management client, used to initiate archive creation, lifecycle operations, and traceability query requests; A blockchain network, consisting of multiple consensus nodes, is an immutable ledger used to store on-chain summaries of archives and records of all lifecycle events. The smart contract module, deployed on the blockchain network, contains contract code for performing file registration, event logging, and traceability logic queries; An off-chain archive storage system is used to store the full data files and metadata of digital archives, and is anchored to the blockchain network through hash values; The traceability service engine communicates with the blockchain network and off-chain archive storage system to parse traceability requests, invoke smart contracts, integrate on-chain and off-chain data, and construct various traceability views as described in claim 1.

10. A blockchain-based full lifecycle traceability management system for archives according to claim 9, characterized in that, The smart contract module includes at least: an archive registration contract for verifying and recording the initial on-chain information of archives; an event processing contract for verifying operation permissions and structurally recording lifecycle events; an association management contract for maintaining and querying the association identifiers between archives; and a traceability query contract for efficiently retrieving and returning the required traceability data set from the blockchain ledger by combining query conditions according to predetermined logic.

Images