A multi-stamp stamping system based on a blockchain smart contract

Abstract

The present application belongs to the technical field of information security, and particularly relates to a multi-seal stamping system based on a block chain smart contract. The present application realizes the cooperation of multiple units and multiple seals, initiatively adds a multi-seal approval mode on the platform side, covers the blank of such a scene in the market, and realizes that units that join the platform can join the seal approval flow; the present application proposes a set of localized or platformized seal verification logic based on a smart contract relying on specific hardware equipment, and does not need to rely on a verification code to perform manual verification on a webpage, thereby truly reducing the verification workload and realizing that the device can only be automatically verified locally before being started.

Description

Technical Field

[0001] This invention belongs to the field of information security technology, specifically relating to a multi-seal stamping system based on blockchain smart contracts. Background Technology

[0002] Existing blockchain-based seal management platforms cannot solve the problems of automatic seal unlocking and verification of seal results in multi-party seal usage scenarios. For documents requiring multiple signatures (such as project acceptance documents), there is usually a strict sealing order, and subsequent units can only seal after the preceding units have completed their seals. In existing solutions, each seal application must go through the existing system, and each subsequent node must always check the authenticity of the seal used by the previous node before it can seal.

[0003] Moreover, although existing technologies allow blockchain platforms to record the stamping results and generate verification information, users still need to log in to the platform and enter a lengthy verification code (which must be sent to the inquirer by relevant personnel from the previous stamping node) to verify the information if they require verification. While this enhances the credibility of the stamping behavior, it increases the verification and operational costs for users. In particular, when verification is required across multiple companies, all companies need to log in to the platform and repeat the above steps several times to complete a compliant multi-party stamping, which is both cumbersome and impractical.

[0004] Therefore, this invention designs a multi-seal stamping system based on smart contracts. Users only need to open the seal to perform local verification of the previous seal usage. After the verification information is true and reliable and the comparison is successful, the seal can be unlocked by fingerprint and stamped. No additional operation is required from the seal manager, truly realizing "open and stamp", delivering the workload of manual review to the underlying technology, and truly realizing the simplification, standardization and intelligence of the seal usage process. Summary of the Invention

[0005] The following provides a brief overview of one or more aspects to offer a basic understanding of them. This overview is not an exhaustive summary of all conceived aspects, nor is it intended to identify key or decisive elements of all aspects, nor to define the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form to prepare for the more detailed descriptions that follow.

[0006] The main objective of this invention is to address the aforementioned technical problems in existing technologies and provide a multi-seal stamping system based on blockchain smart contracts. The entire stamping process of this invention supports cross-company and cross-department creation, including the creation and execution of a user's application to stamp document X by Company A, with the platform creating smart contracts based on a preset process.

[0007] To solve the above problems, the solution of the present invention is:

[0008] A multi-seal stamping method based on blockchain smart contracts includes:

[0009] Receive the key stamping information of the first stamp in the previous node of the stamping process sent by the stamp management platform, and the first hash value of the first stamp sent by the blockchain server.

[0010] A second hash value is generated based on the received key information about the first seal's stamping.

[0011] Determine whether the first Hash value and the second Hash value meet a preset rule, and allow the stamping operation if the preset rule is met.

[0012] Preferably, in the above-mentioned multi-seal stamping method based on blockchain smart contracts, the first Hash value is generated by the first seal and then uploaded to the blockchain server.

[0013] Preferably, in the above-mentioned multi-seal stamping method based on blockchain smart contracts, the key stamping information of the first seal is generated by the first seal after stamping and uploaded to the seal management platform in plaintext.

[0014] Preferably, in the above-mentioned multi-seal stamping method based on blockchain smart contracts, the stamping operation is allowed when the first Hash value is the same as the second Hash value.

[0015] Preferably, in the above-mentioned multi-seal stamping method based on blockchain smart contracts, the stamping process generation includes:

[0016] After the seal management platform approves the seal-using unit selected by the seal-using applicant, it receives a multi-party seal-using application submitted by the seal-using applicant. The multi-party seal-using application includes the reason for seal-using, the required seal, the multi-seal-using process, and uploads the seal-using documents.

