Machine account management method and device based on block chain evidence storage technology, equipment and storage medium

Abstract

The invention discloses a machine account management method and device based on a block chain evidence storage technology, equipment and a storage medium, and relates to the technical field of block chains, and the method comprises the steps: carrying out the mapping relation configuration of a machine account sensitive field of machine account data and a data evidence storage chain block based on a preset dynamic mapping table and a business demand, calling a Hash value algorithm to generate a Hash value for the machine account data, and storing the Hash value to a data storage chain based on a mapping relation configuration result; calling a logic rule verification mechanism of the smart contract to perform logic verification on the approval operation information, calling the smart contract to record the approval operation information after the verification is passed, and storing the approval operation information to a process evidence storage chain in a preset double-chain evidence storage framework, so as to utilize the data evidence storage chain and the process evidence storage chain to manage ledger data; wherein the approval opinion is a decision basis corresponding to the approval process of the approval request; and the data evidence storage chain and the process evidence storage chain are bound based on the approval identifier in the preset double-chain evidence storage architecture, so that the ledger management efficiency is improved.

Description

Technical Field

[0001] This invention relates to the field of blockchain technology, and in particular to a ledger management method, apparatus, equipment and storage medium based on blockchain evidence storage technology. Background Technology

[0002] Currently, there are many pain points in the management of various ledger data (such as population information, asset registration, inspection records, etc.) in grassroots governance scenarios.

[0003] Regarding the risk of data tampering, traditional ledgers primarily rely on centralized databases for storage. In this model, administrators possess high privileges, enabling them to directly modify data through the backend. However, malicious users who gain such privileges or exploit system vulnerabilities can easily tamper with data in the backend, significantly compromising its authenticity. This can distort the data upon which grassroots governance is based, impacting the scientific rigor and accuracy of decision-making and posing potential risks and hidden dangers to grassroots governance.

[0004] In terms of traceability efficiency, existing systems have significant shortcomings. They only record the final state of data, failing to record crucial information during the data's flow, such as the specific modification time, the operator, and the content before the modification. This results in a lack of sufficient clues and evidence when tracing the data's evolution, often requiring staff to spend considerable time and effort investigating. In some cases, due to severe information gaps, it is impossible to accurately reconstruct the data's evolution, seriously impacting work efficiency and the accuracy of problem identification.

[0005] Regarding the approval process, current record changes typically require manual completion of approval forms. This paper-based process is severely disconnected from electronic data. On one hand, paper approval forms are prone to loss or damage, leading to the loss of evidence and hindering subsequent auditing and oversight. On the other hand, because the paper-based process and electronic data are not effectively integrated, some criminals may exploit this loophole to forge approval processes or tamper with approval forms, resulting in falsified procedures and undermining the standardization and seriousness of grassroots governance.

[0006] It is worth noting that blockchain technology, with its decentralized, immutable, and traceable characteristics, offers a feasible path to solve the aforementioned problems from a technical perspective. However, in reality, most existing blockchain applications focus on fields such as finance and supply chain management. These solutions are often designed and developed based on the specific needs and characteristics of these fields. For grassroots record-keeping scenarios, there is a lack of lightweight solutions that are suitable for this purpose, failing to directly meet the actual needs of record-keeping data management in grassroots governance.

[0007] As can be seen from the above, how to improve the efficiency of ledger management based on blockchain evidence storage technology is an urgent problem to be solved. Summary of the Invention

[0008] In view of this, the purpose of this invention is to provide a ledger management method, apparatus, device, and storage medium based on blockchain evidence storage technology, which can improve the efficiency of ledger management in the process of ledger management based on blockchain evidence storage technology. The specific solution is as follows:

[0009] Firstly, this application provides a ledger management method based on blockchain evidence storage technology, including:

[0010] Using a preset dynamic mapping table and based on business requirements, the mapping relationship is configured for the sensitive fields of the ledger data and the corresponding evidence storage chain blocks of the data evidence storage chain. The mapping relationship configuration result is obtained so that when a change in the ledger data is detected, a preset hash value determination algorithm is called and a corresponding hash value is generated based on the ledger data. Based on the mapping relationship configuration result, the hash value is stored in the data evidence storage chain in the preset dual-chain evidence storage architecture.

[0011] When an approval request is received, the logical rule verification mechanism corresponding to the smart contract in the blockchain is invoked to perform logical verification on the approval operation information corresponding to the approval request, including the operator's identifier, electronic signature, and approval opinion, and to obtain the verification result.

[0012] If the verification result indicates that the verification is successful, the smart contract is invoked to record the approval operation information corresponding to the approval request, including the operator identifier, electronic signature, and approval opinion. The approval operation information is then stored in the process evidence storage chain of the preset dual-chain evidence storage architecture, so as to utilize the data evidence storage chain and the process evidence storage chain to manage ledger data. The approval opinion is the decision basis corresponding to the approval process of the approval request. The data evidence storage chain and the process evidence storage chain are bound based on the approval identifier in the preset dual-chain evidence storage architecture.

[0013] Optionally, the step of configuring a mapping relationship between the ledger sensitive fields of the ledger data and the corresponding evidence storage chain blocks based on business requirements using a preset dynamic mapping table, and obtaining a mapping relationship configuration result, so that when a change in the ledger data is detected, a preset hash value determination algorithm is invoked to generate a corresponding hash value based on the ledger data, and the hash value is stored in the data evidence storage chain in the preset dual-chain evidence storage architecture based on the mapping relationship configuration result, including:

[0014] By using a preset dynamic mapping table and based on business requirements, the sensitive fields of the ledger and the evidence storage chain blocks are mapped at the field level to obtain the mapping relationship configuration result;

