Block chain-based explosive full life cycle supervision method and system

Abstract

The invention relates to an explosive full life cycle supervision method based on a block chain, and the method comprises the following steps: S1, building a network based on an FISCO BCOS alliance chain; s2, adopting a physical unclonable function and a cryptographic Hash algorithm to generate a unique encrypted identity label, and binding the unique encrypted identity label with a physical explosive entity in a strong cryptographic manner; s3, deploying an intelligent contract of a coding supervision state machine, and defining a state and a transfer rule; s4, automatically executing triple security verification; s5, the compliance state is transferred to the uplink to form non-tampering data; s6, monitoring the state flow in real time and detecting abnormity; and S7, realizing full-life-cycle traceability and visual auditing based on the work code. The method has the advantages that the physical-digital disjunction problem is thoroughly solved, beforehand compliance interception is achieved, data islands are broken, the integrity of supervision information is close to 100%, the defect rate is close to zero, the whole process is controllable and traceable, and the supervision efficiency and safety are greatly improved.

Description

Technical Field

[0001] This invention relates to the field of supply chain supervision technology, specifically to a blockchain-based method and system for the full lifecycle supervision of explosives. Background Technology

[0002] As highly dangerous and specialized materials, the safety supervision of explosives throughout their entire life cycle (production, transportation, storage, use, and disposal) is crucial. However, the existing regulatory system suffers from the following major technical deficiencies: Blockchain technology, with its decentralized, immutable, and traceable characteristics, offers a potential solution to trust issues in supply chain supervision. Existing blockchain-based traceability technologies typically employ a "one item, one code" approach combined with hash-based evidence storage. This involves scanning QR codes or ordinary RFID tags to record the hash values ​​of a product's production and logistics information on the blockchain, preventing data tampering afterward.

[0003] However, this general blockchain traceability solution has the following significant technical drawbacks when applied to explosives supervision scenarios with complex physical environments, numerous circulation links, and extremely high safety requirements: First, the binding mechanism between physical entities and on-chain identities is fragile. Current technologies mainly rely on ordinary physical identifiers (such as QR codes) as carriers of digital identities. These identifiers are easily copied, forged, or illegally transferred from the original object. Once a physical tag is copied onto illegal explosives, or the tag is separated from the physical object, although the blockchain can guarantee the immutability of on-chain data, it cannot verify the authenticity of the off-chain physical entity, leading to a physical-digital disconnect problem where "on-chain data is compliant, but off-chain physical objects are illegal."

[0004] Second, there is a lack of automated, dynamic oversight capabilities. In existing blockchain traceability applications, smart contracts often passively record data uploaded by various participants. However, in the oversight of explosives, the transition of states (such as from "in transit" to "in storage") relies heavily on complex preconditions (such as compliance with environmental parameters, multi-party authorization, and identity verification). Current technology lacks a mechanism to encode these complex oversight rules into a deterministic state machine, making it impossible to proactively intercept and automatically verify transactions before they occur. This still necessitates significant reliance on manual offline review, making it difficult to prevent violations.

[0005] Therefore, how to achieve a strong cryptographic binding between the physical explosive entity and its on-chain digital identity, and how to construct a regulatory state machine model capable of automatically executing complex regulatory rules, are key issues that current technologies have not yet effectively addressed. There is an urgent need to provide a blockchain-based method and system for the full lifecycle regulation of explosives to solve these problems. Summary of the Invention

[0006] Purpose of the invention This invention aims to overcome the shortcomings of existing technologies and provide a blockchain-based method and system for the full lifecycle supervision of explosives. Through a three-code fusion mechanism, a unique and unforgeable encrypted digital identity corresponding to the physical explosive is constructed, solving the physical-to-digital binding problem. A regulatory state machine model encodes discrete regulatory processes into automatically executable smart contracts, achieving automated compliance verification and state control throughout the entire process. By constructing a consortium blockchain network, a trusted, transparent, and tamper-proof data-sharing ledger is established among the participants, breaking down data silos and achieving end-to-end trusted traceability.

