Bottled water full-process traceability management method and system applying block chain technology

Abstract

The invention provides a bottled water full-process traceability management method and system applying a block chain technology. Relates to the technical field of product quality safety and block chain management, and comprises an identifier binding module, the identifier binding module collects multi-source data of the whole process of bottled water, the identifier binding module generates a unique package identifier based on the multi-source data, the identifier binding module binds each batch of products with the unique package identifier, and the unique package identifier is stored in the database; generating a looped event record; and the data standardization module is used for carrying out format verification and standardization processing on the looped event record according to a cross-subject unified data standard to form a credible event record. According to the bottled water full-process traceability management method and system applying the block chain technology, information islands and manual check overhead are reduced, end-to-end traceability of water sources, purification, filling, storage, transportation and sales is realized, and performance, cost and compliance auditing requirements are considered.

Description

Technical Field

[0001] This invention relates to the field of product quality and safety and blockchain management technology, specifically to a method and system for full-process traceability management of bottled water using blockchain technology. Background Technology

[0002] The existing bottled water production and distribution system typically includes stages such as water source collection, purification and filtration, bottling and packaging, warehousing and transportation, and end-user sales. To ensure product quality and safety, different stages generally use internal enterprise databases, barcodes, or QR codes for information recording and batch tracking. Some large enterprises have introduced IoT sensors and cloud data platforms to achieve visualized management of production parameters and logistics information. By scanning packaging labels, consumers can access some production and testing information, which improves product transparency and ease of supervision to some extent. Significant progress has been made in information collection and management, laying the foundation for the informatization of the bottled water industry.

[0003] However, existing technologies still have significant shortcomings. Data at each stage is scattered across independent systems of different entities, lacking unified and reliable data standards, resulting in information silos. The lack of secure and reliable data sharing mechanisms among supply chain participants makes it difficult for regulatory authorities and consumers to verify product information throughout the entire process. Real-time updates and traceability analysis of multi-source data are not possible, failing to meet the bottled water industry's needs for dynamic quality supervision and source responsibility traceability. Therefore, a blockchain-based end-to-end traceability management method is needed to achieve reliable data sharing, transparent and traceable processes, and efficient regulatory collaboration. Summary of the Invention

[0004] To address the shortcomings of existing technologies, this invention provides a method and system for full-process traceability management of bottled water using blockchain technology. The technical problem this invention aims to solve is: how to achieve cross-entity trusted sharing and local verification through selective disclosure and zero-knowledge compliance proof, thereby eliminating data silos and realizing full-process verifiable traceability.

[0005] To achieve the above objectives, the present invention provides the following technical solution: a method and system for full-process traceability management of bottled water using blockchain technology, comprising:

[0006] The identification binding module collects multi-source data from the entire bottled water process, generates a unique packaging identifier based on the multi-source data, and binds each batch of products to the unique packaging identifier, generating a step-by-step event record.

[0007] The data standardization module performs format verification and standardization processing on the process-oriented event records based on a cross-entity unified data standard to form a reliable event record;

[0008] The blockchain consensus and evidence storage module performs signature validity verification, data standard consistency verification, and event sequence verification on the trusted event records through smart contracts to form consensus event records. The blockchain consensus and evidence storage module writes the consensus event records into on-chain evidence storage to obtain on-chain indexes. The blockchain consensus and evidence storage module writes the consensus event records into off-chain controlled storage through hash references to achieve a one-to-one correspondence between on-chain immutability and complete off-chain mapping.

[0009] The access control module implements a selective disclosure strategy for participants based on decentralized identity and policy contracts, and only opens verifiable access interfaces for authorized fields.

[0010] The traceability and verification module reconstructs the entire process event sequence based on the on-chain index. It then derives a consistency verification result based on the digital signature and hash fingerprint of the entire process event sequence, thereby confirming the authenticity and sequence of records. When the consistency verification result is valid, it generates zero-knowledge proofs for temperature thresholds, logistics time limits, and permission sets. The verification end issues verifiable compliance conclusions locally based solely on commitments and proofs without exposing the original data. When the consistency verification result is invalid, it writes an anomaly flag on the chain and triggers a circulation blocking instruction.