[0015] When the ledger data changes, a data snapshot corresponding to the data before and after the data change process is generated based on the change result. The data difference is determined based on the data snapshot. Then, a preset hash value determination algorithm is called to determine the hash value corresponding to the data difference.

[0016] Based on the mapping relationship configuration result, the evidence storage chain block corresponding to the hash value is determined, so as to store the hash value in the evidence storage chain block corresponding to the data evidence storage chain in the preset dual-chain evidence storage architecture, and generate an evidence storage certificate; the evidence storage certificate includes the block height and data change identifier corresponding to the evidence storage chain block.

[0017] Optionally, after storing the hash value into the data storage chain in the preset dual-chain evidence storage architecture based on the mapping relationship configuration result, the method further includes:

[0018] When a change in ledger data is detected, the timestamp, operator identity identifier, and device fingerprint corresponding to the data change process are extracted based on the mapping relationship configuration result, and the timestamp, operator identity identifier, and device fingerprint are set as metadata;

[0019] The metadata is stored in a data storage chain corresponding to the hash value to obtain a chain-stored change record; wherein, the data storage chain only stores hash digests, and all data in the data storage chain is immutable; the hash value is a hash value used to verify data consistency; the change record is a record of data storage of ledger data.

[0020] Optionally, when an approval request is received, the logical rule verification mechanism corresponding to the smart contract in the blockchain is invoked to perform logical verification on the approval operation information corresponding to the approval request, including the operator identifier, electronic signature, and approval opinion, to obtain the verification result, including:

[0021] When an approval request is received, the ledger type and modified fields corresponding to the approval request are determined, and the logical rule verification mechanism corresponding to the smart contract in the blockchain is invoked. Based on the ledger type and the modified fields, it is determined whether the initiator of the approval request has the corresponding authority, and the authority judgment result is obtained.

[0022] If the permission judgment result indicates that the initiator has the corresponding permission, then the data logic verification rules of the smart contract are invoked to perform a data logic consistency judgment on the approval request, and a consistency judgment result is obtained.

[0023] If the permission judgment result or the consistency judgment result indicates that the judgment has failed, the approval constraint mechanism in the smart contract is invoked to monitor abnormal behavior, and then the warning notification rules are used to generate warning notification information based on the abnormal behavior.

[0024] Optionally, the step of invoking the approval constraint mechanism in the smart contract to monitor abnormal behavior, and then using early warning notification rules and generating early warning notification information based on the abnormal behavior, includes:

[0025] The approval constraint mechanism in the smart contract is invoked to monitor the modification operations of the ledger data in real time, and when the number of times the same field is modified within a preset time period is greater than the preset field modification threshold, an early warning information is automatically generated using the early warning notification rules.

[0026] The warning information is sent to the warning processing center so that the warning processing center can perform corresponding processing based on the warning information; wherein, the warning information includes ledger data modification information, operator identity information, and ledger data approval process identifier;

[0027] When the warning information is generated, the smart contract is invoked to suspend the ledger data modification operation until the warning processing center completes the review operation of the ledger data modification operation.

[0028] Optionally, if the verification result indicates that the verification is successful, the smart contract is invoked to record the approval operation information corresponding to the approval request, including the operator identifier, electronic signature, and approval opinion, and the approval operation information is stored in the process evidence storage chain of the preset dual-chain evidence storage architecture, including:

[0029] If the verification result indicates that the verification is successful, the smart contract is invoked to record the approval operation information corresponding to the approval request, including the operator's identifier, electronic signature, and approval opinion; the approval operation information includes application submission information, preliminary review information, and final review information.

[0030] The approval operation information is stored in the process evidence storage chain in the preset dual-chain evidence storage architecture, and the approval identifier corresponding to the process evidence storage chain and the data evidence storage chain is determined. The process evidence storage chain is invoked and the approval process corresponding to each data change operation is recorded in the process evidence storage chain and the data evidence storage chain based on the approval identifier, so as to use the process evidence storage chain to review the compliance of the approval operation information.

[0031] Secondly, this application provides a ledger management device based on blockchain evidence storage technology, comprising:

[0032] The hash value generation module is used to configure the mapping relationship between the ledger sensitive fields of the ledger data and the corresponding evidence storage chain blocks of the data storage chain based on the business requirements using a preset dynamic mapping table, so as to obtain the mapping relationship configuration result. When the ledger data is detected to have changed, the preset hash value determination algorithm is called and the corresponding hash value is generated based on the ledger data. Based on the mapping relationship configuration result, the hash value is stored in the data storage chain of the preset dual-chain evidence storage architecture.

[0033] The verification result determination module is used to call the logical rule verification mechanism corresponding to the smart contract in the blockchain when an approval request is received to perform logical verification on the approval operation information corresponding to the approval request, including the operator identifier, electronic signature and approval opinion, and obtain the verification result.

[0034] The ledger data management module is used to, if the verification result indicates that the verification is successful, call the smart contract to record the approval operation information corresponding to the approval request, including the operator identifier, electronic signature, and approval opinion, and store the approval operation information in the process evidence storage chain of the preset dual-chain evidence storage architecture, so as to manage the ledger data using the data evidence storage chain and the process evidence storage chain; wherein, the approval opinion is the decision basis corresponding to the approval process of the approval request; the data evidence storage chain and the process evidence storage chain are bound based on the approval identifier in the preset dual-chain evidence storage architecture.

[0035] Optionally, the hash value generation module includes:

[0036] The mapping relationship configuration result generation unit is used to perform field-level mapping between ledger sensitive fields and evidence storage chain blocks based on a preset dynamic mapping table and business requirements to obtain the mapping relationship configuration result.

[0037] The data snapshot determination unit is used to generate a data snapshot corresponding to the data change process before and after the data change when the ledger data changes, to determine the data difference part based on the data snapshot, and then call a preset hash value determination algorithm to determine the hash value corresponding to the data difference part.