[0007] To achieve the above objectives, the present invention provides the following technical solution: A blockchain-based approach to the full lifecycle regulation of explosives includes the following steps: S1: Based on the FISCO BCOS consortium blockchain platform, it unites production unit nodes, distribution unit nodes, user unit nodes and regulatory agency nodes, and adopts a hybrid consensus mechanism of PBFT and PoA to build a consortium blockchain network and generate a blockchain network for the entire life cycle of explosives. S2: In the explosive lifecycle blockchain network, a unique encrypted identity is generated for each physical explosive entity using a Physical Unclonable Function (PUF) and a cryptographic hash algorithm, and the identity is strongly cryptographically bound to the physical explosive entity to generate an encrypted identity strongly bound to the physical entity. S3: On the blockchain network covering the entire life cycle of explosives, deploy smart contracts and their associated encrypted identities that are strongly bound to physical entities. Use smart contracts to encode and execute a regulatory state machine that defines the life cycle states and state transition rules of explosives. S4: Based on the aforementioned regulatory state machine model, an automatic smart contract execution mechanism is adopted. When any state transition request is triggered during the life cycle of the explosive, the corresponding smart contract automatically performs security verification and generates a state transition instruction that has passed security verification. S5: Based on the securely verified state transition instructions, a hybrid consensus algorithm of PBFT and PoA is used to reach a consensus in the permissioned consortium blockchain network and record it, generating immutable on-chain data; S6: Based on the immutable on-chain data, predefined monitoring rules are used to monitor and detect anomalies in the state transition event stream in real time, and generate on-chain alarm information; S7: Based on the immutable on-chain data, traceability query technology is used to display the complete lifecycle event chain according to the working code (WC_e) and generate a full lifecycle visual audit report.

[0008] As a further description of the above solution, step S1 specifically includes: Based on the FISCO BCOS consortium blockchain platform, a three-layer regulatory network is constructed, comprising a physical sensing layer, a smart contract module layer, and a blockchain ledger layer. The smart contract module layer deploys identity management contracts, production registration contracts, circulation transaction contracts, and detonation record contracts written in Solidity. The network adopts a hybrid consensus mechanism combining PBFT and PoA.

[0009] As a further description of the above scheme, step S2 generates a unique encrypted identity for each physical explosive entity, and the specific steps are as follows: S21: Collect the manufacturing information data of the physical explosive entity as the explosive code (EC_e); S22: Apply a predefined challenge C_init to the physically unclonable function chip embedded with the physical explosive entity and obtain its unique response R_init. Perform a cryptographic hash operation on the response to generate the chip code (CID_e), i.e., CID_e=H(R_init); S23: The regulatory agency uses its private key sk_R to digitally sign the hash values ​​of the explosive code (EC_e) and the production unit's public key pk_PU to generate a regulatory code (RC_e), i.e., RC_e=Sign(sk_R,H(EC_e[1](@context-ref?id=16)||pk_PU)); S24: The explosive code (EC_e), chip code (CID_e) and regulatory code (RC_e) are concatenated with a generation timestamp T_gen, and the unique encrypted identity identifier, namely the working code (WC_e), is generated using the cryptographic hash function H. WC_e = H(EC_e[1](@context-ref?id=17)||CID_e||RC_e||T_gen).

[0010] As a further description of the above scheme, the step S2 of strongly cryptographically binding the identifier with the physical explosive entity specifically involves: The calculated working code (WC_e) is written into the one-time programmable storage area of ​​the physically unclonable function chip; at the same time, the production registration contract is invoked to record the working code (WC_e) and its associated initial state on the distributed ledger of the consortium blockchain network.

[0011] As a further description of the above scheme, the supervisory state machine model in step S3 is defined as a six-tuple M_RSM=(S,P,Σ,δ,s0,F), where: S is a set of states, including: in production, awaiting shipment, in transit, in storage, activated, and detonated; P represents the set of participant roles, including: production units, distribution units, user units, and regulatory agencies; Σ represents a set of actions, including: registration, delivery, receiving, warehousing, outbound, activation, and detonation; δ:S×Σ×P→S is a state transition function implemented by smart contract encoding. Its execution depends on the current state, the request action, the requester role, and a series of predefined conditions. s0 represents the initial state "in production"; F is the set of final states {"detonated"}.

[0012] As a further description of the above scheme, the security verification in step S4 includes at least: identity legitimacy verification, state compliance verification, and physical-digital consistency verification. The identity verification process involves verifying whether the digital signature of the transaction initiator matches the role and permissions registered on the blockchain. The state compliance verification is as follows: verifying whether the state transition of the request conforms to the state transition function δ defined in the regulatory state machine model; The physical-digital consistency verification is as follows: for activation or detonation critical operations, the smart contract needs to verify whether the physical identification information read on-site is consistent with the identity registered on the chain.

[0013] As a further description of the above scheme, the physical-digital consistency verification specifically includes: The smart contract retrieves the original generation timestamp T_gen stored on the chain based on the working code (WC_e) in the request; the requester needs to submit the explosive code (EC_e'), chip code (CID_e'), and regulatory code (RC_e') obtained from the real-time scanning of the physical explosive entity; the smart contract recalculates WC_computed=H(EC_e'[1](@context-ref?id=31)||CID_e'||RC_e'||T_gen), and the verification passes only when WC_computed is completely equal to the WC_e stored on the chain.

[0014] As a further description of the above scheme, step S5 specifically includes: The verification nodes package the transactions verified in step S4, reach a consensus using a hybrid consensus algorithm of PBFT and PoA, generate new blocks and append them to the distributed ledger of each node, and update the index table with the working code (WC_e) as the key.