[0011] Preferably, the identifier binding module includes a visual encoding carrier and an invisible radio frequency carrier. The visual encoding carrier queries the packaging identifier of the entire bottled water process, and the invisible radio frequency carrier stores the device public key identifier and production batch number of the entire bottled water process. The identifier binding module binds the packaging identifier, the device public key identifier, the production batch number, and each batch of products.

[0012] Preferably, the segmented event record includes packaging identifier, subject identity identifier, segment type, geographical location, trusted timestamp, and segment sequence number to ensure that the segment sequence corresponding to the same packaging identifier is unique and verifiable.

[0013] Preferably, the consensus event record includes verifiable fields, fields necessary for fulfillment, product origin, cold chain compliance and certificate validity, and the participating parties include regulators, logistics providers, distributors and consumers.

[0014] Preferably, the selective disclosure strategy includes: the regulatory authority can only obtain the verifiable fields, the logistics provider and the distributor can only obtain the fields necessary for fulfillment, and the consumer can only obtain the product origin, the cold chain compliance, and the validity of the certificates, thereby achieving trusted sharing across entities without exposing commercially sensitive information.

[0015] Preferably, the zero-knowledge proof includes a range proof, a set membership proof, and a time interval proof. The zero-knowledge proof is verified locally at the verification end. The range proof is used to prove that the temperature does not exceed a threshold throughout the process. The set membership proof is used to prove that the water source or production license number belongs to the licensed set. The time interval proof is used to prove that the time difference between the arrival and departure of the product is within the constraint interval.

[0016] Preferably, the circulation blocking instruction is delivered to the production, warehousing and sales systems through an on-chain event subscription mechanism. After receiving the circulation blocking instruction, the sales system automatically prohibits outbound shipments and transaction recording, and records the reason and time of the blocking for auditing purposes.

[0017] Preferably, the traceability and verification module quantifies compliance risk through a compliance confidence index, the model formula of which is:

[0018] ,

[0019] in, For compliance confidence indicators, This represents the maximum temperature throughout the entire process, in units of... , Temperature threshold, unit: , This is the temperature over-limit penalty coefficient, in units of... , The maximum time interval between adjacent logistics events, in hours. The maximum allowed time interval, in hours. This is the penalty coefficient for exceeding the time interval limit, in hours. , represents the number of failed zero-knowledge proofs, expressed in units of . The failure proof penalty coefficient is expressed in units of... , For compliance confidence indicators, dimensionless and ,when If the consistency check result is not consistent, it is determined that the consistency check result is not valid.

[0020] A method for full-process traceability management of bottled water using blockchain technology includes:

[0021] S1. Collect multi-source data of the entire bottled water process, generate a unique packaging identifier based on the multi-source data, bind each batch of products with the unique packaging identifier, and form a process-based event record.

[0022] S2. Standardize and format the process event records according to the cross-entity unified data standard to obtain reliable event records;

[0023] S3. Verify the signature validity, data standard consistency, and event sequence of the trusted event record through a smart contract to form a consensus event record. Write the consensus event record to the chain for storage and obtain the chain index.

[0024] S4. Reconstruct the full-process event sequence of the target product based on the on-chain index, and verify the consistency of the digital signature and hash of the target product based on the full-process event sequence. When the digital signature is consistent, generate and verify a zero-knowledge proof; when the digital signature is inconsistent, write an anomaly flag on the chain and trigger a circulation blocking instruction.

[0025] This invention provides a method and system for full-process traceability management of bottled water using blockchain technology. It has the following beneficial effects:

[0026] This bottled water end-to-end traceability management method and system, utilizing blockchain technology, is based on unique identifier binding and a unified event model. It uses smart contracts to complete signature, standard, and sequence verification, and employs a one-to-one mapping between on-chain indexes and off-chain original text hashes to ensure records are tamper-proof, sequence is verifiable, and audits are reproducible. Cross-entity integration eliminates the need for repeated data cleaning and reconciliation, reducing information silos and manual verification overhead, and achieving end-to-end traceability of water source, purification, bottling, warehousing, transportation, and sales.