[0038] The evidence storage certificate generation unit is used to determine the evidence storage chain block corresponding to the hash value based on the mapping relationship configuration result, so as to store the hash value in the evidence storage chain block corresponding to the data evidence storage chain in the preset dual-chain evidence storage architecture, and generate an evidence storage certificate; the evidence storage certificate includes the block height and data change identifier corresponding to the evidence storage chain block.

[0039] Thirdly, this application provides an electronic device, comprising:

[0040] Memory, used to store computer programs;

[0041] A processor is used to execute the computer program to implement the aforementioned ledger management method based on blockchain evidence storage technology.

[0042] Fourthly, this application provides a computer-readable storage medium for storing a computer program, wherein the computer program, when executed by a processor, implements the aforementioned ledger management method based on blockchain evidence storage technology.

[0043] As can be seen from the above, before implementing ledger management based on blockchain evidence storage technology, this application needs to utilize a preset dynamic mapping table and configure the mapping relationship between the ledger's sensitive fields and the corresponding evidence storage chain blocks based on business requirements. This mapping relationship configuration result allows the system to, when a change in ledger data is detected, invoke a preset hash value determination algorithm to generate a corresponding hash value based on the ledger data, and store the hash value in the data storage chain within the preset dual-chain evidence storage architecture based on the mapping relationship configuration result. When an approval request is received, the system invokes the logical rule verification mechanism corresponding to the smart contract in the blockchain to verify the approval request. The approval operation information corresponding to the approval request, including the operator's identifier, electronic signature, and approval opinion, is logically verified to obtain a verification result. If the verification result indicates that the verification is successful, the smart contract is invoked to record the approval operation information corresponding to the approval request, including the operator's identifier, electronic signature, and approval opinion, and the approval operation information is stored in the process storage chain in the preset dual-chain storage architecture to manage the ledger data using the data storage chain and the process storage chain. Among them, the approval opinion is the decision basis corresponding to the approval process of the approval request. The data storage chain and the process storage chain are bound based on the approval identifier in the preset dual-chain storage architecture.

[0044] Therefore, this application first requires configuring a mapping relationship between the sensitive fields of the ledger data and the corresponding evidence storage chain blocks based on business needs using a pre-set dynamic mapping table. This mapping relationship configuration result allows the system to call a pre-set hash value determination algorithm and generate a corresponding hash value based on the ledger data when a change in the ledger data is detected. The hash value is then stored in the data storage chain within the pre-set dual-chain evidence storage architecture based on the mapping relationship configuration result. Secondly, when an approval request is received, the logical rule verification mechanism corresponding to the smart contract in the blockchain is invoked to logically verify the approval operation information corresponding to the approval request, including the operator's identifier, electronic signature, and approval opinion, obtaining the verification result. Finally, if the verification result indicates that the verification passed, the smart contract is invoked to record the approval operation information corresponding to the approval request, including the operator's identifier, electronic signature, and approval opinion, and this approval operation information is stored in the process evidence storage chain within the pre-set dual-chain evidence storage architecture. This allows for the management of ledger data using both the data storage chain and the process evidence storage chain. This improves the efficiency of ledger management in the process of ledger management based on blockchain evidence storage technology, thereby enhancing the user experience. Attached Figure Description

[0045] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on the provided drawings without creative effort.

[0046] Figure 1 This application discloses a flowchart of a ledger management method based on blockchain evidence storage technology.

[0047] Figure 2 This is a schematic diagram of a ledger management device based on blockchain evidence storage technology disclosed in this application.

[0048] Figure 3 This is a structural diagram of an electronic device disclosed in this application. Detailed Implementation

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

[0050] Currently, the management of various ledger data in grassroots governance scenarios faces numerous pain points: regarding data tampering risks, traditional ledgers primarily rely on centralized databases for storage; regarding traceability efficiency, existing systems have significant shortcomings, merely recording the final state of the data; and regarding approval processes, current ledger changes typically require manual completion of approval forms. Therefore, this application provides a ledger management method based on blockchain-based evidence storage technology, which can improve the efficiency of ledger management in the process of using blockchain-based evidence storage technology.

[0051] See Figure 1 As shown in the figure, an embodiment of the present invention discloses a ledger management method based on blockchain evidence storage technology, including:

[0052] Step S11: Utilize a preset dynamic mapping table and configure the mapping relationship between the ledger sensitive fields of the ledger data and the corresponding evidence storage chain blocks of the data evidence storage chain based on business requirements to obtain the mapping relationship configuration result. This is so that when a change in the ledger data is detected, a preset hash value determination algorithm is called to generate a corresponding hash value based on the ledger data, and the hash value is stored in the data evidence storage chain of the preset dual-chain evidence storage architecture based on the mapping relationship configuration result.

[0053] In this embodiment, a data storage chain needs to be established for data storage. This data storage chain is mainly responsible for storing a series of key metadata such as hash fingerprints, timestamps, operator identification (e.g., digital certificates), and device fingerprints of the ledger data. This metadata can clearly and accurately reflect various attributes and operation-related information of the data.

[0054] Subsequently, whenever the ledger data changes, the system automatically generates a hash value for the current state of the entry based on a preset algorithm mechanism, such as the MD5 algorithm. This hash value is a unique and tamper-proof digital "fingerprint" of the current state of the data. The system then writes this hash value into the data storage chain, thus forming an irreversible change record. Furthermore, this application embodiment introduces a "dynamic mapping table" mechanism. Through this mechanism, this application embodiment can configure the mapping relationship between ledger fields and blockchain storage chain blocks according to actual needs, thereby achieving efficient association between the two.