[0015] A blockchain-based explosives lifecycle monitoring system for executing the above methods includes: a network construction and identity management module, a unique identity generation and binding module, a monitoring state machine contract module, an automated verification execution module, a consensus and ledger storage module, a real-time monitoring and alarm module, and an audit traceability analysis module; The network construction and identity management module is used to build and manage the permissioned consortium blockchain network and the digital identities of each participant, and to provide a network operating environment for the unique identity generation and binding module, the regulatory state machine contract module and the automated verification execution module. The unique identity generation and binding module is used in step S3 to generate a working code (WC_e) and complete the physical and on-chain binding. The unique identity generation and binding module operates based on the legitimate identities of production units and regulatory agencies verified by the network construction and identity management module. The generated working code and associated initial state are synchronized to the consensus and ledger storage module, and at the same time, it provides the benchmark data for physical-digital identity comparison for the automated verification execution module. The regulatory state machine contract module is used to define and deploy smart contracts encoded with the regulatory state machine model logic, and to provide the automated verification execution module with a calling interface for state transition rules and compliance verification logic. The automated verification execution module is used to call the regulatory state machine contract module when a transaction is triggered, automatically execute the security verification in step S4, and send the verified legitimate transaction instruction to the consensus and ledger storage module. The consensus and ledger storage module is used to receive transactions submitted by the automated verification and execution module, reach consensus on them, and maintain an immutable distributed ledger. At the same time, it provides data sources for the real-time monitoring and alarm module and the audit traceability analysis module through event logs and a status database. The real-time monitoring and alarm module is used to listen to on-chain events generated by the consensus and ledger storage module, and to detect and report anomalies according to predefined rules. The audit traceability analysis module is used to retrieve ledger data in the consensus and ledger storage module, query and visualize the complete lifecycle event chain based on the working code (WC_e).

[0016] Advantages and effects of the present invention 1. This invention achieves a strong cryptographic binding between physical entities and on-chain digital identities, solving the problem of "physical-digital disconnect." Existing technologies typically rely on ordinary QR codes or RFID tags, which are easily copied or transferred. This invention employs Physically Unclonable Function (PUF) technology, utilizing the microscopic physical characteristics of the chip manufacturing process to generate a unique chip code. This chip code is then multi-hash-bound with the explosive code and the regulatory code signed by the regulatory agency to generate a unique working code. This strong cryptographic binding mechanism ensures the unique correspondence between digital identities and physical entities, fundamentally eliminating the possibility of tag copying, forgery, and illegal replacement, achieving "one item, one certificate; certificate and item as one."

[0017] 2. This invention automates the regulatory process and enables proactive compliance interception, resolving the regulatory lag issue of passive recording. Existing blockchain traceability solutions typically use smart contracts merely as tools for passively recording data. This invention creatively introduces a regulatory state machine model and automatically performs security verifications (including identity legitimacy, state compliance, and physical-digital consistency) through smart contracts. This mechanism transforms complex regulatory rules into automatically executable code logic, enabling proactive interception of transactions before they occur. It ensures that only operations conforming to state transition rules (e.g., only "activated" states can transition to "detonated") are recorded on the blockchain, significantly improving regulatory efficiency and reducing the risk of human error.

[0018] 3. A decentralized and efficient cross-organizational collaborative environment has been constructed, breaking down data silos and trust barriers. Addressing the issues of easily tampered and opaque data in existing centralized systems, this invention, based on the FISCO BCOS consortium blockchain platform, constructs a permissioned network comprising production, distribution, usage, and regulatory nodes. By employing a hybrid consensus mechanism of PBFT and PoA, not only are information silos between participants broken down, ensuring all parties collaborate based on the same immutable "facts," but high throughput and low latency are also achieved while maintaining regulatory authority.

[0019] 4. Significantly improved traceability and data integrity throughout the entire lifecycle, achieving an order-of-magnitude reduction in defect rates. Through real-time monitoring and full lifecycle visual auditing, regulatory agencies can detect anomalies and trace their origins in real time based on the immutable on-chain data index (WC). Experiments show that, thanks to the automated verification and tamper-proof records throughout the entire process, this system can effectively intercept illegal operations, rapidly improve the integrity of explosives regulatory information to nearly 100%, and reduce the rate of regulatory defects such as illegal substitution and data inconsistency to near zero, achieving a qualitative leap from "post-event accountability" to "full-process controllability." Attached Figure Description

[0020] Figure 1 This is a schematic diagram of the overall process of the method of the present invention; Figure 2 This is a schematic diagram of the three-layer architecture of the blockchain-based explosives lifecycle monitoring system of the present invention; Figure 3 This is a flowchart illustrating the process of generating a unique encrypted identity identifier through the fusion of three codes according to the present invention. Figure 4 This is a schematic diagram of the state transition of the regulatory state machine of the present invention; Figure 5 This is a detailed diagram of the automated security verification process of the present invention; Figure 6 This is a graph showing the experimental performance of the explosives monitoring information integrity of the present invention. Figure 7 This is a graph comparing the defect rate of the blockchain-based explosives lifecycle monitoring system of the present invention with that of traditional systems. Detailed Implementation

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