[0027] Regarding sharing and compliance verification, this invention combines decentralized identity with selective disclosure, outputting compliance conclusions through commitment and zero-knowledge proofs. Regulators and consumers can independently verify locally without exposing commercially sensitive data, thus balancing trust and privacy from the source. On-chain anomaly markers trigger circulation blocking, forming an executable risk control loop. Layered evidence storage and field-level authorization facilitate the addition of new entities and rule expansion, balancing performance, cost, and compliance audit requirements. Attached Figure Description

[0028] Figure 1 This is a schematic diagram of the internal structure of the present invention;

[0029] Figure 2 This is a schematic diagram of dual-carrier identifier binding;

[0030] Figure 3 This is a schematic diagram of the smart contract verification logic;

[0031] Figure 4 This is a schematic diagram of on-chain and off-chain storage mapping. Detailed Implementation

[0032] 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.

[0033] Example 1

[0034] like Figure 1-4 As shown, this embodiment of the invention provides a full-process traceability management system for bottled water using blockchain technology, including an identification binding module. The identification binding module collects multi-source data from the entire bottled water process, generates a unique packaging identifier based on the multi-source data, and binds each batch of products to the unique packaging identifier, generating a step-by-step event record.

[0035] The identification binding module includes a visual coding carrier and an invisible radio frequency carrier. The visual coding carrier queries the packaging identification throughout the entire bottled water process, while the invisible radio frequency carrier stores the equipment public key identification and production batch number throughout the entire bottled water process. The identification binding module binds the packaging identification, equipment public key identification, and production batch number to each batch of products.

[0036] The segmented event record includes packaging identification, subject identity identification, segment type, geographical location, trusted timestamp, and segment sequence number to ensure that the segment sequence corresponding to the same packaging identification is unique and verifiable.

[0037] The specific implementation method is as follows:

[0038] Data collection and batch determination: Collect data from various stages including water source, purification, bottling, packaging, warehousing, transportation, and sales. Use Coordinated Universal Time (UTC) for the time and latitude and longitude coordinates for the location to form batch information. Batch information includes water source number, production line number, production start and end time, shift, and batch number.

[0039] Unique Packaging Identifier Generation: The batch information, packaging serial number, timestamp, equipment identification mark, and random number are combined into the original identifier according to the preset field order. The original identifier is then processed for summary and error verification to obtain a verifiable unique packaging identifier.

[0040] Dual-carrier writing: The unique packaging identifier is printed on the bottle or outer carton as a QR code or data matrix, and simultaneously written into the near-field RFID tag, with read-only protection set.

[0041] Consistency verification: The two types of carriers are read simultaneously by the reading and writing device to verify whether the summary and the verification information are consistent and valid. If they are inconsistent, the label is rejected and the reason, time and job tag number are recorded.

[0042] Event logging and trusted encapsulation: Based on the successful binding result, a segmented event record is generated, written by the edge device, forming a trusted event record and entering the queue to be added to the chain.

[0043] Anomaly Handling and Coordination: Anomalies such as duplication, collision, time out-of-bounds, and counter backtracking are handled in a tiered manner, generating anomaly event records. Trusted event records serve as inputs for subsequent data standardization and on-chain evidence storage, ensuring a one-to-one correspondence.

[0044] The data standardization module performs format verification and standardization processing on the process-oriented event records based on the unified data standards across entities, forming reliable event records.

[0045] The blockchain consensus and evidence storage module uses smart contracts to verify the signature validity, data standard consistency, and event sequence of trusted event records, forming consensus event records. The blockchain consensus and evidence storage module writes the consensus event records to on-chain evidence storage, obtaining an on-chain index. The blockchain consensus and evidence storage module also writes the consensus event records to off-chain controlled storage through hash references, achieving a one-to-one correspondence between on-chain immutability and complete off-chain mapping.