[0055] Regarding field-level mapping configuration, this application embodiment sets the correspondence between sensitive fields in the ledger and blockchain evidence storage blocks according to business needs. For example, the "Subsidy Amount" field in the "Disability Subsidy Ledger" is mapped to the hash of the Nth block in the data chain. Similarly, the "Place of Origin" field in the "Household Registration Change Record" can be mapped to another specific block hash. An automatic triggering mechanism is introduced to ensure the real-time nature and security of the data.

[0056] Specifically, a pre-defined dynamic mapping table is used to configure the mapping relationship between the sensitive fields of the ledger data and the corresponding evidence storage chain blocks based on business requirements. This mapping relationship configuration result allows the system to call a pre-defined hash value determination algorithm to generate a corresponding hash value based on the ledger data when a change in the ledger data is detected. The hash value is then stored in the data storage chain within the pre-defined dual-chain evidence storage architecture based on the mapping relationship configuration result. This process can include: using a pre-defined dynamic mapping table to perform field-level mapping between the sensitive fields of the ledger and the evidence storage chain blocks based on business requirements; generating a data snapshot corresponding to the data before and after the change based on the change result, identifying the data differences based on the data snapshot, and then calling the pre-defined hash value determination algorithm to determine the hash value corresponding to the data differences; determining the evidence storage chain block corresponding to the hash value based on the mapping relationship configuration result, storing the hash value in the evidence storage chain block corresponding to the data storage chain in the pre-defined dual-chain evidence storage architecture, and generating an evidence storage certificate; the evidence storage certificate includes the block height corresponding to the evidence storage chain block and a data change identifier.

[0057] In this embodiment, after storing the hash value to the data storage chain in the preset dual-chain storage architecture based on the mapping relationship configuration result, all records in this embodiment will form the entire process of data changes from the initial state to the current state. In the actual storage process, the data itself is not directly uploaded to the chain. Instead, only the hash digest of the data is extracted to verify data consistency. This design avoids the performance problems caused by directly storing large amounts of raw data on the blockchain, ensuring both data security and verifiability while effectively optimizing the utilization of storage resources.

[0058] Specifically, after storing the hash value into the data storage chain in the preset dual-chain storage architecture based on the mapping relationship configuration result, it may further include: when a change in the ledger data is detected, extracting the timestamp, operator identity identifier, and device fingerprint corresponding to the data change process based on the mapping relationship configuration result, and setting the timestamp, operator identity identifier, and device fingerprint as metadata; storing the metadata into the data storage chain corresponding to the hash value to obtain a chain-stored change record; wherein, the data storage chain only stores hash digests, and all data in the data storage chain is tamper-proof; the hash value is a hash value used to verify data consistency; the change record is a record of data storage of the ledger data.

[0059] Step S12: When an approval request is received, the logical rule verification mechanism corresponding to the smart contract in the blockchain is invoked to perform logical verification on the approval operation information corresponding to the approval request, including the operator identifier, electronic signature, and approval opinion, and the verification result is obtained.

[0060] In this embodiment, when the ledger data changes, the system automatically triggers a series of processes. First, the system generates a complete snapshot of the data before and after the modification, recording the state of the data before and after the change for subsequent comparison and verification. Then, it calculates the hash value of the data difference, using an algorithm to ensure the accuracy and uniqueness of the data difference, thereby accurately identifying the changed content of the data. Subsequently, the system packages the calculated hash value, the operator's digital certificate, and the approval process ID into a complete and tamper-proof transaction, and securely uploads it to the blockchain. Finally, it returns a proof of authenticity (including block height and transaction ID) to the ledger module, providing authoritative proof of the modification of the ledger data.

[0061] Furthermore, regarding mandatory permission verification, this application's embodiments introduce smart contracts. These contracts can accurately determine whether the current operator possesses the corresponding operational permissions based on the ledger type and the specific fields to be modified. In one specific implementation, taking the "modification of information for low-income households" as an example, due to the sensitivity and importance of this information, which involves numerous livelihood security issues, it must be ultimately reviewed by the director of the Civil Affairs Bureau. Similarly, "updating the deceased population" directly relates to multiple aspects of social management, thus requiring confirmation by a police officer from the local police station. This mandatory verification and approval process ensures that every approval operation complies with the prescribed permission requirements, preventing unauthorized approvals.

[0062] It's worth noting that logical rule validation is also a crucial function of smart contracts. Contracts embed rigorous business logic rules. For example, in personnel information management, for individuals clearly marked as "dead," it's logically and practically impossible for new employment records to be created. Smart contracts can readily identify such illogical operations and prevent them in time, avoiding data chaos and errors. Similarly, for users without property records, according to relevant regulations and actual circumstances, property subsidies should not be added. Smart contracts strictly adhere to this logical rule to prevent unreasonable subsidy distributions and ensure the fair allocation and use of resources.

[0063] Specifically, upon receiving an approval request, the logical rule verification mechanism corresponding to the smart contract in the blockchain is invoked to logically verify the approval operation information corresponding to the approval request, including the operator's identifier, electronic signature, and approval opinion. The verification result can include: upon receiving an approval request, determining the ledger type and modified fields corresponding to the approval request, and invoking the logical rule verification mechanism corresponding to the smart contract in the blockchain to determine whether the initiator of the approval request has the corresponding authority based on the ledger type and modified fields, thus obtaining an authority judgment result; if the authority judgment result indicates that the initiator has the corresponding authority, the data logic verification rules of the smart contract are invoked to perform a data logic consistency judgment on the approval request, thus obtaining a consistency judgment result; if the authority judgment result or the consistency judgment result indicates that the judgment fails, the approval constraint mechanism in the smart contract is invoked to monitor abnormal behavior, and then an early warning notification is generated based on the abnormal behavior using the early warning notification rules.