[0022] A blockchain-based approach to the full lifecycle regulation of explosives includes the following steps: S1: Based on the FISCO BCOS consortium blockchain platform, it unites production unit nodes, distribution unit nodes, user unit nodes and regulatory agency nodes, and adopts a hybrid consensus mechanism of PBFT and PoA to build a consortium blockchain network and generate a blockchain network for the entire life cycle of explosives. S2: In the blockchain network for the entire life cycle of explosives, a unique encrypted identity is generated for each physical explosive entity using a Physically Unclonable Function (PUF) and a cryptographic hash algorithm. This identity is then strongly cryptographically bound to the physical explosive entity, generating an encrypted identity strongly bound to the physical entity. S3: On the blockchain network covering the entire lifecycle of explosives, deploy smart contracts and their associated encrypted identities that are strongly bound to physical entities. Use smart contracts to encode and execute a regulatory state machine that defines the lifecycle states and state transition rules of explosives. S4: Based on the regulatory state machine model, a smart contract automatic execution mechanism is adopted. When any state transition request is triggered during the life cycle of the explosive, the corresponding smart contract automatically performs security verification and generates a state transition instruction that has passed security verification. S5: Based on securely verified state transition instructions, it uses a hybrid consensus algorithm of PBFT and PoA to achieve consensus and record data in a permissioned consortium blockchain network, generating immutable on-chain data; S6: Based on immutable on-chain data, predefined monitoring rules are used to monitor and detect anomalies in the state transition event stream in real time, and generate on-chain alarm information. S7: Based on immutable on-chain data, this application employs traceability query technology to display the complete lifecycle event chain according to the working code (WC_e), generating a full lifecycle visual audit report. This application significantly improves the traceability and data integrity of the entire lifecycle, achieving an order-of-magnitude reduction in the defect rate. Through real-time monitoring and full lifecycle visual auditing, regulatory agencies can perceive anomalies and trace their sources in real time based on the immutable on-chain data index (WC). Experiments show that, thanks to the automated verification and tamper-proof records throughout the entire process, this system can effectively intercept illegal operations, rapidly improve the integrity of explosives regulatory information to nearly 100%, and reduce the regulatory defect rate such as illegal replacement and data inconsistency to near zero, achieving a qualitative leap from "post-event accountability" to "full-process controllability."

[0023] Step S1 of the present invention specifically includes: Based on the FISCO BCOS consortium blockchain platform, a three-layer regulatory network is constructed, comprising a physical sensing layer, a smart contract module layer, and a blockchain ledger layer. The smart contract module layer deploys identity management contracts, production registration contracts, circulation transaction contracts, and detonation record contracts written in Solidity. The network adopts a hybrid consensus mechanism combining PBFT and PoA.

[0024] In step S2 of this invention, a unique encrypted identity is generated for each physical explosive entity. The specific steps are as follows: S21: Collect manufacturing information data of physical explosive entities as explosive code (EC_e); S22: Apply a predefined challenge C_init to the physically unclonable function chip embedded with the physical explosive entity and obtain its unique response R_init. Perform a cryptographic hash operation on the response to generate the chip code (CID_e), i.e., CID_e=H(R_init); S23: The regulatory agency uses its private key sk_R to digitally sign the hash value of the explosive code (EC_e) and the production unit's public key pk_PU to generate the regulatory code (RC_e), i.e., RC_e=Sign(sk_R,H(EC_e[1](@context-ref?id=16)||pk_PU)); S24: Concatenate the explosive code (EC_e), chip code (CID_e), and regulatory code (RC_e) with a generation timestamp T_gen, and use the cryptographic hash function H to generate a unique encrypted identity identifier, namely the working code (WC_e), WC_e=H(EC_e[1](@context-ref?id=17)||CID_e||RC_e||T_gen).

[0025] In step S2 of the present invention, the strong cryptographic binding of the identifier with the physical explosive entity specifically involves: The calculated working code (WC_e) is written into the one-time programmable storage area of ​​the physically unclonable function (PUF) chip; simultaneously, the production registration contract is invoked to record the working code (WC_e) and its associated initial state on the distributed ledger of the consortium blockchain network. This application achieves a strong cryptographic binding between physical entities and on-chain digital identities, solving the problem of "physical-digital disconnect." Existing technologies typically rely on ordinary QR codes or RFID tags, which are easily copied or transferred. This invention employs Physically Unclonable Function (PUF) technology, utilizing the microscopic physical characteristics of the chip manufacturing process to generate a unique chip code, and then binding it with the explosive code and the regulatory code signed by the regulatory agency through multiple hashes to generate a unique working code. This strong cryptographic binding mechanism ensures the unique correspondence between digital identities and physical entities, fundamentally eliminating the possibility of tag copying, forgery, and illegal replacement, achieving "one item, one certificate, and certificate and item as one."