[0017] Based on the multi-party stamping application, a stamping unit is selected to approve the multi-party stamping application, and a stamping process covering at least multiple seals is generated after the approval is passed.

[0018] A seal based on a blockchain smart contract includes:

[0019] The communication module is used to receive the key stamping information of the first stamp in the previous node of the stamping process sent by the stamp management platform, and to receive the first hash value of the first stamp sent by the blockchain server.

[0020] The control module is used to generate a second hash value based on the received key information of the first stamp, and to allow or refuse to perform the stamping operation based on the judgment result of whether the first hash value and the second hash value meet the preset rules.

[0021] Preferably, the above-mentioned seal based on a blockchain smart contract further includes:

[0022] The fingerprint module is used to receive fingerprints and perform fingerprint verification operations, and allow the stamping operation after successful verification.

[0023] Preferably, the above-mentioned seal based on a blockchain smart contract further includes: an image acquisition module, used to capture the stamping image and upload it to the seal management platform.

[0024] Preferably, the above-mentioned seal based on a blockchain smart contract further includes: an encryption chip for encrypting the first hash value.

[0025] A seal management system based on blockchain smart contracts includes:

[0026] The seal management platform is used to generate and store the stamping process, receive the key stamping information sent by the first seal at the previous node of the stamping process, and send the key stamping information to the second seal in response to the query request of the second seal at the next node of the stamping process.

[0027] The blockchain server receives the first hash value generated from the key stamping information sent by the first stamp at the previous node of the stamping process, and sends the first hash value to the second stamp in response to the query request of the second stamp at the next node of the stamping process.

[0028] Therefore, the advantages of the present invention are:

[0029] 1. It has enabled collaboration among multiple units and multiple seals, and has innovatively added a multi-seal approval mode on the platform side, covering the gap in such scenarios in the market, and enabling any unit that joins the platform to join the seal approval process;

[0030] 2. Based on specific hardware devices, a set of localized or platform-based seal verification logic based on smart contracts is proposed, which eliminates the need for manual verification based on verification codes, truly reducing the verification workload and enabling the device to open after local verification. Attached Figure Description

[0031] The accompanying drawings, which are incorporated herein and form a part of the specification, illustrate embodiments of the invention and, together with the specification, further serve to explain the principles of the invention and to enable those skilled in the art to make and use this disclosure.

[0032] Figure 1 A schematic diagram illustrating the stamping application process in an embodiment of the present invention is shown;

[0033] Figure 2 A schematic diagram illustrating the stamping process in an embodiment of the present invention is shown;

[0034] Figure 3 This invention illustrates a schematic diagram of the stamping process for three companies and four seals in an embodiment of the invention.

[0035] Figure 4 An illustration of Hash information verification in an embodiment of the present invention is shown;

[0036] Figure 5 A schematic diagram of a seal in an embodiment of the present invention is shown.

[0037] Embodiments of the present invention will be described with reference to the accompanying drawings. Detailed Implementation

[0038] Example

[0039] This invention discloses a stamping system design based on blockchain + IoT devices. The entire system requires specific hardware devices and software platforms to be implemented. Unlike ordinary blockchain stamping device management platforms, the entire stamping process supports cross-company and cross-department creation, including the creation and execution of stamping applications for document X by users of company A. The platform creates smart contracts based on preset processes.

[0040] In this embodiment, the smart seal receives a stamping instruction from the seal-using platform. The smart seal uploads key seal-using field information, and the blockchain middleware records this event on the chain and activates the smart contract. After the seal manager of Company B unlocks the seal, they will automatically receive the seal-using record and stamping application from the previous node transmitted by the seal-using management platform. The seal manager of Company B will locally calculate the seal-using record directly transmitted from the previous node, generate a seal-using hash1, and compare it with the seal-using hash2 value stored in the blockchain node server. If the two match, the smart contract will be automatically executed to push the seal-opening instruction to the device. The seal manager of Company B can open and use the seal after their identity is verified. After use, a new seal-using record is generated and pushed by the platform to the next device. If the hash1 and hash2 values ​​do not match, the seal manager cannot unlock the seal through this application, and the next seal-using node will not receive the application, and so on for subsequent nodes.