[0064] In this embodiment, an early warning notification mechanism is established to add a security barrier to the approval process. When the system detects abnormal behavior, such as the same field being modified more than three times within 24 hours, this is highly likely due to operational errors or potential risks of violations. At this time, the system will automatically trigger an early warning notification, quickly sending relevant information to the administrator or regulatory department. The administrator and regulatory department can intervene promptly, conduct in-depth investigations and analyses of the abnormal situation, and take appropriate measures to resolve it, thereby effectively preventing the potential problems from escalating further and ensuring the normal operation of the approval process and data security.

[0065] Specifically, the process involves invoking the approval constraint mechanism within the smart contract to monitor abnormal behavior, and then using early warning notification rules to generate early warning notification information based on the abnormal behavior. This can include: invoking the approval constraint mechanism within the smart contract to monitor ledger data modification operations in real time, and automatically generating early warning information using early warning notification rules when the number of modifications to the same field within a preset time period exceeds a preset field modification threshold; sending the early warning information to the early warning processing center so that the early warning processing center can take appropriate action based on the early warning information; wherein, the early warning information includes ledger data modification information, operator identity information, and ledger data approval process identifier; when early warning information is generated, invoking the smart contract to suspend ledger data modification operations until the early warning processing center completes the review of the ledger data modification operations.

[0066] Step S13: If the verification result indicates that the verification is successful, the smart contract is invoked to record the approval operation information corresponding to the approval request, including the operator identifier, electronic signature, and approval opinion. The approval operation information is then stored in the process evidence storage chain of the preset dual-chain evidence storage architecture to manage the ledger data using the data evidence storage chain and the process evidence storage chain. The approval opinion is the decision basis corresponding to the approval process of the approval request. The data evidence storage chain and the process evidence storage chain are bound based on the approval identifier in the preset dual-chain evidence storage architecture.

[0067] In this embodiment, to rigorously record the approval process, a process evidence storage chain is designed, whose core responsibility is to record every detailed step in the approval process. During the approval process, all approval actions, whether it's the initial stage of submitting the application or key steps such as preliminary review and final review, are recorded through smart contracts. The recorded content includes information such as the operator ID, electronic signature, and approval comments. The operator ID identifies the specific person performing the approval operation, the electronic signature further enhances the security and reliability of identity verification, and the approval comments provide detailed decision-making basis for the entire approval process.

[0068] Specifically, if the verification result indicates that the verification is successful, the smart contract is invoked to record the approval operation information corresponding to the approval request, including the operator's identifier, electronic signature, and approval opinion. This approval operation information is then stored in the process evidence storage chain within the preset dual-chain evidence storage architecture. This process may include: if the verification result indicates that the verification is successful, the smart contract is invoked to record the approval operation information corresponding to the approval request, including the operator's identifier, electronic signature, and approval opinion; the approval operation information includes application submission information, preliminary review information, and final review information; the approval operation information is stored in the process evidence storage chain within the preset dual-chain evidence storage architecture, and approval identifiers corresponding to the process evidence storage chain and the data evidence storage chain are determined. The process evidence storage chain is then invoked, and based on the approval identifiers, the approval process corresponding to each data change operation is recorded in both the process evidence storage chain and the data evidence storage chain, thereby utilizing the process evidence storage chain to review the compliance of the approval operation information.

[0069] It is worth noting that the aforementioned process evidence chain and data evidence chain are not isolated but are bound together by a unique identifier (such as an approval number). This binding mechanism tightly links data and processes, achieving a two-way association between "data and process." Through this association, not only can the processing status of data throughout the entire process be traced, but the compliance of the process can also be reviewed and verified.

[0070] In this embodiment, when a record of data is modified, the system simultaneously records the changed hash value on the data chain and the approval process on the workflow chain. If a dispute arises during subsequent data processing or use, the workflow chain can be used to trace whether the approval authority was compliant, and the data chain can be used to verify whether the data has been tampered with, thus ensuring the authenticity and integrity of the data. This dual-chain evidence storage architecture provides a solid guarantee for secure data management and the standardized execution of processes.

[0071] In one specific implementation, taking "community-based elderly subsidy ledger management" as an example, the corresponding operation flow of this application embodiment is as follows:

[0072] First, in the data initialization phase, this application embodiment stores fields such as the elderly person's name, ID number, residential address, and subsidy amount into the ledger database. Then, an initial data snapshot is generated and a hash value is calculated and written into the data storage chain. Subsequently, an approval process record is created synchronously and written into the process storage chain.

[0073] Secondly, during the data modification stage, the embodiment of this application can initiate the modification of the "subsidy amount" via PC or mobile terminal. Subsequently, the system calls the digital certificate signature to verify the operator's identity and trigger the approval process. The approver needs to complete the verification through electronic signature. Then, the smart contract is called to verify the permissions and modification logic. If it is legal, the next step is taken.

[0074] Finally, during the data upload phase, after the data is modified, the system generates snapshots of the old and new versions, calculates the hash value corresponding to the difference data, and then packages the hash value, operator information, and approval process ID into the data chain. Then, it generates and returns the evidence certificate to the ledger module to record that the modification has been uploaded to the chain.

[0075] As can be seen from the above, this embodiment first requires using a preset dynamic mapping table and configuring the mapping relationship between the ledger sensitive fields of the ledger data and the corresponding evidence storage chain blocks of the data evidence storage chain based on business needs. This results in a mapping relationship configuration. When a change in the ledger data is detected, a preset hash value determination algorithm is invoked to generate a corresponding hash value based on the ledger data. The hash value is then stored in the data evidence storage chain within the preset dual-chain evidence storage architecture based on the mapping relationship configuration result. Secondly, when an approval request is received, the logical rule verification mechanism corresponding to the smart contract in the blockchain is invoked to logically verify the approval operation information corresponding to the approval request, including the operator identifier, electronic signature, and approval opinion, obtaining a verification result. Finally, if the verification result indicates that the verification is successful, the smart contract is invoked to record the approval operation information corresponding to the approval request, including the operator identifier, electronic signature, and approval opinion, and this approval operation information is stored in the process evidence storage chain within the preset dual-chain evidence storage architecture. This allows for the management of ledger data using both the data evidence storage chain and the process evidence storage chain. This improves the efficiency of ledger management in the process of ledger management based on blockchain evidence storage technology, thereby enhancing the user experience.