[0026] The supervisory state machine model in step S3 of this invention is defined as a six-tuple M_RSM=(S,P,Σ,δ,s0,F), where: S is a set of states, including: in production, awaiting shipment, in transit, in storage, activated, and detonated; P represents the set of participant roles, including: production units, distribution units, user units, and regulatory agencies; Σ represents a set of actions, including: registration, delivery, receiving, warehousing, outbound, activation, and detonation; δ:S×Σ×P→S is a state transition function implemented by smart contract encoding. Its execution depends on the current state, the request action, the requester role, and a series of predefined conditions. s0 represents the initial state "in production"; F is the set of final states {"detonated"}.

[0027] The security verification in step S4 of this invention includes at least: identity legitimacy verification, state compliance verification, and physical-digital consistency verification. Identity verification involves verifying whether the digital signature of the transaction initiator matches the role and permissions registered on the blockchain. State compliance verification is as follows: verify whether the state transition of the request conforms to the state transition function δ defined in the regulatory state machine model; The physical-digital consistency check is as follows: For activation or detonation critical operations, the smart contract needs to verify whether the physical identifier information read on-site is consistent with the identity registered on the chain.

[0028] The physical-digital consistency verification of this invention specifically includes: The smart contract retrieves the original generation timestamp T_gen stored on the chain based on the working code (WC_e) in the request; the requester needs to submit the explosive code (EC_e'), chip code (CID_e'), and regulatory code (RC_e') obtained from the real-time scanning of the physical explosive entity; the smart contract recalculates WC_computed=H(EC_e'[1](@context-ref?id=31)||CID_e'||RC_e'||T_gen), and the verification is successful only when WC_computed is completely equal to the WC_e stored on the chain. This application realizes the automated execution of the regulatory process and the "pre-event" compliance interception, and solves the problem of regulatory lag in "passive recording". Existing blockchain traceability schemes usually only use smart contracts as a tool for passively recording data. This invention creatively introduces a regulatory state machine model and automatically executes security verification (including identity legality, state compliance, and physical-digital consistency) through smart contracts. This mechanism transforms complex regulatory rules into automatically executable code logic, enabling proactive interception of transactions before they occur. It ensures that only operations that comply with state transition rules (e.g., only "activated" state can transition to "detonate") can be recorded on the blockchain, greatly improving regulatory efficiency and reducing the risk of human violations.

[0029] Step S5 of this invention specifically involves: the verification node packaging the transactions verified in step S4, reaching consensus using a hybrid consensus algorithm of PBFT and PoA, generating new blocks and appending them to the distributed ledger of each node, while simultaneously updating the index table with the working code (WC_e) as the key. This application constructs a decentralized and efficient cross-organizational collaborative environment, breaking down data silos and trust barriers. Addressing the issues of easily tampered and opaque data in existing centralized systems, this invention, based on the FISCOBCOS consortium blockchain platform, constructs a permissioned network comprising production, distribution, usage, and regulatory nodes. By employing a hybrid consensus mechanism of PBFT and PoA, not only are information silos between participants broken down, ensuring all parties collaborate based on the same immutable "facts," but high throughput and low latency are also achieved while maintaining regulatory authority.

[0030] A blockchain-based explosives lifecycle monitoring system for executing the above methods includes: a network construction and identity management module, a unique identity generation and binding module, a monitoring state machine contract module, an automated verification execution module, a consensus and ledger storage module, a real-time monitoring and alarm module, and an audit traceability analysis module; The network construction and identity management module is used to build and manage the permissioned consortium blockchain network and the digital identities of each participant, and provides a network operating environment for the unique identity generation and binding module, the regulatory state machine contract module and the automated verification execution module. The unique identity generation and binding module is used in step S3 to generate a working code (WC_e) and complete the physical and on-chain binding. The unique identity generation and binding module operates based on the legitimate identities of production units and regulatory agencies verified by the network construction and identity management module. The generated working code and associated initial state are synchronized to the consensus and ledger storage module, and at the same time, it provides the benchmark data for physical-digital identity comparison for the automated verification execution module. The regulatory state machine contract module is used to define and deploy smart contracts that are encoded with regulatory state machine model logic, and provides an interface for calling state transition rules and compliance verification logic for the automated verification and execution module. The automated verification execution module is used to call the regulatory state machine contract module when a transaction is triggered, automatically execute the security verification in step S4, and send the verified legal transaction instructions to the consensus and ledger storage module. The consensus and ledger storage module is used to receive transactions submitted by the automated verification and execution module, conduct consensus on them, and maintain an immutable distributed ledger. At the same time, it provides data sources for the real-time monitoring and alarm module and the audit traceability analysis module through event logs and state databases. The real-time monitoring and alarm module is used to listen to on-chain events generated by the consensus and ledger storage module, and detect and report anomalies according to predefined rules; The audit traceability analysis module is used to retrieve ledger data in the consensus and ledger storage module, query and visualize the complete lifecycle event chain based on the working code (WC_e).

