CN112200569A - Block chain-based digital seal using method and device and electronic equipment - Google Patents
Block chain-based digital seal using method and device and electronic equipment Download PDFInfo
- Publication number
- CN112200569A CN112200569A CN202011075470.6A CN202011075470A CN112200569A CN 112200569 A CN112200569 A CN 112200569A CN 202011075470 A CN202011075470 A CN 202011075470A CN 112200569 A CN112200569 A CN 112200569A
- Authority
- CN
- China
- Prior art keywords
- digital seal
- digital
- seal
- signed
- signature
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims abstract description 96
- 238000012795 verification Methods 0.000 claims abstract description 69
- 238000012545 processing Methods 0.000 claims abstract description 38
- 238000012790 confirmation Methods 0.000 claims description 67
- 210000001503 joint Anatomy 0.000 claims description 31
- 230000004044 response Effects 0.000 claims description 20
- 238000007789 sealing Methods 0.000 claims description 7
- 230000004927 fusion Effects 0.000 claims description 5
- 238000012800 visualization Methods 0.000 claims 4
- 238000010586 diagram Methods 0.000 description 16
- 230000008569 process Effects 0.000 description 16
- 238000005516 engineering process Methods 0.000 description 8
- RTZKZFJDLAIYFH-UHFFFAOYSA-N Diethyl ether Chemical compound CCOCC RTZKZFJDLAIYFH-UHFFFAOYSA-N 0.000 description 6
- 230000008520 organization Effects 0.000 description 6
- 230000006870 function Effects 0.000 description 5
- 230000007246 mechanism Effects 0.000 description 5
- 238000012544 monitoring process Methods 0.000 description 4
- 230000003993 interaction Effects 0.000 description 3
- 238000003058 natural language processing Methods 0.000 description 3
- 230000002085 persistent effect Effects 0.000 description 3
- 238000012546 transfer Methods 0.000 description 3
- 230000009471 action Effects 0.000 description 2
- 230000008859 change Effects 0.000 description 2
- 230000000977 initiatory effect Effects 0.000 description 2
- 238000012015 optical character recognition Methods 0.000 description 2
- OKTJSMMVPCPJKN-UHFFFAOYSA-N Carbon Chemical compound [C] OKTJSMMVPCPJKN-UHFFFAOYSA-N 0.000 description 1
- 241000270295 Serpentes Species 0.000 description 1
- 230000006399 behavior Effects 0.000 description 1
- 230000008901 benefit Effects 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 238000004590 computer program Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 229910021389 graphene Inorganic materials 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 239000003999 initiator Substances 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 239000003607 modifier Substances 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 210000000056 organ Anatomy 0.000 description 1
- 238000004806 packaging method and process Methods 0.000 description 1
- 230000000737 periodic effect Effects 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/38—Payment protocols; Details thereof
- G06Q20/382—Payment protocols; Details thereof insuring higher security of transaction
- G06Q20/3821—Electronic credentials
- G06Q20/38215—Use of certificates or encrypted proofs of transaction rights
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/30—Authentication, i.e. establishing the identity or authorisation of security principals
- G06F21/31—User authentication
- G06F21/33—User authentication using certificates
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/30—Authentication, i.e. establishing the identity or authorisation of security principals
- G06F21/31—User authentication
- G06F21/36—User authentication by graphic or iconic representation
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/60—Protecting data
- G06F21/64—Protecting data integrity, e.g. using checksums, certificates or signatures
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/38—Payment protocols; Details thereof
- G06Q20/382—Payment protocols; Details thereof insuring higher security of transaction
- G06Q20/3829—Payment protocols; Details thereof insuring higher security of transaction involving key management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/38—Payment protocols; Details thereof
- G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
- G06Q20/401—Transaction verification
- G06Q20/4014—Identity check for transactions
Landscapes
- Engineering & Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Business, Economics & Management (AREA)
- Theoretical Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Accounting & Taxation (AREA)
- Physics & Mathematics (AREA)
- Finance (AREA)
- General Business, Economics & Management (AREA)
- Strategic Management (AREA)
- Computer Hardware Design (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Health & Medical Sciences (AREA)
- Bioethics (AREA)
- General Health & Medical Sciences (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
- Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
Abstract
One or more embodiments of the present specification provide a method, an apparatus, and an electronic device for using a digital seal based on a block chain, which are applied to a node device in the block chain; the intelligent contract is deployed in the block chain and used for signing and processing the electronic file; the method comprises the following steps: receiving a digital seal use transaction initiated by a digital seal user; wherein the digital seal usage transaction comprises an electronic document; responding to the transaction of using the digital seal, calling signature verification logic corresponding to an intelligent contract code in an intelligent contract, identifying the file type of the electronic file, and verifying whether the identified file type of the electronic file is matched with the signature type bound with the digital seal; if the identified file type of the electronic file is matched with the signature type bound by the digital seal, signature logic corresponding to an intelligent contract code in an intelligent contract is further called, the digital seal stored in the block chain is obtained, and signature processing is carried out on the electronic file based on the digital seal.
Description
Technical Field
One or more embodiments of the present disclosure relate to the field of blockchain technologies, and in particular, to a method and an apparatus for using a digital seal based on a blockchain, and an electronic device.
Background
The block chain technology, also called distributed ledger technology, is an emerging technology in which several computing devices participate in "accounting" together, and a complete distributed database is maintained together. The blockchain technology has been widely used in many fields due to its characteristics of decentralization, transparency, participation of each computing device in database records, and rapid data synchronization between computing devices.
Disclosure of Invention
The present specification proposes a block chain-based digital seal using method, which is applied to a node device in the block chain; the intelligent contract is deployed in the block chain and used for signing and processing the electronic file; the method comprises the following steps:
receiving a digital seal use transaction initiated by a digital seal user; the digital seal usage transaction comprises an electronic file to be signed;
responding to the digital seal use transaction, calling signature verification logic corresponding to an intelligent contract code in the intelligent contract, identifying the file type of the electronic file to be signed, and verifying whether the identified file type of the electronic file to be signed is matched with the signature type bound to the digital seal;
if the identified file type of the electronic file to be signed is matched with the signature type bound by the digital seal, further calling signature logic corresponding to an intelligent contract code in the intelligent contract, acquiring the digital seal stored in the block chain, and carrying out signature processing on the electronic file to be signed based on the digital seal.
Optionally, the method further comprises:
if the identified file type of the electronic file to be signed is not matched with the signature type bound with the digital seal, generating an illegal use record of the digital seal corresponding to the digital seal;
issuing the illegal use record of the digital seal to the block chain for storing the certificate; or issuing the illegal use record of the digital seal to a judicial chain in cross-chain butt joint with the block chain for evidence storage.
Optionally, the block chain stores a binding relationship between the digital seal and identity information of a legal user of the digital seal; the digital seal use transaction also comprises the identity information of the digital seal user;
before the calling the signature verification logic corresponding to the intelligent contract code in the intelligent contract, identifying the file type of the electronic file to be signed, and verifying whether the identified file type of the electronic file to be signed is matched with the signature type bound to the digital seal, the method further comprises the following steps:
verifying the identity information of the user of the digital seal in the use transaction of the digital seal based on the identity information of the legal user bound with the digital seal stored in the blockchain;
if the verification of the identity information of the digital seal user in the digital seal use transaction is passed, signature verification logic corresponding to an intelligent contract code in the intelligent contract is called, the file type of the electronic file to be signed is identified, and whether the identified file type of the electronic file to be signed is matched with the signature type bound by the digital seal is verified.
Optionally, the method further comprises:
and if the identified file type of the electronic file to be signed is not matched with the signature type bound with the digital seal, generating an illegal use event of the digital seal corresponding to a legal user bound with the digital seal, so that when a client of the legal user acquires the illegal use event of the digital seal, a prompt message indicating that the digital seal is illegally used is output to the legal user in response to the illegal use event of the digital seal.
Optionally, the method further comprises:
if the verification of the identity information of the digital seal user in the digital seal use transaction is not passed, generating an illegal use record of the digital seal corresponding to the identity information of the digital seal user;
issuing the illegal use record of the digital seal to the block chain for storing the certificate; or issuing the illegal use record of the digital seal to a judicial chain in cross-chain butt joint with the block chain for evidence storage.
Optionally, the identity information includes a public key in a CA certificate held by a legitimate user of the digital stamp.
Optionally, the identity information further comprises a combination of one or more of the following:
the identity of a legal user of the digital seal;
a blockchain account identifier of a legal user of the digital seal;
image information of a physical seal held by a legitimate user of the digital seal.
Optionally, the legal user is a claimant of the digital seal.
Optionally, before the further invoking of a signing logic corresponding to an intelligent contract code in the intelligent contract, acquiring the digital seal stored in the block chain, and performing signing processing on the electronic file to be signed based on the digital seal, the method further includes:
calling use confirmation logic corresponding to the intelligent contract codes in the intelligent contract, indicating a claiming party of the digital seal to carry out use confirmation on the digital seal, further calling signature logic corresponding to the intelligent contract codes in the intelligent contract after obtaining a use confirmation result of the claiming party on the digital seal, obtaining the digital seal stored in the block chain, and carrying out signature processing on the electronic file to be signed based on the digital seal.
Optionally, the instructing the claiming policy of the digital stamp to confirm the use of the digital stamp includes:
and generating a use confirmation event corresponding to a claiming party of the digital seal, so that the claiming party responds to the use confirmation event to perform use confirmation on the digital seal when acquiring the use confirmation event.
Optionally, the block chain stores a corresponding relationship between the identifier of the digital seal and the signature type of the digital seal; the digital seal usage transaction also comprises an identification of the digital seal;
the verifying whether the identified file type of the electronic file to be signed is matched with the signature type bound with the digital seal or not comprises the following steps:
determining a signature type corresponding to the identifier of the digital seal in the transaction of using the digital seal based on the corresponding relation of the certificate stored in the block chain, and verifying whether the identified file type of the electronic file to be signed is matched with the signature type corresponding to the identifier of the digital seal;
the acquiring the digital seal stored in the block chain includes:
and acquiring the digital seal stored in the block chain and corresponding to the identification of the digital seal in the digital seal use transaction.
Optionally, the method further comprises:
after the electronic file to be signed is signed based on the acquired digital seal, generating a signature record corresponding to the digital seal;
issuing the generated signature record to the block chain for storing the certificate; or issuing the generated signature record to a judicial chain in cross-chain butt joint with the block chain for evidence storage.
Optionally, the digital seal user is an enterprise; the digital seal is a official seal of the enterprise.
Optionally, the digital stamp includes a pattern image of the digital stamp;
the signing and sealing processing of the electronic file to be signed and sealed based on the digital seal comprises the following steps:
identifying a signature position in the electronic file to be signed;
adding the pattern image of the digital seal to the signature position, and carrying out image fusion with the electronic file to be signed.
Optionally, the style image of the digital stamp visually fuses identity information of a claimant of the digital stamp.
The specification also provides a block chain-based digital seal using method, which is applied to a Baas platform in butt joint with node equipment in the block chain; the intelligent contract is deployed in the block chain and used for signing and processing the electronic file; the method comprises the following steps:
receiving a digital seal use request initiated by a digital seal user; the digital seal using request comprises an electronic file to be signed;
responding to the digital seal use request, identifying the file type of the electronic file to be signed, and checking whether the identified file type of the electronic file to be signed is matched with the signature type bound by the digital seal;
and if the identified file type of the electronic file to be signed is matched with the signature type bound with the digital seal, sending an intelligent contract calling transaction to the node equipment, so that the node equipment responds to the intelligent contract calling transaction, calling signature logic corresponding to an intelligent contract code in the intelligent contract, acquiring the digital seal stored in the block chain, and signing the electronic file to be signed based on the digital seal.
Optionally, the method further comprises:
if the identified file type of the electronic file to be signed is not matched with the signature type bound with the digital seal, generating an illegal use record of the digital seal corresponding to the digital seal;
issuing the illegal use record of the digital seal to the block chain for storing the certificate; or issuing the illegal use record of the digital seal to a judicial chain in cross-chain butt joint with the block chain for evidence storage.
Optionally, the block chain stores a binding relationship between the digital seal and identity information of a legal user of the digital seal; the digital seal use request also comprises the identity information of the digital seal user;
before the identifying the file type of the electronic file to be signed and verifying whether the identified file type of the electronic file to be signed is matched with the signature type bound to the digital seal, the method further comprises the following steps:
verifying the identity information of the user of the digital seal in the digital seal use request based on the identity information of the legal user bound with the digital seal stored in the block chain;
and if the verification of the identity information of the digital seal user in the digital seal using request passes, identifying the file type of the electronic file to be signed, and verifying whether the identified file type of the electronic file to be signed is matched with the signature type bound with the digital seal.
Optionally, the method further comprises:
if the identified file type of the electronic file to be signed is not matched with the signature type bound with the digital seal, sending an illegal use message of the digital seal to a legal user bound with the digital seal, so that when a client of the legal user obtains the illegal use message of the digital seal, the client responds to the illegal use message of the digital seal to output prompt information indicating that the digital seal is illegally used to the legal user.
Optionally, the method further comprises:
if the verification of the identity information of the digital seal user in the digital seal use transaction is not passed, generating an illegal use record of the digital seal corresponding to the identity information of the digital seal user;
issuing the illegal use record of the digital seal to the block chain for storing the certificate; or issuing the illegal use record of the digital seal to a judicial chain in cross-chain butt joint with the block chain for evidence storage.
Optionally, the identity information includes a public key in a CA certificate held by a legitimate user of the digital stamp.
Optionally, the identity information further comprises a combination of one or more of the following:
the identity of a legal user of the digital seal;
a blockchain account identifier of a legal user of the digital seal;
image information of a physical seal held by a legitimate user of the digital seal.
Optionally, the legal user is a claimant of the digital seal.
Optionally, before sending the smart contract invocation transaction to the node device, the method further includes:
and indicating the claiming policy of the digital seal to confirm the use of the digital seal, and sending an intelligent contract calling transaction to the node equipment after obtaining the use confirmation result of the claiming policy on the digital seal.
Optionally, the instructing the claiming policy of the digital stamp to confirm the use of the digital stamp includes:
and sending an approval indicating message to the claimant so that the claimant can confirm the use of the digital seal in response to the approval indicating message.
Optionally, the block chain stores a corresponding relationship between the identifier of the digital seal and the signature type of the digital seal; the digital seal usage transaction also comprises an identification of the digital seal;
the verifying whether the identified file type of the electronic file to be signed is matched with the signature type bound with the digital seal or not comprises the following steps:
and determining a signature type corresponding to the identifier of the digital seal in the digital seal use transaction based on the corresponding relation of the certificate stored in the block chain, and verifying whether the identified file type of the electronic file to be signed is matched with the signature type corresponding to the identifier of the digital seal.
Optionally, the digital seal user is an enterprise; the digital seal is a official seal of the enterprise.
Optionally, the digital stamp includes a pattern image of the digital stamp.
Optionally, the pattern image of the digital stamp visually fuses identity information of the digital stamp claiming party.
The present specification also provides a block chain-based digital seal using apparatus, which is applied to a node device in the block chain; the intelligent contract is deployed in the block chain and used for signing and processing the electronic file; the device comprises:
the receiving module is used for receiving a digital seal using transaction initiated by a digital seal using party; the digital seal usage transaction comprises an electronic file to be signed;
the verification module is used for responding to the digital seal use transaction, calling signature verification logic corresponding to the intelligent contract code in the intelligent contract, identifying the file type of the electronic file to be signed, and verifying whether the identified file type of the electronic file to be signed is matched with the signature type bound by the digital seal;
and the signature module is used for further calling signature logic corresponding to an intelligent contract code in the intelligent contract to acquire the digital seal stored in the block chain and performing signature processing on the electronic file to be signed based on the digital seal if the identified file type of the electronic file to be signed is matched with the signature type bound by the digital seal.
Optionally, the apparatus further comprises:
the first generation module generates an illegal use record of the digital seal corresponding to the digital seal if the identified file type of the electronic file to be signed is not matched with the signature type bound by the digital seal;
the first evidence storage module is used for issuing the illegal use record of the digital seal to the block chain for evidence storage; or issuing the illegal use record of the digital seal to a judicial chain in cross-chain butt joint with the block chain for evidence storage.
Optionally, the block chain stores a binding relationship between the digital seal and identity information of a legal user of the digital seal; the digital seal use transaction also comprises the identity information of the digital seal user;
the device further comprises:
the verification module is used for verifying the identity information of the digital seal user in the digital seal use transaction based on the identity information of the legal user bound with the digital seal stored in the block chain and verified before calling signature verification logic corresponding to an intelligent contract code in the intelligent contract, identifying the file type of the electronic file to be signed and verifying whether the identified file type of the electronic file to be signed is matched with the signature type bound with the digital seal;
the checking module:
if the verification of the identity information of the digital seal user in the digital seal use transaction is passed, signature verification logic corresponding to an intelligent contract code in the intelligent contract is called, the file type of the electronic file to be signed is identified, and whether the identified file type of the electronic file to be signed is matched with the signature type bound by the digital seal is verified.
Optionally, the apparatus further comprises:
and the prompting module is used for generating a digital seal illegal use event corresponding to a legal user bound with the digital seal if the identified file type of the electronic file to be signed is not matched with the signature type bound with the digital seal, so that when a client of the legal user acquires the digital seal illegal use event, a prompting message indicating that the digital seal is illegally used is output to the legal user in response to the digital seal illegal use event.
Optionally, the apparatus further comprises:
the second generation module generates an illegal use record of the digital seal corresponding to the identity information of the digital seal user if the verification of the identity information of the digital seal user in the use transaction of the digital seal is not passed;
the second evidence storage module is used for issuing the illegal use record of the digital seal to the block chain for evidence storage; or issuing the illegal use record of the digital seal to a judicial chain in cross-chain butt joint with the block chain for evidence storage.
Optionally, the identity information includes a public key in a CA certificate held by a legitimate user of the digital stamp.
Optionally, the identity information further comprises a combination of one or more of the following:
the identity of a legal user of the digital seal;
a blockchain account identifier of a legal user of the digital seal;
image information of a physical seal held by a legitimate user of the digital seal.
Optionally, the legal user is a claimant of the digital seal.
Optionally, the apparatus further comprises:
the confirming module is used for calling signing logic corresponding to an intelligent contract code in the intelligent contract to obtain the digital seal stored in the block chain, calling the use confirming logic corresponding to the intelligent contract code in the intelligent contract before signing the electronic file to be signed based on the digital seal, indicating a claiming party of the digital seal to carry out use confirmation on the digital seal, further calling the signing logic corresponding to the intelligent contract code in the intelligent contract after obtaining a use confirming result of the claiming party on the digital seal, obtaining the digital seal stored in the block chain, and signing the electronic file to be signed based on the digital seal.
Optionally, the confirmation module:
and generating a use confirmation event corresponding to a claiming party of the digital seal, so that the claiming party responds to the use confirmation event to perform use confirmation on the digital seal when acquiring the use confirmation event.
Optionally, the block chain stores a corresponding relationship between the identifier of the digital seal and the signature type of the digital seal; the digital seal usage transaction also comprises an identification of the digital seal;
the checking module:
determining a signature type corresponding to the identifier of the digital seal in the transaction of using the digital seal based on the corresponding relation of the certificate stored in the block chain, and verifying whether the identified file type of the electronic file to be signed is matched with the signature type corresponding to the identifier of the digital seal;
the signature module is:
and acquiring the digital seal stored in the block chain and corresponding to the identification of the digital seal in the digital seal use transaction.
Optionally, the apparatus further comprises:
the third generation module generates a signature record corresponding to the digital seal after the electronic file to be signed is signed based on the acquired digital seal;
the third certificate storing module is used for issuing the generated signature record to the block chain for certificate storage; or issuing the generated signature record to a judicial chain in cross-chain butt joint with the block chain for evidence storage.
Optionally, the digital seal user is an enterprise; the digital seal is a official seal of the enterprise.
Optionally, the digital stamp includes a pattern image of the digital stamp;
the signing and sealing processing of the electronic file to be signed and sealed based on the digital seal comprises the following steps:
identifying a signature position in the electronic file to be signed;
adding the pattern image of the digital seal to the signature position, and carrying out image fusion with the electronic file to be signed.
Optionally, the style image of the digital stamp visually fuses identity information of a claimant of the digital stamp.
The present specification also provides a block chain-based digital seal using apparatus, which is applied to a Baas platform in butt joint with node devices in the block chain; the intelligent contract is deployed in the block chain and used for signing and processing the electronic file; the device comprises:
the receiving module is used for receiving a digital seal using request initiated by a digital seal using party; the digital seal using request comprises an electronic file to be signed;
the verification module responds to the digital seal use request, identifies the file type of the electronic file to be signed and verifies whether the identified file type of the electronic file to be signed is matched with the signature type bound with the digital seal or not;
and the signature module is used for sending an intelligent contract calling transaction to the node equipment if the identified file type of the electronic file to be signed is matched with the signature type bound by the digital seal, so that the node equipment responds to the intelligent contract calling transaction, calls signature logic corresponding to an intelligent contract code in the intelligent contract, acquires the digital seal stored in the block chain, and carries out signature processing on the electronic file to be signed based on the digital seal.
Optionally, the apparatus further comprises:
the first generation module generates an illegal use record of the digital seal corresponding to the digital seal if the identified file type of the electronic file to be signed is not matched with the signature type bound by the digital seal;
the first evidence storage module is used for issuing the illegal use record of the digital seal to the block chain for evidence storage; or issuing the illegal use record of the digital seal to a judicial chain in cross-chain butt joint with the block chain for evidence storage.
Optionally, the block chain stores a binding relationship between the digital seal and identity information of a legal user of the digital seal; the digital seal use request also comprises the identity information of the digital seal user;
the device further comprises:
the verification module is used for verifying the identity information of the digital seal user in the digital seal use request based on the identity information of the legal user bound with the digital seal stored in the block chain before identifying the file type of the electronic file to be signed and verifying whether the identified file type of the electronic file to be signed is matched with the signature type bound with the digital seal;
the checking module:
and if the verification of the identity information of the digital seal user in the digital seal using request passes, identifying the file type of the electronic file to be signed, and verifying whether the identified file type of the electronic file to be signed is matched with the signature type bound with the digital seal.
Optionally, the apparatus further comprises:
and the prompting module is used for sending an illegal digital seal use message to a legal user bound with the digital seal if the identified file type of the electronic file to be signed is not matched with the signature type bound with the digital seal, so that when the client of the legal user obtains the illegal digital seal use message, the prompting module responds to the illegal digital seal use message and outputs prompting information indicating that the digital seal is illegally used to the legal user.
Optionally, the apparatus further comprises:
the second generation module generates an illegal use record of the digital seal corresponding to the identity information of the digital seal user if the verification of the identity information of the digital seal user in the use transaction of the digital seal is not passed;
the second evidence storage module is used for issuing the illegal use record of the digital seal to the block chain for evidence storage; or issuing the illegal use record of the digital seal to a judicial chain in cross-chain butt joint with the block chain for evidence storage.
Optionally, the identity information includes a public key in a CA certificate held by a legitimate user of the digital stamp.
Optionally, the identity information further comprises a combination of one or more of the following:
the identity of a legal user of the digital seal;
a blockchain account identifier of a legal user of the digital seal;
image information of a physical seal held by a legitimate user of the digital seal.
Optionally, the legal user is a claimant of the digital seal.
Optionally, the apparatus further comprises:
and the confirmation module indicates the claiming party of the digital seal to confirm the use of the digital seal before sending the intelligent contract calling transaction to the node equipment, and sends the intelligent contract calling transaction to the node equipment after obtaining the use confirmation result of the claiming party on the digital seal.
Optionally, the confirmation module:
and sending an approval indicating message to the claimant so that the claimant can confirm the use of the digital seal in response to the approval indicating message.
Optionally, the block chain stores a corresponding relationship between the identifier of the digital seal and the signature type of the digital seal; the digital seal usage transaction also comprises an identification of the digital seal;
the checking module:
and determining a signature type corresponding to the identifier of the digital seal in the digital seal use transaction based on the corresponding relation of the certificate stored in the block chain, and verifying whether the identified file type of the electronic file to be signed is matched with the signature type corresponding to the identifier of the digital seal.
Optionally, the digital seal user is an enterprise; the digital seal is a official seal of the enterprise.
Optionally, the digital stamp includes a pattern image of the digital stamp.
Optionally, the pattern image of the digital stamp visually fuses identity information of the digital stamp claiming party.
This specification also proposes an electronic device including:
a processor;
a memory for storing processor-executable instructions;
wherein the processor implements the steps of any of the above methods by executing the executable instructions.
The present specification also contemplates a computer-readable storage medium having stored thereon computer instructions which, when executed by a processor, implement the steps of any of the methods described above.
In the technical scheme, the file type of the electronic file to be signed can be automatically identified, and when the file type of the electronic file to be signed is determined to be matched with the signature type bound with the digital seal required by a digital seal user, the digital seal is allowed to be used for signing the electronic file to be signed, so that the use safety and reliability of the digital seal can be ensured.
Drawings
FIG. 1 is a schematic diagram of a creation flow of an intelligent contract shown herein;
FIG. 2 is a schematic diagram illustrating the call flow of an intelligent contract shown in this specification;
FIG. 3 is a schematic diagram of the creation and invocation flow of an intelligent contract shown in the present specification;
FIG. 4 is a schematic diagram of a blockchain-based digital stamp using system shown in an exemplary embodiment of the present description;
FIG. 5 is a flow chart illustrating a method for using a blockchain-based digital stamp in accordance with an exemplary embodiment of the present description;
FIG. 6 is a diagram illustrating a type binding interface in accordance with an exemplary embodiment of the present description;
FIG. 7 is a schematic view of a pattern image of a digital stamp shown in an exemplary embodiment of the present description;
FIG. 8 is a schematic diagram illustrating a use registration interface in accordance with an exemplary embodiment of the present description;
FIG. 9 is a schematic diagram of another block chain based digital stamp using system shown in an exemplary embodiment of the present description;
FIG. 10 is a flow chart illustrating another method of using a blockchain-based digital stamp in accordance with an exemplary embodiment of the present description;
FIG. 11 is a diagram illustrating a hardware configuration of an electronic device in accordance with an exemplary embodiment of the present disclosure;
FIG. 12 is a block diagram of a block chain based digital stamp using apparatus shown in an exemplary embodiment of the present specification;
FIG. 13 is a block diagram of another block chain based digital stamp using apparatus, according to an exemplary embodiment of the present specification.
Detailed Description
Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The implementations described in the following exemplary embodiments do not represent all implementations consistent with one or more embodiments of the present specification. Rather, they are merely examples of apparatus and methods consistent with certain aspects of one or more embodiments of the specification, as detailed in the claims which follow.
It should be noted that: in other embodiments, the steps of the corresponding methods are not necessarily performed in the order shown and described herein. In some other embodiments, the method may include more or fewer steps than those described herein. Moreover, a single step described in this specification may be broken down into multiple steps for description in other embodiments; multiple steps described in this specification may be combined into a single step in other embodiments.
Blockchains are generally divided into three types: public chain (Public Blockchain), Private chain (Private Blockchain) and alliance chain (Consortium Blockchain). Furthermore, there may be a combination of the above types, such as private chain + federation chain, federation chain + public chain, and so on.
Among them, the most decentralized is the public chain. The public chain is represented by bitcoin and ether house, and participants (also called nodes in the block chain) joining the public chain can read data records on the chain, participate in transactions, compete for accounting rights of new blocks, and the like. Moreover, each node can freely join or leave the network and perform related operations.
Private chains are the opposite, with the network's write rights controlled by an organization or organization and the data read rights specified by the organization. Briefly, a private chain may be a weakly centralized system with strict restrictions on nodes and a small number of nodes. This type of blockchain is more suitable for use within a particular establishment.
A federation chain is a block chain between a public chain and a private chain, and "partial decentralization" can be achieved. Each node in a federation chain typically has a physical organization or organization corresponding to it; the nodes are authorized to join the network and form a benefit-related alliance, and block chain operation is maintained together.
Based on the basic characteristics of a blockchain, a blockchain is usually composed of several blocks. The time stamps corresponding to the creation time of the block are recorded in the blocks respectively, and all the blocks form a time-ordered data chain according to the time stamps recorded in the blocks strictly.
The real data generated by the physical world can be constructed into a standard transaction (transaction) format supported by a block chain, then is issued to the block chain, the node equipment in the block chain performs consensus processing on the received transaction, and after the consensus is achieved, the node equipment serving as an accounting node in the block chain packs the transaction into a block and performs persistent evidence storage in the block chain.
The consensus algorithm supported in the blockchain may include:
the first kind of consensus algorithm, namely the consensus algorithm that the node device needs to contend for the accounting right of each round of accounting period; consensus algorithms such as Proof of Work (POW), Proof of equity (POS), Proof of commission rights (DPOS), etc.;
the second kind of consensus algorithm, namely the consensus algorithm which elects accounting nodes in advance for each accounting period (without competing for accounting right); for example, a consensus algorithm such as a Practical Byzantine Fault Tolerance (PBFT) is used.
In a blockchain network employing a first type of consensus algorithm, node devices competing for billing rights can execute a transaction upon receipt. One of the node devices competing for the accounting right may win in the process of competing for the accounting right in the current round, and become an accounting node. The accounting node may package the received transaction with other transactions to generate a latest block and send the generated latest block or a block header of the latest block to other node devices for consensus.
In the block chain network adopting the second type of consensus algorithm, the node equipment with the accounting right is agreed before accounting in the current round. Thus, the node device, after receiving the transaction, may send the transaction to the accounting node if it is not the accounting node of its own round. For the accounting node of the current round, the transaction may be performed during or before packaging the transaction with other transactions to generate the latest block. After generating the latest block, the accounting node may send the latest block or a block header of the latest block to other node devices for consensus.
As described above, regardless of which consensus algorithm is used by the blockchain, the accounting node of the current round may pack the received transaction to generate the latest block, and send the generated latest block or the block header of the latest block to other node devices for consensus verification. If no problem is verified after other node equipment receives the latest block or the block header of the latest block, the latest block can be added to the tail of the original block chain, so that the accounting process of the block chain is completed. The transaction contained in the block may also be performed by other nodes in verifying the new block or block header sent by the accounting node.
In the field of blockchain, an important concept is account (account); taking an ether house as an example, the ether house generally divides an account into an external account and a contract account; the external account is an account directly controlled by the user and is also called as a user account; and the contract account is created by the user through an external account, the account containing the contract code (i.e. the smart contract). Of course, for some blockchain items derived from the ethernet-based architecture (such as ant blockchains), the account types supported by the blockchain may be further expanded, and are not particularly limited in this specification.
For accounts in a blockchain, the account status of the account is usually maintained through a structure. When a transaction in a block is executed, the status of the account associated with the transaction in the block chain is also typically changed.
Taking etherhouses as an example, the structure of an account usually includes fields such as Balance, Nonce, Code and Storage. Wherein:
a Balance field for maintaining the current account Balance of the account;
a Nonce field for maintaining a number of transactions for the account; the counter is used for guaranteeing that each transaction can be processed only once, and replay attack is effectively avoided;
a Code field for maintaining a contract Code for the account; in practical applications, only the hash value of the contract Code is typically maintained in the Code field; thus, the Code field is also commonly referred to as the Codhash field.
A Storage field for maintaining the Storage contents of the account (default field value is null); for a contract account, a separate storage space is usually allocated to store the storage content of the contract account; this separate storage space is often referred to as the account storage of the contract account. The storage content of the contract account is usually constructed into a data structure of an MPT (Merkle Patricia Trie) tree and stored in the independent storage space; in which, the Storage content based on the contract account is constructed into an MPT tree, which is also commonly referred to as a Storage tree. Whereas the Storage field typically maintains only the root node of the Storage tree; thus, the Storage field is also commonly referred to as the Storage root field.
Wherein, for the external account, the field values of the Code field and the Storage field shown above are both null values.
For most blockchain items, a Merkle tree is typically used; alternatively, the data is stored and maintained based on the data structure of the Merkle tree. Taking etherhouses as an example, the etherhouses use MPT tree (a Merkle tree variation) as a data organization form for organizing and managing important data such as account status, transaction information, and the like.
The Etherhouse designs three MPT trees, namely an MPT state tree, an MPT transaction tree and an MPT receipt tree, aiming at data needing to be stored and maintained in a block chain. In addition to the above three MPT trees, there is actually a Storage tree constructed based on the Storage content of the contract account.
An MPT state tree, which is an MPT tree organized by account state data of all accounts in a blockchain; an MPT transaction tree, which is an MPT tree organized by transaction (transaction) data in a blockchain; the MPT receipt tree is organized into transaction (receipt) receipts corresponding to each transaction generated after the transactions in the block are executed. The hash values of the root nodes of the MPT state tree, the MPT transaction tree, and the MPT receipt tree shown above are eventually added to the block header of the corresponding block.
The MPT transaction tree and the MPT receipt tree correspond to the blocks, namely each block has the MPT transaction tree and the MPT receipt tree. The MPT state tree is a global MPT tree, which does not correspond to a specific tile, but covers account state data of all accounts in the tile chain.
It should be noted that, each time a latest block is generated in the blockchain, after a transaction in the latest block is executed, the account status of the accounts (which may be an external account or a contract account) related to the executed transaction in the blockchain is usually changed;
for example, when a "transfer transaction" is completed in a block, the balances of the transferring party account and the transferring party account associated with the "transfer transaction" (i.e., the field values of the Balance fields of these accounts) are usually changed.
After the transaction in the latest block generated by the blockchain is completed, the node device needs to construct an MPT state tree according to the current account state data of all accounts in the blockchain because the account state in the current blockchain changes, so as to maintain the latest state of all accounts in the blockchain.
That is, each time a latest block is generated in the block chain and the account status in the block chain changes after the transaction in the latest block is completed, the node device needs to reconstruct an MPT status tree based on the latest account status data of all accounts in the block chain. In other words, each block in the block chain has a corresponding MPT state tree; the MPT status tree maintains the latest account status of all accounts in the blockchain after the transaction in the block is completed.
In practical applications, whether public, private, or alliance, it is possible to provide the functionality of a smart contract (smart contract). An intelligent contract on a blockchain is a contract on a blockchain that can be executed triggered by a transaction. An intelligent contract may be defined in the form of code.
Taking an Etherhouse as an example, a user is supported to create and call some complex logic in the Etherhouse network. The ethernet workshop is used as a programmable block chain, and the core of the ethernet workshop is an ethernet workshop virtual machine (EVM), and each ethernet workshop node can run the EVM. The EVM is a well-behaved virtual machine through which various complex logic can be implemented. The user issuing and invoking smart contracts in the etherhouse is running on the EVM. In fact, the EVM directly runs virtual machine code (virtual machine bytecode, hereinafter referred to as "bytecode"), so the intelligent contract deployed on the blockchain may be bytecode.
After Bob sends a transaction (transaction) containing information to create a smart contract to the ethernet network, each node may perform the transaction in the EVM, as shown in fig. 1. In fig. 1, the From field of the transaction is used To record the address of the account initiating the creation of the intelligent contract, the contract code stored in the field value of the Data field of the transaction may be byte code, and the field value of the To field of the transaction is a null account. After the nodes reach the agreement through the consensus mechanism, the intelligent contract is successfully created, and the follow-up user can call the intelligent contract.
After the intelligent contract is established, a contract account corresponding to the intelligent contract appears on the block chain, and the block chain has a specific address; for example, "0 x68e12cf284 …" in each node in fig. 1 represents the address of the contract account created; the contract Code (Code) and account store (Storage) will be maintained in the account store for that contract account. The behavior of the intelligent contract is controlled by the contract code, while the account storage of the intelligent contract preserves the state of the contract. In other words, the intelligent contract causes a virtual account to be generated on the blockchain that contains the contract code and account storage.
As mentioned above, the Data field containing the transaction that created the intelligent contract may hold the byte code of the intelligent contract. A bytecode consists of a series of bytes, each of which can identify an operation. Based on the multiple considerations of development efficiency, readability and the like, a developer can select a high-level language to write intelligent contract codes instead of directly writing byte codes. For example, the high-level language may employ a language such as Solidity, Serpent, LLL, and the like. For intelligent contract code written in a high-level language, the intelligent contract code can be compiled by a compiler to generate byte codes which can be deployed on a blockchain.
Taking the Solidity language as an example, the contract code written by it is very similar to a Class (Class) in the object-oriented programming language, and various members including state variables, functions, function modifiers, events, etc. can be declared in one contract. A state variable is a value permanently stored in an account Storage (Storage) field of an intelligent contract to save the state of the contract.
As shown in FIG. 2, still taking the Etherhouse as an example, after Bob sends a transaction containing the information of the calling intelligent contract to the Etherhouse network, each node can execute the transaction in the EVM. In fig. 2, the From field of the transaction is used To record the address of the account initiating the intelligent contract invocation, the To field is used To record the address of the intelligent contract invocation, and the Data field of the transaction is used To record the method and parameters of the intelligent contract invocation. After invoking the smart contract, the account status of the contract account may change. Subsequently, a client may view the account status of the contract account through the accessed block link point (e.g., node 1 in fig. 2).
The intelligent contract can be independently executed at each node in the blockchain network in a specified mode, and all execution records and data are stored on the blockchain, so that after the transaction is executed, transaction certificates which cannot be tampered and lost are stored on the blockchain.
A schematic diagram of creating an intelligent contract and invoking the intelligent contract is shown in fig. 3. An intelligent contract is created in an Ethernet workshop and needs to be subjected to the processes of compiling the intelligent contract, changing the intelligent contract into byte codes, deploying the intelligent contract to a block chain and the like. The intelligent contract is called in the Ethernet workshop, a transaction pointing to the intelligent contract address is initiated, the EVM of each node can respectively execute the transaction, and the intelligent contract code is distributed and operated in the virtual machine of each node in the Ethernet workshop network.
The event mechanism of the intelligent contract is a mode for the interaction between the intelligent contract and the out-of-chain entity. For intelligent contracts deployed on blockchains, direct interaction with out-of-chain entities is generally not possible; for example, the intelligent contract cannot generally send the call result of the intelligent contract to the call initiator of the intelligent contract point to point after the call is completed.
The call results (including intermediate results and final call results) generated by the intelligent contract in the call process are usually recorded in the form of events (events) to the transaction log (transaction logs) of the transaction that called the intelligent contract, and stored in the storage space of the node device. The entity outside the chain which needs to interact with the intelligent contract can acquire the calling result of the intelligent contract by monitoring the transaction log stored in the storage space of the node equipment;
for example, in the case of an Etherhouse, the transaction log will eventually be stored in the MPT receipt tree described above as part of the receipt (receipt) of the transaction pen transaction that invoked the smart contract. And the entity outside the chain interacting with the intelligent contract can monitor the transaction receipts stored in the storage space of the node device on the MPT receipt tree and acquire the events generated by the intelligent contract from the monitored transaction receipts.
The intelligent contracts deployed on the blockchains can only reference data contents stored on the blockchains generally; in practical applications, for some complex business scenarios implemented based on the intelligent contract technology, the intelligent contract may need to refer to some external data on the data entities outside the chain.
In this scenario, the intelligent contract deployed on the blockchain may refer to data on the data entities outside the chain through the Oracle prediction machine, thereby implementing data interaction between the intelligent contract and the data entities in the real world. Data entities outside the chain may include, for example, centralized servers or data centers deployed outside the chain, and so on.
It should be noted that the cross-link relay is used to connect two block chains, and the Oracle.
In practical application, when a predicting machine is deployed for an intelligent contract on a block chain, a predicting machine intelligent contract corresponding to the predicting machine can be deployed on the block chain; the intelligent contract of the prediction machine is used for maintaining external data sent to the intelligent contract on the block chain by the prediction machine; for example, external data sent by the predictive machine to the smart contract on the blockchain may be stored in the account storage space of the predictive machine smart contract.
When a target intelligent contract on the blockchain is called, external data required by the target intelligent contract can be read from the account storage space of the prediction machine intelligent contract to complete the calling process of the intelligent contract.
It should be noted that, when sending external data to the smart contract on the blockchain, the prediction engine may use an active sending method or a passive sending method.
In one implementation, the data entity outside the chain may send external data to be provided to the target intelligent contract to the intelligent contract of the language prediction machine after signing by using the private key of the language prediction machine; for example, in time, the signed external data may be sent to the intelligent contract of the prediction machine in a periodic sending manner;
the intelligent contract of the language predicting machine can maintain a CA (certificate authority) certificate of the language predicting machine, after external data sent by a data entity outside a chain is received, a signature of the external data can be verified by using a public key of the language predicting machine maintained in the CA certificate, and after the signature passes, the external data sent by the data entity outside the chain is stored in an account storage space of the intelligent contract of the language predicting machine.
In another implementation, when a target intelligent contract on a blockchain is called, if external data required by the target intelligent contract is not read from an account storage space of the intelligent contract of the language predictive controller, the intelligent contract of the language predictive controller may interact with the language predictive controller by using an event mechanism of the intelligent contract, and the language predictive controller sends the external data required by the target intelligent contract to the account storage space of the intelligent contract of the language predictive controller.
For example, when a target intelligent contract on a blockchain is called, if external data required by the target intelligent contract is not read from an account storage space of the intelligent contract of the language predictive machine, the intelligent contract of the language predictive machine can generate an external data acquisition event, record the external data acquisition event into a transaction log of the transaction calling the intelligent contract, and store the transaction log into a storage space of a node device; the predicting machine can monitor a transaction log generated by the predicting machine intelligent contract stored in the storage space of the node equipment, respond to the monitored external data acquisition event after monitoring the external data acquisition event in the transaction log, and send the external data required by the target intelligent contract to the predicting machine intelligent contract.
Referring to fig. 4, fig. 4 is a schematic diagram of a block chain-based digital stamp using system according to an exemplary embodiment of the present disclosure.
In a blockchain-based digital stamp usage system as shown in fig. 4, a smart contract may be deployed on the blockchain. Wherein, the intelligent contract can comprise an intelligent contract code used for signing and sealing the electronic file; in particular, the intelligent contract code of the intelligent contract may include intelligent contract code corresponding to signature checking logic, intelligent contract code corresponding to signature logic, and so on. In practical application, by executing the intelligent contract code corresponding to the signature verification logic in the intelligent contract, the signature verification logic can be realized, and the signature verification is carried out on the electronic file to be signed and the digital seal; by executing the intelligent contract codes corresponding to the signature logic in the intelligent contract, the signature logic can be realized, and the signature processing is carried out on the electronic file to be signed based on the digital seal.
It should be noted that, for a specific process of creating and invoking an intelligent contract, reference may be made to the foregoing process of creating and invoking an intelligent contract, which is not described herein again.
In a specific implementation, a user may initiate a transaction for invoking the intelligent contract deployed on the blockchain through a client that establishes a connection with a node device in the blockchain. When the node device in the blockchain receives the transaction, the transaction can be sent to other node devices in the blockchain to perform consensus processing on the transaction, and after the transaction consensus passes, the intelligent contract code in the intelligent contract is executed to realize signature processing on the electronic file.
In practical applications, the client may be deployed on an electronic device, where the electronic device may be a server, a computer, a mobile phone, a tablet device, a notebook computer, a Personal Digital assistant (pda), or the like; similarly, the electronic device added to the block chain as a node device may also be a server, a computer, a mobile phone, a tablet device, a notebook computer, a palm computer, or the like; this is not limited by the present description.
Referring to fig. 5, fig. 5 is a flowchart illustrating a block chain-based digital stamp using method according to an exemplary embodiment of the present disclosure.
In combination with the block chain-based digital seal using system shown in fig. 4, the block chain-based digital seal using method can be applied to the node device in the block chain shown in fig. 4; the block chain-based digital seal using method can comprise the following steps:
In this embodiment, an intelligent contract may be deployed on the blockchain. A user (called a digital seal user) needing to use a digital seal can initiate a transaction (called a digital seal use transaction) for calling the intelligent contract deployed on the blockchain through a client connected with the node equipment in the blockchain; the digital seal usage transaction may include an electronic document to be signed.
In this embodiment, the node device in the block chain may respond to a digital seal usage transaction, call a signature verification logic corresponding to an intelligent contract code in the intelligent contract, namely execute the intelligent contract code corresponding to the signature verification logic in the intelligent contract, identify a file type of an electronic file to be signed in the digital seal usage transaction, and verify whether the identified file type of the electronic file to be signed matches a signature type bound to a digital seal that needs to be used by a user of the digital seal.
Specifically, referring to the aforementioned process of persisting the evidence storing data in the blockchain, the client may construct a digital seal usage transaction for invoking the intelligent contract deployed on the blockchain, and issue the digital seal usage transaction to the blockchain for evidence storing. That is, the node device in the blockchain that is docked with the client may receive the digital seal usage transaction first, and then send the digital seal usage transaction to other node devices in the blockchain. When each node device in the block chain receives the digital seal use transaction, the common identification processing can be carried out on the digital seal use transaction. After agreement is reached, a node device in the blockchain can package digital seal usage transactions into blocks in which persistent verifications are made.
For the digital seal usage transaction packaged into the block, the node device in the block chain can respond to the digital seal usage transaction, execute the intelligent contract code corresponding to the signature verification logic in the intelligent contract, identify the file type of the electronic file to be signed in the digital seal usage transaction, and verify whether the identified file type of the electronic file to be signed is matched with the signature type bound with the digital seal required by the digital seal user.
In practical application, the digital seal user may specifically represent a national administrative organ, a public institution, a social group or an enterprise which needs to use the seal during work, and the digital seal user may be one user or a user group consisting of a plurality of users; the use approving party corresponding to the digital seal can be specifically an approving party with the approval authority of using the digital seal for the digital seal user, and the use approving party can be only one or a plurality of use approving parties; this is not limited by the present description.
Taking an enterprise as an example, the enterprise itself can be used as a digital seal user, and a digital seal of a official seal representing the enterprise is used.
Specifically, the enterprise may initiate a digital seal usage transaction for using a common seal of the enterprise through a client that establishes a connection with a node device in the blockchain, for example: one employee from the employees of the enterprise may be selected as a representative of the enterprise, and a digital seal usage transaction may be initiated via the client. The node equipment in the block chain can respond to the use transaction of the digital seal, call signature verification logic corresponding to the intelligent contract code in the intelligent contract, identify the file type of the electronic file to be signed in the use transaction of the digital seal, and verify whether the identified file type of the electronic file to be signed is matched with the signature type bound by the used digital seal.
In one embodiment, the electronic file to be signed may be processed based on a Natural Language Processing (NLP) algorithm to identify a file type of the electronic file to be signed.
In practical applications, the file type of the electronic file to be signed may be an administrative notice of an enterprise, a check, an invoice and the like of the enterprise, and the description does not limit this.
It should be noted that, if the electronic file to be signed is a file stored in an image form (e.g., a PDF file, a picture obtained by scanning a paper file, etc.), the electronic file to be signed may be processed based on an OCR (Optical Character Recognition) algorithm to identify characters in the electronic file to be signed, and then the characters in the identified electronic file to be signed may be processed based on an NLP algorithm to identify a file type of the electronic file to be signed.
In one embodiment, the digital seal usage transaction may further include identification of the digital seal that the digital seal user needs to use. In addition, the corresponding relation between the identification of the digital seal and the signature type of the digital seal can be stored in the block chain in advance; subsequently, when the signature type bound to the digital seal that the user of the digital seal needs to use is determined, the signature type corresponding to the identifier of the digital seal can be searched in the corresponding relation based on the identifier of the digital seal in the transaction of using the digital seal, and the found signature type is determined as the signature type bound to the digital seal.
It should be noted that the correspondence between the identifier of the digital seal and the signature type of the digital seal may be specifically stored in a storage space of a contract account of the intelligent contract, that is, the correspondence may be maintained by the intelligent contract.
In practical application, for a digital seal, the signature type bound with the digital seal is a file type allowed to be signed by using the digital seal; the signature types of different types of digital seals may differ. The types of the digital seal may include: official seal, financial seal, invoice seal, contract seal, corporate seal, etc.; the signature types bound to the various types of digital seals may be set based on actual requirements, for example: the types of signatures that bind to the business's official seal may include: administrative notes for the enterprise, etc.; the types of signatures bound to financial seals may include: checks, invoices, and the like.
For example, the client used by the claimant of the digital seal (i.e. the user claiming the digital seal) may output a type binding interface as shown in fig. 6 to the claimant of the digital seal after the claimant is successful. As shown in fig. 6, the claimant of the digital stamp may input the file type allowed to be signed by using the digital stamp in the type binding interface, and click an "ok" button in the type binding interface after completing the input; when the client detects the click operation aiming at the 'confirmation' button, the client can take the file type input by the claimant of the digital seal as the signature type bound with the digital seal, and the corresponding relation between the identification of the digital seal and the signature type of the digital seal is issued to the block chain for storing the certificate.
The correspondence relationship between the identifier of the digital seal stored in the blockchain and the signature type of the digital seal is assumed to be as shown in table 1 below:
TABLE 1
Subsequently, if the identifier of the digital seal (i.e. the identifier of the digital seal in the digital seal use transaction) that the digital seal user needs to use is identifier 1, type a may be determined as the signature type bound to the digital seal; if the identifier of the digital seal required to be used by the digital seal user is identifier 2, type A and type B can be determined as signature types bound with the digital seal; and so on.
When the signature type bound with the digital seal required to be used by the digital seal user is determined, the identified file type of the electronic file to be signed in the digital seal use transaction can be matched with the signature type bound with the digital seal, namely whether the identified file type of the electronic file to be signed is the same as any signature type bound with the digital seal is determined; if the electronic file to be signed is the same as the signature type bound with the digital seal, the identified file type of the electronic file to be signed can be considered to be matched with the signature type bound with the digital seal; if the identified file type of the electronic file to be signed is different from all the signature types bound with the digital seal, the identified file type of the electronic file to be signed can be considered to be not matched with the signature types bound with the digital seal.
Continuing with table 1 above as an example, if the identifier of the digital seal that the user of the digital seal needs to use is identifier 2, and the file type of the electronic file to be signed in the identified transaction of using the digital seal is type B, it may be determined that the file type of the identified electronic file to be signed matches the signature type bound to the digital seal.
In another example, if the identifier of the digital seal that the user of the digital seal needs to use is identifier 2, and the file type of the electronic file to be signed in the identified transaction for using the digital seal is type C, it may be determined that the identified file type of the electronic file to be signed does not match the signature type bound to the digital seal.
In this embodiment, under the condition that the file type of the electronic file to be signed in the identified transaction for using the digital seal is verified with the signature type bound to the digital seal that needs to be used by the user of the digital seal, if the identified file type of the electronic file to be signed is matched with the signature type bound to the digital seal, the signature logic corresponding to the intelligent contract code in the intelligent contract may be further invoked, that is, the intelligent contract code corresponding to the signature logic in the intelligent contract is executed, the digital seal stored in the block chain is obtained, and the signature processing is performed on the electronic file to be signed based on the obtained digital seal.
In one embodiment, the digital seal usage transaction may further include identification of the digital seal that the digital seal user needs to use. In this case, the digital stamp corresponding to the identifier of the digital stamp in the digital stamp use transaction stored in the block chain may be acquired based on the identifier of the digital stamp in the digital stamp use transaction, and may be used as the digital stamp that the user of the digital stamp needs to use.
In one embodiment shown, the digital stamp may specifically include a pattern image of the digital stamp. In this case, when the electronic file to be signed is signed based on the digital seal, the signature position in the electronic file to be signed may be identified, the style image of the digital seal may be added to the signature position, and the style image of the digital seal added to the signature position may be image-fused with the electronic file to be signed. And subsequently, displaying the image of the electronic file for the user to view, wherein the pattern image of the digital seal is arranged at the signature position.
Further, in an embodiment, the pattern image of the digital stamp may visually fuse the identity information of the claiming party of the digital stamp. Taking the pattern image of the digital stamp as shown in fig. 7 as an example, the "SFA" in the pattern image is the watermark information of the identity information a of the enterprise a as the claiming party of the digital stamp; in this way, the acquaintance can view the identity information A of the enterprise A through the watermark information.
In an embodiment shown, after the electronic file to be signed is signed based on the digital seal, a signature record corresponding to the digital seal may be generated, and the generated signature record may be issued to the block chain for storage; alternatively, the generated signature record may be issued to another blockchain (called a judicial chain) for storing judicial data, which is docked with the blockchain across chains, for storing evidence. Wherein, the signature record can record the information of the related information of the digital seal user, the related information of the digital seal, the signature time, the signature place (such as the positioning position information submitted by the digital seal user) and the original content (or data abstract) of the electronic document to be signed; the specific setting can be preset by technicians according to actual requirements.
In an embodiment shown, in the case of verifying the file type of the electronic file to be signed in the identified transaction of using the digital seal and the signature type bound to the digital seal that needs to be used by the user of the digital seal, if the identified file type of the electronic file to be signed does not match the signature type bound to the digital seal, an illegal use record of the digital seal corresponding to the digital seal may be generated, and the generated illegal use record of the digital seal is issued to the block chain for evidence storage; or, the generated illegal use record of the digital seal can be issued to a judicial chain for evidence storage. The digital seal illegal use record can record identity information in digital seal use transaction (namely identity information of a user who illegally uses the digital seal), related information of the digital seal, illegal use time, illegal use place (for example, positioning position information submitted by the user who illegally uses the digital seal) and information of original content (or data abstract) of an electronic file to be signed and the like; the specific setting can be preset by technicians according to actual requirements.
In one embodiment, the digital seal usage transaction may further include identity information of the party using the digital seal. In addition, the binding relationship between the digital seal and the identity information of the legal user of the digital seal can be stored in the block chain in advance; subsequently, when the identity information of the legal user bound with the digital seal needed by the digital seal user is determined, the identity information corresponding to the identity of the digital seal can be searched in the binding relation based on the identity of the digital seal in the digital seal use transaction, and the searched identity information is determined as the identity information of the legal user bound with the digital seal.
It should be noted that the binding relationship between the digital seal and the identity information of the legal user of the digital seal may be specifically stored in the storage space of the contract account of the intelligent contract, that is, the binding relationship may be maintained by the intelligent contract.
The legal user of the digital seal may be a claiming user of the digital seal, or a user who binds the identity information with the digital seal after the claiming user of the digital seal successfully claims the digital seal, which is not limited in this specification.
For example, the client used by the claimant of the digital seal may output a usage registration interface as shown in fig. 8 to the claimant of the digital seal after the claimant succeeds. As shown in fig. 8, the claiming party of the digital stamp may input the identity information of the using party permitted to use the digital stamp in the usage registration interface, and click the "confirm" button in the usage registration interface after completing the input; when the client detects the click operation aiming at the 'confirmation' button, the client can take the identity information input by the claimant of the digital seal as the identity information of the legal user bound with the digital seal, and the binding relation between the identification of the digital seal and the identity information of the legal user of the digital seal is issued to the block chain for storing the certificate.
It is assumed that the correspondence between the identifier of the digital seal stored in the blockchain and the signature type of the digital seal is as shown in table 2 below:
TABLE 2
Subsequently, if the identifier of the digital seal that the digital seal user needs to use (i.e. the identifier of the digital seal in the digital seal use transaction) is identifier 1, the identity information of the legal user bound to the digital seal includes: identity information of claimant 1 (i.e. the claimant of the digital seal claimant identifier 1); if the identifier of the digital seal that the digital seal user needs to use is identifier 2, the identity information of the legal user bound with the digital seal includes: identity information of the claimant 2 (namely the claimant of the digital seal of the claimant identifier 2), identity information of the user 1 and identity information of the user 2; and so on.
In this case, before the signature verification logic corresponding to the intelligent contract code in the intelligent contract is called to verify the electronic file to be signed in the digital seal use transaction and the digital seal, the identity information in the digital seal use transaction can be verified based on the identity information of the legal user bound to the digital seal stored in the block chain, namely, whether the identity information in the digital seal use transaction is matched with the identity information of any legal user bound to the digital seal is determined; if the digital seal is matched with the identification card, the digital seal can be considered to pass the authentication of the identification information in the transaction; if the identity information in the transaction of using the digital seal is not matched with the identity information of all legal users bound with the digital seal, the verification of the identity information in the transaction of using the digital seal can be considered to be failed.
If the verification of the identity information in the transaction of using the digital seal is passed, the signature verification logic corresponding to the intelligent contract code in the intelligent contract can be called to verify the electronic file to be signed in the transaction of using the digital seal and the digital seal.
However, if the verification of the identity information in the digital seal use transaction is not passed, the illegal use record of the digital seal corresponding to the identity information in the digital seal use transaction can be generated, and the generated illegal use record of the digital seal is issued to the block chain for storing the certificate; or, the generated illegal use record of the digital seal can be issued to a judicial chain for evidence storage. The digital seal illegal use record can record identity information in digital seal use transaction (namely identity information of a user who illegally uses the digital seal), related information of the digital seal, illegal use time, illegal use place (for example, positioning position information submitted by the user who illegally uses the digital seal) and information of original content (or data abstract) of an electronic file to be signed and the like; the specific setting can be preset by technicians according to actual requirements.
In an embodiment shown, in a case that the identified file type of the electronic file to be signed in the digital seal usage transaction and the signature type bound to the digital seal that the digital seal user needs to use are verified, if the identified file type of the electronic file to be signed does not match the signature type bound to the digital seal, referring to the event mechanism of the aforementioned intelligent contract, the intelligent contract may generate an event (referred to as an illegal use event of the digital seal) corresponding to a legal user bound to the digital seal; wherein, the illegal use event of the digital seal is used for indicating that the digital seal is illegally used.
In this case, when the client of any legal user of the digital seal indicated by the digital seal illegal use event obtains the digital seal illegal use event, the client may output prompt information indicating that the digital seal is illegally used to the legal user in response to the digital seal illegal use event, for example: a text box showing that the digital seal is illegally used can be output to the legal user; or, the sound-light alarm can be output to the legal user according to the preset alarm sound light.
Specifically, the illegal use event of the digital seal may be recorded in a transaction log of the use transaction of the digital seal or an intelligent contract log of the intelligent contract, and stored in the block chain.
The client of the legal user can acquire the illegal use event of the digital seal by monitoring the transaction log or the intelligent contract log stored in the block chain, and respond to the illegal use event of the digital seal and output prompt information indicating that the digital seal is illegally used to the legal user.
Or the client of the legal user may subscribe the digital seal illegal use event to the SDK deployed on the node device in the block chain as the event notification center, and when the SDK detects that the digital seal illegal use event is generated, the SDK may send the digital seal illegal use event to the client of the legal user, so that the client of the legal user may obtain the digital seal illegal use event, and output prompt information indicating that the digital seal is illegally used to the legal user in response to the digital seal illegal use event.
In one embodiment, for a digital stamp user, the identity information of the digital stamp user may include: the public key in the ca (certificate authority) certificate held by the digital stamp using party.
In practical application, on one hand, different digital seal users hold different CA certificates, and the public keys and the private keys in the different CA certificates are different; on the other hand, the public key is a public key, and the private key is a private key held by the user. Therefore, for a digital stamp using party, the public key in the CA certificate held by the digital stamp using party can be used as the identity information for referring to the digital stamp using party.
Further, in one embodiment shown, for a digital stamp user, the identity information of the digital stamp user may further include one or more of the following combinations: the identity of the user of the digital seal (such as account login password, face information or fingerprint information, etc.); a blockchain account identifier of the digital seal user; image information of a physical seal held by a user of the digital seal; etc. may be used to refer to information on the party using the digital stamp.
In an embodiment shown, before the signature logic corresponding to the intelligent contract code in the intelligent contract is called to obtain the digital seal and the electronic file to be signed is signed based on the digital seal, the use confirmation logic corresponding to the intelligent contract code in the intelligent contract may be called first to instruct the claimant of the digital seal to perform use confirmation on the digital seal, and after the use confirmation result of the claimant on the digital seal is obtained, the signature logic corresponding to the intelligent contract code in the intelligent contract is called to obtain the digital seal and the electronic file to be signed is signed based on the digital seal.
Further, in one illustrated embodiment, with reference to the aforementioned event mechanism of the smart contract, the smart contract may generate an event (referred to as a usage confirmation event) corresponding to the claimant of the digital seal; wherein, the use confirmation event is used for indicating the claiming party of the digital seal to confirm the use of the digital seal.
In this case, when the claimant instructed by the use confirmation event acquires the use confirmation event, the claimant may perform use confirmation on the digital stamp in response to the use confirmation event, for example: the client used by the claiming party can respond to the use confirmation event, display the related information of the digital seal using party and the digital seal to the claiming party, and the claiming party confirms the use of the digital seal based on the related information.
Specifically, the usage confirmation event may be recorded in a transaction log of the digital stamp usage transaction or an intelligent contract log of the intelligent contract, and stored in the block chain.
The claimant can acquire the use confirmation event by monitoring the transaction log or the intelligent contract log stored in the block chain, and can respond to the use confirmation event to confirm the use of the digital seal.
Or, the claiming party may subscribe the usage confirmation event to an SDK deployed on a node device in the blockchain as an event notification center, and when the SDK detects that the usage confirmation event is generated, the claiming party may send the usage confirmation event to the claiming party, so that the claiming party may obtain the usage confirmation event and perform usage confirmation on the digital seal in response to the usage confirmation event.
In the technical scheme, the node device in the blockchain responds to a received digital seal use transaction initiated by a digital seal user, transfers a signature check logic deployed in an intelligent contract on the blockchain, identifies the file type of an electronic file to be signed in the digital seal use transaction, checks whether the identified file type of the electronic file to be signed is matched with the signature type bound by the digital seal, and if the identified file type of the electronic file to be signed is matched with the signature type bound by the digital seal, can further call the signature logic in the intelligent contract to obtain the digital seal stored in the blockchain and perform signature processing on the electronic file to be signed in the digital seal use transaction based on the digital seal. By adopting the mode, the file type of the electronic file to be signed can be automatically identified, and when the file type of the electronic file to be signed is determined to be matched with the signature type bound by the digital seal required by a digital seal user, the digital seal is allowed to be used for signing the electronic file to be signed, so that the use safety and reliability of the digital seal can be ensured.
Referring to fig. 9, fig. 9 is a schematic diagram of another block chain-based digital stamp using system according to an exemplary embodiment of the present disclosure.
In a blockchain-based digital stamp usage system as shown in fig. 9, a smart contract may be deployed on the blockchain. Wherein, the intelligent contract can comprise an intelligent contract code used for signing and sealing the electronic file; in particular, the intelligent contract code of the intelligent contract may include intelligent contract code or the like corresponding to signing logic. In practical application, the signature logic can be realized by executing the intelligent contract code corresponding to the signature logic in the intelligent contract, and the signature processing is carried out on the electronic file to be signed based on the digital seal.
It should be noted that, for a specific process of creating and invoking an intelligent contract, reference may be made to the foregoing process of creating and invoking an intelligent contract, which is not described herein again.
During specific implementation, a user can initiate a digital seal using request through a client side which establishes connection with a Baas (Block as a service) platform; the Baas platform may establish a connection with the client and the node device in the block chain, respectively. When receiving the digital seal use request, the Baas platform can firstly identify the file type of the electronic file to be signed in the digital seal use request, check whether the identified file type of the electronic file to be signed is matched with the signature type bound to the digital seal, and then send a transaction for calling the intelligent contract deployed on the block chain to the node equipment in the block chain when the identified file type of the electronic file to be signed is matched with the signature type bound to the digital seal. When the node device in the blockchain receives the transaction, the transaction can be sent to other node devices in the blockchain so as to perform consensus processing on the transaction, and after the transaction consensus passes, the intelligent contract code in the intelligent contract is executed, so that the electronic file to be signed is signed.
In practical applications, the client may be deployed on an electronic device, where the electronic device may be a server, a computer, a mobile phone, a tablet device, a notebook computer, a Personal Digital assistant (pda), or the like; the above-described Baas platform may be deployed on an electronic device, which may be a server, a computer, or the like; the electronic device added to the block chain as the node device may be a server, a computer, a mobile phone, a tablet device, a notebook computer, a palm computer, or the like; this is not limited by the present description.
Referring to fig. 10, fig. 10 is a flowchart illustrating another block chain-based digital stamp using method according to an exemplary embodiment of the present disclosure.
In conjunction with the block chain based digital stamp using system shown in fig. 9, the block chain based digital stamp using method can be applied to the bas platform shown in fig. 9; the block chain-based digital seal using method can comprise the following steps:
step 1001, receiving a digital seal using request initiated by a digital seal using party; the digital seal using request comprises an electronic file to be signed;
step 1002, in response to the digital seal use request, identifying the file type of the electronic file to be signed, and verifying whether the identified file type of the electronic file to be signed is matched with the signature type bound with the digital seal;
step 1003, if the identified file type of the electronic file to be signed is matched with the signature type bound by the digital seal, sending an intelligent contract calling transaction to the node equipment, so that the node equipment responds to the intelligent contract calling transaction, calling signature logic corresponding to an intelligent contract code in the intelligent contract, acquiring the digital seal stored in the block chain, and signing the electronic file to be signed based on the digital seal.
In this embodiment, an intelligent contract may be deployed on the blockchain. A user (called a digital seal user) needing to use the digital seal can initiate a digital seal using request through a client side which establishes connection with the Baas platform; the digital seal use request may include an electronic file to be signed.
In this embodiment, the Baas platform may respond to the digital seal usage request, identify a file type of the electronic file to be signed in the digital seal usage request, and verify whether the identified file type of the electronic file to be signed matches a signature type bound to the digital seal that needs to be used by the digital seal user.
In this embodiment, under the condition that the file type of the electronic file to be signed in the identified digital seal use request is verified with the signature type bound to the digital seal that the digital seal user needs to use, if the identified file type of the electronic file to be signed is matched with the signature type bound to the digital seal, the Baas platform may send an intelligent contract invoking transaction for invoking the intelligent contract deployed on the blockchain to the node device in the blockchain. The node equipment in the block chain can respond to the intelligent contract calling transaction, call the signature logic corresponding to the intelligent contract code in the intelligent contract, namely execute the intelligent contract code corresponding to the signature logic in the intelligent contract, acquire the digital seal stored in the block chain, and perform signature processing on the electronic file to be signed based on the acquired digital seal.
In an embodiment shown, in a case that the file type of the electronic file to be signed in the identified transaction of using the digital seal is verified with the signature type bound to the digital seal that the user of the digital seal needs to use, if the identified file type of the electronic file to be signed is not matched with the signature type bound to the digital seal, the Baas platform may generate an illegal use record of the digital seal corresponding to the digital seal, and issue the illegal use record of the digital seal to the blockchain for evidence storage, or issue the illegal use record of the digital seal to a judicial chain that is in cross-chain butt joint with the blockchain for evidence storage.
In an embodiment shown, a binding relationship between the digital seal and identity information of a legal user of the digital seal may be stored in the blockchain; the digital seal use request may further include identity information of the digital seal user.
In this case, before the Baas platform identifies the file type of the electronic file to be signed and verifies whether the identified file type of the electronic file to be signed and the signature type bound to the digital seal are matched, the identity information of the legal user bound to the digital seal, which is stored in the block chain, is acquired, and then the identity information of the digital seal user in the digital seal use request is verified based on the acquired identity information of the legal user bound to the digital seal; if the verification of the identity information of the digital seal user in the digital seal using request is passed, the Baas platform can identify the file type of the electronic file to be signed and check whether the identified file type of the electronic file to be signed is matched with the signature type bound with the digital seal.
In an embodiment shown, in a case that the file type of the identified electronic file to be signed in the digital seal usage transaction is verified with the signature type bound to the digital seal that the digital seal user needs to use, if the identified file type of the electronic file to be signed does not match with the signature type bound to the digital seal, the Baas platform may send a digital seal illegal use message to a legal user bound to the digital seal, so that when the client of the legal user acquires the digital seal illegal use message, a prompt message indicating that the digital seal is illegally used is output to the legal user in response to the digital seal illegal use message.
In an embodiment shown, if the verification of the identity information of the digital seal user in the digital seal use request is not passed, the above-mentioned Baas platform may generate a digital seal illegal use record corresponding to the identity information of the digital seal user, and issue the digital seal illegal use record to the blockchain for storage, or issue the digital seal illegal use record to a judicial chain in cross-chain butt joint with the blockchain for storage.
In one illustrated embodiment, the identity information may include a public key in a CA certificate held by a legitimate user of the digital stamp.
Further, in one embodiment shown, the identity information may also include a combination of one or more of the following: the identity of a legal user of the digital seal; a blockchain account identifier of a legal user of the digital seal; image information of a physical seal held by a legitimate user of the digital seal.
In one illustrated embodiment, the legitimate user may be the claimant of the digital seal.
In an illustrated embodiment, the above-mentioned Baas platform may instruct a claiming party of the digital seal to confirm the use of the digital seal before sending the intelligent contract invoking transaction to the node device, and send the intelligent contract invoking transaction to the node device after obtaining a result of confirming the use of the digital seal by the claiming party.
Further, in one illustrated embodiment, an approval indication message may be sent by the above-mentioned Baas platform to the claimant, so that the claimant performs a confirmation of use for the digital stamp in response to the approval indication message.
In an embodiment shown, the block chain may store a correspondence between an identifier of the digital seal and a signature type of the digital seal; the digital stamp use transaction may further include an identification of the digital stamp.
In this case, the above-mentioned Baas platform may determine, based on the correspondence relationship of the certificate stored in the block chain, a signature type corresponding to the identifier of the digital seal in the digital seal usage transaction, and check whether the identified file type of the electronic file to be signed matches the signature type corresponding to the identifier of the digital seal.
In one embodiment shown, the digital stamp user may be an enterprise; the digital seal may be a official seal of the enterprise.
In one illustrated embodiment, the digital stamp may include a pattern image of the digital stamp.
Further, in one embodiment shown, the pattern image of the digital stamp may visually fuse the identity information of the digital stamp claiming party.
It should be noted that, for a specific manner in which the Baas platform executes the steps 1001 to 1003, reference may be made to a specific manner in which the node device in the block chain executes the steps 501 to 503 in the block chain-based digital seal claiming method shown in fig. 5, and this description is not repeated herein.
In the technical scheme, the Baas platform can respond to a received digital seal use request initiated by a digital seal user, identify a file type of an electronic file to be signed in the digital seal use request, check whether the identified file type of the electronic file to be signed is matched with a signature type bound to the digital seal, and if the identified file type of the electronic file to be signed is matched with the signature type bound to the digital seal, further send an intelligent contract call transaction to node equipment in a block chain, call signature logic in the intelligent contract by the node equipment in the block chain, obtain the digital seal stored in the block chain, and perform seal processing on the electronic file to be signed in the digital seal use transaction based on the digital seal. By adopting the mode, the file type of the electronic file to be signed can be automatically identified, and when the file type of the electronic file to be signed is determined to be matched with the signature type bound by the digital seal required by a digital seal user, the digital seal is allowed to be used for signing the electronic file to be signed, so that the use safety and reliability of the digital seal can be ensured.
Corresponding to the embodiment of the block chain-based digital stamp using method, the specification also provides an embodiment of a block chain-based digital stamp using device.
The embodiment of the block chain-based digital seal using device can be applied to electronic equipment. The device embodiments may be implemented by software, or by hardware, or by a combination of hardware and software. Taking a software implementation as an example, as a logical device, the device is formed by reading, by a processor of the electronic device where the device is located, a corresponding computer program instruction in the nonvolatile memory into the memory for operation. From a hardware aspect, as shown in fig. 11, the present specification is a hardware structure diagram of an electronic device where a digital stamp using apparatus based on a block chain is located, except for the processor, the memory, the network interface, and the nonvolatile memory shown in fig. 11, the electronic device where the apparatus is located in the embodiment may also include other hardware according to an actual function used by the digital stamp based on the block chain, which is not described again.
Referring to fig. 12, fig. 12 is a block diagram of a block chain-based digital stamp using apparatus according to an exemplary embodiment of the present disclosure. The block chain-based digital seal using apparatus 120 may be applied to an electronic device as shown in fig. 10, where the electronic device may be a node device in the block chain, and an intelligent contract is deployed in the block chain for signing an electronic file; the apparatus 120 may include:
a receiving module 1201 for receiving a digital seal usage transaction initiated by a digital seal using party; the digital seal usage transaction comprises an electronic file to be signed;
the verification module 1202 is used for responding to the digital seal use transaction, calling signature verification logic corresponding to an intelligent contract code in the intelligent contract, identifying the file type of the electronic file to be signed, and verifying whether the identified file type of the electronic file to be signed is matched with the signature type bound by the digital seal;
and the signing module 1203 further calls a signing logic corresponding to the intelligent contract code in the intelligent contract to acquire the digital seal stored in the block chain if the identified file type of the electronic file to be signed is matched with the signing type bound by the digital seal, and signs the electronic file to be signed based on the digital seal.
In this embodiment, the apparatus 120 may further include:
a first generating module 1204, configured to generate an illegal use record of the digital seal corresponding to the digital seal if the identified file type of the electronic file to be signed is not matched with the signature type bound to the digital seal;
the first evidence storing module 1205 issues the illegal use record of the digital seal to the block chain for storing the evidence; or issuing the illegal use record of the digital seal to a judicial chain in cross-chain butt joint with the block chain for evidence storage.
In this embodiment, the block chain stores a binding relationship between the digital seal and identity information of a legal user of the digital seal; the digital seal use transaction also comprises the identity information of the digital seal user;
the apparatus 120 may further include:
the verification module 1206 is used for verifying the identity information of the digital seal user in the digital seal usage transaction based on the identity information of the legal user bound with the digital seal stored in the block chain before calling signature verification logic corresponding to an intelligent contract code in the intelligent contract, identifying the file type of the electronic file to be signed and verifying whether the identified file type of the electronic file to be signed is matched with the signature type bound with the digital seal;
the verification module 1202:
if the verification of the identity information of the digital seal user in the digital seal use transaction is passed, signature verification logic corresponding to an intelligent contract code in the intelligent contract is called, the file type of the electronic file to be signed is identified, and whether the identified file type of the electronic file to be signed is matched with the signature type bound by the digital seal is verified.
In this embodiment, the apparatus 120 may further include:
a prompting module 1207, generating an illegal use event of the digital seal corresponding to a legal user bound with the digital seal if the identified file type of the electronic file to be signed is not matched with the signature type bound with the digital seal, so that when a client of the legal user acquires the illegal use event of the digital seal, a prompting message indicating that the digital seal is illegally used is output to the legal user in response to the illegal use event of the digital seal.
In this embodiment, the apparatus 120 may further include:
a second generating module 1208, configured to generate an illegal use record of the digital seal corresponding to the identity information of the user of the digital seal if the verification of the identity information of the user of the digital seal in the use transaction of the digital seal fails;
the second evidence storing module 1209 is used for issuing the illegal use record of the digital seal to the block chain for storing the evidence; or issuing the illegal use record of the digital seal to a judicial chain in cross-chain butt joint with the block chain for evidence storage.
In this embodiment, the identity information includes a public key in a CA certificate held by a legitimate user of the digital stamp.
In this embodiment, the identity information further includes a combination of one or more of the following:
the identity of a legal user of the digital seal;
a blockchain account identifier of a legal user of the digital seal;
image information of a physical seal held by a legitimate user of the digital seal.
In this embodiment, the legal user is a claimant of the digital seal.
In this embodiment, the apparatus 120 may further include:
the confirming module 1210 is configured to, before further invoking signature logic corresponding to an intelligent contract code in the intelligent contract, obtain the digital seal stored in the block chain, and before signing the electronic file to be signed based on the digital seal, invoke use confirming logic corresponding to the intelligent contract code in the intelligent contract, instruct a claiming party of the digital seal to perform use confirmation on the digital seal, and after obtaining a result of the use confirmation on the digital seal by the claiming party, further invoke signature logic corresponding to the intelligent contract code in the intelligent contract, obtain the digital seal stored in the block chain, and sign the electronic file to be signed based on the digital seal.
In this embodiment, the confirmation module 1210:
and generating a use confirmation event corresponding to a claiming party of the digital seal, so that the claiming party responds to the use confirmation event to perform use confirmation on the digital seal when acquiring the use confirmation event.
In this embodiment, the block chain stores a correspondence between the identifier of the digital seal and the signature type of the digital seal; the digital seal usage transaction also comprises an identification of the digital seal;
the verification module 1202:
determining a signature type corresponding to the identifier of the digital seal in the transaction of using the digital seal based on the corresponding relation of the certificate stored in the block chain, and verifying whether the identified file type of the electronic file to be signed is matched with the signature type corresponding to the identifier of the digital seal;
the signature module 1203:
and acquiring the digital seal stored in the block chain and corresponding to the identification of the digital seal in the digital seal use transaction.
In this embodiment, the apparatus 120 may further include:
a third generating module 1211, configured to generate a signature record corresponding to the digital seal after performing signature processing on the electronic file to be signed based on the acquired digital seal;
the third evidence storing module 1212 is configured to issue the generated signature record to the block chain for evidence storage; or issuing the generated signature record to a judicial chain in cross-chain butt joint with the block chain for evidence storage.
In this embodiment, the digital seal user is an enterprise; the digital seal is a official seal of the enterprise.
In this embodiment, the digital stamp includes a pattern image of the digital stamp;
the signing and sealing processing of the electronic file to be signed and sealed based on the digital seal comprises the following steps:
identifying a signature position in the electronic file to be signed;
adding the pattern image of the digital seal to the signature position, and carrying out image fusion with the electronic file to be signed.
In this embodiment, the style image of the digital stamp is visually fused with the identity information of the claimant of the digital stamp.
Referring to fig. 13, fig. 13 is a block diagram of another block chain-based digital stamp using apparatus according to an exemplary embodiment of the present disclosure. The block chain-based digital stamp using apparatus 130 may be applied to an electronic device as shown in fig. 10, which may be a Baas platform interfacing with node devices in the block chain; the intelligent contract is deployed in the block chain and used for signing and processing the electronic file; the apparatus 130 may include:
a receiving module 1301, which receives a digital seal using request initiated by a digital seal using party; the digital seal using request comprises an electronic file to be signed;
the verification module 1302, in response to the digital seal usage request, identifies the file type of the electronic file to be signed, and verifies whether the identified file type of the electronic file to be signed matches the signature type bound to the digital seal;
and the signing module 1303, if the identified file type of the electronic file to be signed is matched with the signing type bound to the digital seal, sends an intelligent contract calling transaction to the node device, so that the node device responds to the intelligent contract calling transaction, calls a signing logic corresponding to an intelligent contract code in the intelligent contract, acquires the digital seal stored in the block chain, and signs the electronic file to be signed based on the digital seal.
In this embodiment, the apparatus 130 may further include:
a first generating module 1304, configured to generate an illegal use record of the digital seal corresponding to the digital seal if the identified file type of the electronic file to be signed is not matched with the signature type bound to the digital seal;
the first evidence storing module 1305 is used for issuing the illegal use record of the digital seal to the block chain for storing the evidence; or issuing the illegal use record of the digital seal to a judicial chain in cross-chain butt joint with the block chain for evidence storage.
In this embodiment, the block chain stores a binding relationship between the digital seal and identity information of a legal user of the digital seal; the digital seal use request also comprises the identity information of the digital seal user;
the apparatus 130 may further include:
the verification module 1306 is configured to verify, based on identity information of a legitimate user bound to the digital seal and stored in the block chain, identity information of the digital seal user in the digital seal use request before identifying a file type of the electronic file to be signed and verifying whether the identified file type of the electronic file to be signed is matched with a signature type bound to the digital seal;
the verification module 1302:
and if the verification of the identity information of the digital seal user in the digital seal using request passes, identifying the file type of the electronic file to be signed, and verifying whether the identified file type of the electronic file to be signed is matched with the signature type bound with the digital seal.
In this embodiment, the apparatus 130 may further include:
a prompt module 1307, configured to send a digital seal illegal use message to a legal user bound to the digital seal if the identified file type of the electronic file to be signed does not match the signature type bound to the digital seal, so that when the client of the legal user obtains the digital seal illegal use message, a prompt message indicating that the digital seal is illegally used is output to the legal user in response to the digital seal illegal use message.
In this embodiment, the apparatus 130 may further include:
a second generating module 1308 for generating an illegal use record of the digital seal corresponding to the identity information of the user of the digital seal if the verification of the identity information of the user of the digital seal in the use transaction of the digital seal fails;
the second evidence storing module 1309 issues the illegal use record of the digital seal to the block chain for storing evidence; or issuing the illegal use record of the digital seal to a judicial chain in cross-chain butt joint with the block chain for evidence storage.
In this embodiment, the identity information includes a public key in a CA certificate held by a legitimate user of the digital stamp.
In this embodiment, the identity information further includes a combination of one or more of the following:
the identity of a legal user of the digital seal;
a blockchain account identifier of a legal user of the digital seal;
image information of a physical seal held by a legitimate user of the digital seal.
In this embodiment, the legal user is a claimant of the digital seal.
In this embodiment, the apparatus 130 may further include:
the confirmation module 1310 is configured to instruct a claiming party of the digital seal to perform usage confirmation on the digital seal before sending the intelligent contract calling transaction to the node device, and send the intelligent contract calling transaction to the node device after obtaining a usage confirmation result of the claiming party on the digital seal.
In this embodiment, the confirmation module 1310:
and sending an approval indicating message to the claimant so that the claimant can confirm the use of the digital seal in response to the approval indicating message.
In this embodiment, the block chain stores a correspondence between the identifier of the digital seal and the signature type of the digital seal; the digital seal usage transaction also comprises an identification of the digital seal;
the verification module 1302:
and determining a signature type corresponding to the identifier of the digital seal in the digital seal use transaction based on the corresponding relation of the certificate stored in the block chain, and verifying whether the identified file type of the electronic file to be signed is matched with the signature type corresponding to the identifier of the digital seal.
In this embodiment, the digital seal user is an enterprise; the digital seal is a official seal of the enterprise.
In this embodiment, the digital stamp includes a pattern image of the digital stamp.
In this embodiment, the pattern image of the digital stamp visually fuses the identity information of the digital stamp claimant.
The implementation process of the functions and actions of each module in the above device is specifically described in the implementation process of the corresponding step in the above method, and is not described herein again.
For the device embodiments, since they substantially correspond to the method embodiments, reference may be made to the partial description of the method embodiments for relevant points. The above-described embodiments of the apparatus are merely illustrative, wherein the modules described as separate parts may or may not be physically separate, and the parts displayed as modules may or may not be physical modules, may be located in one place, or may be distributed on a plurality of network modules. Some or all of the modules can be selected according to actual needs to achieve the purpose of the solution in the specification. One of ordinary skill in the art can understand and implement it without inventive effort.
The systems, devices, modules or units illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product with certain functions. A typical implementation device is a computer, which may take the form of a personal computer, laptop computer, cellular telephone, camera phone, smart phone, personal digital assistant, media player, navigation device, email messaging device, game console, tablet computer, wearable device, or a combination of any of these devices.
In a typical configuration, a computer includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
The memory may include forms of volatile memory in a computer readable medium, Random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.
Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic disk storage, quantum memory, graphene-based storage media or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave.
It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
The foregoing description has been directed to specific embodiments of this disclosure. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims may be performed in a different order than in the embodiments and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing may also be possible or may be advantageous.
The terminology used in the description of the one or more embodiments is for the purpose of describing the particular embodiments only and is not intended to be limiting of the description of the one or more embodiments. As used in one or more embodiments of the present specification and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items.
It should be understood that although the terms first, second, third, etc. may be used in one or more embodiments of the present description to describe various information, such information should not be limited to these terms. These terms are only used to distinguish one type of information from another. For example, first information may also be referred to as second information, and similarly, second information may also be referred to as first information, without departing from the scope of one or more embodiments herein. The word "if" as used herein may be interpreted as "at … …" or "when … …" or "in response to a determination", depending on the context.
The above description is only for the purpose of illustrating the preferred embodiments of the one or more embodiments of the present disclosure, and is not intended to limit the scope of the one or more embodiments of the present disclosure, and any modifications, equivalent substitutions, improvements, etc. made within the spirit and principle of the one or more embodiments of the present disclosure should be included in the scope of the one or more embodiments of the present disclosure.
Claims (60)
1. A digital seal using method based on block chain is applied to node equipment in the block chain; the intelligent contract is deployed in the block chain and used for signing and processing the electronic file; the method comprises the following steps:
receiving a digital seal use transaction initiated by a digital seal user; the digital seal usage transaction comprises an electronic file to be signed;
responding to the digital seal use transaction, calling signature verification logic corresponding to an intelligent contract code in the intelligent contract, identifying the file type of the electronic file to be signed, and verifying whether the identified file type of the electronic file to be signed is matched with the signature type bound to the digital seal;
if the identified file type of the electronic file to be signed is matched with the signature type bound by the digital seal, further calling signature logic corresponding to an intelligent contract code in the intelligent contract, acquiring the digital seal stored in the block chain, and carrying out signature processing on the electronic file to be signed based on the digital seal.
2. The method of claim 1, further comprising:
if the identified file type of the electronic file to be signed is not matched with the signature type bound with the digital seal, generating an illegal use record of the digital seal corresponding to the digital seal;
issuing the illegal use record of the digital seal to the block chain for storing the certificate; or issuing the illegal use record of the digital seal to a judicial chain in cross-chain butt joint with the block chain for evidence storage.
3. The method according to claim 1, wherein the block chain stores a binding relationship between the digital seal and identity information of a legal user of the digital seal; the digital seal use transaction also comprises the identity information of the digital seal user;
before the calling the signature verification logic corresponding to the intelligent contract code in the intelligent contract, identifying the file type of the electronic file to be signed, and verifying whether the identified file type of the electronic file to be signed is matched with the signature type bound to the digital seal, the method further comprises the following steps:
verifying the identity information of the user of the digital seal in the use transaction of the digital seal based on the identity information of the legal user bound with the digital seal stored in the blockchain;
if the verification of the identity information of the digital seal user in the digital seal use transaction is passed, signature verification logic corresponding to an intelligent contract code in the intelligent contract is called, the file type of the electronic file to be signed is identified, and whether the identified file type of the electronic file to be signed is matched with the signature type bound by the digital seal is verified.
4. The method of claim 3, further comprising:
and if the identified file type of the electronic file to be signed is not matched with the signature type bound with the digital seal, generating an illegal use event of the digital seal corresponding to a legal user bound with the digital seal, so that when a client of the legal user acquires the illegal use event of the digital seal, a prompt message indicating that the digital seal is illegally used is output to the legal user in response to the illegal use event of the digital seal.
5. The method of claim 3, further comprising:
if the verification of the identity information of the digital seal user in the digital seal use transaction is not passed, generating an illegal use record of the digital seal corresponding to the identity information of the digital seal user;
issuing the illegal use record of the digital seal to the block chain for storing the certificate; or issuing the illegal use record of the digital seal to a judicial chain in cross-chain butt joint with the block chain for evidence storage.
6. The method of claim 3, the identity information comprising a public key in a CA certificate held by a legitimate user of the digital stamp.
7. The method of claim 6, the identity information further comprising a combination of one or more of the following:
the identity of a legal user of the digital seal;
a blockchain account identifier of a legal user of the digital seal;
image information of a physical seal held by a legitimate user of the digital seal.
8. The method according to any one of claims 3-7, wherein said legitimate user is a claimant of said digital seal.
9. The method according to claim 8, before further invoking a signing logic corresponding to an intelligent contract code in the intelligent contract, acquiring the digital seal stored in the block chain, and signing the electronic file to be signed based on the digital seal, further comprising:
calling use confirmation logic corresponding to the intelligent contract codes in the intelligent contract, indicating a claiming party of the digital seal to carry out use confirmation on the digital seal, further calling signature logic corresponding to the intelligent contract codes in the intelligent contract after obtaining a use confirmation result of the claiming party on the digital seal, obtaining the digital seal stored in the block chain, and carrying out signature processing on the electronic file to be signed based on the digital seal.
10. The method of claim 9, the instructing a claiming guideline for the digital seal to validate use of the digital seal comprising:
and generating a use confirmation event corresponding to a claiming party of the digital seal, so that the claiming party responds to the use confirmation event to perform use confirmation on the digital seal when acquiring the use confirmation event.
11. The method according to claim 1, wherein the blockchain stores a corresponding relationship between the identification of the digital seal and the signature type of the digital seal; the digital seal usage transaction also comprises an identification of the digital seal;
the verifying whether the identified file type of the electronic file to be signed is matched with the signature type bound with the digital seal or not comprises the following steps:
determining a signature type corresponding to the identifier of the digital seal in the transaction of using the digital seal based on the corresponding relation of the certificate stored in the block chain, and verifying whether the identified file type of the electronic file to be signed is matched with the signature type corresponding to the identifier of the digital seal;
the acquiring the digital seal stored in the block chain includes:
and acquiring the digital seal stored in the block chain and corresponding to the identification of the digital seal in the digital seal use transaction.
12. The method of claim 1, further comprising:
after the electronic file to be signed is signed based on the acquired digital seal, generating a signature record corresponding to the digital seal;
issuing the generated signature record to the block chain for storing the certificate; or issuing the generated signature record to a judicial chain in cross-chain butt joint with the block chain for evidence storage.
13. The method of claim 1, wherein the party using the digital seal is an enterprise; the digital seal is a official seal of the enterprise.
14. The method according to claim 1, said digital stamp including a pattern image of said digital stamp;
the signing and sealing processing of the electronic file to be signed and sealed based on the digital seal comprises the following steps:
identifying a signature position in the electronic file to be signed;
adding the pattern image of the digital seal to the signature position, and carrying out image fusion with the electronic file to be signed.
15. The method according to claim 14, wherein said digital stamp form image visualization incorporates identity information of a claimant of said digital stamp.
16. A digital seal using method based on block chain is applied to a Baas platform which is in butt joint with node equipment in the block chain; the intelligent contract is deployed in the block chain and used for signing and processing the electronic file; the method comprises the following steps:
receiving a digital seal use request initiated by a digital seal user; the digital seal using request comprises an electronic file to be signed;
responding to the digital seal use request, identifying the file type of the electronic file to be signed, and checking whether the identified file type of the electronic file to be signed is matched with the signature type bound by the digital seal;
and if the identified file type of the electronic file to be signed is matched with the signature type bound with the digital seal, sending an intelligent contract calling transaction to the node equipment, so that the node equipment responds to the intelligent contract calling transaction, calling signature logic corresponding to an intelligent contract code in the intelligent contract, acquiring the digital seal stored in the block chain, and signing the electronic file to be signed based on the digital seal.
17. The method of claim 16, further comprising:
if the identified file type of the electronic file to be signed is not matched with the signature type bound with the digital seal, generating an illegal use record of the digital seal corresponding to the digital seal;
issuing the illegal use record of the digital seal to the block chain for storing the certificate; or issuing the illegal use record of the digital seal to a judicial chain in cross-chain butt joint with the block chain for evidence storage.
18. The method according to claim 16, wherein the blockchain stores a binding relationship between the digital seal and identity information of a legal user of the digital seal; the digital seal use request also comprises the identity information of the digital seal user;
before the identifying the file type of the electronic file to be signed and verifying whether the identified file type of the electronic file to be signed is matched with the signature type bound to the digital seal, the method further comprises the following steps:
verifying the identity information of the user of the digital seal in the digital seal use request based on the identity information of the legal user bound with the digital seal stored in the block chain;
and if the verification of the identity information of the digital seal user in the digital seal using request passes, identifying the file type of the electronic file to be signed, and verifying whether the identified file type of the electronic file to be signed is matched with the signature type bound with the digital seal.
19. The method of claim 18, further comprising:
if the identified file type of the electronic file to be signed is not matched with the signature type bound with the digital seal, sending an illegal use message of the digital seal to a legal user bound with the digital seal, so that when a client of the legal user obtains the illegal use message of the digital seal, the client responds to the illegal use message of the digital seal to output prompt information indicating that the digital seal is illegally used to the legal user.
20. The method of claim 18, further comprising:
if the verification of the identity information of the digital seal user in the digital seal use transaction is not passed, generating an illegal use record of the digital seal corresponding to the identity information of the digital seal user;
issuing the illegal use record of the digital seal to the block chain for storing the certificate; or issuing the illegal use record of the digital seal to a judicial chain in cross-chain butt joint with the block chain for evidence storage.
21. The method according to claim 18, said identity information comprising a public key in a CA certificate held by a legitimate user of said digital stamp.
22. The method of claim 21, the identity information further comprising a combination of one or more of the following:
the identity of a legal user of the digital seal;
a blockchain account identifier of a legal user of the digital seal;
image information of a physical seal held by a legitimate user of the digital seal.
23. The method according to any one of claims 18-22, wherein said legitimate user is a claimant of said digital seal.
24. The method of claim 23, prior to sending a smart contract invocation transaction to the node device, further comprising:
and indicating the claiming policy of the digital seal to confirm the use of the digital seal, and sending an intelligent contract calling transaction to the node equipment after obtaining the use confirmation result of the claiming policy on the digital seal.
25. The method according to claim 24, said instructing a claiming guideline for the digital seal to validate use of the digital seal comprising:
and sending an approval indicating message to the claimant so that the claimant can confirm the use of the digital seal in response to the approval indicating message.
26. The method according to claim 16, wherein the blockchain stores a correspondence between the identification of the digital seal and the signature type of the digital seal; the digital seal usage transaction also comprises an identification of the digital seal;
the verifying whether the identified file type of the electronic file to be signed is matched with the signature type bound with the digital seal or not comprises the following steps:
and determining a signature type corresponding to the identifier of the digital seal in the digital seal use transaction based on the corresponding relation of the certificate stored in the block chain, and verifying whether the identified file type of the electronic file to be signed is matched with the signature type corresponding to the identifier of the digital seal.
27. The method according to claim 16, wherein the digital seal user is an enterprise; the digital seal is a official seal of the enterprise.
28. The method according to claim 16, said digital stamp including a pattern image of said digital stamp.
29. The method according to claim 28, wherein said digital stamp form image visualization incorporates identity information of said digital stamp claimant.
30. A digital seal using device based on a block chain is applied to node equipment in the block chain; the intelligent contract is deployed in the block chain and used for signing and processing the electronic file; the device comprises:
the receiving module is used for receiving a digital seal using transaction initiated by a digital seal using party; the digital seal usage transaction comprises an electronic file to be signed;
the verification module is used for responding to the digital seal use transaction, calling signature verification logic corresponding to the intelligent contract code in the intelligent contract, identifying the file type of the electronic file to be signed, and verifying whether the identified file type of the electronic file to be signed is matched with the signature type bound by the digital seal;
and the signature module is used for further calling signature logic corresponding to an intelligent contract code in the intelligent contract to acquire the digital seal stored in the block chain and performing signature processing on the electronic file to be signed based on the digital seal if the identified file type of the electronic file to be signed is matched with the signature type bound by the digital seal.
31. The apparatus of claim 30, further comprising:
the first generation module generates an illegal use record of the digital seal corresponding to the digital seal if the identified file type of the electronic file to be signed is not matched with the signature type bound by the digital seal;
the first evidence storage module is used for issuing the illegal use record of the digital seal to the block chain for evidence storage; or issuing the illegal use record of the digital seal to a judicial chain in cross-chain butt joint with the block chain for evidence storage.
32. The apparatus according to claim 30, wherein the blockchain stores a binding relationship between the digital seal and identity information of a legal user of the digital seal; the digital seal use transaction also comprises the identity information of the digital seal user;
the device further comprises:
the verification module is used for verifying the identity information of the digital seal user in the digital seal use transaction based on the identity information of the legal user bound with the digital seal stored in the block chain and verified before calling signature verification logic corresponding to an intelligent contract code in the intelligent contract, identifying the file type of the electronic file to be signed and verifying whether the identified file type of the electronic file to be signed is matched with the signature type bound with the digital seal;
the checking module:
if the verification of the identity information of the digital seal user in the digital seal use transaction is passed, signature verification logic corresponding to an intelligent contract code in the intelligent contract is called, the file type of the electronic file to be signed is identified, and whether the identified file type of the electronic file to be signed is matched with the signature type bound by the digital seal is verified.
33. The apparatus of claim 32, the apparatus further comprising:
and the prompting module is used for generating a digital seal illegal use event corresponding to a legal user bound with the digital seal if the identified file type of the electronic file to be signed is not matched with the signature type bound with the digital seal, so that when a client of the legal user acquires the digital seal illegal use event, a prompting message indicating that the digital seal is illegally used is output to the legal user in response to the digital seal illegal use event.
34. The apparatus of claim 32, the apparatus further comprising:
the second generation module generates an illegal use record of the digital seal corresponding to the identity information of the digital seal user if the verification of the identity information of the digital seal user in the use transaction of the digital seal is not passed;
the second evidence storage module is used for issuing the illegal use record of the digital seal to the block chain for evidence storage; or issuing the illegal use record of the digital seal to a judicial chain in cross-chain butt joint with the block chain for evidence storage.
35. The apparatus according to claim 32, wherein the identity information comprises a public key in a CA certificate held by a legitimate user of the digital stamp.
36. The apparatus of claim 6, the identity information further comprising a combination of one or more of:
the identity of a legal user of the digital seal;
a blockchain account identifier of a legal user of the digital seal;
image information of a physical seal held by a legitimate user of the digital seal.
37. An apparatus according to any one of claims 32 to 36, wherein said legitimate user is a claimant of said digital seal.
38. The apparatus of claim 37, further comprising:
the confirming module is used for calling signing logic corresponding to an intelligent contract code in the intelligent contract to obtain the digital seal stored in the block chain, calling the use confirming logic corresponding to the intelligent contract code in the intelligent contract before signing the electronic file to be signed based on the digital seal, indicating a claiming party of the digital seal to carry out use confirmation on the digital seal, further calling the signing logic corresponding to the intelligent contract code in the intelligent contract after obtaining a use confirming result of the claiming party on the digital seal, obtaining the digital seal stored in the block chain, and signing the electronic file to be signed based on the digital seal.
39. The apparatus of claim 38, the confirmation module to:
and generating a use confirmation event corresponding to a claiming party of the digital seal, so that the claiming party responds to the use confirmation event to perform use confirmation on the digital seal when acquiring the use confirmation event.
40. The apparatus according to claim 30, wherein the blockchain stores a correspondence between the identification of the digital seal and the signature type of the digital seal; the digital seal usage transaction also comprises an identification of the digital seal;
the checking module:
determining a signature type corresponding to the identifier of the digital seal in the transaction of using the digital seal based on the corresponding relation of the certificate stored in the block chain, and verifying whether the identified file type of the electronic file to be signed is matched with the signature type corresponding to the identifier of the digital seal;
the signature module is:
and acquiring the digital seal stored in the block chain and corresponding to the identification of the digital seal in the digital seal use transaction.
41. The apparatus of claim 30, further comprising:
the third generation module generates a signature record corresponding to the digital seal after the electronic file to be signed is signed based on the acquired digital seal;
the third certificate storing module is used for issuing the generated signature record to the block chain for certificate storage; or issuing the generated signature record to a judicial chain in cross-chain butt joint with the block chain for evidence storage.
42. The apparatus according to claim 30, wherein the digital seal user is an enterprise; the digital seal is a official seal of the enterprise.
43. The apparatus according to claim 30, said digital stamp including a pattern image of said digital stamp;
the signing and sealing processing of the electronic file to be signed and sealed based on the digital seal comprises the following steps:
identifying a signature position in the electronic file to be signed;
adding the pattern image of the digital seal to the signature position, and carrying out image fusion with the electronic file to be signed.
44. The apparatus according to claim 43, wherein said digital stamp form image visualization incorporates identity information of a claimant of said digital stamp.
45. A digital seal using device based on a block chain is applied to a Baas platform which is in butt joint with node equipment in the block chain; the intelligent contract is deployed in the block chain and used for signing and processing the electronic file; the device comprises:
the receiving module is used for receiving a digital seal using request initiated by a digital seal using party; the digital seal using request comprises an electronic file to be signed;
the verification module responds to the digital seal use request, identifies the file type of the electronic file to be signed and verifies whether the identified file type of the electronic file to be signed is matched with the signature type bound with the digital seal or not;
and the signature module is used for sending an intelligent contract calling transaction to the node equipment if the identified file type of the electronic file to be signed is matched with the signature type bound by the digital seal, so that the node equipment responds to the intelligent contract calling transaction, calls signature logic corresponding to an intelligent contract code in the intelligent contract, acquires the digital seal stored in the block chain, and carries out signature processing on the electronic file to be signed based on the digital seal.
46. The apparatus of claim 45, further comprising:
the first generation module generates an illegal use record of the digital seal corresponding to the digital seal if the identified file type of the electronic file to be signed is not matched with the signature type bound by the digital seal;
the first evidence storage module is used for issuing the illegal use record of the digital seal to the block chain for evidence storage; or issuing the illegal use record of the digital seal to a judicial chain in cross-chain butt joint with the block chain for evidence storage.
47. The apparatus according to claim 45, wherein the blockchain stores a binding relationship between the digital seal and identity information of a legal user of the digital seal; the digital seal use request also comprises the identity information of the digital seal user;
the device further comprises:
the verification module is used for verifying the identity information of the digital seal user in the digital seal use request based on the identity information of the legal user bound with the digital seal stored in the block chain before identifying the file type of the electronic file to be signed and verifying whether the identified file type of the electronic file to be signed is matched with the signature type bound with the digital seal;
the checking module:
and if the verification of the identity information of the digital seal user in the digital seal using request passes, identifying the file type of the electronic file to be signed, and verifying whether the identified file type of the electronic file to be signed is matched with the signature type bound with the digital seal.
48. The apparatus of claim 47, further comprising:
and the prompting module is used for sending an illegal digital seal use message to a legal user bound with the digital seal if the identified file type of the electronic file to be signed is not matched with the signature type bound with the digital seal, so that when the client of the legal user obtains the illegal digital seal use message, the prompting module responds to the illegal digital seal use message and outputs prompting information indicating that the digital seal is illegally used to the legal user.
49. The apparatus of claim 47, further comprising:
the second generation module generates an illegal use record of the digital seal corresponding to the identity information of the digital seal user if the verification of the identity information of the digital seal user in the use transaction of the digital seal is not passed;
the second evidence storage module is used for issuing the illegal use record of the digital seal to the block chain for evidence storage; or issuing the illegal use record of the digital seal to a judicial chain in cross-chain butt joint with the block chain for evidence storage.
50. The apparatus according to claim 47, said identity information comprising a public key in a CA certificate held by a legitimate user of said digital stamp.
51. The apparatus of claim 50, the identity information further comprising a combination of one or more of:
the identity of a legal user of the digital seal;
a blockchain account identifier of a legal user of the digital seal;
image information of a physical seal held by a legitimate user of the digital seal.
52. The apparatus according to any one of claims 47-51, wherein said legitimate user is a claimant of said digital seal.
53. The apparatus of claim 52, further comprising:
and the confirmation module indicates the claiming party of the digital seal to confirm the use of the digital seal before sending the intelligent contract calling transaction to the node equipment, and sends the intelligent contract calling transaction to the node equipment after obtaining the use confirmation result of the claiming party on the digital seal.
54. The apparatus of claim 53, the confirmation module to:
and sending an approval indicating message to the claimant so that the claimant can confirm the use of the digital seal in response to the approval indicating message.
55. The apparatus according to claim 45, wherein the blockchain stores a correspondence between the identifier of the digital seal and the signature type of the digital seal; the digital seal usage transaction also comprises an identification of the digital seal;
the checking module:
and determining a signature type corresponding to the identifier of the digital seal in the digital seal use transaction based on the corresponding relation of the certificate stored in the block chain, and verifying whether the identified file type of the electronic file to be signed is matched with the signature type corresponding to the identifier of the digital seal.
56. The apparatus according to claim 45, wherein the digital seal user is an enterprise; the digital seal is a official seal of the enterprise.
57. The apparatus according to claim 45, wherein the digital stamp includes a pattern image of the digital stamp.
58. The apparatus according to claim 57, wherein said digital stamp form image visualization incorporates identity information of said digital stamp claimant.
59. An electronic device, comprising:
a processor;
a memory for storing processor-executable instructions;
wherein the processor implements the method of any of claims 1-15 or 16-29 by executing the executable instructions.
60. A computer readable storage medium having stored thereon computer instructions which, when executed by a processor, implement the method of any one of claims 1-15 or 16-29.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011075470.6A CN112200569B (en) | 2020-10-09 | 2020-10-09 | Digital seal using method and device based on block chain and electronic equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011075470.6A CN112200569B (en) | 2020-10-09 | 2020-10-09 | Digital seal using method and device based on block chain and electronic equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112200569A true CN112200569A (en) | 2021-01-08 |
| CN112200569B CN112200569B (en) | 2024-05-28 |
Family
ID=74014182
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011075470.6A Active CN112200569B (en) | 2020-10-09 | 2020-10-09 | Digital seal using method and device based on block chain and electronic equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112200569B (en) |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113468862A (en) * | 2021-07-08 | 2021-10-01 | 微易签(杭州)科技有限公司 | Method and device for creating layout file by block chain, electronic equipment and storage medium |
| CN113469658A (en) * | 2021-07-12 | 2021-10-01 | 支付宝(杭州)信息技术有限公司 | Block chain-based physical seal using method and device and electronic equipment |
| CN113689293A (en) * | 2021-08-09 | 2021-11-23 | 深圳前海微众银行股份有限公司 | Method and device for determining intelligent contract file in alliance chain |
| CN114331437A (en) * | 2021-12-30 | 2022-04-12 | 蚂蚁区块链科技(上海)有限公司 | Block chain-based digital seal using method and device |
| CN115131029A (en) * | 2022-06-28 | 2022-09-30 | 蚂蚁区块链科技(上海)有限公司 | Block chain-based digital file signing method and device |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2019101226A2 (en) * | 2019-02-28 | 2019-05-31 | Alibaba Group Holding Limited | System and method for generating digital marks |
| CN110490004A (en) * | 2018-06-11 | 2019-11-22 | 腾讯科技（深圳）有限公司 | Processing method, client, computer equipment and the medium of Electronic Signature file |
| CN110598460A (en) * | 2019-09-27 | 2019-12-20 | 腾讯科技（深圳）有限公司 | Block chain-based electronic signature method and device and storage medium |
| CN111460420A (en) * | 2020-02-19 | 2020-07-28 | 山东爱城市网信息技术有限公司 | Method, device and medium for using electronic seal based on block chain |
| CN111738748A (en) * | 2020-08-14 | 2020-10-02 | 支付宝(杭州)信息技术有限公司 | Block chain-based stamping processing method and device |
-
2020
- 2020-10-09 CN CN202011075470.6A patent/CN112200569B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110490004A (en) * | 2018-06-11 | 2019-11-22 | 腾讯科技（深圳）有限公司 | Processing method, client, computer equipment and the medium of Electronic Signature file |
| WO2019101226A2 (en) * | 2019-02-28 | 2019-05-31 | Alibaba Group Holding Limited | System and method for generating digital marks |
| CN110598460A (en) * | 2019-09-27 | 2019-12-20 | 腾讯科技（深圳）有限公司 | Block chain-based electronic signature method and device and storage medium |
| CN111460420A (en) * | 2020-02-19 | 2020-07-28 | 山东爱城市网信息技术有限公司 | Method, device and medium for using electronic seal based on block chain |
| CN111738748A (en) * | 2020-08-14 | 2020-10-02 | 支付宝(杭州)信息技术有限公司 | Block chain-based stamping processing method and device |
Non-Patent Citations (1)
| Title |
|---|
| 崔建远: "合同解释语境中的印章及其意义", 清华法学, vol. 12, no. 4, pages 167 - 179 * |
Cited By (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113468862A (en) * | 2021-07-08 | 2021-10-01 | 微易签(杭州)科技有限公司 | Method and device for creating layout file by block chain, electronic equipment and storage medium |
| CN113469658A (en) * | 2021-07-12 | 2021-10-01 | 支付宝(杭州)信息技术有限公司 | Block chain-based physical seal using method and device and electronic equipment |
| CN113689293A (en) * | 2021-08-09 | 2021-11-23 | 深圳前海微众银行股份有限公司 | Method and device for determining intelligent contract file in alliance chain |
| CN113689293B (en) * | 2021-08-09 | 2024-02-06 | 深圳前海微众银行股份有限公司 | Method and device for determining intelligent contract file in alliance chain |
| CN114331437A (en) * | 2021-12-30 | 2022-04-12 | 蚂蚁区块链科技(上海)有限公司 | Block chain-based digital seal using method and device |
| CN115131029A (en) * | 2022-06-28 | 2022-09-30 | 蚂蚁区块链科技(上海)有限公司 | Block chain-based digital file signing method and device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112200569B (en) | 2024-05-28 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111026789B (en) | Block chain-based electronic bill query method and device and electronic equipment | |
| CN110471984B (en) | Service processing method and device based on block chain and electronic equipment | |
| CN112101938B (en) | Digital seal using method and device based on block chain and electronic equipment | |
| CN110706114B (en) | Block chain-based default asset processing method and device and electronic equipment | |
| CN110765200B (en) | Asset procurement method and device based on block chain and electronic equipment | |
| CN112200569B (en) | Digital seal using method and device based on block chain and electronic equipment | |
| CN110458631B (en) | Bill number distribution method and device based on block chain and electronic equipment | |
| CN110471986B (en) | Bill real name getting method and device based on block chain and electronic equipment | |
| CN111681017B (en) | Goods batch true checking method and device based on block chain and electronic equipment | |
| CN111539731A (en) | Block chain-based federal learning method and device and electronic equipment | |
| CN112100588A (en) | Block chain-based digital seal application method and device and electronic equipment | |
| CN112801658B (en) | Cross-border resource transfer authenticity auditing method and device and electronic equipment | |
| CN111738724B (en) | Cross-border resource transfer authenticity auditing method and device, and electronic equipment | |
| CN111506652B (en) | Traffic accident handling method and device based on block chain and electronic equipment | |
| CN111639125A (en) | Resource circulation method and device based on block chain | |
| US11250438B2 (en) | Blockchain-based reimbursement splitting | |
| CN111402033A (en) | Asset information management method and device based on block chain | |
| CN112258189A (en) | Block chain-based subscription management method and device and electronic equipment | |
| CN110443612B (en) | Block chain-based reimbursement expense segmentation method and device and electronic equipment | |
| CN113849191B (en) | Intelligent contract deployment method, system, device and storage medium | |
| CN114331437A (en) | Block chain-based digital seal using method and device | |
| CN113095825A (en) | Asset management method and device based on block chain and electronic equipment | |
| CN110727735B (en) | Method, device and equipment for cooperatively completing task event based on block chain technology | |
| CN114925405A (en) | Block chain-based digital seal verification method and device and electronic equipment | |
| CN111383118A (en) | Asset management method and device based on block chain and electronic equipment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| REG | Reference to a national code |
Ref country code: HK Ref legal event code: DE Ref document number: 40044678 Country of ref document: HK |
|
| GR01 | Patent grant | ||
| GR01 | Patent grant |