[0076] Accordingly, see Figure 2 As shown, this application also provides a ledger management device based on blockchain evidence storage technology, including:

[0077] The hash value generation module 11 is used to configure the mapping relationship between the ledger sensitive fields of the ledger data and the evidence storage chain blocks corresponding to the data storage chain based on the business requirements using a preset dynamic mapping table, so as to obtain the mapping relationship configuration result. When the ledger data is detected to have changed, the preset hash value determination algorithm is called and the corresponding hash value is generated based on the ledger data. Based on the mapping relationship configuration result, the hash value is stored in the data storage chain in the preset dual-chain evidence storage architecture.

[0078] The verification result determination module 12 is used to call the logical rule verification mechanism corresponding to the smart contract in the blockchain when an approval request is received to perform logical verification on the approval operation information corresponding to the approval request, including the operator identifier, electronic signature and approval opinion, and obtain the verification result.

[0079] The ledger data management module 13 is used to, if the verification result indicates that the verification is successful, call the smart contract to record the approval operation information corresponding to the approval request, including the operator identifier, electronic signature, and approval opinion, and store the approval operation information in the process evidence storage chain of the preset dual-chain evidence storage architecture, so as to manage the ledger data using the data evidence storage chain and the process evidence storage chain; wherein, the approval opinion is the decision basis corresponding to the approval process of the approval request; the data evidence storage chain and the process evidence storage chain are bound based on the approval identifier in the preset dual-chain evidence storage architecture.

[0080] In some specific embodiments, the hash value generation module 11 may specifically include:

[0081] The mapping relationship configuration result generation unit is used to perform field-level mapping between ledger sensitive fields and evidence storage chain blocks based on a preset dynamic mapping table and business requirements to obtain the mapping relationship configuration result.

[0082] The data snapshot determination unit is used to generate a data snapshot corresponding to the data change process before and after the data change when the ledger data changes, to determine the data difference part based on the data snapshot, and then call a preset hash value determination algorithm to determine the hash value corresponding to the data difference part.

[0083] The evidence storage certificate generation unit is used to determine the evidence storage chain block corresponding to the hash value based on the mapping relationship configuration result, so as to store the hash value in the evidence storage chain block corresponding to the data evidence storage chain in the preset dual-chain evidence storage architecture, and generate an evidence storage certificate; the evidence storage certificate includes the block height and data change identifier corresponding to the evidence storage chain block.

[0084] In some specific embodiments, the ledger management device based on blockchain evidence storage technology may further include:

[0085] The metadata determination unit is used to extract the timestamp, operator identity identifier, and device fingerprint corresponding to the data change process based on the mapping relationship configuration result when a change in ledger data is detected, and to set the timestamp, operator identity identifier, and device fingerprint as metadata;

[0086] A change record determination unit is used to store the metadata into a data storage chain corresponding to the hash value to obtain a chain-stored change record; wherein, the data storage chain only stores hash digests, and all data in the data storage chain is immutable; the hash value is a hash value used to verify data consistency; the change record is a record for data storage of ledger data.

[0087] In some specific embodiments, the verification result determination module 12 may specifically include:

[0088] The permission judgment result determination unit is used to determine the ledger type and modified fields corresponding to the approval request when an approval request is received, and to call the logical rule verification mechanism corresponding to the smart contract in the blockchain to determine whether the initiator of the approval request has the corresponding permission based on the ledger type and the modified fields, so as to obtain the permission judgment result.

[0089] The consistency judgment result determination unit is used to call the data logic verification rules of the smart contract to perform a data logic consistency judgment on the approval request if the permission judgment result indicates that the initiator has the corresponding permission, and obtain a consistency judgment result.

[0090] An abnormal behavior monitoring unit is used to monitor abnormal behavior by calling the approval constraint mechanism in the smart contract if the permission judgment result or the consistency judgment result indicates that the judgment has failed, and then using the early warning notification rules to generate early warning notification information based on the abnormal behavior.

[0091] In some specific embodiments, the verification result determination module 12 may specifically include:

[0092] The early warning information generation unit is used to call the approval constraint mechanism in the smart contract to monitor the modification operation of the ledger data in real time, and automatically generate early warning information using the early warning notification rules when it is detected that the number of times the same field is modified within a preset time period is greater than the preset field modification threshold.

[0093] The early warning information sending unit is used to send the early warning information to the early warning processing center so that the early warning processing center can perform corresponding processing based on the early warning information; wherein, the early warning information includes ledger data modification information, operator identity information, and ledger data approval process identifier;

[0094] The smart contract invocation unit is used to invoke the smart contract to suspend the ledger data modification operation when the warning information is generated, until the warning processing center completes the review operation of the ledger data modification operation.

[0095] In some specific embodiments, the ledger data management module 13 may specifically include:

[0096] An approval operation information determination unit is used to, if the verification result indicates that the verification is passed, call the smart contract to record the approval operation information corresponding to the approval request, including the operator identifier, electronic signature, and approval opinion; the approval operation information includes application submission information, preliminary review information, and final review information;

[0097] An approval operation information storage unit is used to store the approval operation information in the process evidence storage chain in the preset dual-chain evidence storage architecture, and to determine the approval identifier corresponding to the process evidence storage chain and the data evidence storage chain, so as to call the process evidence storage chain and record the approval process corresponding to each data change operation in the process evidence storage chain and the data evidence storage chain based on the approval identifier, so as to use the process evidence storage chain to review the compliance of the approval operation information.