[0046] The consensus event log includes verifiable fields, fields necessary for fulfillment, product origin, cold chain compliance, and certification validity. Participants include regulators, logistics providers, distributors, and consumers. The selective disclosure strategy involves: regulators only accessing verifiable fields, logistics providers and distributors only accessing fields necessary for fulfillment, and consumers only accessing product origin, cold chain compliance, and certification validity. This achieves trusted cross-entity sharing without exposing commercially sensitive information.

[0047] The specific implementation method is as follows:

[0048] Input and Example: Taking a product with batch number 2025-10-09-01 and packaging label number 20251009-01-0837 as an example, select three reliable events: filling and capping, warehousing and shelving, and cold chain handover. Each event includes the subject's identity identifier, process number, time, location, and summary verification value.

[0049] Smart contracts undergo three checks: 1. Signature validity check: Verify the digital signature of each event; reject contracts with invalid signatures. 2. Data standard consistency check: Check if required fields are complete and if time and coordinate formats conform to a unified standard. 3. Event sequence check: Under the same package identifier, the sequence number must increment, and time cannot be reversed.

[0050] Consensus event record formation: After all three verifications above pass, the consensus packaging process is initiated to obtain the consensus event record.

[0051] On-chain evidence storage and indexing: Write the minimum necessary information for consensus event records onto the chain, including packaging identifier, stage number, unified time, subject identity fingerprint and digest verification value, and generate an on-chain index.

[0052] Off-chain controlled storage: The full text of events is stored in a controlled object repository, and content addressing and retrieval are performed based on the digest verification value, with access logs enabled. The on-chain index corresponds one-to-one with the off-chain original text for subsequent traceability.

[0053] Inconsistency Handling: When the on-chain digest verification value is inconsistent with the off-chain original text, it is marked as an inconsistency in evidence storage, the external disclosure of the packaging label is suspended, and the relevant parties are notified to review it.

[0054] Field-based hierarchical disclosure:

[0055] Regulatory side: Verifiable fields, such as packaging labels, entity identity fingerprints, time, location, summary verification values, cold chain compliance conclusions, and certificate validity.

[0056] Logistics providers and distributors: Fields necessary for fulfillment, such as delivery vehicle license plate, loading and unloading platform, and receiving time window. At the same time, logistics providers and distributors can only see the conclusion that compliance has been passed, and the original details are not displayed.

[0057] Consumers: Product origin, batch information, cold chain compliance conclusions and certificate validity, but internal business details are not displayed.

[0058] Anomalies and Blocking: If the signature is invalid, the data standard is non-compliant, the order is abnormal, or the evidence is inconsistent, the contract will immediately refuse to upload to the chain or write an anomaly mark on the chain, triggering a circulation blocking instruction. The sales end will prohibit the release of goods and transaction recording according to the triggered circulation blocking instruction, and record the reason and time for auditing.

[0059] The access control module implements a selective disclosure strategy for participants based on decentralized identities and policy contracts, only opening verifiable access interfaces for authorized fields.

[0060] The traceability and verification module reconstructs the entire process event sequence based on the on-chain index. It then derives a consistency verification result based on the digital signature and hash fingerprint of the entire process event sequence, thereby confirming the authenticity and sequence of records. When the consistency verification result is valid, it generates zero-knowledge proofs for temperature thresholds, logistics time limits, and permission sets. The verification end issues verifiable compliance conclusions locally based solely on commitments and proofs without exposing the original data. When the consistency verification result is invalid, it writes an anomaly flag on the chain and triggers a circulation blocking instruction.

[0061] Zero-knowledge proofs include range proofs, set membership proofs, and time interval proofs. Zero-knowledge proofs are verified locally at the verification end. Range proofs are used to prove that the temperature does not exceed the threshold throughout the process. Set membership proofs are used to prove that the water source or production license number belongs to the licensed set. Time interval proofs are used to prove that the time difference between the arrival and departure of the product is within the constraint interval.

[0062] The circulation blocking instruction is delivered to the production, warehousing and sales systems through the on-chain event subscription mechanism. After receiving the circulation blocking instruction, the sales system automatically prohibits the outbound delivery and transaction recording, and records the reason and time of the blocking for auditing purposes.