[0041] This embodiment is divided into two processes: application for multi-party stamping and execution of multi-party stamping.

[0042] like Figure 1 The image shows the application process requiring multiple signatures. Specifically, it includes:

[0043] S1. The applicant submits the application request by logging into the platform and needs to select the unit to be stamped (the selected unit needs to be managed by the platform).

[0044] S2. After the units to be stamped have submitted the application, the applicant must log in to the platform again to submit a multi-seal application. At this stage, the applicant needs to provide the reason for using the seal, the seal required, the multi-seal stamping process, and upload the stamped documents.

[0045] S3. The stamping platform sends an internal message to remind each approval node to approve the work. Once the approval is approved, the stamping process is successfully created and an internal message notification is sent (this article takes the A01, A02, B01, and C01 processes as examples).

[0046] Please refer to Figure 2 The multivariate printing process of this application includes:

[0047] S1. The applicant for the stamped document logs into the platform and selects the multi-party stamped document application process that has been approved.

[0048] S2. After the first person in charge of the seal opens the device, the platform pushes the application form to device A01. The person in charge of the seal unlocks the device by fingerprint or password, and the device stamps the seal a fixed number of times. After the stamping is completed, the device performs localized hash calculation on the key information of the stamp and uploads the calculation result hash1 to the blockchain server. It also uploads the plaintext information X of the key information of the stamp to the seal management platform. The seal management platform locates the next device to use the seal according to the preset process and pushes the application form to device A02.

[0049] After the seal is powered on, devices S3 and A02 will receive an approval form pushed by the platform. At the same time, they will also receive the plaintext information of A01 seal usage (this information is only used for local calculation of A02 seal) transmitted by the platform and the hash1 value transmitted by the blockchain node server. Device A02 performs local hash calculation on the A01 seal usage information X to obtain the hash2 value. Device A02 compares the hash1 value and the hash2 value locally. If they match, the application form can be unlocked (if multiple application forms match, a button needs to be pressed to select).

[0050] S4. The stamping logic for each subsequent stamp follows the loop of S3 and S4.

[0051] Reference Figure 3 Taking a multi-seal collaboration process spanning 3 companies and 4 seals as an example, the complete verification steps of the entire system are:

[0052] S1. When the application is initiated and arrives at node A01, the person in charge of the A01 seal unlocks it with their fingerprint to use the seal. The key information of the seal application is collected by the CPU, calculated into hash1, and recorded on the chain. If the A01 seal needs to process multiple seal application information at the same time, the key information of this seal application record can also be collected by the blockchain front-end server, calculated into hash1 value, and recorded on the chain.

[0053] S2: The A01 seal call gateway transmits the key field plaintext information X of this stamping action to the seal management platform server. After receiving X, the platform server automatically addresses the A02 seal according to the stamping process and pushes the plaintext information X and the seal application form to the A02 device.

[0054] S3: The A02 seal is powered on and receives the plaintext information X from the A01 seal from the IoT platform. It calls the preset algorithm within the device (which is the same as the algorithm described in S1) to calculate X as hash2. At the same time, the A02 seal requests the hash1 value (generated in S1 and agreed upon by the entire network) from the nearest blockchain node server. The A02 seal compares the hash1 value with the hash2 value. If they match, the seal opening instruction is executed. At this time, the application form appears on the A02 seal screen. When the A02 device detects the fingerprint of the person in charge of the seal, it can unlock the seal and generate a seal usage record Y locally.

[0055] S4: After the A02 stamp is used up, the device will calculate the stamping record Y and generate a hash3 on the blockchain. It will also call the smart contract to write the message "A02 node stamping is finished, B01 stamp can accept application form" to the platform.

[0056] S5, S8: Same as S2

[0057] S6, S9: Same as S3

[0058] S7, S10: Same as S4

