CN112200569B - Digital seal using method and device based on block chain and electronic equipment - Google Patents
Digital seal using method and device based on block chain and electronic equipment Download PDFInfo
- Publication number
- CN112200569B CN112200569B CN202011075470.6A CN202011075470A CN112200569B CN 112200569 B CN112200569 B CN 112200569B CN 202011075470 A CN202011075470 A CN 202011075470A CN 112200569 B CN112200569 B CN 112200569B
- Authority
- CN
- China
- Prior art keywords
- digital
- seal
- digital seal
- stamp
- signed
- 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.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 99
- 238000012795 verification Methods 0.000 claims abstract description 73
- 238000012545 processing Methods 0.000 claims abstract description 33
- 238000012790 confirmation Methods 0.000 claims description 71
- 238000003032 molecular docking Methods 0.000 claims description 21
- 238000012800 visualization Methods 0.000 claims description 6
- 230000004927 fusion Effects 0.000 claims description 5
- 210000001503 joint Anatomy 0.000 claims description 4
- 238000010586 diagram Methods 0.000 description 16
- 230000008569 process Effects 0.000 description 16
- 230000004044 response Effects 0.000 description 10
- 238000005516 engineering process Methods 0.000 description 9
- 230000008520 organization Effects 0.000 description 7
- 230000005540 biological transmission Effects 0.000 description 5
- 230000008859 change Effects 0.000 description 5
- 230000006870 function Effects 0.000 description 5
- 230000007246 mechanism Effects 0.000 description 5
- 238000012546 transfer Methods 0.000 description 4
- 238000012544 monitoring process Methods 0.000 description 3
- 238000003058 natural language processing Methods 0.000 description 3
- 230000000977 initiatory effect Effects 0.000 description 2
- 230000003993 interaction Effects 0.000 description 2
- 238000012015 optical character recognition Methods 0.000 description 2
- 230000002085 persistent effect Effects 0.000 description 2
- 229920001690 polydopamine Polymers 0.000 description 2
- 230000000007 visual effect Effects 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
- 238000013475 authorization Methods 0.000 description 1
- 230000006399 behavior Effects 0.000 description 1
- 230000008901 benefit Effects 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 238000004590 computer program Methods 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 229910021389 graphene Inorganic materials 0.000 description 1
- 239000003999 initiator Substances 0.000 description 1
- 239000003607 modifier Substances 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000004806 packaging method and process Methods 0.000 description 1
- 230000000737 periodic effect Effects 0.000 description 1
- 230000002688 persistence Effects 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 238000010200 validation analysis Methods 0.000 description 1
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 disclosure provide a method, an apparatus, and an electronic device for using a digital stamp based on a blockchain, which are applied to node devices in the blockchain; an intelligent contract deployed in the blockchain for signing the electronic file; the method comprises the following steps: receiving a digital seal use transaction initiated by a digital seal user; wherein the digital stamp use transaction includes an electronic file; 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, and verifying whether the identified file type of the electronic file is matched with the signature type bound by the digital seal; if the identified file type of the electronic file is matched with the signature type bound by the digital seal, further calling signature logic corresponding to the intelligent contract code in the intelligent contract, acquiring the digital seal stored in the blockchain, and carrying out signature processing 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 blockchain-based digital stamp using method, a blockchain-based digital stamp using device, and an electronic device.
Background
Blockchain technology, also known as distributed ledger technology, is an emerging technology that is commonly engaged in "accounting" by several computing devices, together maintaining a complete distributed database. The blockchain technology has the characteristics of decentralization, disclosure transparency, capability of participating in database recording by each computing device and capability of rapidly performing data synchronization among the computing devices, so that the blockchain technology is widely applied in a plurality of fields.
Disclosure of Invention
The application of the digital seal based on the block chain is provided by the specification, and the digital seal based on the block chain is applied to node equipment in the block chain; an intelligent contract deployed in the blockchain for signing an electronic file; the method comprises the following steps:
Receiving a digital seal use transaction initiated by a digital seal user; wherein the digital seal use 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 by 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 blockchain, and performing 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 by the digital seal, generating a digital seal illegal use record corresponding to the digital seal;
Issuing the illegal use records of the digital seal to the blockchain for certification; or issuing the illegal use record of the digital seal to a judicial chain in cross-chain docking with the block chain for certification.
Optionally, the blockchain stores the binding relation of identity information of the digital seal and a legal user of the digital seal; the digital seal using transaction also comprises identity information of the digital seal using party;
the signature verification logic corresponding to the intelligent contract code in the intelligent contract is called, the file type of the electronic file to be signed is identified, and before verifying whether the identified file type of the electronic file to be signed is matched with the signature type bound by the digital seal, the method further comprises the steps of:
Verifying the identity information of the digital stamp user in the digital stamp use transaction based on the identity information of the legal user bound with the digital stamp stored in the blockchain;
if the identity information of the digital seal user in the digital seal use transaction passes verification, invoking 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.
Optionally, the method further comprises:
If the file type of the electronic file to be signed is not matched with the signature type bound by the digital seal, generating a digital seal illegal use event corresponding to a legal user bound by the digital seal, so that when the client of the legal user acquires the digital seal illegal use event, responding to the digital seal illegal use event and outputting 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 a digital seal illegal use record corresponding to the identity information of the digital seal user;
Issuing the illegal use records of the digital seal to the blockchain for certification; or issuing the illegal use record of the digital seal to a judicial chain in cross-chain docking with the block chain for certification.
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 the legal user of the digital seal;
a blockchain account identifier of a legal user of the digital stamp;
image information of a physical seal held by a legal user of the digital seal.
Optionally, the legal user is a claimant of the digital stamp.
Optionally, the further calling the signature logic corresponding to the intelligent contract code in the intelligent contract, obtaining the digital seal stored in the blockchain, and before signing the electronic file to be signed based on the digital seal, further includes:
invoking use confirmation logic corresponding to an intelligent contract code in the intelligent contract, indicating a claimant of the digital seal to confirm the use of the digital seal, further invoking signature logic corresponding to the intelligent contract code in the intelligent contract after acquiring a use confirmation result of the claimant to the digital seal, acquiring the digital seal stored in the block chain, and performing signature processing on the electronic file to be signed based on the digital seal.
Optionally, the indicating the claimant of the digital stamp confirms the use of the digital stamp, including:
And generating a use confirmation event corresponding to the claimant of the digital seal, so that the claimant responds to the use confirmation event to carry out use confirmation on the digital seal when acquiring the use confirmation event.
Optionally, the corresponding relation between the identification of the digital seal and the signature type of the digital seal is stored in the blockchain; the digital seal using transaction also comprises an identification of the digital seal;
The checking whether the file type of the identified electronic file to be signed is matched with the signature type bound by the digital seal comprises the following steps:
determining a signature type corresponding to the identification of the digital stamp in the digital stamp-using transaction based on the corresponding relation of the certificates stored in the blockchain, and checking whether the identified file type of the electronic file to be signed is matched with the signature type corresponding to the identification of the digital stamp;
The obtaining the digital stamp stored in the blockchain includes:
And acquiring the digital seal corresponding to the identification of the digital seal in the digital seal using transaction stored in the blockchain.
Optionally, the method further comprises:
After signing the electronic file to be signed based on the obtained digital seal, generating a signature record corresponding to the digital seal;
Issuing the generated signature record to the blockchain for certification; or issuing the generated signature record to a judicial chain in cross-chain connection with the blockchain for certification.
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 processing of the electronic file to be signed based on the digital seal comprises the following steps:
identifying a signature position in the electronic file to be signed;
And 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 pattern image of the digital seal is visually fused with the identity information of the claimant of the digital seal.
The specification also provides a digital seal using method based on the block chain, which is applied to a Baas platform in butt joint with node equipment in the block chain; an intelligent contract deployed in the blockchain for signing an electronic file; the method comprises the following steps:
Receiving a digital seal use request initiated by a digital seal user; wherein the digital seal use request comprises an electronic file to be signed;
identifying the file type of the electronic file to be signed in response to the digital seal use request, 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;
If the identified file type of the electronic file to be signed is matched with the signature type bound by the digital seal, an intelligent contract calling transaction is sent to the node equipment, so that the node equipment responds to the intelligent contract calling transaction, signature logic corresponding to an intelligent contract code in the intelligent contract is called, the digital seal stored in the block chain is obtained, and signature processing is carried out 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 by the digital seal, generating a digital seal illegal use record corresponding to the digital seal;
Issuing the illegal use records of the digital seal to the blockchain for certification; or issuing the illegal use record of the digital seal to a judicial chain in cross-chain docking with the block chain for certification.
Optionally, the blockchain stores the binding relation of identity information of the digital seal and a legal user of the digital seal; the digital seal use request also comprises the identity information of the digital seal user;
The method comprises the steps of identifying the file type of the electronic file to be signed, 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 further comprising:
Verifying the identity information of the digital stamp user in the digital stamp use request based on the identity information of the legal user bound with the digital stamp stored in the blockchain;
If the identification information of the digital stamp using party in the digital stamp using request passes verification, 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 stamp.
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 a digital seal illegal use message to a legal user bound with the digital seal, so that when the client of the legal user acquires the digital seal illegal use message, responding to the digital seal illegal use message and outputting 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 a digital seal illegal use record corresponding to the identity information of the digital seal user;
Issuing the illegal use records of the digital seal to the blockchain for certification; or issuing the illegal use record of the digital seal to a judicial chain in cross-chain docking with the block chain for certification.
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 the legal user of the digital seal;
a blockchain account identifier of a legal user of the digital stamp;
image information of a physical seal held by a legal user of the digital seal.
Optionally, the legal user is a claimant of the digital stamp.
Optionally, before sending the smart contract invoking transaction to the node device, the method further includes:
And indicating a claimant of the digital seal to confirm the use of the digital seal, and sending an intelligent contract invoking transaction to the node equipment after acquiring a result of confirming the use of the digital seal by the claimant.
Optionally, the indicating the claimant of the digital stamp confirms the use of the digital stamp, including:
and sending an approval indication message to the claimant so that the claimant responds to the approval indication message to carry out use confirmation on the digital seal.
Optionally, the corresponding relation between the identification of the digital seal and the signature type of the digital seal is stored in the blockchain; the digital seal using transaction also comprises an identification of the digital seal;
The checking whether the file type of the identified electronic file to be signed is matched with the signature type bound by the digital seal comprises the following steps:
and determining a signature type corresponding to the identification of the digital seal in the digital seal using transaction based on the corresponding relation of the certificates stored in the blockchain, and checking whether the identified file type of the electronic file to be signed is matched with the signature type corresponding to the identification 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 seal is visually fused with the identity information of the digital seal claimant.
The specification also provides a digital seal using device based on the block chain, which is applied to node equipment in the block chain; an intelligent contract deployed in the blockchain for signing an electronic file; the device comprises:
the receiving module is used for receiving a digital seal use transaction initiated by a digital seal user; wherein the digital seal use 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 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 signature module is used for further calling signature logic corresponding to the intelligent contract code in the intelligent contract if the identified file type of the electronic file to be signed is matched with the signature type bound by the digital seal, 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 apparatus further comprises:
the first generation module is used for generating a digital stamp illegal use record corresponding to the digital stamp if the file type of the identified electronic file to be signed is not matched with the signature type bound by the digital stamp;
The first evidence storage module is used for issuing the illegal use records of the digital seal to the blockchain for evidence storage; or issuing the illegal use record of the digital seal to a judicial chain in cross-chain docking with the block chain for certification.
Optionally, the blockchain stores the binding relation of identity information of the digital seal and a legal user of the digital seal; the digital seal using transaction also comprises identity information of the digital seal using party;
The apparatus further comprises:
The verification module is used for verifying the identity information of the digital stamp user in the digital stamp use transaction based on the identity information of the legal user bound with the digital stamp stored in the blockchain before invoking 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 stamp;
the verification module is used for:
if the identity information of the digital seal user in the digital seal use transaction passes verification, invoking 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.
Optionally, the apparatus further comprises:
And the prompting module is used for generating a digital stamp illegal use event corresponding to a legal user bound with the digital stamp if the file type of the electronic file to be signed is not matched with the signature type bound with the digital stamp, so that when the client of the legal user acquires the digital stamp illegal use event, responding to the digital stamp illegal use event and outputting prompting information indicating that the digital stamp is illegally used to the legal user.
Optionally, the apparatus further comprises:
The second generation module is used for generating a digital stamp illegal use record corresponding to the identity information of the digital stamp using party if the identity information of the digital stamp using party in the digital stamp using transaction is not verified;
The second evidence storage module is used for issuing the illegal use records of the digital seal to the blockchain for evidence storage; or issuing the illegal use record of the digital seal to a judicial chain in cross-chain docking with the block chain for certification.
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 the legal user of the digital seal;
a blockchain account identifier of a legal user of the digital stamp;
image information of a physical seal held by a legal user of the digital seal.
Optionally, the legal user is a claimant of the digital stamp.
Optionally, the apparatus further comprises:
And the confirmation module is used for calling the use confirmation logic corresponding to the intelligent contract code in the intelligent contract before further calling the signing logic corresponding to the intelligent contract code in the intelligent contract to acquire the digital seal stored in the block chain and signing the electronic file to be signed based on the digital seal, indicating a claimator of the digital seal to confirm the use of the digital seal, and further calling the signing logic corresponding to the intelligent contract code in the intelligent contract after acquiring the use confirmation result of the claimator to the digital seal to acquire 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 the claimant of the digital seal, so that the claimant responds to the use confirmation event to carry out use confirmation on the digital seal when acquiring the use confirmation event.
Optionally, the corresponding relation between the identification of the digital seal and the signature type of the digital seal is stored in the blockchain; the digital seal using transaction also comprises an identification of the digital seal;
the verification module is used for:
determining a signature type corresponding to the identification of the digital stamp in the digital stamp-using transaction based on the corresponding relation of the certificates stored in the blockchain, and checking whether the identified file type of the electronic file to be signed is matched with the signature type corresponding to the identification of the digital stamp;
The signature module:
And acquiring the digital seal corresponding to the identification of the digital seal in the digital seal using transaction stored in the blockchain.
Optionally, the apparatus further comprises:
The third generation module is used for generating a signature record corresponding to the digital seal after signing the electronic file to be signed based on the acquired digital seal;
The third certificate storing module is used for releasing the generated signature record to the blockchain for certificate storing; or issuing the generated signature record to a judicial chain in cross-chain connection with the blockchain for certification.
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 processing of the electronic file to be signed based on the digital seal comprises the following steps:
identifying a signature position in the electronic file to be signed;
And 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 pattern image of the digital seal is visually fused with the identity information of the claimant of the digital seal.
The specification also provides a digital seal using device based on the block chain, which is applied to a Baas platform in butt joint with node equipment in the block chain; an intelligent contract deployed in the blockchain for signing an electronic file; the device comprises:
The receiving module is used for receiving a digital seal use request initiated by a digital seal user; wherein the digital seal use request comprises an electronic file to be signed;
The verification module is used for responding 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 by the digital seal;
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 blockchain, and performs signature processing on the electronic file to be signed based on the digital seal.
Optionally, the apparatus further comprises:
the first generation module is used for generating a digital stamp illegal use record corresponding to the digital stamp if the file type of the identified electronic file to be signed is not matched with the signature type bound by the digital stamp;
The first evidence storage module is used for issuing the illegal use records of the digital seal to the blockchain for evidence storage; or issuing the illegal use record of the digital seal to a judicial chain in cross-chain docking with the block chain for certification.
Optionally, the blockchain stores the binding relation of identity information of the digital seal and a legal user of the digital seal; the digital seal use request also comprises the identity information of the digital seal user;
The apparatus 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 blockchain 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 verification module is used for:
If the identification information of the digital stamp using party in the digital stamp using request passes verification, 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 stamp.
Optionally, the apparatus further comprises:
And the prompting module is used for sending a digital seal illegal use message to a legal user bound with the digital seal if the 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 acquires the digital seal illegal use message, responding to the digital seal illegal use message and outputting prompting information indicating that the digital seal is illegally used to the legal user.
Optionally, the apparatus further comprises:
The second generation module is used for generating a digital stamp illegal use record corresponding to the identity information of the digital stamp using party if the identity information of the digital stamp using party in the digital stamp using transaction is not verified;
The second evidence storage module is used for issuing the illegal use records of the digital seal to the blockchain for evidence storage; or issuing the illegal use record of the digital seal to a judicial chain in cross-chain docking with the block chain for certification.
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 the legal user of the digital seal;
a blockchain account identifier of a legal user of the digital stamp;
image information of a physical seal held by a legal user of the digital seal.
Optionally, the legal user is a claimant of the digital stamp.
Optionally, the apparatus further comprises:
and the confirmation module is used for indicating a claimant of the digital seal to confirm the use of the digital seal before sending the intelligent contract calling transaction to the node equipment, and sending the intelligent contract calling transaction to the node equipment after acquiring the confirmation result of the claimant of the use of the digital seal.
Optionally, the confirmation module:
and sending an approval indication message to the claimant so that the claimant responds to the approval indication message to carry out use confirmation on the digital seal.
Optionally, the corresponding relation between the identification of the digital seal and the signature type of the digital seal is stored in the blockchain; the digital seal using transaction also comprises an identification of the digital seal;
the verification module is used for:
and determining a signature type corresponding to the identification of the digital seal in the digital seal using transaction based on the corresponding relation of the certificates stored in the blockchain, and checking whether the identified file type of the electronic file to be signed is matched with the signature type corresponding to the identification 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 seal is visually fused with the identity information of the digital seal claimant.
The present specification also proposes an electronic device comprising:
A processor;
A memory for storing processor-executable instructions;
Wherein the processor implements the steps of any of the methods described above by executing the executable instructions.
The present specification also proposes 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 by the digital seal which needs to be used 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 smart contract creation process shown in the present specification;
FIG. 2 is a schematic diagram of the call flow of a smart contract shown in the present specification;
FIG. 3 is a schematic diagram of the creation and invocation flow of a smart contract shown in the present specification;
FIG. 4 is a schematic diagram of a blockchain-based digital stamp use system shown in an exemplary embodiment of the present disclosure;
FIG. 5 is a flow chart illustrating a method of using a blockchain-based digital stamp in accordance with an exemplary embodiment of the present description;
FIG. 6 is a schematic diagram of one type of binding interface shown in an exemplary embodiment of the present disclosure;
FIG. 7 is a schematic representation of a pattern image of a digital stamp according to an exemplary embodiment of the present disclosure;
FIG. 8 is a schematic diagram of a use registration interface shown in an exemplary embodiment of the present disclosure;
FIG. 9 is a schematic diagram of another blockchain-based digital stamp use system shown in an exemplary embodiment of the present description;
FIG. 10 is a flowchart illustrating another blockchain-based digital stamp use method in accordance with an exemplary embodiment of the present disclosure;
Fig. 11 is a hardware configuration diagram of an electronic device shown in an exemplary embodiment of the present specification;
FIG. 12 is a block diagram of a blockchain-based digital stamp using device shown in an exemplary embodiment of the present disclosure;
Fig. 13 is a block diagram of another blockchain-based digital stamp using device shown in an exemplary embodiment of the present description.
Detailed Description
Reference will now be made in detail to exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, the same numbers in different drawings refer to 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 aspects of one or more embodiments of the present description as detailed in the accompanying claims.
It should be noted that: in other embodiments, the steps of the corresponding method are not necessarily performed in the order shown and described in this specification. In some other embodiments, the method may include more or fewer steps than described in this specification. Furthermore, individual steps described in this specification, in other embodiments, may be described as being split into multiple steps; while various 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 federated chain (Consortium Blockchain). In addition, there may be combinations of the above types, such as private chain+federation chain, federation chain+public chain, and the like.
Among them, the highest degree of decentralization is the public chain. The public chain is represented by bitcoin, ethernet, and participants joining the public chain (also referred to as nodes in the blockchain) can read data records on the chain, participate in transactions, and compete for accounting rights for new blocks, etc. Moreover, each node can freely join or leave the network and perform relevant operations.
The private chain is the opposite, the write rights of the network are controlled by an organization or organization, and the data read rights are specified by the organization. In short, the private chain may be a weakly centralized system with strict restrictions on the nodes and a small number of nodes. This type of blockchain is more suitable for use within a particular organization.
The alliance chain is a block chain between public and private chains, and can realize 'partial decentralization'. Each node in the federation chain typically has an entity organization or organization corresponding thereto; nodes join the network by authorization and form a benefit-related federation, which collectively maintains blockchain operation.
Based on the basic characteristics of a blockchain, a blockchain is typically made up 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 strictly according to the time stamps recorded in the blocks.
For real data generated in the physical world, the real data can be constructed into a standard transaction (transaction) format supported by a blockchain, then the transaction is issued to the blockchain, the node equipment in the blockchain performs consensus processing on the received transaction, and after the consensus is achieved, the node equipment serving as an accounting node in the blockchain packages the transaction into a block, and the persistence is performed in the blockchain.
Among other things, the consensus algorithm supported in the blockchain may include:
A first type of consensus algorithm, namely a consensus algorithm that node equipment needs to contend for the accounting rights of the accounting period of each round; for example, consensus algorithms such as Proof of Work (POW), proof of equity (POS), proof of commission (DELEGATED PROOF OF STAKE, DPOS);
A second type of consensus algorithm, namely a consensus algorithm which pre-elects accounting nodes (without competing for accounting rights) for each round of accounting period; for example, a consensus algorithm such as Bayesian fault tolerance (PRACTICAL BYZANTINE FAULT TOLERANCE, PBFT) is used.
In blockchain networks employing a first type of consensus algorithm, node devices competing for accounting rights may perform a transaction after receiving the transaction. One of the node devices competing for the accounting rights may win out of the process of competing for the accounting rights in this round, becoming an accounting node. The accounting node may package the received transaction with other transactions to generate the latest chunk and send the generated latest chunk or chunks of the latest chunk to other node devices for consensus.
In blockchain networks employing a second type of consensus algorithm, node devices with accounting rights are already well-established prior to this round of accounting. Thus, after receiving a transaction, the node device may send the transaction to the billing node if it is not itself the billing node for the current round. For the billing node of the present 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 the block head of the latest block to other node devices for consensus.
As described above, regardless of which consensus algorithm is used by the blockchain as shown above, the accounting node of the round may package the received transaction to generate the latest chunk and send the generated latest chunk or chunks of the latest chunk to other node devices for consensus verification. If the other node equipment receives the latest block or the block head of the latest block, and is verified to have no problem, the latest block can be added to the end of the original blockchain, so that the accounting process of the blockchain is completed. Other nodes may also execute transactions contained in the block during the verification of the new block or block header from the accounting node.
In the blockchain domain, an important concept is account (account); taking an ethernet as an example, the ethernet generally divides accounts into two types, an external account and a contract account; the external account is an account directly controlled by the user, and is also called a user account; the contract account is an account (i.e., smart contract) that is created by the user through an external account and contains a contract code. Of course, for some blockchain projects (such as ant blockchains) derived from the ethernet-based architecture, the account types supported by the blockchains can be further expanded, which is not particularly limited in this specification.
For accounts in a blockchain, the account status of the account is typically maintained by a structure. When a transaction in a block is executed, the status of the account in the blockchain associated with the transaction will typically change.
Taking ethernet as an example, the structure of an account typically includes fields such as Balance, nonce, code, and Storage. Wherein:
a Balance field for maintaining a 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 effectively avoiding replay attack;
A Code field for maintaining a contract Code for the account; in practical applications, only the hash value of the contract Code is usually maintained in the Code field; thus, the Code field is also commonly referred to as Codehash field.
A Storage field for maintaining the stored contents of the account (default field value is null); for a contract account, a separate storage space is generally allocated to store the storage content of the contract account; this separate storage space is commonly referred to as the account store for the contract account. The stored content of the contract account is stored in the independent storage space by a data structure which is generally constructed into MPT (Merkle Patricia Trie) trees; among them, the MPT tree constructed based on the stored contents of the contract account is also commonly referred to as Storage tree. Whereas the Storage field typically only maintains the root node of the Storage tree; thus, the Storage field is also commonly referred to as StorageRoot field.
For the external account, the field values of the Code field and the Storage field shown above are null values.
For most blockchain projects, merkle trees are typically used; or store and maintain data based on the Merkle tree data structure. Taking the ethernet as an example, the ethernet uses an MPT tree (a Merkle tree variant) as a data organization form, which is used to organize and manage important data such as account status, transaction information, and the like.
The ethernet house designs three MPT trees, an MPT status tree, an MPT transaction tree, and an MPT receipt tree, respectively, for the data in the blockchain that needs to be stored and maintained. In addition to the above three MPT trees, there is actually one Storage tree built based on the stored contents of the contract account.
An MPT state tree, which is an MPT tree organized by account state data for all accounts in the blockchain; MPT transaction trees, which are MPT trees organized from transaction (transaction) data in a blockchain; the MPT receipt tree is an MPT tree organized by transaction (receipt) receipts corresponding to each transaction generated after the execution of the transactions in the block. The hash values of the root nodes of the MPT status tree, MPT transaction tree, and MPT receipt tree shown above are eventually added to the block header of the corresponding block.
Wherein, the MPT transaction tree and the MPT receipt tree correspond to blocks, i.e. each block has its own MPT transaction tree and MPT receipt tree. Whereas the MPT state tree is a global MPT tree and does not correspond to a particular block, but covers account state data for all accounts in the blockchain.
It should be noted that, each time the blockchain generates a latest block, after the transaction in the latest block is executed, the account status of the accounts (which may be external accounts or contract accounts) related to the executed transaction in the blockchain will also generally change accordingly;
For example, when a "transfer transaction" in a block is completed, the balances of the transfer account and the transfer account associated with the "transfer transaction" (i.e., the field values of the Balance fields of these accounts) will typically change.
After the transaction in the latest block generated by the block chain is executed, the node equipment needs to construct an MPT state tree according to the current account state data of all accounts in the block chain because the account state in the current block chain is changed, so as to maintain the latest state of all accounts in the block chain.
That is, each time a latest block is generated in the blockchain, and after the transaction in the latest block is executed, the account state in the blockchain is changed, and the node device needs to reconstruct an MPT state tree based on the latest account state data of all accounts in the blockchain. In other words, each block in the blockchain has an MPT state tree corresponding to it; the MPT status tree maintains the most current account status for all accounts in the blockchain after transactions in the blockchain have been executed.
In practical applications, whether public, private or federated, it is possible to provide smart contract (smart contract) functionality. Intelligent contracts on a blockchain are contracts on a blockchain that can be executed by a transaction trigger. The smart contracts may be defined in the form of codes.
Taking the ethernet as an example, a user is supported to create and invoke some complex logic in the ethernet network. The ethernet is used as a programmable blockchain, and the core of the ethernet is an Ethernet Virtual Machine (EVM), and each ethernet node can run the EVM. EVM is a graphics-based virtual machine through which various complex logic can be implemented. The user's issuing and invoking of the smart contract in the ethernet is running on the EVM. In fact, the EVM runs directly on virtual machine code (virtual machine bytecode, hereinafter "bytecode"), so the smart contract deployed on the blockchain may be bytecode.
As shown in fig. 1, bob sends a transaction (transaction) containing information to create a smart contract to the ethernet network, and each node may execute the transaction in the EVM. The From field of the transaction in fig. 1 is used To record an address of an account initiating creation of an intelligent contract, the contract code stored by the field value of the Data field of the transaction may be a byte code, and the field value of the To field of the transaction is an account null. After agreement is reached between nodes through the consensus mechanism, the intelligent contract is successfully created, and the subsequent user can call the intelligent contract.
After the intelligent contract is created, a contract account corresponding to the intelligent contract appears on the blockchain and has a specific address; for example, "0x68e12cf284 …" in each node in FIG. 1 represents the address of this contract account created; the contract Code (Code) and the account store (Storage) will be saved in the account store of the contract account. The behavior of the smart contract is controlled by the contract code, and the account store of the smart contract maintains the state of the contract. In other words, the smart contract causes a virtual account to be generated on the blockchain that includes the contract code and account store.
The foregoing mentions that the Data field containing the transaction that created the smart contract holds may be the bytecode of the smart contract. Bytecode consists of a series of bytes, each of which can identify an operation. Based on various aspects 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, a high-level language such as Solidity, serpent, LLL language may be employed. For smart contract code written in a high-level language, it may be compiled by a compiler to generate bytecodes that may be deployed onto a blockchain.
Taking Solidity language as an example, the contract code written with it is very similar to classes (classes) in object-oriented programming languages, and multiple members can be declared in a contract, including state variables, functions, function modifiers, events, and so on. The state variable is a value permanently stored in an account store (Storage) field of the smart contract for saving the state of the contract.
Still taking the ethernet as an example, as shown in fig. 2, bob sends a transaction containing the call intelligent contract information to the ethernet network, and each node can execute the transaction in the EVM. The From field of the transaction in fig. 2 is used for recording the address of the account initiating the call of the smart contract, the To field is used for recording the address of the called smart contract, and the Data field of the transaction is used for recording the method and parameters for calling the smart contract. 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 blockchain node (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, all execution records and data are stored on the blockchain, so that when the transaction is executed, transaction credentials which cannot be tampered and cannot be lost are stored on the blockchain.
A schematic diagram of creating a smart contract and invoking a smart contract is shown in fig. 3. To create an intelligent contract in the ethernet, the intelligent contract needs to be written, changed into byte codes, deployed to a blockchain and the like. The intelligent contract is called in the Ethernet, a transaction pointing to the intelligent contract address is initiated, EVM of each node can execute the transaction respectively, and intelligent contract codes are distributed and run in the virtual machine of each node in the Ethernet network.
The event mechanism of an intelligent contract is one way in which the intelligent contract interacts with an off-chain entity. For intelligent contracts deployed on blockchains, it is often not possible to interact directly with off-chain entities; for example, the intelligent contract typically cannot send the calling result of the intelligent contract to the calling initiator of the intelligent contract point-to-point after the completion of the call.
The calling results (including intermediate results and final calling results) generated during the calling process of the intelligent contract are generally recorded in the form of events (event) into a transaction log (transactions) of the transaction calling the intelligent contract, and are stored in the storage space of the node device. An off-chain entity needing 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, using the Ethernet as an example, the transaction log may ultimately be stored in the MPT receipt tree described above as part of the receipt (receipt) of the transaction pen invoking the smart contract. And the off-chain entity interacting with the intelligent contract can monitor the transaction receipts on the MPT receipt tree stored in the storage space of the node device and acquire events generated by the intelligent contract from the monitored transaction receipts.
Intelligent contracts deployed on blockchains can generally only reference data content stored on blockchains; in practical applications, however, for some complex business scenarios implemented based on smart contract technology, smart contracts may also need to reference external data on some off-chain data entities.
In this scenario, the intelligent contracts deployed on the blockchain may reference data on data entities outside the chain through the Oracle predictor, thereby enabling data interactions between the intelligent contracts and the real world data entities. Wherein the data entities outside the chain may include, for example, centralized servers or data centers deployed outside the chain, etc.
It should be noted that, the cross-chain relay is used to connect two blockchains, and the Oracle predictor is used to connect the blockchain and the data entity outside the chain, so as to realize the data interaction between the blockchain and the real world.
In practical application, when a prophetic contract on a blockchain is deployed, a prophetic contract corresponding to the prophetic contract can be deployed on the blockchain; the intelligent contracts of the propulsor are used for maintaining external data sent to the intelligent contracts on the blockchain by the propulsor; for example, external data that is predictive of smart contracts issued to blockchains may be stored in the account memory space of the predictive smart contracts.
When a target smart contract on the blockchain is called, external data required by the target smart contract can be read from the account storage space of the foresight smart contract to complete the calling process of the smart contract.
When external data is transmitted to the intelligent contract on the blockchain, the prophetic machine may adopt an active transmission mode or a passive transmission mode.
In one implementation, the data entity outside the chain may sign external data that needs to be provided to the target intelligent contract with the private key of the predictor and send the signed external data to the predictor intelligent contract; for example, in time, the signed external data may be sent to the predictor smart contract by a periodic transmission;
The intelligent contract of the propranator can maintain a CA certificate of the propranator, after receiving external data sent by a data entity outside the chain, the public key of the propranator maintained in the CA certificate can be used for verifying the signature of the external data, and after the signature passes the verification, the external data sent by the data entity outside the chain is stored in the account storage space of the intelligent contract of the propranator.
In another implementation, when a target smart contract on a blockchain is invoked, if external data required by the target smart contract is not read from the account storage space of the predictor smart contract, the predictor smart contract may interact with the predictor using an event mechanism of the smart contract, and the external data required by the target smart contract is sent to the account storage space of the predictor smart contract by the predictor.
For example, when a target smart contract on a blockchain is invoked, if external data required by the target smart contract is not read from the account storage space of the predictive smart contract, at this time, the predictive smart contract may generate an external data acquisition event, record the external data acquisition event into a transaction log of the transaction invoking the smart contract, and store the transaction log into the storage space of the node device; the predictor may monitor a transaction log generated by the predictor smart contract stored in the storage space of the node device, and after monitoring an external data acquisition event in the transaction log, respond to the monitored external data acquisition event, and send external data required by the target smart contract to the predictor smart contract.
Referring to fig. 4, fig. 4 is a schematic diagram of a digital stamp using system based on a blockchain according to an exemplary embodiment of the present disclosure.
In a blockchain-based digital stamp use system as shown in fig. 4, a smart contract may be deployed on the blockchain. Wherein the smart contract may include smart contract code for signing the electronic file; in particular, the smart contract code of the smart contract may include a smart contract code corresponding to signature verification logic, a smart contract code corresponding to signature logic, and so on. In practical application, the signature verification logic can be realized by executing the intelligent contract code corresponding to the signature verification logic in the intelligent contract, and signature verification is carried out on the electronic file to be signed and the digital seal; by executing the intelligent contract code corresponding to the signature logic in the intelligent contract, the signature logic can be realized, and the electronic file to be signed is signed based on the digital seal.
It should be noted that, the specific process of creating and calling the smart contract may refer to the foregoing process of creating and calling the smart contract, which is not described herein.
In particular implementations, a user may initiate a transaction to invoke the smart contract deployed on the blockchain through a client establishing a connection with a node device in the blockchain. When the node equipment in the blockchain receives the transaction, the transaction can be sent to other node equipment in the blockchain so as to carry out consensus processing on the transaction, and after the transaction consensus is passed, an intelligent contract code in the intelligent contract is executed to realize signature processing on the electronic file.
In practical applications, the client may be disposed 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 (PDAs, personal DIGITAL ASSISTANTS), etc.; likewise, the electronic device added as the node device to the blockchain may be a server, a computer, a mobile phone, a tablet device, a notebook computer, a palm computer, etc.; this description is not limiting.
Referring to fig. 5, fig. 5 is a flowchart illustrating a method for using a blockchain-based digital stamp according to an exemplary embodiment of the present disclosure.
In connection with the blockchain-based digital stamp use system shown in fig. 4, the blockchain-based digital stamp use method described above may be applied to a node device in the blockchain shown in fig. 4; the digital seal using method based on the block chain can comprise the following steps:
Step 501, receiving a digital seal use transaction initiated by a digital seal user; wherein the digital seal use transaction comprises an electronic file to be signed;
Step 502, in response to the digital seal use transaction, invoking signature verification logic corresponding to an intelligent contract code in the intelligent contract, 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 by the digital seal;
step 503, 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 the intelligent contract code in the intelligent contract, obtaining the digital seal stored in the blockchain, and performing signature processing on the electronic file to be signed based on the digital seal.
In this embodiment, smart contracts may be deployed on the blockchain described above. A user who needs to use a digital stamp (referred to as a digital stamp user) can initiate a transaction (referred to as a digital stamp use transaction) for invoking the smart contract deployed on the blockchain through a client that establishes a connection with a node device in the blockchain; wherein the digital stamp use transaction may include an electronic file to be signed.
In this embodiment, the node device in the blockchain may respond to the digital stamp use transaction, call signature verification logic corresponding to the intelligent contract code in the intelligent contract, that is, 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 stamp use transaction, and verify whether the identified file type of the electronic file to be signed matches a signature type bound by the digital stamp to be used by the digital stamp user.
Specifically, with reference to the foregoing process of persisting certification data in a blockchain, the client may construct a digital stamp use transaction for invoking the intelligent contract deployed on the blockchain, and issue the digital stamp use transaction to the blockchain for certification. That is, the node device in the blockchain that interfaces with the client may first receive the digital stamp use transaction and then send the digital stamp use transaction to other node devices in the blockchain. When receiving the digital seal using transaction, each node device in the block chain can carry out consensus processing on the digital seal using transaction. After agreement is reached, node devices in the blockchain may package the digital stamp use transactions into blocks where persistent certification is performed.
For a digital seal use transaction packaged into a block, the node equipment in the block chain can respond to the digital seal use transaction, execute an intelligent contract code corresponding to signature verification logic in the intelligent contract, identify the file type of an electronic file to be signed in the digital seal use transaction, and verify whether the identified file type of the electronic file to be signed is matched with the signature type bound by the digital seal needed to be used by a digital seal user.
In practical application, the digital seal using party can specifically represent national administrative authorities, public institutions, social groups or enterprises and the like needing to use the seal in work, and the digital seal using party can be one user or a user group consisting of a plurality of users; the use approval party corresponding to the digital seal can be specifically an approval party with approval authority for the digital seal user to use the digital seal, and the use approval party can be one or a plurality of use approval parties; this description is not limiting.
Taking an enterprise as an example, the enterprise can be used as a digital seal user by using a digital seal representing the official seal of the enterprise.
Specifically, the enterprise may initiate a digital stamp use transaction for using the enterprise's official seal through a client establishing a connection with a node device in the blockchain, for example: one employee can be selected from the staff of the enterprise as a representative of the enterprise, and a digital stamp use transaction is initiated through the client. The node device in the blockchain can respond to the digital seal use transaction, 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 digital seal use transaction, and verify whether the identified file type of the electronic file to be signed is matched with the signature type bound by the digital seal.
In one embodiment shown, the electronic file to be signed may be processed based on NLP (Natural Language Processing ) algorithm to identify the file type of the electronic file to be signed.
In practical applications, the document type of the electronic document to be signed may be an administrative notice of an enterprise, and checks, invoices, etc. of the enterprise, which is not limited in this specification.
It should be noted that if the electronic file to be signed is a file stored in an image form (for example, 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 text in the identified electronic file to be signed may be processed based on an NLP algorithm to identify the file type of the electronic file to be signed.
In one embodiment, the digital stamp-using transaction may further include an identification of the digital stamp that the digital stamp-using party 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; when determining the signature type bound with the digital seal needed by the digital seal user, the method can search the signature type corresponding to the identification of the digital seal in the corresponding relation based on the identification of the digital seal in the digital seal use transaction, and determine the searched signature type as the signature type bound with the digital seal.
It should be noted that, the correspondence between the identifier of the digital stamp and the signature type of the digital stamp may be specifically stored in the storage space of the 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 the file type allowed to use the digital seal for signature processing; the signature types of different types of digital stamps may be different. The types of the digital seal can comprise: official seal, financial seal, invoice seal, contract seal, legal seal, and the like; the signature types bound with the digital seals of the respective types can be set based on actual requirements, for example: the signature types bound to the business's official seal may include: administrative notices of the enterprise, etc.; the signature types bound to the financial signature may include: checks, invoices, etc.
For example, the client used by the claimant of the digital stamp (i.e. the user claimant of the digital stamp) may output a type binding interface as shown in fig. 6 to the claimant of the digital stamp after the claimant is successful. As shown in fig. 6, the claimant of the digital stamp may input a file type that is allowed to be signed using the digital stamp in the type binding interface, and click a "confirm" button in the type binding interface after completing the input; when the client detects the clicking operation aiming at the 'confirm' button, the file type input by the claimant of the digital seal can be used 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 blockchain for storing.
The correspondence between the identification of the digital stamp stored in the blockchain and the signature type of the digital stamp is assumed as shown in table 1 below:
TABLE 1
Subsequently, if the identifier of the digital stamp that the digital stamp user needs to use (i.e., the identifier of the digital stamp in the digital stamp use transaction) is the identifier 1, the type a may be determined as a signature type bound to the digital stamp; if the identification of the digital stamp needed by the digital stamp user is the identification 2, the type A and the type B can be determined as signature types bound with the digital stamp; and so on.
When the signature type bound with the digital seal needed by the digital seal user is determined, the file type of the identified 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 file type of the identified electronic file to be signed is the same as any signature type bound with the digital seal is determined; if the electronic files are the same, the file type of the identified electronic file to be signed is considered to be matched with the signature type bound by the digital seal; if the identified file type of the electronic file to be signed and all signature types bound with the digital seal are different, the identified file type of the electronic file to be signed can be considered to be not matched with the signature type bound with the digital seal.
Continuing with table 1 above as an example, if the identifier of the digital stamp that the digital stamp user needs to use is identifier 2 and the identified file type of the electronic file to be signed in the digital stamp use transaction is type B, it may be determined that the identified file type of the electronic file to be signed matches the signature type bound by the digital stamp.
In another example, if the identifier of the digital stamp that the digital stamp user needs to use is identifier 2 and the file type of the identified electronic file to be signed in the digital stamp use transaction is type C, it may be determined that the file type of the identified electronic file to be signed does not match the signature type bound by the digital stamp.
In this embodiment, in the case that the file type of the identified electronic file to be signed in the transaction using the digital stamp is verified with the signature type bound by the digital stamp to be used by the party using the digital stamp, if the identified file type of the electronic file to be signed matches with the signature type bound by the digital stamp, 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 stamp stored in the blockchain is obtained, and signature processing is performed on the electronic file to be signed based on the obtained digital stamp.
In one embodiment, the digital stamp-using transaction may further include an identification of the digital stamp that the digital stamp-using party needs to use. In this case, the digital stamp stored in the blockchain corresponding to the identification of the digital stamp in the digital stamp-using transaction may be acquired as the digital stamp to be used by the digital stamp-using party based on the identification of the digital stamp in the digital stamp-using transaction.
In one embodiment, the digital stamp may include a pattern image of the digital stamp. In this case, when the electronic document to be signed is signed based on the digital stamp, the signature position in the electronic document to be signed may be first identified, then the pattern image of the digital stamp may be added to the signature position, and the pattern image of the digital stamp added to the signature position may be image-fused with the electronic document to be signed. And then, displaying the pattern image of the digital seal at the signature position in the image of the electronic file displayed to the user for the user to view.
Further, in one embodiment, the pattern image of the digital stamp may be visualized to fuse the identity information of the claimant of the digital stamp. Taking a pattern image of the digital seal as shown in fig. 7 as an example, an "SFA" in the pattern image is watermark information of identity information a of enterprise a as a claimant of the digital seal; in this way, the identity information a of the enterprise a can be viewed by the knowledgeable person through the watermark information.
In one embodiment, after the electronic file to be signed is signed based on the digital seal, a signature record corresponding to the digital seal can be generated, and the generated signature record is issued to the blockchain for certification; or the generated signature record can be issued to another blockchain (called a judicial chain) for storing judicial data, which is in cross-chain connection with the blockchain for storing the judicial data. The signature record can record information such as related information of a digital seal user, related information of the digital seal, signature time, signature place (for example, positioning position information submitted by the digital seal user), original content (or data abstract) of an electronic file to be signed and the like; specifically, the method can be preset by technicians according to actual requirements.
In the illustrated embodiment, under the condition that the file type of the identified electronic file to be signed in the transaction using the digital seal is verified with the signature type bound by the digital seal to be used by the digital seal user, if the file type of the identified electronic file to be signed is not matched with the signature type bound by the digital seal, a digital seal illegal use record corresponding to the digital seal can be generated, and the generated digital seal illegal use record is issued to the blockchain for certification; or the generated illegal use record of the digital seal can be issued to a judicial chain for certification. The digital stamp illegal use record can record information such as identity information (namely identity information of a user who illegally uses the digital stamp) in a digital stamp use transaction, related information of the digital stamp, illegal use time, illegal use place (for example, positioning position information submitted by the user who illegally uses the digital stamp), original content (or data abstract) of an electronic file to be signed and the like; specifically, the method can be preset by technicians according to actual requirements.
In one embodiment, the digital stamp-using transaction may further include identity information of the digital stamp-using party. In addition, the binding relation 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; when determining the identity information of the legal user bound with the digital stamp needed to be used by the digital stamp user, the identity information corresponding to the digital stamp identification can be searched in the binding relation based on the digital stamp identification in the digital stamp use transaction, and the searched identity information is determined as the identity information of the legal user bound with the digital stamp.
It should be noted that, the binding relationship between the digital stamp and the identity information of the legal user of the digital stamp may be 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 the claimant of the digital seal, or the claimant of the digital seal may be the user who binds the identity information with the digital seal after successfully claimant of the digital seal, which is not limited in this specification.
For example, the client used by the claimant of the digital stamp may output a use registration interface as shown in fig. 8 to the claimant of the digital stamp after the claimant is successful. As shown in fig. 8, the claimant of the digital stamp can input the identity information of the user permitted to use the digital stamp in the use registration interface, and click a "confirm" button in the use registration interface after the input is completed; when the client detects the clicking operation aiming at the 'confirm' button, the identity information input by the claimant of the digital seal can be used 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 card.
The correspondence between the identification of the digital stamp stored in the blockchain and the signature type of the digital stamp is assumed as shown in table 2 below:
TABLE 2
Subsequently, if the identifier of the digital stamp that the digital stamp user needs to use (i.e., the identifier of the digital stamp in the digital stamp use transaction) is the identifier 1, the identity information of the legal user bound to the digital stamp includes: identity information of claimant 1 (i.e., claimant of the digital stamp of claimant 1); if the identification of the digital stamp to be used by the digital stamp user is the identification 2, the identity information of the legal user bound with the digital stamp comprises: identity information of claimant 2 (i.e. claimant of the digital stamp claimant 2), identity information of user 1, identity information of user 2; and so on.
In this case, before invoking signature verification logic corresponding to the intelligent contract code in the intelligent contract to verify the electronic file to be signed in the digital seal using transaction and the digital seal, the identity information of the legal user bound with the digital seal stored in the blockchain may be verified, that is, it is determined whether the identity information in the digital seal using transaction is matched with the identity information of any legal user bound with the digital seal; if the digital seal is matched, the identity information in the digital seal using transaction can be considered to pass verification; if the identity information in the digital seal using transaction is not matched with the identity information of all legal users bound with the digital seal, the identity information verification in the digital seal using transaction can be considered to be failed.
If the verification of the identity information in the digital seal using transaction is passed, 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 digital seal using transaction and the digital seal.
However, if the verification of the identity information in the digital seal use transaction is not passed, a digital seal illegal use record corresponding to the identity information in the digital seal use transaction can be generated, and the generated digital seal illegal use record is issued to the blockchain for verification; or the generated illegal use record of the digital seal can be issued to a judicial chain for certification. The digital stamp illegal use record can record information such as identity information (namely identity information of a user who illegally uses the digital stamp) in a digital stamp use transaction, related information of the digital stamp, illegal use time, illegal use place (for example, positioning position information submitted by the user who illegally uses the digital stamp), original content (or data abstract) of an electronic file to be signed and the like; specifically, the method can be preset by technicians according to actual requirements.
In the illustrated embodiment, in the case of verifying the file type of the identified electronic file to be signed in the above-mentioned digital stamp-using transaction with the signature type of the digital stamp binding that the above-mentioned digital stamp-using party needs to use, if the file type of the identified electronic file to be signed does not match with the signature type of the digital stamp binding, referring to the event mechanism of the aforementioned smart contract, the smart contract may generate an event corresponding to the legal user of the digital stamp binding (referred to as a digital stamp illegal use event); the illegal use event of the digital stamp is used for indicating that the digital stamp is illegally used.
In this case, when the client of any legal user of the digital stamp indicated by the digital stamp illegal use event acquires the digital stamp illegal use event, a prompt message indicating that the digital stamp is illegally used may be output to the legal user in response to the digital stamp illegal use event, for example: a text box showing that the digital stamp is illegally used can be output to the legal user; or can output audible and visual alarm to the legal user according to preset alarm audible and visual alarm.
Specifically, the digital stamp illegal use event may be recorded in a transaction log of the digital stamp use transaction or an intelligent contract log of the intelligent contract, and stored in the blockchain.
The client of the legal user can acquire the illegal use event of the digital stamp by monitoring the transaction log or the intelligent contract log stored in the blockchain, and respond to the illegal use event of the digital stamp to output prompt information indicating that the digital stamp is illegally used to the legal user.
Or the client of the legal user can subscribe the illegal use event of the digital stamp with the SDK serving as an event notification center arranged on the node equipment in the block chain, and when the SDK detects that the illegal use event of the digital stamp is generated, the illegal use event of the digital stamp can be sent to the client of the legal user, so that the client of the legal user can acquire the illegal use event of the digital stamp, and prompt information indicating that the digital stamp is illegally used is output to the legal user in response to the illegal use event of the digital stamp.
In one embodiment shown, for a digital stamp user, the identity information of the digital stamp user may include: the digital stamp uses a public key in CA (Certificate Authority) certificates held by the party.
In practical application, on one hand, different digital seal users hold different CA certificates, and public keys and private keys in the different CA certificates are different; on the other hand, a public key is a public key, and a private key is a private key held by a user. Thus, for a digital stamp user, the public key in the CA certificate held by the digital stamp user may be used as the identity information for referring to the digital stamp user.
Further, in one embodiment shown, for a digital stamp user, the digital stamp user's identity information may also include a combination of one or more of the following: the identity of the user of the digital seal (such as account login password, face information or fingerprint information); the block chain account identification 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 about the party using the digital stamp.
In the illustrated embodiment, before invoking the signing logic corresponding to the intelligent contract code in the intelligent contract to obtain the digital seal, and signing the electronic file to be signed based on the digital seal, invoking the usage confirmation logic corresponding to the intelligent contract code in the intelligent contract to instruct the claimant of the digital seal to conduct usage confirmation on the digital seal, invoking the signing logic corresponding to the intelligent contract code in the intelligent contract after obtaining the usage confirmation result of the claimant on the digital seal to obtain the digital seal, and signing the electronic file to be signed based on the digital seal.
Further, in one illustrated embodiment, referring to the event mechanism of the aforementioned smart contract, the smart contract may generate an event (referred to as a usage validation event) corresponding to the claimant of the digital stamp; wherein the usage confirmation event is used for indicating a claimant of the digital seal to confirm the usage of the digital seal.
In this case, the claimant indicated by the use confirmation event, upon acquisition of the use confirmation event, may perform use confirmation on the digital stamp in response to the use confirmation event, for example: the client used by the claimant can respond to the use confirmation event to display the related information of the digital seal user and the digital seal to the claimant, and the claimant 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 a smart contract log of the smart contract, and stored in the blockchain.
The claimant may obtain the usage confirmation event by listening to the transaction log or the smart contract log stored in the blockchain, and respond to the usage confirmation event to perform usage confirmation on the digital stamp.
Or the claimant can subscribe to the use confirmation event with an SDK as an event notification center arranged on the node equipment in the blockchain, and when the SDK detects that the use confirmation event is generated, the claimant can send the use confirmation event to the claimant so that the claimant can acquire the use confirmation event and respond to the use confirmation event to carry out use confirmation on the digital seal.
In the above technical solution, the node device in the blockchain may respond to the received digital stamp using transaction initiated by the digital stamp using party, invoke signature verification logic in the intelligent contract deployed on the blockchain, identify the file type of the electronic file to be signed in the digital stamp using transaction, verify whether the identified file type of the electronic file to be signed matches the signature type bound to the digital stamp, and if the identified file type of the electronic file to be signed matches the signature type bound to the digital stamp, further invoke signature logic in the intelligent contract to obtain the digital stamp stored in the blockchain, and perform signature processing on the electronic file to be signed in the digital stamp using transaction based on the digital stamp. 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 matched with the signature type bound by the digital seal needed 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 blockchain-based digital stamp use system according to an exemplary embodiment of the present disclosure.
In a blockchain-based digital stamp use system as shown in fig. 9, a smart contract may be deployed on the blockchain. Wherein the smart contract may include smart contract code for signing the electronic file; specifically, the smart contract code of the smart contract may include a smart contract code corresponding to signature logic, or the like. 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 electronic file to be signed is signed based on the digital seal.
It should be noted that, the specific process of creating and calling the smart contract may refer to the foregoing process of creating and calling the smart contract, which is not described herein.
In specific implementation, a user can initiate a digital seal use request through a client end which establishes connection with a Baas (Blockchain AS A SERVICE) platform; the Baas platform may establish connection with the client and the node device in the blockchain respectively. When receiving the digital seal using request, the Baas platform can identify the file type of the electronic file to be signed in the digital seal using request, check whether the identified file type of the electronic file to be signed is matched with the signature type bound by the digital seal, and send a transaction for calling the intelligent contract deployed on the block chain to 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 by the digital seal. When the node equipment in the blockchain receives the transaction, the transaction can be sent to other node equipment in the blockchain so as to carry out consensus processing on the transaction, and after the transaction consensus is passed, an intelligent contract code in the intelligent contract is executed so as to realize signature processing on the electronic file to be signed.
In practical applications, the client may be disposed 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 (PDAs, personal DIGITAL ASSISTANTS), etc.; the Baas platform can be deployed on an electronic device, which can be a server, a computer, etc.; the electronic device added into the blockchain as the node device can be a server, a computer, a mobile phone, a tablet device, a notebook computer, a palm computer and the like; this description is not limiting.
Referring to fig. 10, fig. 10 is a flowchart illustrating another blockchain-based digital stamp using method according to an exemplary embodiment of the present disclosure.
In connection with the blockchain-based digital stamp use system shown in fig. 9, the blockchain-based digital stamp use method described above may be applied to the Baas platform shown in fig. 9; the digital seal using method based on the block chain can comprise the following steps:
Step 1001, receiving a digital seal use request initiated by a digital seal user; wherein the digital seal use request comprises an electronic file to be signed;
Step 1002, in response to the digital seal use request, identifying a 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 a signature type bound by 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 device, so that the node device 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 blockchain, and performs signature processing on the electronic file to be signed based on the digital seal.
In this embodiment, smart contracts may be deployed on the blockchain described above. A user needing to use the digital seal (called a digital seal user) can initiate a digital seal use request through a client end which establishes connection with the Baas platform; the digital stamp use request may include an electronic file to be signed.
In this embodiment, the Baas platform may identify a file type of the electronic file to be signed in the digital stamp use request in response to the digital stamp use request, and verify whether the identified file type of the electronic file to be signed matches a signature type bound by the digital stamp to be used by the digital stamp user.
In this embodiment, in the case of verifying that the file type of the identified electronic file to be signed in the digital stamp use request and the signature type bound by the digital stamp that needs to be used by the digital stamp user, if the identified file type of the electronic file to be signed matches the signature type bound by the digital stamp, the Baas platform may send an intelligent contract invoking transaction for invoking the intelligent contract deployed on the blockchain to a node device in the blockchain. The node equipment in the blockchain can respond to the intelligent contract call transaction, call 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 blockchain, and carry out signature processing on the electronic file to be signed based on the acquired digital seal.
In an embodiment shown, in the case of verifying the file type of the identified electronic file to be signed in the above-mentioned digital seal using transaction and the signature type bound to the digital seal that needs to be used by the above-mentioned digital seal using party, 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 above-mentioned Baas platform may generate a digital seal illegal use record corresponding to the digital seal, and issue the digital seal illegal use record to the blockchain for certification, or issue the digital seal illegal use record to a judicial chain that is in cross-chain interface with the blockchain for certification.
In one embodiment shown, the blockchain may have a binding relationship therein that verifies the identity information of the digital stamp and the legitimate user of the digital stamp; the digital stamp use request may further include identity information of the digital stamp use party.
In this case, before the above 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 matches the signature type bound to the digital stamp, the identity information of the legal user bound to the digital stamp stored in the blockchain is acquired first, and then verification is performed for the identity information of the digital stamp user in the digital stamp use request based on the acquired identity information of the legal user bound to the digital stamp; if the identity information of the digital stamp user in the digital stamp use request passes verification, the Baas platform can identify the file type of the electronic file to be signed and verify whether the identified file type of the electronic file to be signed is matched with the signature type bound by the digital stamp.
In an embodiment shown, in the case of verifying the file type of the identified electronic file to be signed in the digital seal using transaction with the signature type bound to the digital seal to be used by the digital seal using party, 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, the client of the legal user responds to the digital seal illegal use message to output prompt information indicating that the digital seal is illegally used to the legal user.
In one embodiment, if the verification of the identity information of the digital stamp user in the digital stamp use request is not passed, the Baas platform may generate a digital stamp illegal use record corresponding to the identity information of the digital stamp user, and issue the digital stamp illegal use record to the blockchain for certification, or issue the digital stamp illegal use record to a judicial chain that is in cross-chain docking with the blockchain for certification.
In one embodiment shown, 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 the legal user of the digital seal; a blockchain account identifier of a legal user of the digital stamp; image information of a physical seal held by a legal user of the digital seal.
In one embodiment shown, the legitimate user may be a claimant of the digital stamp.
In one embodiment shown, the Baas platform may instruct a claimant of the digital stamp to confirm use of the digital stamp before sending the smart contract invoking transaction to the node device, and send the smart contract invoking transaction to the node device after obtaining a result of confirmation of use of the digital stamp by the claimant.
Further, in one embodiment shown, an approval indication message may be sent by the Baas platform to the claimant to cause the claimant to acknowledge use of the digital stamp in response to the approval indication message.
In one embodiment, the blockchain may store a correspondence between the identification of the digital stamp and the signature type of the digital stamp; the digital stamp use transaction may also include an identification of the digital stamp.
In this case, the above Baas platform may determine, based on the correspondence of the certificates stored in the blockchain, a signature type corresponding to the identifier of the digital stamp in the transaction in which the digital stamp is used, and verify whether the file type of the identified electronic file to be signed matches the signature type corresponding to the identifier of the digital stamp.
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 embodiment shown, 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 be visually fused with the identity information of the digital stamp claimant.
It should be noted that, for a specific manner of executing the steps 1001 to 1003 by the Baas platform, reference may be made to a specific manner of executing the steps 501 to 503 by a node device in the blockchain-based digital seal claim method shown in fig. 5, which is not described herein in detail.
In the above technical solution, the Baas platform may respond to a received digital stamp use request initiated by a digital stamp user, identify a file type of an electronic file to be signed in the digital stamp use request, verify whether the identified file type of the electronic file to be signed matches a signature type bound to the digital stamp, and if the identified file type of the electronic file to be signed matches the signature type bound to the digital stamp, send an intelligent contract call transaction to a node device in a blockchain to call signature logic in the intelligent contract by the node device in the blockchain, obtain the digital stamp stored in the blockchain, and perform signature processing on the electronic file to be signed in the digital stamp use transaction based on the digital stamp. 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 matched with the signature type bound by the digital seal needed 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 foregoing embodiments of the blockchain-based digital stamp using method, the present specification also provides embodiments of a blockchain-based digital stamp using device.
Embodiments of the blockchain-based digital stamp using apparatus of the present specification may be applied to electronic devices. The apparatus embodiments may be implemented by software, or may be implemented by hardware or a combination of hardware and software. Taking software implementation as an example, the device in a logic sense is formed by reading corresponding computer program instructions in a nonvolatile memory into a memory by a processor of an electronic device where the device is located for operation. In terms of hardware, as shown in fig. 11, a hardware structure diagram of an electronic device where the blockchain-based digital seal using apparatus is located in the present specification is shown, and in addition to 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 generally includes other hardware according to the actual functions of the blockchain-based digital seal, which will not be described herein.
Referring to fig. 12, fig. 12 is a block diagram of a digital stamp using apparatus based on a blockchain according to an exemplary embodiment of the present disclosure. The digital stamp using apparatus 120 based on the blockchain may be applied to an electronic device as shown in fig. 10, which may be used as a node device in the blockchain, and an intelligent contract for signing an electronic file is deployed in the blockchain; the apparatus 120 may include:
A receiving module 1201 for receiving a digital stamp use transaction initiated by a digital stamp use party; wherein the digital seal use 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 a signature module 1203, 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 the intelligent contract code in the intelligent contract, obtaining the digital seal stored in the block chain, and performing signature processing on 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 a digital stamp illegal use record corresponding to the digital stamp if the identified file type of the electronic file to be signed is not matched with the signature type bound by the digital stamp;
The first certification storing module 1205 issues the illegal use records of the digital seal to the blockchain for certification; or issuing the illegal use record of the digital seal to a judicial chain in cross-chain docking with the block chain for certification.
In this embodiment, the blockchain stores a binding relationship between the digital stamp and identity information of a legal user of the digital stamp; the digital seal using transaction also comprises identity information of the digital seal using party;
the apparatus 120 may further include:
The verification module 1206 is used for verifying the identity information of the digital stamp user in the digital stamp use transaction based on the identity information of the legal user bound with the digital stamp stored in the blockchain before invoking 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 stamp;
The verification module 1202:
if the identity information of the digital seal user in the digital seal use transaction passes verification, invoking 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.
In this embodiment, the apparatus 120 may further include:
and a prompt module 1207, configured to generate a digital stamp illegal use event corresponding to a legal user bound to the digital stamp if the identified file type of the electronic file to be signed does not match the signature type bound to the digital stamp, so that when the client of the legal user acquires the digital stamp illegal use event, respond to the digital stamp illegal use event and output prompt information indicating that the digital stamp is illegally used to the legal user.
In this embodiment, the apparatus 120 may further include:
a second generation module 1208 that generates a digital stamp illegitimate use record corresponding to the identity information of the digital stamp-using party if the verification of the identity information of the digital stamp-using party in the digital stamp-using transaction is not passed;
a second certification module 1209, for issuing the illegal use record of the digital stamp to the blockchain for certification; or issuing the illegal use record of the digital seal to a judicial chain in cross-chain docking with the block chain for certification.
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 the legal user of the digital seal;
a blockchain account identifier of a legal user of the digital stamp;
image information of a physical seal held by a legal user of the digital seal.
In this embodiment, the legal user is a claimant of the digital stamp.
In this embodiment, the apparatus 120 may further include:
The confirmation module 1210 further invokes signing logic corresponding to an intelligent contract code in the intelligent contract, acquires the digital stamp stored in the blockchain, invokes the use confirmation logic corresponding to the intelligent contract code in the intelligent contract before signing the electronic file to be signed based on the digital stamp, instructs a claimator of the digital stamp to conduct use confirmation on the digital stamp, and further invokes signing logic corresponding to the intelligent contract code in the intelligent contract after acquiring a result of the use confirmation on the digital stamp by the claimator, acquires the digital stamp stored in the blockchain, and signs the electronic file to be signed based on the digital stamp.
In this embodiment, the confirmation module 1210:
And generating a use confirmation event corresponding to the claimant of the digital seal, so that the claimant responds to the use confirmation event to carry out use confirmation on the digital seal when acquiring the use confirmation event.
In this embodiment, the corresponding relationship between the identifier of the digital stamp and the signature type of the digital stamp is stored in the blockchain; the digital seal using transaction also comprises an identification of the digital seal;
The verification module 1202:
determining a signature type corresponding to the identification of the digital stamp in the digital stamp-using transaction based on the corresponding relation of the certificates stored in the blockchain, and checking whether the identified file type of the electronic file to be signed is matched with the signature type corresponding to the identification of the digital stamp;
The signature module 1203:
And acquiring the digital seal corresponding to the identification of the digital seal in the digital seal using transaction stored in the blockchain.
In this embodiment, the apparatus 120 may further include:
A third generation module 1211, configured to generate a signature record corresponding to the digital stamp after performing signature processing on the electronic file to be signed based on the obtained digital stamp;
A third certification module 1212 for issuing the generated signature record to the blockchain for certification; or issuing the generated signature record to a judicial chain in cross-chain connection with the blockchain for certification.
In this embodiment, the digital stamp 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 processing of the electronic file to be signed based on the digital seal comprises the following steps:
identifying a signature position in the electronic file to be signed;
And 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 pattern image visualization of the digital stamp incorporates the identity information of the claimant of the digital stamp.
Referring to fig. 13, fig. 13 is a block diagram of another blockchain-based digital stamp using device according to an exemplary embodiment of the present disclosure. The blockchain-based digital stamp using device 130 may be applied to an electronic device as shown in fig. 10, which may be used as a Baas platform for interfacing with node devices in the blockchain; an intelligent contract deployed in the blockchain for signing an electronic file; the apparatus 130 may include:
a receiving module 1301 for receiving a digital stamp use request initiated by a digital stamp user; wherein the digital seal use request comprises an electronic file to be signed;
The verification module 1302 is used for responding 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 by the digital seal;
And the signing module 1303 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 calls signing logic corresponding to an intelligent contract code in the intelligent contract in response to the intelligent contract calling transaction, acquires the digital seal stored in the block chain, and performs signing processing on the electronic file to be signed based on the digital seal.
In this embodiment, the apparatus 130 may further include:
a first generation module 1304, configured to generate a digital stamp illegal use record corresponding to the digital stamp if the identified file type of the electronic file to be signed does not match the signature type bound to the digital stamp;
The first evidence storage module 1305 issues the illegal use records 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 docking with the block chain for certification.
In this embodiment, the blockchain stores a binding relationship between the digital stamp and identity information of a legal user of the digital stamp; 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 verifies the identity information of the digital stamp user in the digital stamp use request based on the identity information of the legal user bound with the digital stamp stored in the blockchain 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 stamp;
the verification module 1302:
If the identification information of the digital stamp using party in the digital stamp using request passes verification, 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 stamp.
In this embodiment, the apparatus 130 may further include:
And the prompting module 1307 is used for sending a digital stamp illegal use message to a legal user bound with the digital stamp if the file type of the electronic file to be signed is not matched with the signature type bound with the digital stamp, so that when the client of the legal user acquires the digital stamp illegal use message, responding to the digital stamp illegal use message and outputting prompting information indicating that the digital stamp is illegally used to the legal user.
In this embodiment, the apparatus 130 may further include:
A second generation module 1308 for generating a digital stamp illegitimate use record corresponding to the identity information of the digital stamp using party if the verification of the identity information of the digital stamp using party in the digital stamp using transaction is not passed;
a second certification module 1309 for issuing the illegal use records of the digital seal to the blockchain for certification; or issuing the illegal use record of the digital seal to a judicial chain in cross-chain docking with the block chain for certification.
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 the legal user of the digital seal;
a blockchain account identifier of a legal user of the digital stamp;
image information of a physical seal held by a legal user of the digital seal.
In this embodiment, the legal user is a claimant of the digital stamp.
In this embodiment, the apparatus 130 may further include:
And a confirmation module 1310, before sending the intelligent contract invoking transaction to the node device, for instructing a claimant of the digital seal to confirm the use of the digital seal, and after obtaining the confirmation result of the claimant on the use of the digital seal, sending the intelligent contract invoking transaction to the node device.
In this embodiment, the confirmation module 1310:
and sending an approval indication message to the claimant so that the claimant responds to the approval indication message to carry out use confirmation on the digital seal.
In this embodiment, the corresponding relationship between the identifier of the digital stamp and the signature type of the digital stamp is stored in the blockchain; the digital seal using transaction also comprises an identification of the digital seal;
the verification module 1302:
and determining a signature type corresponding to the identification of the digital seal in the digital seal using transaction based on the corresponding relation of the certificates stored in the blockchain, and checking whether the identified file type of the electronic file to be signed is matched with the signature type corresponding to the identification of the digital seal.
In this embodiment, the digital stamp 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 visualization of the digital stamp fuses the identity information of the digital stamp claimant.
The implementation process of the functions and roles of each module in the above device is specifically shown in the implementation process of the corresponding steps in the above method, and will not be described herein again.
For the device embodiments, reference is made to the description of the method embodiments for the relevant points, since they essentially correspond to the method embodiments. The apparatus embodiments described above are merely illustrative, wherein the modules illustrated as separate components may or may not be physically separate, and the components shown as modules may or may not be physical, i.e., may be located in one place, or may be distributed over a plurality of network modules. Some or all of the modules may be selected according to actual needs to achieve the purposes of the present description. Those of ordinary skill in the art will understand and implement the present invention without undue burden.
The system, apparatus, module or unit set forth in the above embodiments may be implemented in particular by a computer chip or entity, or by a product having a certain function. A typical implementation device is a computer, which may be in the form of a personal computer, laptop computer, cellular telephone, camera phone, smart phone, personal digital assistant, media player, navigation device, email 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 volatile memory in a computer-readable medium, random Access Memory (RAM) and/or nonvolatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of computer-readable media.
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 storage media for a computer 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, read only 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 or other magnetic storage devices, or any other non-transmission medium, which can be used to store information that can be accessed by the computing device. Computer-readable media, as defined herein, does not include transitory computer-readable media (transmission media), such as modulated data signals and carrier waves.
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 one … …" does not exclude the presence of other like elements in a process, method, article or apparatus that comprises the element.
The foregoing describes specific embodiments of the present disclosure. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims can 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 are also possible or may be advantageous.
The terminology used in the one or more embodiments of the specification is for the purpose of describing particular embodiments only and is not intended to be limiting of the one or more embodiments of the specification. As used in this specification, one or more embodiments 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 or 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, these 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 of the present description. The word "if" as used herein may be interpreted as "at … …" or "at … …" or "in response to a determination" depending on the context.
The foregoing description of the preferred embodiment(s) is (are) merely intended to illustrate the embodiment(s) of the present invention, and it is not intended to limit the embodiment(s) of the present invention to the particular embodiment(s) described.
Claims (56)
1. A digital seal using method based on a block chain is applied to node equipment in the block chain; an intelligent contract deployed in the blockchain for signing an electronic file; the block chain stores the binding relation of the identity information of the digital seal and the legal user of the digital seal; the method comprises the following steps:
receiving a digital seal use transaction initiated by a digital seal user; the digital seal using transaction comprises an electronic file to be signed and identity information of a digital seal using party;
Responding to the digital seal use transaction, and 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, which is stored in the blockchain;
If the identity information of the digital seal user in the digital seal use transaction passes verification, invoking 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;
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 blockchain, and performing signature processing on the electronic file to be signed based on the digital seal.
2. The method of claim 1, the method further comprising:
If the identified file type of the electronic file to be signed is not matched with the signature type bound by the digital seal, generating a digital seal illegal use record corresponding to the digital seal;
Issuing the illegal use records of the digital seal to the blockchain for certification; or issuing the illegal use record of the digital seal to a judicial chain in cross-chain docking with the block chain for certification.
3. The method of claim 1, the method further comprising:
If the file type of the electronic file to be signed is not matched with the signature type bound by the digital seal, generating a digital seal illegal use event corresponding to a legal user bound by the digital seal, so that when the client of the legal user acquires the digital seal illegal use event, responding to the digital seal illegal use event and outputting prompt information indicating that the digital seal is illegally used to the legal user.
4. The method of claim 1, the method further comprising:
if the verification of the identity information of the digital seal user in the digital seal use transaction is not passed, generating a digital seal illegal use record corresponding to the identity information of the digital seal user;
Issuing the illegal use records of the digital seal to the blockchain for certification; or issuing the illegal use record of the digital seal to a judicial chain in cross-chain docking with the block chain for certification.
5. The method of claim 1, the identity information comprising a public key in a CA certificate held by a legitimate user of the digital stamp.
6. The method of claim 5, the identity information further comprising a combination of one or more of the following:
The identity of the legal user of the digital seal;
a blockchain account identifier of a legal user of the digital stamp;
image information of a physical seal held by a legal user of the digital seal.
7. The method of claim 1, wherein the legitimate user is a claimant of the digital stamp.
8. The method of claim 7, wherein the further invoking signature logic corresponding to the smart contract code in the smart contract obtains the digital stamp stored in the blockchain, and further comprises, before signing the electronic file to be signed based on the digital stamp:
invoking use confirmation logic corresponding to an intelligent contract code in the intelligent contract, indicating a claimant of the digital seal to confirm the use of the digital seal, further invoking signature logic corresponding to the intelligent contract code in the intelligent contract after acquiring a use confirmation result of the claimant to the digital seal, acquiring the digital seal stored in the block chain, and performing signature processing on the electronic file to be signed based on the digital seal.
9. The method of claim 8, the instructing the claimant of the digital stamp to confirm use of the digital stamp, comprising:
And generating a use confirmation event corresponding to the claimant of the digital seal, so that the claimant responds to the use confirmation event to carry out use confirmation on the digital seal when acquiring the use confirmation event.
10. The method of claim 1, wherein the blockchain has a correspondence between the identification of the digital stamp and the signature type of the digital stamp stored therein; the digital seal using transaction also comprises an identification of the digital seal;
The checking whether the file type of the identified electronic file to be signed is matched with the signature type bound by the digital seal comprises the following steps:
determining a signature type corresponding to the identification of the digital stamp in the digital stamp-using transaction based on the corresponding relation of the certificates stored in the blockchain, and checking whether the identified file type of the electronic file to be signed is matched with the signature type corresponding to the identification of the digital stamp;
The obtaining the digital stamp stored in the blockchain includes:
And acquiring the digital seal corresponding to the identification of the digital seal in the digital seal using transaction stored in the blockchain.
11. The method of claim 1, the method further comprising:
After signing the electronic file to be signed based on the obtained digital seal, generating a signature record corresponding to the digital seal;
Issuing the generated signature record to the blockchain for certification; or issuing the generated signature record to a judicial chain in cross-chain connection with the blockchain for certification.
12. The method of claim 1, wherein the digital stamp user is an enterprise; the digital seal is a official seal of the enterprise.
13. The method of claim 1, the digital stamp comprising a pattern image of the digital stamp;
The signing processing of the electronic file to be signed based on the digital seal comprises the following steps:
identifying a signature position in the electronic file to be signed;
And adding the pattern image of the digital seal to the signature position, and carrying out image fusion with the electronic file to be signed.
14. The method of claim 13, wherein the digital stamp pattern image visualization incorporates identity information of a claimant of the digital stamp.
15. A digital seal using method based on a block chain is applied to Baas platforms which are in butt joint with node equipment in the block chain; an intelligent contract deployed in the blockchain for signing an electronic file; the block chain stores the binding relation of the identity information of the digital seal and the legal user of the digital seal; the method comprises the following steps:
Receiving a digital seal use request initiated by a digital seal user; the digital seal use request comprises an electronic file to be signed and identity information of a digital seal user;
Responding to the digital seal use request, and 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, which is stored in the blockchain;
If the identity information of the digital stamp user in the digital stamp use request passes verification, 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 stamp;
If the identified file type of the electronic file to be signed is matched with the signature type bound by the digital seal, an intelligent contract calling transaction is sent to the node equipment, so that the node equipment responds to the intelligent contract calling transaction, signature logic corresponding to an intelligent contract code in the intelligent contract is called, the digital seal stored in the block chain is obtained, and signature processing is carried out on the electronic file to be signed based on the digital seal.
16. The method of claim 15, the method further comprising:
If the identified file type of the electronic file to be signed is not matched with the signature type bound by the digital seal, generating a digital seal illegal use record corresponding to the digital seal;
Issuing the illegal use records of the digital seal to the blockchain for certification; or issuing the illegal use record of the digital seal to a judicial chain in cross-chain docking with the block chain for certification.
17. The method of claim 15, the method 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 a digital seal illegal use message to a legal user bound with the digital seal, so that when the client of the legal user acquires the digital seal illegal use message, responding to the digital seal illegal use message and outputting prompt information indicating that the digital seal is illegally used to the legal user.
18. The method of claim 15, the method further comprising:
if the verification of the identity information of the digital seal user in the digital seal use transaction is not passed, generating a digital seal illegal use record corresponding to the identity information of the digital seal user;
Issuing the illegal use records of the digital seal to the blockchain for certification; or issuing the illegal use record of the digital seal to a judicial chain in cross-chain docking with the block chain for certification.
19. The method of claim 15, the identity information comprising a public key in a CA certificate held by a legitimate user of the digital stamp.
20. The method of claim 19, the identity information further comprising a combination of one or more of the following:
The identity of the legal user of the digital seal;
a blockchain account identifier of a legal user of the digital stamp;
image information of a physical seal held by a legal user of the digital seal.
21. The method of claim 15, wherein the legitimate user is a claimant of the digital stamp.
22. The method of claim 21, prior to sending a smart contract call transaction to the node device, further comprising:
And indicating a claimant of the digital seal to confirm the use of the digital seal, and sending an intelligent contract invoking transaction to the node equipment after acquiring a result of confirming the use of the digital seal by the claimant.
23. The method of claim 22, the instructing the claimant of the digital stamp to confirm use of the digital stamp, comprising:
and sending an approval indication message to the claimant so that the claimant responds to the approval indication message to carry out use confirmation on the digital seal.
24. The method of claim 15, wherein the blockchain has a correspondence between the identification of the digital stamp and the signature type of the digital stamp stored therein; the digital seal using transaction also comprises an identification of the digital seal;
The checking whether the file type of the identified electronic file to be signed is matched with the signature type bound by the digital seal comprises the following steps:
and determining a signature type corresponding to the identification of the digital seal in the digital seal using transaction based on the corresponding relation of the certificates stored in the blockchain, and checking whether the identified file type of the electronic file to be signed is matched with the signature type corresponding to the identification of the digital seal.
25. The method of claim 15, wherein the digital stamp-using party is an enterprise; the digital seal is a official seal of the enterprise.
26. The method of claim 15, the digital stamp comprising a pattern image of the digital stamp.
27. The method of claim 26, wherein the digital stamp style image visualization incorporates identity information of the digital stamp claimant.
28. A digital seal using device based on a block chain, which is applied to node equipment in the block chain; an intelligent contract deployed in the blockchain for signing an electronic file; the block chain stores the binding relation of the identity information of the digital seal and the legal user of the digital seal; the device comprises:
The receiving module is used for receiving a digital seal use transaction initiated by a digital seal user; the digital seal using transaction comprises an electronic file to be signed and identity information of a digital seal using party;
The verification module responds to the digital seal use transaction, and verifies 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, which is stored in the blockchain;
The verification module is used for calling signature verification logic corresponding to an intelligent contract code in the intelligent contract if verification of identity information of the digital seal user in the digital seal use transaction is passed, 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 the intelligent contract code in the intelligent contract if the identified file type of the electronic file to be signed is matched with the signature type bound by the digital seal, 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.
29. The apparatus of claim 28, the apparatus further comprising:
the first generation module is used for generating a digital stamp illegal use record corresponding to the digital stamp if the file type of the identified electronic file to be signed is not matched with the signature type bound by the digital stamp;
The first evidence storage module is used for issuing the illegal use records of the digital seal to the blockchain for evidence storage; or issuing the illegal use record of the digital seal to a judicial chain in cross-chain docking with the block chain for certification.
30. The apparatus of claim 28, the apparatus further comprising:
And the prompting module is used for generating a digital stamp illegal use event corresponding to a legal user bound with the digital stamp if the file type of the electronic file to be signed is not matched with the signature type bound with the digital stamp, so that when the client of the legal user acquires the digital stamp illegal use event, responding to the digital stamp illegal use event and outputting prompting information indicating that the digital stamp is illegally used to the legal user.
31. The apparatus of claim 28, the apparatus further comprising:
The second generation module is used for generating a digital stamp illegal use record corresponding to the identity information of the digital stamp using party if the identity information of the digital stamp using party in the digital stamp using transaction is not verified;
The second evidence storage module is used for issuing the illegal use records of the digital seal to the blockchain for evidence storage; or issuing the illegal use record of the digital seal to a judicial chain in cross-chain docking with the block chain for certification.
32. The apparatus of claim 28, the identity information comprising a public key in a CA certificate held by a legitimate user of the digital stamp.
33. The apparatus of claim 32, the identity information further comprising a combination of one or more of the following:
The identity of the legal user of the digital seal;
a blockchain account identifier of a legal user of the digital stamp;
image information of a physical seal held by a legal user of the digital seal.
34. The apparatus of claim 28, the legitimate user being a claimant of the digital stamp.
35. The apparatus of claim 34, the apparatus further comprising:
And the confirmation module is used for calling the use confirmation logic corresponding to the intelligent contract code in the intelligent contract before further calling the signing logic corresponding to the intelligent contract code in the intelligent contract to acquire the digital seal stored in the block chain and signing the electronic file to be signed based on the digital seal, indicating a claimator of the digital seal to confirm the use of the digital seal, and further calling the signing logic corresponding to the intelligent contract code in the intelligent contract after acquiring the use confirmation result of the claimator to the digital seal to acquire the digital seal stored in the block chain and signing the electronic file to be signed based on the digital seal.
36. The device of claim 35, the confirmation module to:
And generating a use confirmation event corresponding to the claimant of the digital seal, so that the claimant responds to the use confirmation event to carry out use confirmation on the digital seal when acquiring the use confirmation event.
37. The apparatus of claim 28, wherein the blockchain has stored therein a correspondence of an identification of the digital stamp to a signature type of the digital stamp; the digital seal using transaction also comprises an identification of the digital seal;
the verification module is used for:
determining a signature type corresponding to the identification of the digital stamp in the digital stamp-using transaction based on the corresponding relation of the certificates stored in the blockchain, and checking whether the identified file type of the electronic file to be signed is matched with the signature type corresponding to the identification of the digital stamp;
The signature module:
And acquiring the digital seal corresponding to the identification of the digital seal in the digital seal using transaction stored in the blockchain.
38. The apparatus of claim 28, the apparatus further comprising:
The third generation module is used for generating a signature record corresponding to the digital seal after signing the electronic file to be signed based on the acquired digital seal;
The third certificate storing module is used for releasing the generated signature record to the blockchain for certificate storing; or issuing the generated signature record to a judicial chain in cross-chain connection with the blockchain for certification.
39. The apparatus of claim 28, the digital stamp-using party being an enterprise; the digital seal is a official seal of the enterprise.
40. The apparatus of claim 28, the digital stamp comprising a pattern image of the digital stamp;
The signing processing of the electronic file to be signed based on the digital seal comprises the following steps:
identifying a signature position in the electronic file to be signed;
And adding the pattern image of the digital seal to the signature position, and carrying out image fusion with the electronic file to be signed.
41. The apparatus of claim 40 wherein the digital stamp pattern image visualization incorporates identity information of a claimant of the digital stamp.
42. A digital seal using device based on a block chain, which is applied to a Baas platform in butt joint with node equipment in the block chain; an intelligent contract deployed in the blockchain for signing an electronic file; the block chain stores the binding relation of the identity information of the digital seal and the legal user of the digital seal; the device comprises:
The receiving module is used for receiving a digital seal use request initiated by a digital seal user; the digital seal use request comprises an electronic file to be signed and identity information of a digital seal user;
The verification module responds to the digital seal use request and verifies 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, which is stored in the blockchain;
The verification module is used for 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 if the identification information of the digital seal user in the digital seal use request passes verification;
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 blockchain, and performs signature processing on the electronic file to be signed based on the digital seal.
43. The apparatus of claim 42, further comprising:
the first generation module is used for generating a digital stamp illegal use record corresponding to the digital stamp if the file type of the identified electronic file to be signed is not matched with the signature type bound by the digital stamp;
The first evidence storage module is used for issuing the illegal use records of the digital seal to the blockchain for evidence storage; or issuing the illegal use record of the digital seal to a judicial chain in cross-chain docking with the block chain for certification.
44. The apparatus of claim 42, further comprising:
And the prompting module is used for sending a digital seal illegal use message to a legal user bound with the digital seal if the 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 acquires the digital seal illegal use message, responding to the digital seal illegal use message and outputting prompting information indicating that the digital seal is illegally used to the legal user.
45. The apparatus of claim 42, further comprising:
The second generation module is used for generating a digital stamp illegal use record corresponding to the identity information of the digital stamp using party if the identity information of the digital stamp using party in the digital stamp using transaction is not verified;
The second evidence storage module is used for issuing the illegal use records of the digital seal to the blockchain for evidence storage; or issuing the illegal use record of the digital seal to a judicial chain in cross-chain docking with the block chain for certification.
46. The apparatus of claim 42, wherein the identity information comprises a public key in a CA certificate held by a legitimate user of the digital stamp.
47. The apparatus of claim 46, the identity information further comprising a combination of one or more of the following:
The identity of the legal user of the digital seal;
a blockchain account identifier of a legal user of the digital stamp;
image information of a physical seal held by a legal user of the digital seal.
48. The apparatus of claim 42, wherein the legitimate user is a claimant of the digital stamp.
49. The apparatus of claim 48, further comprising:
and the confirmation module is used for indicating a claimant of the digital seal to confirm the use of the digital seal before sending the intelligent contract calling transaction to the node equipment, and sending the intelligent contract calling transaction to the node equipment after acquiring the confirmation result of the claimant of the use of the digital seal.
50. The apparatus of claim 49, the confirmation module:
and sending an approval indication message to the claimant so that the claimant responds to the approval indication message to carry out use confirmation on the digital seal.
51. The apparatus of claim 42, wherein the blockchain has stored therein a correspondence of the identity of the digital stamp and the signature type of the digital stamp; the digital seal using transaction also comprises an identification of the digital seal;
the verification module is used for:
and determining a signature type corresponding to the identification of the digital seal in the digital seal using transaction based on the corresponding relation of the certificates stored in the blockchain, and checking whether the identified file type of the electronic file to be signed is matched with the signature type corresponding to the identification of the digital seal.
52. The apparatus of claim 42, wherein the digital stamp-using party is an enterprise; the digital seal is a official seal of the enterprise.
53. The apparatus of claim 42, wherein the digital stamp comprises a pattern image of the digital stamp.
54. The apparatus of claim 53 wherein the digital seal pattern image visualization incorporates identity information of the digital seal claimant.
55. An electronic device, comprising:
A processor;
A memory for storing processor-executable instructions;
Wherein the processor is configured to implement the method of any one of claims 1-14 or 15-27 by executing the executable instructions.
56. A computer readable storage medium having stored thereon computer instructions which, when executed by a processor, implement the method of any of claims 1-14 or 15-27.
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 CN112200569A (en) | 2021-01-08 |
| CN112200569B true 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) |
Families Citing this family (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 |
| 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 |
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 |
|---|
| 崔建远.合同解释语境中的印章及其意义.清华法学.2018,第12卷(第4期),第167-179页. * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112200569A (en) | 2021-01-08 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112101938B (en) | Digital seal using method and device based on block chain and electronic equipment | |
| CN111026789B (en) | Block chain-based electronic bill query method and device and electronic equipment | |
| CN112200569B (en) | Digital seal using method and device based on block chain and electronic equipment | |
| CN110766550B (en) | Asset query method and device based on block chain and electronic equipment | |
| TWI762818B (en) | Blockchain-based invoice creation method and device, electronic device | |
| CN111914023B (en) | Bill management method and device based on blockchain and electronic equipment | |
| CN111539731A (en) | Block chain-based federal learning method and device and electronic equipment | |
| US10956903B2 (en) | Obtaining a blockchain-based, real-name, electronic bill | |
| CN110458631B (en) | Bill number distribution method and device based on block chain and electronic equipment | |
| CN112650978B (en) | Infringement detection method and device based on block chain and electronic equipment | |
| US11423473B2 (en) | Blockchain-based leasing | |
| CN111681017A (en) | Goods batch true checking method and device based on block chain 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 | |
| CN112100588A (en) | Block chain-based digital seal application method and device and electronic equipment | |
| US11250438B2 (en) | Blockchain-based reimbursement splitting | |
| CN111639125A (en) | Resource circulation method and device based on block chain | |
| CN111402033A (en) | Asset information management method and device based on block chain | |
| CN111814193B (en) | Information sharing method, device and equipment | |
| CN111429250A (en) | Data management method and device in escort scene | |
| CN112258189A (en) | Block chain-based subscription management method and device and electronic equipment | |
| CN114331437A (en) | Block chain-based digital seal using method and device | |
| CN110033367A (en) | Based on the contract record method and device of block chain, electronic equipment | |
| CN110458541B (en) | Object replacement method and device based on block chain | |
| CN114925405A (en) | Block chain-based digital seal verification method and device 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 |