[0063] The traceability and verification module quantifies compliance risk through compliance confidence indicators. The model formula for the compliance confidence indicators is as follows:

[0064] .

[0065] in, For compliance confidence indicators, This represents the maximum temperature throughout the entire process, in units of... , Temperature threshold, unit: , This is the temperature over-limit penalty coefficient, in units of... , The maximum time interval between adjacent logistics events, in hours. The maximum allowed time interval, in hours. This is the penalty coefficient for exceeding the time interval limit, in hours. , represents the number of failed zero-knowledge proofs, expressed in units of . The failure proof penalty coefficient is expressed in units of... , For compliance confidence indicators, dimensionless and ,when If the consistency check result is not valid, it is determined that the consistency check result is invalid.

[0066] The specific implementation method is as follows:

[0067] Index Restructuring: Events corresponding to the same packaging identifier are retrieved based on the on-chain index and automatically arranged according to the stage number and time sequence to form a complete sequence. Example sequence: Filling and capping → Warehousing and shelving → Cold chain handover → In-store acceptance.

[0068] Consistency Verification: Each event's digital signature is verified to be valid, its digest fingerprint matches the on-chain record, the sequence number under the same packaging identifier only increases and does not decrease, and there is no time rollback. Conclusion: All three event signatures are valid, the sequence numbers are incrementing, and there is no time rollback; therefore, they are determined to be consistent.

[0069] A proof is generated when consistency is achieved:

[0070] Temperature range verification: The temperature of the bottled water did not exceed 8℃ throughout the entire process; the conclusion is "passed," and the original temperature curve of the bottled water will not be disclosed. Time interval verification: The duration of any dwell time did not exceed 90 minutes; the conclusion is "passed," and the complete time details of the bottled water will not be disclosed. Permit set verification: Both the water source and production license numbers are within the permit list; the conclusion is "passed."

[0071] Local verification and conclusion output: The regulatory or consumer terminal completes the verification locally based solely on the on-chain commitment and proof, and the conclusion is that it passes. The temperature details, route details and internal documents of the bottled water are not displayed.

[0072] Anomalies and Blocking: If the signature is invalid, the digest fingerprint does not match, the serial number or time is abnormal, or any proof fails, an anomaly flag is written on the chain and a blocking instruction is sent to the production, warehousing, and sales systems. The sales system automatically prohibits outbound delivery and accounting, and records the reason and time of the blocking for auditing purposes.

[0073] A method for full-process traceability management of bottled water using blockchain technology includes:

[0074] S1. Collect multi-source data from the entire bottled water process, generate a unique packaging identifier based on the multi-source data, and bind each batch of products with the unique packaging identifier to form a process-based event record.

[0075] S2. Based on the unified data standard across entities, the process-oriented event records are standardized and their formats are validated to obtain reliable event records.

[0076] S3. Through smart contracts, the signature validity, data standard consistency, and event sequence of trusted event records are verified to form consensus event records. The consensus event records are then written to the blockchain for storage, resulting in an on-chain index.

[0077] S4. Reconstruct the full-process event sequence of the target product based on the on-chain index. Verify the consistency of the digital signature and hash of the target product based on the full-process event sequence. If the digital signature is consistent, generate and verify the zero-knowledge proof. If the digital signature is inconsistent, write an anomaly flag on the chain and trigger a circulation blocking instruction.

[0078] Example 2

[0079] Unlike Example 1, the application scenario of this example is bottled water with a short-term temperature exceeding the limit.

[0080] Index reconstruction: Based on the on-chain index, retrieve multiple events corresponding to the same packaging identifier, automatically arrange them according to the process number and time sequence to form a complete sequence of filling and capping → warehousing and shelving → cold chain handover → store acceptance.

[0081] Consistency verification: Verify the digital signature and digest fingerprint of each event. If the signature is valid, the digest matches the on-chain record, the sequence number under the same packaging identifier continues to increase, and the time does not roll back, the consistency is determined to be established, and the process proceeds to the proof stage.

[0082] Zero-knowledge proof generation and verification:

[0083] Temperature range proof: Based on on-chain commitments as public evidence, a verifiable proof of the temperature is provided without disclosing the original temperature curve. The local calculation result on the verification end shows a maximum value of 9.3℃, lasting for approximately 7 minutes, which is considered a short-term exceedance of the limit, and the proof conclusion is unsuccessful.

[0084] Time interval proof: Provides proof of the duration of stay; verification result is passed, but the complete time details are not disclosed. Permit set proof: Provides proof of the permit's validity; verification result is passed.

[0085] Handling and On-Chain Recording: The system writes a cold chain anomaly marker on the blockchain and simultaneously sends blocking instructions to the production, warehousing, and sales systems. The warehousing system automatically transfers this batch of products to the frozen area, prohibiting them from being put back on the shelves, and the sales system immediately prohibits outbound shipments and transaction recording. The system also records the reason for the blocking, the blocking time, the identities of the relevant parties, an event summary, and the responsible parties for future audits and spot checks.

[0086] Conditions for review and lifting of restrictions: Enterprises need to submit a self-inspection report of temperature control equipment, equipment operation records during abnormal periods, and rectification explanations. Supplementary proof can be generated based on a new round of data collection and commitments without disclosing detailed temperature information. If the temperature remains stable for four consecutive hours and the review proof is approved, and the regulatory authorities approve it, the blockade will be lifted, and the consumer and distributor interfaces will simultaneously return to compliance status.

[0087] Example 3

[0088] Unlike Example 1, the application scenario in this example is that the licenses for bottled water are not included in the license set.

[0089] Index reconstruction: Based on the on-chain index, four events related to the packaging identification were obtained, arranged in the following order: filling and capping → warehousing and shelving → cold chain handover → in-store acceptance. The fields such as time, location, entity identity, and process number are complete and consistent, proceeding to the next step of verification.

[0090] Consistency verification: All event digital signatures are valid, the digest fingerprint matches the on-chain record, the stage number increments, and the time does not roll back, thus consistency is achieved.

[0091] Zero-knowledge proof generation and verification:

[0092] License Set Proof: Provides proof for the license set. Local verification at the verification end results in failure, indicating the license number has expired or is not listed in the current license list. The verification process only displays the conclusion and a summary of the license, without disclosing sensitive content such as scanned copies of the licenses.

[0093] Temperature range verification: A verification is provided for the temperature, with the highest temperature being 7.6℃. The verification result is passed. Time range verification: A verification is provided for the duration of stay, with the longest stay being 58 minutes. The verification result is passed.

[0094] Handling and On-Chain Recording: The system writes an anomaly flag for the qualification onto the blockchain and issues blocking commands to production, warehousing, and sales systems. On the distributor side, receiving orders are automatically changed to pending review and cannot be entered into the accounting system. The sales system prohibits outbound shipments and records it as the certificate not being in the license set or having expired. The regulatory interface displays a verifiable conclusion of qualification failure, while the consumer side only displays a qualification failure notification without revealing certificate details.

[0095] Review and Unblocking Conditions: Enterprises must submit new valid licenses or complete the supplementary entry and filing of the license list within the specified period. After the license list is updated, a new set of license certificates will be generated based on the new commitment. If the certificate is approved and confirmed by the regulator, an unblocking confirmation will be added on the blockchain, and the block will be automatically lifted. If the supplementary entry is not completed or the certificate is still not approved within the time limit, the blocked status will remain and audit clues will be retained for subsequent administrative inspections.

[0096] Although embodiments of the invention have been shown and described, it will be understood by those skilled in the art that various changes, modifications, substitutions and alterations can be made to these embodiments without departing from the principles and spirit of the invention, the scope of which is defined by the appended claims and their equivalents.

Claims