[0059] In this embodiment, one hash value is calculated by the platform, and the other hash value is calculated locally by the device after receiving the plaintext information. This ensures that even a slight deviation in the seal usage record will prevent normal unlocking, greatly enhancing the system's rigor and anti-interference capabilities. This avoids the problem of incorrect seal opening caused by device-side malfunctions where both the A information sent to the blockchain platform and the B information sent to the seal management platform are incorrect. In this situation, because the two platforms have consistent preset calculation rules, they simultaneously generate erroneous but consistent hash values, which are then pushed to the next seal device. Although the comparison results are consistent for the platform's authentication, the seal can still be opened.

[0060] This embodiment performs hash value calculations on the device side, which can greatly reduce the computing power burden on the platform. During idle times, the device side only needs to collect the information of each stamping and then perform local hash value calculations according to preset rules, and then submit the calculation results to the platform. During busy times, in order to avoid excessive load on the device, stamping records exceeding the computing power threshold can be pushed to the platform for calculation. This allows for flexible use of the idle capacity of the device and the platform, greatly enhancing the smoothness of the system.

[0061] like Figure 4 The diagram shown illustrates the hash comparison process in this embodiment. For the core hash value comparison method in this system, the five pieces of information A, B, C, D, and E must remain consistent. Regardless of the type of information being compared, whether the information is plaintext or a locally calculated hash value, and regardless of the encryption method used to obtain the hash value, any judgment logic such as A=E, A=D, or D=E should be considered as adhering to the same verification principle.

[0062] For example, in this instruction manual, information A is the hash value of the key field of the current stamping behavior of seal A, information B and C are the plaintext information of the key field of the current stamping behavior of seal A, information D is the same as information A, and information E is the hash value generated locally by seal B after receiving information C. If A = E, it means that the stamping behavior of seal A is genuine and credible, and the seal can be unlocked.

[0063] If information A is the plaintext information of the key field of the current stamping action of seal A, information B and C are the same as information A, information D is the hash value of the key field of the current stamping action of seal A calculated by the platform server, and information E is the hash value generated locally by seal B after receiving information C, the device compares information D and E. If they match, the seal is unlocked. This type of verification logic is the same as the logic described above and should not be considered a new invention.

[0064] like Figure 5The diagram shown illustrates the structure of the smart seal device in this embodiment. It includes a fingerprint module, a 4G IoT card, and an integrated CPU chip. The fingerprint module identifies the user; the 4G IoT card enables communication with the system gateway; the integrated CPU chip calculates hash values ​​locally and collects key field information for each seal application; the MCU chip performs hardware-level operations upon receiving instructions from the platform; the national cryptographic encryption chip ensures information security during communication with the blockchain platform and the seal platform; the high-definition camera takes photos for each seal application, uploading the photos to the seal platform for later verification; the high-definition LED screen and physical buttons allow for various user selections and operations; and the universal seal clamp and flip-type ink extraction structure ensure the smart seal device is compatible with 95% of handle-type seals on the market.

[0065] Therefore, as can be seen from the above description, this embodiment has the following advantages:

[0066] 1. It has enabled collaboration among multiple units and multiple seals, and has innovatively added a multi-seal approval mode on the platform side, covering the gap in such scenarios in the market, and enabling any unit that joins the platform to join the seal approval process;

[0067] 2. Based on specific hardware devices, a set of localized or platform-based seal verification logic based on smart contracts is proposed, which eliminates the need for manual verification based on verification codes, truly reducing the verification workload and enabling the device to open after local verification.

[0068] In this embodiment, although the above methods are illustrated and described as a series of actions for the sake of simplicity, it should be understood and appreciated that these methods are not limited by the order of the actions, because according to one or more embodiments, some actions may occur in a different order and / or concurrently with other actions from those illustrated and described herein or not illustrated and described herein but which may be understood by those skilled in the art.