[0031] Example

[0032] This embodiment provides a blockchain-based system for monitoring the entire lifecycle of explosives, the architecture of which is as follows: Figure 1 As shown, it includes: Physical layer: Composed of IoT devices such as RFID tags, GPS modules, and temperature and humidity sensors attached to the explosive packaging or the explosive itself, responsible for collecting location and environmental data in the physical world and uploading it via the network.

[0033] Smart Contract Module Layer: Deployed on the blockchain network, this layer contains a series of smart contracts written in the Solidity language, specifically including: Identity Management Contract: Manages the registration, authentication, and permissions of participating parties (PU, DU, BU, Supervisor).

[0034] Production transaction contract: Implements explosive registration, WorkCode generation, and initial state "MANUFACTURED" recording.

[0035] Transfer transaction contracts (delivery, transportation): realize the transfer of ownership, location update and status change to "IN_TRANSIT" or "STORED".

[0036] Regulatory transaction contracts: allow regulatory agencies to access end-to-end data, set compliance rules, and trigger audits.

[0037] Detonate the transaction contract: Implement activation verification (physical-digital consistency check) before use and record the final "DETONATED" status.

[0038] Blockchain layer: A consortium blockchain network built on FISCO BCOS, with nodes operated by participating parties and regulatory agencies to jointly maintain a distributed, immutable ledger that records all transactions and states.

[0039] The key process is implemented as follows: 1. Production and registration (corresponding to steps S2 and S3): After obtaining on-chain approval from the regulatory agency, the production unit (PU) prepares physical explosives, which are embedded with PUF chips. The PU collects EC_e (explosive code), reads CID_e from the PUF chip, and obtains the digitally signed RC_e (regulatory code) from the regulatory agency. Subsequently, the PU calls the "production transaction contract" and submits EC_e, CID_e, RC_e and the current timestamp T_gen. After the contract verifies the validity of the RC_e signature, it calculates WC_e=SHA256(EC_e[1](@context-ref?id=29)||CID_e||RC_e||T_gen) and creates a new record on the chain with WC_e as the key, and initializes the state to "MANUFACTURED". At the same time, the WC_e is written to the OTP storage area of ​​the PUF chip.

[0040] 2. Transfer and Verification (corresponding to steps S4 and S5): When explosives need to be transferred from PU to DU, DU staff scan the markings (QR code, RFID) on the explosives to obtain EC_e', CID_e', and RC_e', and initiate a "transfer" transaction on the blockchain. The smart contract is triggered: verifying the DU's digital signature (identity legitimacy).

[0041] Check if the current status corresponding to WC_e is "MANUFACTURED" (status compliance).

[0042] Read the associated sensor data to confirm that the environmental parameters are within the threshold. After successful verification, the contract executes the state transition function δ, updates the state to "IN_TRANSIT", and packages this transition transaction (including the operator, time, and location) into a block, which is then permanently uploaded to the blockchain after consensus.

[0043] 3. Activation and Detonation (corresponding steps S4, S5, S6): Before detonation, the user unit (BU) must perform an "activation" operation. BU personnel scan the explosive on-site, obtain real-time physical identifiers EC_e', CID_e', and RC_e', and submit an activation request. The smart contract executes critical consistency checks. Retrieve the original T_gen corresponding to WC_e from the chain.