1. A bottled water end-to-end traceability management system utilizing blockchain technology, characterized in that: include: The identification binding module collects multi-source data from the entire bottled water process, generates a unique packaging identifier based on the multi-source data, and binds each batch of products to the unique packaging identifier, generating a step-by-step event record. The data standardization module performs format verification and standardization processing on the process-oriented event records based on a cross-entity unified data standard to form a reliable event record. The blockchain consensus and evidence storage module performs signature validity verification, data standard consistency verification, and event sequence verification on the trusted event records through smart contracts to form consensus event records. The blockchain consensus and evidence storage module writes the consensus event records into on-chain evidence storage to obtain on-chain indexes. The blockchain consensus and evidence storage module also writes the consensus event records into off-chain controlled storage through hash references. An access control module that implements a selective disclosure strategy for participants based on decentralized identities and policy contracts; The traceability and verification module reconstructs the entire process event sequence based on the on-chain index. The traceability and verification module obtains a consistency verification result based on the digital signature and hash fingerprint of the entire process event sequence. When the consistency verification result is consistent, a zero-knowledge proof is generated for the temperature threshold, logistics time limit and permission set. When the consistency verification result is inconsistent, an anomaly flag is written on the chain and a circulation blocking instruction is triggered.

2. The bottled water full-process traceability management system using blockchain technology as described in claim 1, characterized in that: The identifier binding module includes a visual encoding carrier and an invisible radio frequency carrier. The visual encoding carrier queries the packaging identifier of the entire bottled water process, and the invisible radio frequency carrier stores the device public key identifier and production batch number of the entire bottled water process. The identifier binding module binds the packaging identifier, the device public key identifier, and the production batch number to each batch of products.

3. The bottled water full-process traceability management system using blockchain technology as described in claim 1, characterized in that: The segmented event record includes packaging identifier, subject identity identifier, segment type, geographical location, trusted timestamp, and segment sequence number.

4. The bottled water full-process traceability management system using blockchain technology as described in claim 1, characterized in that: The consensus event record includes verifiable fields, fields necessary for fulfillment, product origin, cold chain compliance and certificate validity, and the participating parties include regulators, logistics providers, distributors and consumers.

5. The bottled water full-process traceability management system using blockchain technology as described in claim 4, characterized in that: The selective disclosure strategy includes: the regulatory authority can only obtain the verifiable fields, the logistics provider and the distributor can only obtain the fields necessary for fulfillment, and the consumer can only obtain the product origin, the cold chain compliance, and the validity of the certificates.

6. The bottled water full-process traceability management system using blockchain technology according to claim 1, characterized in that: The zero-knowledge proof includes range proof, set membership proof, and time interval proof, and the zero-knowledge proof is verified locally at the verification terminal.

7. The bottled water full-process traceability management system using blockchain technology according to claim 1, characterized in that: The circulation blocking instruction is delivered to the production, warehousing and sales systems through an on-chain event subscription mechanism. After receiving the circulation blocking instruction, the sales system automatically prohibits outbound shipments and transaction recording, and records the reason and time of the blocking.

8. The bottled water full-process traceability management system using blockchain technology according to claim 1, characterized in that: The traceability and verification module quantifies compliance risk through a compliance confidence index, the model formula of which is: in, For compliance confidence indicators, This represents the maximum temperature throughout the entire process. Temperature threshold This is the penalty coefficient for exceeding temperature limits. The maximum time interval between adjacent logistics events. To allow the maximum time interval, Penalty coefficient for exceeding time interval limit The number of zero-knowledge proof failures. The penalty coefficient for failure proof. For compliance confidence metrics, when If the consistency check result is not consistent, it is determined that the consistency check result is not valid.

9. A method for full-process traceability management of bottled water using blockchain technology, characterized in that: include: S1. Collect multi-source data of the entire bottled water process, generate a unique packaging identifier based on the multi-source data, bind each batch of products with the unique packaging identifier, and form a process-based event record. S2. Standardize and format the process event records according to the cross-entity unified data standard to obtain reliable event records; S3. Verify the signature validity, data standard consistency, and event sequence of the trusted event record through a smart contract to form a consensus event record. Write the consensus event record to the chain for storage and obtain the chain index. S4. Reconstruct the full-process event sequence of the target product based on the on-chain index, and verify the consistency of the digital signature and hash of the target product based on the full-process event sequence. When the digital signature is consistent, generate and verify a zero-knowledge proof; when the digital signature is inconsistent, write an anomaly flag on the chain and trigger a circulation blocking instruction.

Images