[0069] Those skilled in the art will further appreciate that the various illustrative logic blocks, modules, circuits, and algorithm steps described in conjunction with the embodiments disclosed herein can be implemented as electronic hardware, computer software, or a combination of both. To clearly illustrate this interchangeability between hardware and software, the various illustrative components, blocks, modules, circuits, and steps are described above in a generalized manner in terms of their functionality. Whether such functionality is implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system. Those skilled in the art may implement the described functionality in different ways for each specific application, but such implementation decisions should not be construed as departing from the scope of the invention.

[0070] The steps of the methods or algorithms described in conjunction with the embodiments disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of both. The software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium known in the art. An exemplary storage medium is coupled to a processor such that the processor can read and write information to / from the storage medium. In an alternative, the storage medium may be integrated into the processor. The processor and storage medium may reside in an ASIC. The ASIC may reside in a user terminal. In an alternative, the processor and storage medium may reside as discrete components in the user terminal.

[0071] It should be noted that references to "an embodiment," "an embodiment," "an example embodiment," "some embodiments," etc., in the specification indicate that the described embodiments may include specific features, structures, or characteristics, but each embodiment may not necessarily include said specific features, structures, or characteristics. Furthermore, such phrases do not necessarily refer to the same embodiment. Additionally, when a specific feature, structure, or characteristic is described in connection with an embodiment, whether explicitly described or not, implementing such a feature, structure, or characteristic in conjunction with other embodiments will be within the knowledge of those skilled in the art.

[0072] The prior description of this disclosure is provided to enable any person skilled in the art to make or use this disclosure. Various modifications to this disclosure will be apparent to those skilled in the art, and the general principles defined herein may be applied to other variations without departing from the spirit or scope of this disclosure. Therefore, this disclosure is not intended to be limited to the examples and designs described herein, but should be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A multi-seal stamping method based on blockchain smart contracts, characterized in that, include: Receive the key stamping information of the first stamp in the previous node of the stamping process sent by the stamp management platform, and the first hash value of the first stamp sent by the blockchain server. A second hash value is generated based on the received key information about the first seal's stamping. Determine whether the first Hash value and the second Hash value meet the preset rules, and allow the stamping operation if the preset rules are met; The first hash value is generated by the first seal and then uploaded to the blockchain server; The key information for the first seal is generated by the first seal after it is affixed and uploaded to the seal management platform in plain text. When the first hash value is the same as the second hash value, the stamping operation is allowed; The generation of the stamping process includes: After the seal management platform approves the seal-using unit selected by the seal-using applicant, it receives a multi-party seal-using application submitted by the seal-using applicant. The multi-party seal-using application includes the reason for seal-using, the required seal, the multi-seal-using process, and the uploaded seal documents. Based on the multi-party stamping application, a stamping unit is selected to approve the multi-party stamping application, and a stamping process covering multiple seals is generated after the approval is passed.

2. A seal based on a blockchain smart contract, characterized in that, The seal is used to implement the multi-seal stamping method based on blockchain smart contracts as described in claim 1, including: The communication module is used to receive the key stamping information of the first stamp in the previous node of the stamping process sent by the stamp management platform, and to receive the first hash value of the first stamp sent by the blockchain server. The control module is used to generate a second hash value based on the received key information of the first stamp, and to allow or refuse to perform the stamping operation based on the judgment result of whether the first hash value and the second hash value meet the preset rules. The fingerprint module is used to receive fingerprints and perform fingerprint verification operations, and allow the stamping operation after successful verification; The image acquisition module is used to capture images of the stamp and upload them to the stamp management platform; An encryption chip is used to encrypt the first hash value.

3. A seal management system based on blockchain smart contracts, characterized in that, The seal management system is used to execute the multi-seal stamping method based on blockchain smart contracts as described in claim 1, including: The seal management platform is used to generate and store the stamping process, receive the key stamping information sent by the first seal at the previous node of the stamping process, and send the key stamping information to the second seal in response to the query request of the second seal at the next node of the stamping process. The blockchain server receives the first hash value generated from the key stamping information sent by the first stamp at the previous node of the stamping process, and sends the first hash value to the second stamp in response to the query request from the second stamp at the next node of the stamping process.

Images