[0044] Calculate WC_computed=SHA256(EC_e'||CID_e'||RC_e'||T_gen).

[0045] The WC_computed is compared to the WC_e stored on-chain for complete consistency. Only when they are completely consistent is it proven that the current physical entity matches the registered identity on the chain, preventing mid-process replacement. After the verification passes, the state changes to "ACTIVATED". Subsequently, the detonation operation changes the state to "DETONATED" and records the detonation coordinates, time, and other information.

[0046] 4. Audit and Traceability (corresponding to step S7): The regulatory agency or auditor inputs the WC_e of any explosive on the platform. The system queries the blockchain ledger to obtain all "StateChanged" events related to that WC_e. Specifically, the aforementioned "StateChanged" event is a blockchain log interface (Event Interface) pre-defined in the smart contract, used to automatically trigger after each compliant state transition operation is successfully executed. The data structure of this event includes the following key index fields: working code ($WC_e$, Indexed), state before change (FromState), state after change (ToState), operator account address, and block timestamp. Using the hash pointer structure of the blocks, these events are arranged in chronological order, automatically generating a complete and tamper-proof flow report from production to detonation, displayed in chart form, achieving minute-level accurate traceability.

[0047] Experimental results: such as Figure 6As shown, in existing technologies, due to reliance on manual input and weakly bound tags, the defect rate of regulatory data is typically around 5%-10%, and it is easily forged. However, this invention, by introducing an automated regulatory state machine and a strong binding mechanism with PUF (Power-Only Function) tags, demonstrates through experiments that it can increase the illegal operation interception rate to 100% and reduce the regulatory data defect rate to 0%.

[0048] like Figure 7 As shown, in existing technologies, severe data silos exist between production, distribution, and user units, and physical goods lack a strong association with digital identities during circulation. This leads to information loss or mismatches between physical goods and data during cross-entity handover, making it difficult to guarantee the integrity of regulatory data. This invention, however, introduces strong PUF cryptographic binding to prevent false data entry at the source and combines a hybrid consensus mechanism of PBFT and PoA to ensure the synchronization and storage of transaction data across all network nodes. Experimental data shows that the system can significantly improve the integrity of regulatory information throughout its entire lifecycle from the bottleneck level of existing technologies to nearly 100%. As can be seen from the vertical axis of the graph, the defect rate curve of this invention coincides with the 0 coordinate throughout, while the defect rate curve of the traditional system always deviates from 0. This stark contrast directly demonstrates the absolute advantage of this invention in eliminating regulatory defects, effectively overcoming the vulnerability of existing theoretical models in complex and dynamic industrial environments, and achieving complete end-to-end traceability.

[0049] The above description is merely a preferred embodiment of the present invention and is not intended to limit the scope of protection of the present invention. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present invention should be included within the scope of protection of the present invention.

Claims

1. A blockchain-based method for the full lifecycle supervision of explosives, characterized in that, Includes the following steps: S1: Based on the FISCO BCOS consortium blockchain platform, it unites production unit nodes, distribution unit nodes, user unit nodes and regulatory agency nodes, and adopts a hybrid consensus mechanism of PBFT and PoA to build a consortium blockchain network and generate a blockchain network for the entire life cycle of explosives. S2: In the explosive lifecycle blockchain network, a unique encrypted identity is generated for each physical explosive entity using a Physical Unclonable Function (PUF) and a cryptographic hash algorithm, and the identity is strongly cryptographically bound to the physical explosive entity to generate an encrypted identity strongly bound to the physical entity. S3: On the blockchain network covering the entire life cycle of explosives, deploy smart contracts and their associated encrypted identities that are strongly bound to the physical entities. Use smart contracts to encode and execute a regulatory state machine that defines the life cycle states and state transition rules of explosives. S4: Based on the aforementioned regulatory state machine model, an automatic smart contract execution mechanism is adopted. When any state transition request is triggered during the life cycle of the explosive, the corresponding smart contract automatically performs security verification and generates a state transition instruction that has passed security verification. S5: Based on the securely verified state transition instructions, a hybrid consensus algorithm of PBFT and PoA is used to reach a consensus in the permissioned consortium blockchain network and record it, generating immutable on-chain data; S6: Based on the immutable on-chain data, predefined monitoring rules are used to monitor and detect anomalies in the state transition event stream in real time, and generate on-chain alarm information; S7: Based on the immutable on-chain data, traceability query technology is used to display the complete lifecycle event chain according to the working code (WC_e) and generate a full lifecycle visual audit report.

2. The blockchain-based method for monitoring the entire lifecycle of explosives according to claim 1, characterized in that, Step S1 specifically involves: Based on the FISCO BCOS consortium blockchain platform, a three-layer regulatory network is constructed, comprising a physical sensing layer, a smart contract module layer, and a blockchain ledger layer. The smart contract module layer deploys identity management contracts, production registration contracts, circulation transaction contracts, and detonation record contracts written in Solidity. The network adopts a hybrid consensus mechanism combining PBFT and PoA.

3. The blockchain-based method for monitoring the entire lifecycle of explosives according to claim 2, characterized in that, In step S2, a unique encrypted identity is generated for each physical explosive entity. The specific steps are as follows: S21: Collect the manufacturing information data of the physical explosive entity as the explosive code (EC_e). S22: Apply a predefined challenge C_init to the physically unclonable function chip embedded with the physical explosive entity and obtain its unique response R_init. Perform a cryptographic hash operation on the response to generate the chip code (CID_e), i.e., CID_e=H(R_init); S23: The regulatory agency uses its private key sk_R to digitally sign the hash values ​​of the explosive code (EC_e) and the production unit's public key pk_PU to generate a regulatory code (RC_e), i.e., RC_e=Sign(sk_R, H(EC_e[1](@context-ref?id=16)||pk_PU)); S24: The explosive code (EC_e), chip code (CID_e) and regulatory code (RC_e) are concatenated with a generation timestamp T_gen, and the unique encrypted identity identifier, namely the working code (WC_e), is generated using the cryptographic hash function H. WC_e = H(EC_e[1](@context-ref?id=17)||CID_e||RC_e||T_gen).

4. The blockchain-based method for full lifecycle monitoring of explosives according to claim 3, characterized in that, In step S2, the specific steps for strongly cryptographically binding the identifier to the physical explosive entity are as follows: The calculated working code (WC_e) is written into the one-time programmable storage area of ​​the physically unclonable function chip; at the same time, the production registration contract is invoked to record the working code (WC_e) and its associated initial state on the distributed ledger of the consortium blockchain network.

5. The blockchain-based method for monitoring the entire lifecycle of explosives according to claim 3, characterized in that, The supervisory state machine model in step S3 is defined as a six-tuple M_RSM=(S, P, Σ, δ, s0, F), where: S is a set of states, including: in production, awaiting shipment, in transit, in storage, activated, and detonated; P represents the set of participant roles, including: production units, distribution units, user units, and regulatory agencies; Σ represents a set of actions, including: registration, delivery, receiving, warehousing, outbound, activation, and detonation; δ:S×Σ×P→S is a state transition function implemented by smart contract encoding. Its execution depends on the current state, the request action, the requester role, and a series of predefined conditions. s0 represents the initial state "in production"; F is the set of final states {"detonated"}.

6. The blockchain-based method for monitoring the entire lifecycle of explosives according to claim 5, characterized in that, The security verification in step S4 includes at least: identity legitimacy verification, state compliance verification, and physical-digital consistency verification. The identity verification process involves verifying whether the digital signature of the transaction initiator matches the role and permissions registered on the blockchain. The state compliance verification is as follows: verifying whether the state transition of the request conforms to the state transition function δ defined in the regulatory state machine model; The physical-digital consistency verification is as follows: for activation or detonation critical operations, the smart contract needs to verify whether the physical identification information read on-site is consistent with the identity registered on the chain.

7. The blockchain-based method for monitoring the entire lifecycle of explosives according to claim 6, characterized in that, The physical-digital consistency verification specifically refers to: The smart contract retrieves the original generation timestamp T_gen stored on the chain based on the working code (WC_e) in the request; the requester needs to submit the explosive code (EC_e'), chip code (CID_e'), and regulatory code (RC_e') obtained from the real-time scanning of the physical explosive entity; the smart contract recalculates WC_computed=H(EC_e'[1](@context-ref?id=31)||CID_e'||RC_e'||T_gen), and the verification passes only when WC_computed is completely equal to the WC_e stored on the chain.

8. The blockchain-based method for full lifecycle monitoring of explosives according to claim 1, characterized in that, Step S5 specifically involves: The verification nodes package the transactions verified in step S4, reach a consensus using a hybrid consensus algorithm of PBFT and PoA, generate new blocks and append them to the distributed ledger of each node, and update the index table with the working code (WC_e) as the key.

9. A blockchain-based explosives lifecycle monitoring system for performing the method of any one of claims 1-8, characterized in that, include: The module includes network construction and identity management, unique identity generation and binding, regulatory state machine contract, automated verification and execution, consensus and ledger storage, real-time monitoring and alarm, and audit traceability analysis. The network construction and identity management module is used to build and manage the permissioned consortium blockchain network and the digital identities of each participant, and to provide a network operating environment for the unique identity generation and binding module, the regulatory state machine contract module and the automated verification execution module. The unique identity generation and binding module is used in step S3 to generate a working code (WC_e) and complete the physical and on-chain binding. The unique identity generation and binding module operates based on the legitimate identities of production units and regulatory agencies verified by the network construction and identity management module. The generated working code and associated initial state are synchronized to the consensus and ledger storage module, and at the same time, it provides the benchmark data for physical-digital identity comparison for the automated verification execution module. The regulatory state machine contract module is used to define and deploy smart contracts that encode the logic of the regulatory state machine model, and to provide the automated verification execution module with a calling interface for state transition rules and compliance verification logic. The automated verification execution module is used to call the regulatory state machine contract module when a transaction is triggered, automatically execute the security verification in step S4, and send the verified legitimate transaction instruction to the consensus and ledger storage module. The consensus and ledger storage module is used to receive transactions submitted by the automated verification and execution module, reach consensus on them, and maintain an immutable distributed ledger. At the same time, it provides data sources for the real-time monitoring and alarm module and the audit traceability analysis module through event logs and a status database. The real-time monitoring and alarm module is used to listen to on-chain events generated by the consensus and ledger storage module, and to detect and report anomalies according to predefined rules. The audit traceability analysis module is used to retrieve ledger data in the consensus and ledger storage module, query and visualize the complete lifecycle event chain based on the working code (WC_e).

Images