[0098] Furthermore, embodiments of this application also disclose an electronic device, Figure 3 This is a structural diagram of an electronic device 20 according to an exemplary embodiment. The content of the diagram should not be construed as limiting the scope of this application. The electronic device 20 may specifically include: at least one processor 21, at least one memory 22, a power supply 23, a communication interface 24, an input / output interface 25, and a communication bus 26. The memory 22 stores a computer program, which is loaded and executed by the processor 21 to implement the relevant steps in the ledger management method based on blockchain evidence storage technology disclosed in any of the foregoing embodiments. Furthermore, the electronic device 20 in this embodiment may specifically be an electronic computer.

[0099] In this embodiment, the power supply 23 is used to provide operating voltage for each hardware device on the electronic device 20; the communication interface 24 can create a data transmission channel between the electronic device 20 and external devices, and the communication protocol it follows can be any communication protocol applicable to the technical solution of this application, and is not specifically limited here; the input / output interface 25 is used to acquire external input data or output data to the outside world, and its specific interface type can be selected according to specific application needs, and is not specifically limited here.

[0100] In addition, the memory 22, as a carrier for resource storage, can be a read-only memory, random access memory, disk or optical disk, etc. The resources stored thereon can include operating system 221, computer program 222, etc., and the storage method can be temporary storage or permanent storage.

[0101] The operating system 221 is used to manage and control the various hardware devices on the electronic device 20 and the computer program 222, which may be Windows Server, Netware, Unix, Linux, etc. In addition to including a computer program capable of performing the ledger management method based on blockchain evidence storage technology executed by the electronic device 20 as disclosed in any of the foregoing embodiments, the computer program 222 may further include computer programs capable of performing other specific tasks.

[0102] Furthermore, this application also discloses a computer-readable storage medium for storing a computer program; wherein, when the computer program is executed by a processor, it implements the aforementioned ledger management method based on blockchain evidence storage technology. Specific steps of this method can be found in the corresponding content disclosed in the foregoing embodiments, and will not be repeated here.

[0103] The various embodiments in this specification are described in a progressive manner, with each embodiment focusing on its differences from other embodiments. Similar or identical parts between embodiments can be referred to interchangeably. For the apparatus disclosed in the embodiments, since it corresponds to the method disclosed in the embodiments, the description is relatively simple; relevant parts can be referred to in the method section.

[0104] Those skilled in the art will further recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of both. To clearly illustrate the interchangeability of hardware and software, the components and steps of the various examples have been generally described in terms of functionality in the foregoing description. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0105] The steps of the methods or algorithms described in conjunction with the embodiments disclosed herein can be implemented directly by hardware, a software module executed by a processor, or a combination of both. The software module can be located in random access memory (RAM), main memory, read-only memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium known in the art.

[0106] Finally, it should be noted that in this document, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, 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.

[0107] The technical solutions provided in this application have been described in detail above. Specific examples have been used to illustrate the principles and implementation methods of this application. The descriptions of the above embodiments are only for the purpose of helping to understand the methods and core ideas of this application. At the same time, for those skilled in the art, there will be changes in the specific implementation methods and application scope based on the ideas of this application. Therefore, the content of this specification should not be construed as a limitation of this application.

Claims

1. A method for ledger management based on blockchain storage technology, characterized in that, The application comprises the following steps: A mapping relationship configuration result is obtained by using a preset dynamic mapping table and configuring a mapping relationship between a table sensitive field of the table data and a data storage chain block corresponding to a data storage chain based on business requirements, so that when a change in the table data is monitored, a preset hash value determination algorithm is called and a corresponding hash value is generated based on the table data, and the hash value is stored in a data storage chain in a preset double-chain storage architecture based on the mapping relationship configuration result; When the approval request is received, a logical verification mechanism corresponding to the smart contract in the block chain is called to verify the approval operation information corresponding to the approval request, including the operation party identifier, the electronic seal and the approval opinion, to obtain a verification result; If the verification result indicates that the verification is passed, the smart contract records the approval operation information corresponding to the approval request, including the operation party identifier, the electronic seal and the approval opinion, and stores the approval operation information in the process storage chain in the preset double-chain storage architecture, so as to manage the table data by using the data storage chain and the process storage chain; wherein the approval opinion is the decision basis corresponding to the approval process of the approval request; the data storage chain and the process storage chain are bound based on an approval identifier in the preset double-chain storage architecture. 2.The blockchain-based recordal technology-based ledger management method of claim 1, wherein, The application comprises the following steps: A mapping relationship configuration result is obtained by using a preset dynamic mapping table and configuring a mapping relationship between a table sensitive field of the table data and a data storage chain block corresponding to a data storage chain based on business requirements, so that when a change in the table data is monitored, a preset hash value determination algorithm is called and a corresponding hash value is generated based on the table data, and the hash value is stored in a data storage chain in a preset double-chain storage architecture based on the mapping relationship configuration result; A mapping relationship configuration result is obtained by using a preset dynamic mapping table and configuring a mapping relationship between a table sensitive field of the table data and a data storage chain block corresponding to a data storage chain based on business requirements, so that when a change in the table data is monitored, a preset hash value determination algorithm is called and a corresponding hash value is generated based on the table data, and the hash value is stored in a data storage chain in a preset double-chain storage architecture based on the mapping relationship configuration result; A hash value corresponding to the hash value is determined based on the mapping relationship configuration result, so that the hash value is stored in the data storage chain block corresponding to the data storage chain in the preset double-chain storage architecture, and a storage certificate is generated; the storage certificate comprises a block height corresponding to the data storage chain block and a data change identifier. 3.The blockchain-based recordal technology-based ledger management method of claim 1, wherein, After the hash value is stored in the data storage chain in the preset double-chain storage architecture based on the mapping relationship configuration result, the following steps are further included: When a change in the table data is monitored, a timestamp, an operation party identifier and a device fingerprint corresponding to the data change process are extracted based on the mapping relationship configuration result, and the timestamp, the operation party identifier and the device fingerprint are set as metadata; The metadata is stored into a data storage chain corresponding to the hash value, to obtain a chain-stored change record; wherein, the data storage chain only stores hash digest, and all data in the data storage chain are not tamperable; the hash value is a hash value used for verifying data consistency; the change record is a record of data storage of the ledger data. 4.The blockchain-based recordal technology-based ledger management method of claim 1, wherein, When the approval request is received, a logical rule verification mechanism corresponding to the smart contract in the block chain is called to perform logical verification on the approval operation information corresponding to the approval request, including an operator identifier, an electronic signature and an approval opinion, to obtain a verification result, including: When the approval request is received, the ledger type corresponding to the approval request and the modified field to be modified are determined, and a logical rule verification mechanism corresponding to the smart contract in the block chain is called and based on the ledger type and the modified field to determine whether the initiator of the approval request has corresponding authority, to obtain an authority judgment result; If the authority judgment result represents that the initiator has corresponding authority, the data logic verification rule of the smart contract is called to perform data logic consistency judgment on the approval request, to obtain a consistency judgment result; If the authority judgment result or the consistency judgment result represents that the judgment is not passed, the approval constraint mechanism in the smart contract is called to monitor abnormal behavior, and then a warning notification rule is used to generate warning notification information based on the abnormal behavior. 5.The blockchain-based recordal technology based ledger management method of claim 4, wherein, The calling of the approval constraint mechanism in the smart contract to monitor abnormal behavior, and then the generation of warning notification information based on the abnormal behavior using a warning notification rule, includes: The approval constraint mechanism in the smart contract is called to monitor the ledger data modification operation in real time, and when it is detected that the number of field modification corresponding to the same field in a preset time period is greater than a preset field modification threshold, a warning notification rule is used to automatically generate warning information; The warning information is sent to a warning processing center, so that the warning processing center performs corresponding processing based on the warning information; wherein, the warning information contains ledger data modification information, operator identity information and ledger data approval process identifier; When the warning information is generated, the smart contract is called to suspend the ledger data modification operation until the warning processing center completes the review operation of the ledger data modification operation. 6.The blockchain-based recordal technology based ledger management method according to claim 1, wherein, If the verification result represents that the verification is passed, the smart contract is called to record the approval operation information corresponding to the approval request, including an operator identifier, an electronic signature and an approval opinion, and the approval operation information is stored into a process storage chain in the preset double-chain storage architecture, including: If the verification result represents that the verification is passed, the smart contract is called to record the approval operation information corresponding to the approval request, including an operator identifier, an electronic signature and an approval opinion; the approval operation information includes submission application information, preliminary review information and final review information; The approval operation information is stored into a process evidence chain in the preset double-chain evidence architecture, and an approval identifier corresponding to the process evidence chain and the data evidence chain is determined to call the process evidence chain and record an approval process corresponding to each data change operation into the process evidence chain and the data evidence chain based on the approval identifier, so as to review the compliance of the approval operation information by using the process evidence chain. 7.A ledger management device based on a blockchain storage technology, characterized in that, Comprise: The hash value generation module is configured to map the account sensitive field of the account data and the evidence chain block corresponding to the data evidence chain based on the preset dynamic mapping table and business requirements, and obtain a mapping relationship configuration result, so that when the account data is monitored to be changed, a preset hash value determination algorithm is called and a corresponding hash value is generated based on the account data, and the hash value is stored into the data evidence chain in the preset double-chain evidence architecture based on the mapping relationship configuration result. The verification result determination module is configured to, when receiving an approval request, call a logic rule verification mechanism corresponding to a smart contract in the blockchain to perform logic verification on approval operation information corresponding to the approval request, including an operator identifier, an electronic seal and an approval opinion, and obtain a verification result. The account data management module is configured to, if the verification result indicates that the verification is passed, record the approval operation information corresponding to the approval request, including the operator identifier, the electronic seal and the approval opinion, and store the approval operation information into the process evidence chain in the preset double-chain evidence architecture, so as to manage the account data by using the data evidence chain and the process evidence chain; wherein the approval opinion is a decision basis corresponding to an approval process of the approval request; the data evidence chain and the process evidence chain are bound based on an approval identifier in the preset double-chain evidence architecture. 8.The blockchain-based recordal technology-based ledger management apparatus according to claim 7, wherein, The hash value generation module comprises: The mapping relationship configuration result generation unit is configured to perform field-level mapping of the account sensitive field and the evidence chain block based on a preset dynamic mapping table and business requirements, and obtain a mapping relationship configuration result. The data snapshot determination unit is configured to, when the account data is changed, generate data snapshots corresponding to before and after the data change process based on a change result, determine a data difference part based on the data snapshots, and then determine a hash value corresponding to the data difference part by using a preset hash value determination algorithm. The evidence certificate generation unit is configured to determine an evidence chain block corresponding to the hash value based on the mapping relationship configuration result, store the hash value into the evidence chain block corresponding to the data evidence chain in the preset double-chain evidence architecture, and generate an evidence certificate; the evidence certificate comprises a block height corresponding to the evidence chain block and a data change identifier.

9. An electronic device, comprising: Comprise: A memory for saving a computer program; A processor for executing the computer program to implement the account management method based on the blockchain evidence technology according to any one of claims 1 to 6.

10. A computer-readable storage medium, characterized in that, A memory for saving a computer program, wherein the computer program is executed by a processor to implement the account management method based on the blockchain evidence technology according to any one of claims 1 to 6.

Images