Digital seal application method, device and electronic device based on blockchain

By deploying smart contracts in the blockchain, processing digital seal application transactions and conducting approvals, the security and reliability issues in the application process of digital seals are solved, and the secure creation and identity verification of digital seals are realized.

CN112100588BActive Publication Date: 2024-11-22ANT BLOCKCHAIN TECHNOLOGY (SHANGHAI) CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202010949857.3
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2020-09-10
Publication Date
2024-11-22
Estimated Expiration
2040-09-10

AI Technical Summary

Technical Problem

In the prior art, the application process of digital seals lacks security and reliability, and cannot effectively ensure the identity verification and use of digital seals.

Method used

By deploying smart contracts in the blockchain, receiving application transactions from the applicant for digital seals, calling the application approval logic in the smart contract to determine the applicant for application approval, and creating a digital seal for applicant after approval, and Bind it with identity information to the blockchain for proof storage.

Benefits of technology

It ensures the security and reliability of the creation of digital seals, and realizes identity verification of users through blockchain evidence storage, ensuring the security and reliability of the use of digital seals.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN112100588B_ABST
    Figure CN112100588B_ABST
Patent Text Reader

Abstract

One or more embodiments of the present specification provide a blockchain-based digital seal application method, device and electronic device, which are applied to node devices in the blockchain; a smart contract for creating a digital seal for a digital seal applicant is deployed in the blockchain, and the method includes: receiving a digital seal application transaction initiated by the digital seal applicant; in response to the digital seal application transaction, calling the application approval logic corresponding to the smart contract code in the smart contract, determining at least one application approval party corresponding to the digital seal, and instructing at least one application approval party to apply for and approve the digital seal; if at least one application approval party approves the application for the digital seal, further calling the digital seal creation logic corresponding to the smart contract code in the smart contract, creating a digital seal for the digital seal applicant, and publishing the binding relationship between the created digital seal and the identity information of the digital seal applicant to the blockchain for evidence storage.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] One or more embodiments of the present specification relate to the field of computer application technology, and in particular, to a method, device and electronic device for applying for a digital seal based on blockchain. Background Art

[0002] Blockchain technology, also known as distributed ledger technology, is an emerging technology in which several computing devices jointly participate in "bookkeeping" and jointly maintain a complete distributed database. Blockchain technology has been widely used in many fields because of its decentralized, open and transparent characteristics, each computing device can participate in database records, and data can be quickly synchronized between computing devices. Summary of the invention

[0003] This specification proposes a digital seal application method based on blockchain, which is applied to a node device in the blockchain; a smart contract for creating a digital seal for a digital seal applicant is deployed in the blockchain; the method includes:

[0004] Receive digital seal application transactions initiated by digital seal applicants;

[0005] In response to the digital seal application transaction, calling the application approval logic corresponding to the smart contract code in the smart contract, determining at least one application approval party corresponding to the digital seal, and instructing the at least one application approval party to apply for and approve the digital seal;

[0006] If at least one of the applicants approves the application for the digital seal, the digital seal creation logic corresponding to the smart contract code in the smart contract is further called to create a digital seal for the digital seal applicant, and the binding relationship between the created digital seal and the identity information of the digital seal applicant is published to the blockchain for evidence storage.

[0007] Optionally, the determining of at least one applicant and approver corresponding to the digital seal includes:

[0008] Based on the type of the digital seal applied for, at least one applicant and approver corresponding to the digital seal is determined; and / or based on the identity information of the digital seal applicant, at least one applicant and approver corresponding to the digital seal is determined.

[0009] Optionally, the instructing the at least one application and approval party to conduct application and approval for the digital seal includes:

[0010] A claim approval event corresponding to the at least one claim approval party is generated, so that when the at least one claim approval party obtains the claim approval event, it responds to the claim approval event and performs claim approval for the digital seal.

[0011] Optionally, before calling the digital seal creation logic corresponding to the smart contract code in the smart contract to create a digital seal for the digital seal applicant, the process further includes:

[0012] The approval management logic corresponding to the smart contract code in the smart contract is called to obtain the application approval result of the at least one applicant and approver for the digital seal, and determine whether the application approval of the digital seal by the at least one applicant and approver is passed based on the obtained application approval result.

[0013] Optionally, the method further comprises:

[0014] Generate an application and approval record for the digital seal by the at least one application and approval party, and publish the generated application and approval record to the blockchain for evidence storage.

[0015] Optionally, the method further comprises:

[0016] After creating a digital seal for the digital seal applicant, a creation record corresponding to the digital seal is generated, and the generated creation record is published to the blockchain for evidence storage.

[0017] Optionally, before publishing the binding relationship between the created digital seal and the identity information of the digital seal applicant to the blockchain for evidence storage, the process further includes:

[0018] Acquiring the identity information of the digital seal applicant carried in the digital seal application transaction, and binding the acquired identity information with the created digital seal; and / or,

[0019] Generate a creation completion event corresponding to the digital seal, obtain the identity information of the digital seal applicant submitted to the smart contract in response to the creation completion event when the creation completion event is obtained, and bind the obtained identity information with the created digital seal.

[0020] Optionally, the identity information includes a public key in a CA certificate held by the digital seal applicant.

[0021] Optionally, the identity information further includes one or more combinations of the following:

[0022] The identity of the party applying for the digital seal;

[0023] The blockchain account identifier of the party applying for the digital seal;

[0024] Image information of the physical seal held by the digital seal applicant.

[0025] Optionally, the party applying for the digital seal is an enterprise; and the digital seal is the official seal of the enterprise.

[0026] Optionally, the digital seal created for the digital seal applicant includes a sample image of the digital seal and an identifier assigned to the digital seal.

[0027] Optionally, the pattern image of the digital seal visually integrates the identity information of the digital seal applicant.

[0028] This specification also proposes a digital seal application method based on blockchain, which is applied to a Baas platform connected to a node device in the blockchain; a smart contract for creating a digital seal for a digital seal applicant is deployed in the blockchain; the method includes:

[0029] Receive a digital seal application request initiated by a digital seal applicant;

[0030] In response to the digital seal application request, determining at least one application and approval party corresponding to the digital seal, and instructing the at least one application and approval party to perform application and approval for the digital seal;

[0031] If at least one of the applicants approves the application for the digital seal, a smart contract call transaction is sent to the node device, so that the node device responds to the smart contract call transaction, calls the digital seal creation logic corresponding to the smart contract code in the smart contract, creates a digital seal for the digital seal applicant, and publishes the binding relationship between the created digital seal and the identity information of the digital seal applicant to the blockchain for evidence storage.

[0032] Optionally, the determining of at least one applicant and approver corresponding to the digital seal includes:

[0033] Based on the type of the digital seal applied for, at least one applicant and approver corresponding to the digital seal is determined; and / or based on the identity information of the digital seal applicant, at least one applicant and approver corresponding to the digital seal is determined.

[0034] Optionally, the instructing the at least one application and approval party to conduct application and approval for the digital seal includes:

[0035] An approval instruction message is sent to the at least one application and approval party respectively, so that the at least one application and approval party performs application and approval for the digital seal in response to the application and approval message.

[0036] Optionally, before sending the smart contract call transaction to the node device, the method further includes:

[0037] The application and approval result of the at least one application and approval party for the digital seal is obtained, and based on the obtained application and approval result, it is determined whether the application and approval of the digital seal by the at least one application and approval party is passed.

[0038] Optionally, the method further comprises:

[0039] Generate an application and approval record for the digital seal by the at least one application and approval party, and publish the generated application and approval record to the blockchain for evidence storage.

[0040] Optionally, the identity information includes a public key in a CA certificate held by the digital seal applicant.

[0041] Optionally, the identity information further includes one or more combinations of the following:

[0042] The identity of the party applying for the digital seal;

[0043] The blockchain account identifier of the party applying for the digital seal;

[0044] Image information of the physical seal held by the digital seal applicant.

[0045] Optionally, the party applying for the digital seal is an enterprise; and the digital seal is the official seal of the enterprise.

[0046] Optionally, the digital seal created for the digital seal applicant includes a sample image of the digital seal and an identifier assigned to the digital seal.

[0047] Optionally, the pattern image of the digital seal visually integrates the identity information of the digital seal applicant.

[0048] This specification also proposes a digital seal application device based on blockchain, which is applied to a node device in the blockchain; a smart contract for creating a digital seal for a digital seal applicant is deployed in the blockchain; the device includes:

[0049] A receiving module receives a digital seal application transaction initiated by a digital seal applicant;

[0050] An approval module, in response to the digital seal application transaction, calls the application approval logic corresponding to the smart contract code in the smart contract, determines at least one application approval party corresponding to the digital seal, and instructs the at least one application approval party to perform application approval for the digital seal;

[0051] The creation module further calls the digital seal creation logic corresponding to the smart contract code in the smart contract if the at least one applicant and approver approves the application for the digital seal, creates a digital seal for the digital seal applicant, and publishes the binding relationship between the created digital seal and the identity information of the digital seal applicant to the blockchain for evidence storage.

[0052] Optionally, the approval module:

[0053] Based on the type of the digital seal applied for, at least one applicant and approver corresponding to the digital seal is determined; and / or based on the identity information of the digital seal applicant, at least one applicant and approver corresponding to the digital seal is determined.

[0054] Optionally, the approval module:

[0055] A claim approval event corresponding to the at least one claim approval party is generated, so that when the at least one claim approval party obtains the claim approval event, it responds to the claim approval event and performs claim approval for the digital seal.

[0056] Optionally, the device further comprises:

[0057] The determination module calls the digital seal creation logic corresponding to the smart contract code in the smart contract, and before creating a digital seal for the digital seal applicant, calls the approval management logic corresponding to the smart contract code in the smart contract to obtain the application approval result of the digital seal by at least one applicant and approver, and determines whether the application approval of the digital seal by at least one applicant and approver is passed based on the obtained application approval result.

[0058] Optionally, the device further comprises:

[0059] The first generation module generates an application and approval record for the digital seal by at least one application and approval party, and publishes the generated application and approval record to the blockchain for evidence storage.

[0060] Optionally, the device further comprises:

[0061] The second generation module, after creating a digital seal for the digital seal applicant, generates a creation record corresponding to the digital seal, and publishes the generated creation record to the blockchain for evidence storage.

[0062] Optionally, the device further comprises:

[0063] A binding module, which obtains the identity information of the digital seal applicant carried in the digital seal application transaction before publishing the binding relationship between the created digital seal and the identity information of the digital seal applicant to the blockchain for evidence storage, and binds the obtained identity information to the created digital seal; and / or,

[0064] The binding relationship between the created digital seal and the identity information of the digital seal applicant is generated before being published to the blockchain for evidence storage, and the identity information of the digital seal applicant submitted to the smart contract in response to the creation completion event when the creation completion event is obtained, and the obtained identity information is bound to the created digital seal.

[0065] Optionally, the identity information includes a public key in a CA certificate held by the digital seal applicant.

[0066] Optionally, the identity information further includes one or more combinations of the following:

[0067] The identity of the party applying for the digital seal;

[0068] The blockchain account identifier of the party applying for the digital seal;

[0069] Image information of the physical seal held by the digital seal applicant.

[0070] Optionally, the party applying for the digital seal is an enterprise; and the digital seal is the official seal of the enterprise.

[0071] Optionally, the digital seal created for the digital seal applicant includes a sample image of the digital seal and an identifier assigned to the digital seal.

[0072] Optionally, the pattern image of the digital seal visually integrates the identity information of the digital seal applicant.

[0073] This specification also proposes a digital seal application device based on blockchain, which is applied to a Baas platform connected to a node device in the blockchain; a smart contract for creating a digital seal for a digital seal applicant is deployed in the blockchain; the device includes:

[0074] A receiving module receives a digital seal application request initiated by a digital seal applicant;

[0075] An approval module, in response to the digital seal application request, determines at least one application and approval party corresponding to the digital seal, and instructs the at least one application and approval party to perform application and approval for the digital seal;

[0076] The creation module sends a smart contract call transaction to the node device if at least one of the applicants and approves the application for the digital seal, so that the node device responds to the smart contract call transaction, calls the digital seal creation logic corresponding to the smart contract code in the smart contract, creates a digital seal for the digital seal applicant, and publishes the binding relationship between the created digital seal and the identity information of the digital seal applicant to the blockchain for evidence storage.

[0077] Optionally, the approval module:

[0078] Based on the type of the digital seal applied for, at least one applicant and approver corresponding to the digital seal is determined; and / or based on the identity information of the digital seal applicant, at least one applicant and approver corresponding to the digital seal is determined.

[0079] Optionally, the approval module:

[0080] An approval instruction message is sent to the at least one application and approval party respectively, so that the at least one application and approval party performs application and approval for the digital seal in response to the application and approval message.

[0081] Optionally, the device further comprises:

[0082] The determination module obtains the application and approval result of the digital seal by the at least one application and approval party before sending the smart contract call transaction to the node device, and determines whether the application and approval of the digital seal by the at least one application and approval party is passed based on the obtained application and approval result.

[0083] Optionally, the device further comprises:

[0084] A generation module generates an application and approval record for the digital seal by at least one application and approval party, and publishes the generated application and approval record to the blockchain for evidence storage.

[0085] Optionally, the identity information includes a public key in a CA certificate held by the digital seal applicant.

[0086] Optionally, the identity information further includes one or more combinations of the following:

[0087] The identity of the party applying for the digital seal;

[0088] The blockchain account identifier of the party applying for the digital seal;

[0089] Image information of the physical seal held by the digital seal applicant.

[0090] Optionally, the party applying for the digital seal is an enterprise; and the digital seal is the official seal of the enterprise.

[0091] Optionally, the digital seal created for the digital seal applicant includes a sample image of the digital seal and an identifier assigned to the digital seal.

[0092] Optionally, the pattern image of the digital seal visually integrates the identity information of the digital seal applicant.

[0093] This specification also proposes an electronic device, comprising:

[0094] processor;

[0095] a memory for storing processor-executable instructions;

[0096] The processor implements the steps of any one of the above methods by running the executable instructions.

[0097] The present specification also proposes a computer-readable storage medium on which computer instructions are stored. When the instructions are executed by a processor, the steps of any one of the above methods are implemented.

[0098] In the above technical solution, the node device in the blockchain can respond to the digital seal application transaction initiated by the digital seal applicant, call the application approval logic in the smart contract deployed on the blockchain, determine at least one application approval party corresponding to the digital seal, and instruct at least one application approval policy to apply for and approve the digital seal. If at least one application approval policy approves the application of the digital seal, the digital seal creation logic in the smart contract can be further called to create a digital seal for the digital seal applicant, and the binding relationship between the created digital seal and the identity information of the digital seal applicant can be published to the blockchain for evidence storage.

[0099] In this way, on the one hand, since the digital seal applicant can create the digital seal after the digital seal applicant's application is approved, the security and reliability of the digital seal creation can be guaranteed;

[0100] On the other hand, after a digital seal is created for the digital seal applicant, the digital seal and the identity information of the digital seal applicant are published to the blockchain for evidence storage. Therefore, when the digital seal is used later, the user's identity can be authenticated based on the corresponding binding relationship, thereby ensuring the security and reliability of the use of the digital seal. BRIEF DESCRIPTION OF THE DRAWINGS

[0101] Figure 1 This is a schematic diagram of a smart contract creation process shown in this specification;

[0102] Figure 2 This is a schematic diagram of a smart contract calling process shown in this specification;

[0103] Figure 3 This is a schematic diagram of the creation and calling process of a smart contract shown in this specification;

[0104] Figure 4 It is a schematic diagram of a digital seal application system based on blockchain shown in an exemplary embodiment of this specification;

[0105] Figure 5 This is a flowchart of a method for applying for a digital seal based on blockchain, shown in an exemplary embodiment of this specification;

[0106] Figure 6 is a schematic diagram of a digital seal pattern image shown in an exemplary embodiment of this specification;

[0107] Figure 7 is a schematic diagram of a registration interface shown in an exemplary embodiment of this specification;

[0108] Figure 8 It is a schematic diagram of another blockchain-based digital seal application system shown in an exemplary embodiment of this specification;

[0109] Fig. 9 It is a flowchart of another method for applying for a digital seal based on blockchain, shown in an exemplary embodiment of this specification;

[0110] Fig.10 is a hardware structure diagram of an electronic device shown in an exemplary embodiment of this specification;

[0111] Fig.11 It is a block diagram of a digital seal application device based on blockchain shown in an exemplary embodiment of this specification;

[0112] Fig.12 It is a block diagram of another blockchain-based digital seal application device shown in an exemplary embodiment of this specification. DETAILED DESCRIPTION

[0113] Exemplary embodiments will be described in detail herein, examples of which are shown in the accompanying drawings. When the following description refers to the drawings, the same numbers in different drawings represent the same or similar elements unless otherwise indicated. The implementations described in the following exemplary embodiments do not represent all implementations consistent with one or more embodiments of this specification. Instead, they are merely examples of devices and methods consistent with some aspects of one or more embodiments of this specification as detailed in the appended claims.

[0114] 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 steps included in the method may be more or less than those described in this specification. In addition, a single step described in this specification may be decomposed into multiple steps for description in other embodiments; and multiple steps described in this specification may be combined into a single step for description in other embodiments.

[0115] Blockchain is generally divided into three types: public blockchain, private blockchain and consortium blockchain. In addition, there can also be a combination of the above types, such as private blockchain + consortium blockchain, consortium blockchain + public blockchain, etc.

[0116] Among them, the most decentralized is the public chain. Public chains are represented by Bitcoin and Ethereum. Participants who join the public chain (also called nodes in the blockchain) can read data records on the chain, participate in transactions, and compete for the right to record new blocks. Moreover, each node can freely join or exit the network and perform related operations.

[0117] On the contrary, the private chain has a network whose write permission is controlled by a certain organization or institution, and the data read permission is regulated by the organization. In simple terms, a private chain can be a weakly centralized system with strict restrictions on nodes and a small number of nodes. This type of blockchain is more suitable for use within a specific institution.

[0118] The consortium chain is a blockchain between the public chain and the private chain, which can achieve "partial decentralization". Each node in the consortium chain usually has a corresponding entity or organization; the nodes join the network through authorization and form a stakeholder alliance to jointly maintain the operation of the blockchain.

[0119] Based on the basic characteristics of blockchain, blockchain is usually composed of several blocks. In each of these blocks, a timestamp corresponding to the creation time of the block is recorded. All blocks strictly follow the timestamp recorded in the block to form a data chain that is ordered in time.

[0120] The real data generated in the physical world can be constructed into a standard transaction format supported by the blockchain, and then published to the blockchain. The node devices in the blockchain will perform consensus processing on the received transactions. After reaching a consensus, the node devices in the blockchain that serve as accounting nodes will package the transaction into blocks and store it persistently in the blockchain.

[0121] Among them, the consensus algorithms supported in blockchain can include:

[0122] The first type of consensus algorithm is the consensus algorithm in which node devices need to compete for the right to record in each accounting cycle; for example, consensus algorithms such as Proof of Work (POW), Proof of Stake (POS), and Delegated Proof of Stake (DPOS);

[0123] The second type of consensus algorithm is a consensus algorithm that elects accounting nodes in advance for each accounting cycle (without the need to compete for accounting rights); for example, consensus algorithms such as Practical Byzantine Fault Tolerance (PBFT).

[0124] In a blockchain network that uses the first type of consensus algorithm, node devices competing for the right to record transactions can execute the transaction after receiving it. Among the node devices competing for the right to record transactions, one node device may win in this round of competition for the right to record transactions and become a record node. The record node can package the received transaction with other transactions to generate the latest block, and send the generated latest block or the block header of the latest block to other node devices for consensus.

[0125] In a blockchain network that uses the second type of consensus algorithm, the node devices with the right to record accounts have been agreed upon before this round of accounting. Therefore, after receiving a transaction, if the node device itself is not a record node for this round, it can send the transaction to the record node. For the record node of this round, the transaction can be executed before or during the process of packaging the transaction with other transactions to generate the latest block. After generating the latest block, the record node can send the latest block or the block header of the latest block to other node devices for consensus.

[0126] As described above, no matter which consensus algorithm shown above is adopted by the blockchain, the accounting node of this round can package the received transactions to generate the latest block, and send the generated latest block or the block header of the latest block to other node devices for consensus verification. If other node devices receive the latest block or the block header of the latest block and verify that there is no problem, the latest block can be appended to the end of the original blockchain, thereby completing the accounting process of the blockchain. In the process of other nodes verifying the new block or block header sent by the accounting node, the transactions contained in the block can also be executed.

[0127] In the field of blockchain, an important concept is account. Taking Ethereum as an example, Ethereum usually divides accounts into two categories: external accounts and contract accounts. External accounts are accounts directly controlled by users, also known as user accounts. Contract accounts are accounts created by users through external accounts and contain contract codes (i.e. smart contracts). Of course, for some blockchain projects derived from the Ethereum architecture (such as Ant Blockchain), the account types supported by the blockchain can be further expanded, which is not specifically limited in this manual.

[0128] For accounts in the blockchain, a structure is usually used to maintain the account status. When a transaction in a block is executed, the status of the account related to the transaction in the blockchain will usually change.

[0129] Taking Ethereum as an example, the structure of an account usually includes fields such as Balance, Nonce, Code and Storage. Among them:

[0130] The Balance field is used to maintain the current account balance of the account;

[0131] The Nonce field is used to maintain the number of transactions for the account. It is a counter used to ensure that each transaction can and can only be processed once, effectively avoiding replay attacks.

[0132] The Code field is used to maintain the contract code of the account. In actual applications, the Code field usually only maintains the hash value of the contract code. Therefore, the Code field is also often called the Codehash field.

[0133] The Storage field is used to maintain the storage content of the account (the default field value is empty); for a contract account, an independent storage space is usually allocated to store the storage content of the contract account; this independent storage space is usually referred to as the account storage of the contract account. The storage content of the contract account is usually constructed into an MPT (MerklePatricia Trie) tree data structure and stored in the above-mentioned independent storage space; among them, the MPT tree constructed based on the storage content of the contract account is also usually referred to as a Storage tree. The Storage field usually only maintains the root node of the Storage tree; therefore, the Storage field is also usually referred to as the StorageRoot field.

[0134] For an external account, the field values ​​of the Code field and the Storage field shown above are both empty.

[0135] For most blockchain projects, Merkle trees are usually used; or data structures based on Merkle trees are used to store and maintain data. Taking Ethereum as an example, Ethereum uses MPT trees (a variant of Merkle trees) as a data organization form to organize and manage important data such as account status and transaction information.

[0136] Ethereum has designed three MPT trees for the data that needs to be stored and maintained in the blockchain, namely the MPT state tree, the MPT transaction tree, and the MPT receipt tree. In addition to the above three MPT trees, there is actually a Storage tree built based on the storage content of the contract account.

[0137] The MPT state tree is an MPT tree organized by the account state data of all accounts in the blockchain; the MPT transaction tree is an MPT tree organized by the transaction data in the blockchain; the MPT receipt tree is an MPT tree organized by the transaction receipts corresponding to each transaction generated after the transactions in the block are executed. The hash values ​​of the root nodes of the MPT state tree, MPT transaction tree, and MPT receipt tree shown above will eventually be added to the block header of the corresponding block.

[0138] Among them, the MPT transaction tree and the MPT receipt tree both correspond to blocks, that is, each block has its own MPT transaction tree and MPT receipt tree. The MPT status tree is a global MPT tree, which does not correspond to a specific block, but covers the account status data of all accounts in the blockchain.

[0139] It should be noted that every time a new block is generated in the blockchain, after the transactions in the newest block are executed, the account status of the related accounts (which can be external accounts or contract accounts) of these executed transactions in the blockchain will usually change accordingly;

[0140] For example, when a "transfer transaction" in a block is executed, the balances of the transferor account and the transferee account related to the "transfer transaction" (that is, the field values ​​of the Balance fields of these accounts) will usually change accordingly.

[0141] After the node device completes the execution of the transaction in the latest block generated by the blockchain, since the account status in the current blockchain has changed, the node device needs to build the MPT status tree based on the current account status data of all accounts in the blockchain to maintain the latest status of all accounts in the blockchain.

[0142] That is, every time a new block is generated in the blockchain and the transactions in the new block are executed, the account status in the blockchain changes, and the node devices need to rebuild an MPT state tree based on the latest account status data of all accounts in the blockchain. In other words, each block in the blockchain has a corresponding MPT state tree; the MPT state tree maintains the latest account status of all accounts in the blockchain after the transactions in the block are executed.

[0143] In practical applications, whether it is a public chain, a private chain or a consortium chain, it may provide the function of smart contract. Smart contracts on the blockchain are contracts that can be triggered and executed by transactions on the blockchain. Smart contracts can be defined in the form of code.

[0144] Taking Ethereum as an example, it supports users to create and call some complex logic in the Ethereum network. As a programmable blockchain, Ethereum is centered on the Ethereum Virtual Machine (EVM), and each Ethereum node can run EVM. EVM is a Turing-complete virtual machine that can implement various complex logics. Users publish and call smart contracts in Ethereum on EVM. In fact, EVM directly runs virtual machine code (virtual machine bytecode, hereinafter referred to as "bytecode"), so the smart contracts deployed on the blockchain can be bytecode.

[0145] like Figure 1 As shown in the figure, after Bob sends a transaction containing the information of creating a smart contract to the Ethereum network, each node can execute the transaction in the EVM. Figure 1The From field of the transaction is used to record the address of the account that initiated the creation of the smart contract. The contract code stored in the Data field of the transaction can be bytecode, and the To field of the transaction has a null account value. When the nodes reach an agreement through the consensus mechanism, the smart contract is successfully created, and subsequent users can call this smart contract.

[0146] After a smart contract is created, a contract account corresponding to the smart contract appears on the blockchain and has a specific address; for example, Figure 1 The "0x68e12cf284..." in each node represents the address of the created contract account; the contract code (Code) and account storage (Storage) will be saved in the account storage of the contract account. The behavior of the smart contract is controlled by the contract code, and the account storage of the smart contract saves the state of the contract. In other words, the smart contract generates a virtual account on the blockchain that contains the contract code and account storage.

[0147] As mentioned above, the Data field of the transaction that creates a smart contract can store the bytecode of the smart contract. The bytecode consists of a series of bytes, each of which can identify an operation. Based on development efficiency, readability and other considerations, developers can choose a high-level language to write smart contract code instead of writing bytecode directly. For example, high-level languages ​​can be Solidity, Serpent, LLL, etc. For smart contract code written in a high-level language, it can be compiled by a compiler to generate bytecode that can be deployed on the blockchain.

[0148] Taking Solidity as an example, the contract code written in it is very similar to the class in object-oriented programming language. Multiple members can be declared in a contract, including state variables, functions, function modifiers, events, etc. State variables are values ​​permanently stored in the account storage field of the smart contract, which are used to save the state of the contract.

[0149] like Figure 2 As shown in the figure, still taking Ethereum as an example, after Bob sends a transaction containing the information of calling a smart contract to the Ethereum network, each node can execute the transaction in the EVM. Figure 2 The From field of the transaction is used to record the address of the account that initiates the call to the smart contract, the To field is used to record the address of the smart contract being called, and the Data field of the transaction is used to record the method and parameters of calling the smart contract. After calling the smart contract, the account status of the contract account may change. Later, a client can access the blockchain node (for example Figure 2 Node 1) in the contract account to view the account status.

[0150] Smart contracts can be executed independently on each node in the blockchain network in a prescribed manner, and all execution records and data are stored on the blockchain. Therefore, when such a transaction is executed, the blockchain will store transaction credentials that cannot be tampered with or lost.

[0151] The schematic diagram of creating and calling smart contracts is as follows: Figure 3 To create a smart contract in Ethereum, you need to go through the process of writing the smart contract, converting it into bytecode, and deploying it to the blockchain. To call a smart contract in Ethereum, you initiate a transaction pointing to the smart contract address. The EVM of each node can execute the transaction separately, and the smart contract code is distributed and run in the virtual machine of each node in the Ethereum network.

[0152] The event mechanism of smart contracts is a way for smart contracts to interact with entities outside the chain. For smart contracts deployed on the blockchain, it is usually impossible to directly interact with entities outside the chain; for example, after the smart contract is called, it is usually impossible to send the call result of the smart contract to the caller of the smart contract point-to-point.

[0153] The call results (including intermediate results and final call results) generated by the smart contract during the call process are usually recorded in the form of events in the transaction logs of the transaction that called the smart contract and stored in the storage space of the node device. Off-chain entities that need to interact with smart contracts can obtain the call results of the smart contract by monitoring the transaction logs stored in the storage space of the node device;

[0154] For example, in Ethereum, the transaction log will eventually be stored in the MPT receipt tree described above as part of the receipt of the transaction that called the smart contract. The off-chain entity that interacts with the smart contract can monitor the transaction receipts on the MPT receipt tree stored in the storage space of the node device, and obtain the events generated by the smart contract from the monitored transaction receipts.

[0155] Smart contracts deployed on the blockchain can usually only reference data content stored on the blockchain; in actual applications, 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.

[0156] In this scenario, smart contracts deployed on the blockchain can use Oracle to reference data on off-chain data entities, thereby achieving data interaction between smart contracts and real-world data entities. Among them, off-chain data entities can include centralized servers or data centers deployed outside the chain, etc.

[0157] It should be noted that the cross-chain relay is used to connect two blockchains, while the Oracle oracle is used to connect the blockchain with data entities outside the chain to realize data interaction between the blockchain and the real world.

[0158] In actual applications, when deploying an oracle for a smart contract on a blockchain, an oracle smart contract corresponding to the oracle can be deployed on the blockchain first; wherein the oracle smart contract is used to maintain external data sent by the oracle to the smart contract on the blockchain; for example, the external data sent by the oracle to the smart contract on the blockchain can be stored in the account storage space of the oracle smart contract.

[0159] When the target smart contract on the blockchain is called, the external data required by the target smart contract can be read from the account storage space of the oracle smart contract to complete the calling process of the smart contract.

[0160] It should be noted that when the oracle sends external data to the smart contract on the blockchain, it can use active or passive sending methods.

[0161] In one implementation, the data entity outside the chain can sign the external data that needs to be provided to the target smart contract with the private key of the oracle and send it to the oracle smart contract. For example, at a certain time, the signed external data can be sent to the oracle smart contract in a periodic manner.

[0162] The above-mentioned oracle smart contract can maintain the CA certificate of the oracle. After receiving the external data sent by the data entity outside the chain, the public key of the oracle maintained in the CA certificate can be used to verify the signature of the external data. After the verification is passed, the external data sent by the data entity outside the chain is stored in the account storage space of the oracle smart contract.

[0163] In another implementation method, when the target smart contract on the blockchain is called, if the external data required by the target smart contract is not read from the account storage space of the oracle smart contract, the oracle smart contract can use the event mechanism of the smart contract to interact with the above-mentioned oracle, and the above-mentioned oracle will send the external data required by the target smart contract to the account storage space of the oracle smart contract.

[0164] For example, when the target smart contract on the blockchain is called, if the external data required by the target smart contract is not read from the account storage space of the oracle smart contract, the oracle smart contract can generate an external data acquisition event, record the external data acquisition event in the transaction log of the transaction that called the smart contract, and store the transaction log in the storage space of the node device; and the above-mentioned oracle can monitor the transaction log generated by the oracle smart contract stored in the storage space of the node device, and after monitoring the external data acquisition event in the transaction log, respond to the external data acquisition event monitored, and send the external data required by the above-mentioned target smart contract to the above-mentioned oracle smart contract.

[0165] Please refer to Figure 4 , Figure 4 It is a schematic diagram of a digital seal application system based on blockchain shown in an exemplary embodiment of this specification.

[0166] In such Figure 4 In the blockchain-based digital seal application system shown, a smart contract can be deployed on the blockchain. The smart contract may include a smart contract code for creating a digital seal for a digital seal applicant; specifically, the smart contract code of the smart contract may include a smart contract code corresponding to the application approval logic, and a smart contract code corresponding to the digital seal creation logic, and so on. In practical applications, by executing the smart contract code corresponding to the application approval logic in the smart contract, the application approval logic can be implemented to approve the application of the digital seal; by executing the smart contract code corresponding to the digital seal creation logic in the smart contract, the digital seal creation logic can be implemented to create a digital seal for the digital seal applicant.

[0167] It should be noted that the specific process of creating and calling a smart contract can refer to the creation and calling process of the aforementioned smart contract, and this manual will not go into details here.

[0168] In specific implementation, a user can initiate a transaction for calling the smart contract deployed on the blockchain through a client that establishes a connection with a node device in the blockchain. When the node device in the blockchain receives the transaction, it can send the transaction to other node devices in the blockchain to process the transaction by consensus, and after the consensus is passed, the smart contract code in the smart contract is executed to create a digital seal for the digital seal applicant.

[0169] In actual applications, the above-mentioned client can be deployed on an electronic device, which can be a server, a computer, a mobile phone, a tablet device, a laptop computer, a PDA (Personal Digital Assistants), etc.; similarly, the electronic device added to the above-mentioned blockchain as a node device can also be a server, a computer, a mobile phone, a tablet device, a laptop computer, a PDA, etc.; this specification does not limit this.

[0170] Please refer to Figure 5 , Figure 5 This is a flowchart of a method for applying for a digital seal based on blockchain, shown as an exemplary embodiment of this specification.

[0171] Combined with Figure 4 The blockchain-based digital seal application system shown in the figure, the blockchain-based digital seal application method can be applied to Figure 4 The node device in the blockchain shown; the blockchain-based digital seal application method may include the following steps:

[0172] Step 501, receiving a digital seal application transaction initiated by a digital seal applicant;

[0173] Step 502: In response to the digital seal application transaction, calling the application approval logic corresponding to the smart contract code in the smart contract, determining at least one application approval party corresponding to the digital seal, and instructing the at least one application approval party to perform application approval for the digital seal;

[0174] Step 503: If at least one of the applicants approves the application for the digital seal, the digital seal creation logic corresponding to the smart contract code in the smart contract is further called to create a digital seal for the digital seal applicant, and the binding relationship between the created digital seal and the identity information of the digital seal applicant is published to the blockchain for evidence storage.

[0175] In this embodiment, a smart contract can be deployed on the blockchain. A user who needs to apply for a digital seal (referred to as a digital seal applicant) can initiate a transaction (referred to as a digital seal application transaction) for calling the smart contract deployed on the blockchain through a client that establishes a connection with a node device in the blockchain.

[0176] In this embodiment, the node device in the blockchain can respond to the digital seal application transaction and call the application approval logic corresponding to the smart contract code in the smart contract, that is, execute the smart contract code corresponding to the application approval logic in the smart contract, determine at least one application approval party corresponding to the digital seal that the above-mentioned digital seal applicant needs to apply for, and instruct the determined at least one application approval policy to apply for and approve the digital seal.

[0177] Specifically, referring to the aforementioned process of persisting evidence data in the blockchain, the above-mentioned client can construct a digital seal application transaction for calling the above-mentioned smart contract deployed on the blockchain, and publish the digital seal application transaction to the blockchain for evidence storage. That is, the node device in the blockchain connected to the client can first receive the digital seal application transaction, and then send the digital seal application transaction to other node devices in the blockchain. When receiving the digital seal application transaction, each node device in the blockchain can perform consensus processing on the digital seal application transaction. After reaching a consensus, the node devices in the blockchain can package the digital seal application transaction into a block and perform persistent evidence storage in the blockchain.

[0178] For digital seal application transactions packaged into blocks, the node devices in the blockchain can respond to the digital seal application transactions, execute the smart contract code in the smart contract corresponding to the application approval logic, determine at least one application and approval party corresponding to the digital seal that the above-mentioned digital seal applicant needs to apply for, and instruct the determined at least one application and approval policy to apply for and approve the digital seal.

[0179] In actual application, on the one hand, the digital seal applicant can specifically represent the national administrative organs, institutions, social groups or enterprises that need to use seals in their work. The digital seal applicant can be a single user or a user group composed of multiple users. The applicant and approver corresponding to the digital seal can specifically be an approver with the approval authority for the digital seal application by the digital seal applicant. There can be only one or more applicant and approver parties. This manual does not impose any restrictions on this.

[0180] On the other hand, the application approval policy shall approve the application for the digital seal, that is, the application approval party shall determine whether the digital seal applicant is allowed to apply for the digital seal. Specifically, it may include: the application approval party determines whether the digital seal is reasonable and legal, and whether the digital seal applicant has the right to use the digital seal, etc.

[0181] Taking an enterprise as an example, the enterprise itself can be the digital seal applicant and apply for a digital seal representing the official seal of the enterprise. In this case, the applicants and reviewers corresponding to the digital seal may include: all legal persons of the enterprise and the industrial and commercial administration bureau where the enterprise is located.

[0182] Specifically, the enterprise can initiate a digital seal application transaction for applying for the official seal of the enterprise through a client that establishes a connection with the node device in the above blockchain. For example, one employee can be selected from all employees of the enterprise as the representative of the enterprise, and a digital seal application transaction can be initiated through the client. The node device in the blockchain can respond to the digital seal application transaction, call the application approval logic corresponding to the smart contract code in the smart contract, determine all legal persons of the enterprise and the industrial and commercial administration where the enterprise is located as the application approval party, and instruct the application approval party to apply for and approve the applied digital seal.

[0183] In one embodiment shown, the correspondence between the type of digital seal and the applicant and approver of the digital seal can be stored in the blockchain in advance. When the applicant and approver corresponding to the digital seal that the digital seal applicant needs to apply for is subsequently determined, based on the type of the digital seal, at least one applicant and approver corresponding to the type of the digital seal can be searched in the correspondence, and the applicant and approver can be determined as the at least one applicant and approver corresponding to the digital seal.

[0184] In actual applications, the types of digital seals may include: official seal, financial seal, invoice seal, contract seal, legal person seal, etc.; the applicants and approvers corresponding to each type of digital seal may be set based on actual needs. For example, the applicants and approvers corresponding to the official seal of an enterprise may include: all legal persons of the enterprise, and the industrial and commercial administration bureau where the enterprise is located.

[0185] For example, assume that the correspondence between the types of digital seals stored in the blockchain and the applicants and approvers of the digital seals is as shown in Table 1 below:

[0186]

[0187] Table 1

[0188] Subsequently, if the type of digital seal that the above-mentioned digital seal applicant needs to apply for is type 1, then applicant A can be determined as the applicant corresponding to the digital seal; if the type of digital seal that the above-mentioned digital seal applicant needs to apply for is type 2, then applicant A and applicant B can be determined as the applicants corresponding to the digital seal; and so on.

[0189] Alternatively, the correspondence between the identity information of the digital seal applicant and the applicant and approver of the digital seal can be stored in the blockchain in advance. When subsequently determining the applicant and approver corresponding to the digital seal that the digital seal applicant needs to apply for, the identity information of the digital seal applicant can be used to search for at least one applicant and approver corresponding to the identity information in the correspondence, and the applicant and approver can be determined as the at least one applicant and approver corresponding to the digital seal.

[0190] In actual applications, the applicants and reviewers corresponding to each digital seal applicant can be set based on actual needs. For example, the applicant and reviewer corresponding to an enterprise can include the industrial and commercial administration bureau where the enterprise is located.

[0191] For example, assume that the corresponding relationship between the identity information of the digital seal applicant stored in the blockchain and the digital seal applicant is as shown in Table 2 below:

[0192]

[0193] Table 2

[0194] Subsequently, if the identity information of the above-mentioned digital seal applicant is identity information 1, the applicant A can be determined as the applicant corresponding to the digital seal that the digital seal applicant needs to apply for; if the identity information of the above-mentioned digital seal applicant is identity information 2, the applicant A and the applicant B can be determined as the applicants corresponding to the digital seal that the digital seal applicant needs to apply for; and so on.

[0195] It should be noted that when determining the applicant corresponding to the digital seal that the digital seal applicant needs to apply for, at least one applicant corresponding to the digital seal can also be determined based on the type of the digital seal and the identity information of the digital seal applicant.

[0196] For example, assume that the corresponding relationship between the identity information of the digital seal applicant stored in the blockchain and the digital seal applicant is as shown in Table 3 below:

[0197]

[0198] Table 3

[0199] Subsequently, if the identity information of the above-mentioned digital seal applicant is identity information 1, and the type of digital seal that the digital seal applicant needs to apply for is type 1, then the applicant A can be determined as the applicant corresponding to the digital seal that the digital seal applicant needs to apply for; if the identity information of the above-mentioned digital seal applicant is identity information 2, and the type of digital seal that the digital seal applicant needs to apply for is type 1, then the applicant A and the applicant B can be determined as the applicant corresponding to the digital seal that the digital seal applicant needs to apply for; if the identity information of the above-mentioned digital seal applicant is identity information 1, and the type of digital seal that the digital seal applicant needs to apply for is type 2, then the applicant C can be determined as the applicant corresponding to the digital seal that the digital seal applicant needs to apply for; and so on.

[0200] It should be noted that the above-mentioned corresponding relationship can be specifically stored in the storage space of the contract account of the above-mentioned smart contract, that is, the corresponding relationship can be maintained by the smart contract.

[0201] In one embodiment shown, for a digital seal applicant, the identity information of the digital seal applicant may include: a public key in a CA (Certificate Authority) certificate held by the digital seal applicant.

[0202] In actual applications, on the one hand, different digital seal applicants hold different CA certificates, and the public and private keys in different CA certificates are different; on the other hand, the public key is usually a public key, while the private key is a private key held by the user himself. Therefore, for a digital seal applicant, the public key in the CA certificate held by the digital seal applicant can be used as the identity information used to refer to the digital seal applicant.

[0203] In this case, when the digital seal applicant publishes the data to the above-mentioned blockchain for evidence storage, the digital seal applicant can use the private key in the CA certificate held by the digital seal applicant to sign the data to be stored, and the node device in the blockchain can verify the signature using the public key in the CA certificate held by the digital seal applicant to verify the authenticity of the data to be stored.

[0204] Furthermore, in one embodiment shown, for a digital seal applicant, the identity information of the digital seal applicant may also include one or more combinations of the following: the identity identification of the digital seal applicant (for example: account login password, facial information or fingerprint information, etc.); the blockchain account identification of the digital seal applicant; the image information of the physical seal held by the digital seal applicant; etc., which can be used to refer to the information of the digital seal applicant.

[0205] In one embodiment shown, with reference to the event mechanism of the aforementioned smart contract, when the above-mentioned smart contract is called and at least one applicant and approver corresponding to the digital seal that the above-mentioned digital seal applicant needs to apply for is determined, the smart contract can generate an event corresponding to the applicant and approver (referred to as an application and approval event); wherein the application and approval event is used to instruct the applicant and approver to apply for and approve the digital seal.

[0206] In this case, the applicant and approver indicated by the application and approval event can, upon obtaining the application and approval event, respond to the application and approval event and apply for and approve the digital seal. For example, the client used by the applicant and approver can respond to the application and approval event and display to the applicant and approver the relevant information that the digital seal applicant needs to apply for the digital seal, and the applicant and approver can apply for and approve the digital seal based on the relevant information.

[0207] Specifically, the application approval event can be recorded in the transaction log of the digital seal application transaction or the smart contract log of the smart contract and stored in the blockchain.

[0208] The applicant and approver can obtain the application and approval event by monitoring the transaction log or the smart contract log stored in the blockchain, and approve the application for the digital seal in response to the application and approval event.

[0209] Alternatively, the applicant and approver may subscribe to the application and approval event to the SDK (Software Development Kit) deployed on the node device in the blockchain as the event notification center. When the SDK detects that the application and approval event has been generated, it may send the application and approval event to the applicant and approver, so that the applicant and approver can obtain the application and approval event and, in response to the application and approval event, approve the application for the digital seal.

[0210] In actual applications, the applicant can log in to the client using the account number and password of the applicant, and the client or the node device in the blockchain can determine whether the account number and password entered by the applicant on the client is legal based on the corresponding relationship between the account number and the password stored in the blockchain. If the account number and password entered by the applicant are legal, the client can respond to the acquired application approval event and display the relevant information of the digital seal that the digital seal applicant needs to apply for to the applicant, so that the applicant can apply for and approve the digital seal.

[0211] In this embodiment, when the digital seal is applied for and approved by at least one application approval policy corresponding to the digital seal that the digital seal applicant needs to apply for, if at least one application approval policy approves the application for the digital seal, the digital seal creation logic corresponding to the smart contract code in the above-mentioned smart contract can be further called, that is, the smart contract code corresponding to the digital seal creation logic in the smart contract is executed to create the digital seal for the digital seal applicant, and the binding relationship between the created digital seal and the identity information of the digital seal applicant is published to the above-mentioned blockchain for evidence storage.

[0212] In practical applications, the created digital seal can be stored in the storage space of the contract account of the smart contract.

[0213] In one embodiment shown, the approval management logic corresponding to the smart contract code in the above-mentioned smart contract can be called, that is, the smart contract code corresponding to the approval management logic in the smart contract can be executed, and the application approval result obtained by applying for and approving the digital seal by at least one application approval policy corresponding to the above-mentioned digital seal can be obtained, and based on the application approval result obtained, it can be determined whether the application approval of the digital seal by at least one application approval policy is passed.

[0214] Specifically, for any one of the at least one application and approval party, after the application and approval for the digital seal is carried out, the application and approval party can send the obtained application and approval result to the smart contract through the Oracle oracle. In this case, the smart contract code corresponding to the approval management logic in the smart contract can be executed, and the application and approval result can be received through the Oracle oracle, and based on the received application and approval result, it can be determined whether the application and approval policy has passed the application and approval for the digital seal.

[0215] Alternatively, for any one of the at least one application and approval party, after the application and approval for the digital seal, the application and approval party may publish the application and approval result obtained to the blockchain for evidence storage. In this case, the smart contract code corresponding to the approval management logic in the smart contract may be executed, and the application and approval result may be obtained by monitoring the data stored in the blockchain, and based on the obtained application and approval result, it may be determined whether the application and approval policy has passed the application and approval for the digital seal.

[0216] For example, when the application for the digital seal is approved by the applicant, the applicant can generate an application approval result indicating that the application is approved, and send the application approval result to the smart contract through the Oracle oracle; when the smart contract receives the application approval result through the Oracle oracle, it can determine that the application for the digital seal is approved by the applicant.

[0217] In another example, when the application approval party fails to approve the application for the digital seal, it may generate an application approval result indicating that the approval has not been approved, and send the application approval result to the smart contract through the Oracle oracle; when the smart contract receives the application approval result through the Oracle oracle, it may determine that the application approval policy has failed to approve the application for the digital seal. Alternatively, when the application approval party fails to approve the application for the digital seal, it may not send the application approval result to the smart contract; when the smart contract does not receive the application approval result sent by the application approval party, it may determine that the application approval policy has failed to approve the application for the digital seal.

[0218] Furthermore, in one embodiment shown, an application and approval record for the digital seal by at least one application and approval party may be generated, and the generated application and approval record may be published to the blockchain for evidence storage.

[0219] It should be noted that if there is only one application and approval party corresponding to the above-mentioned digital seal, then when the application and approval policy approves the application of the digital seal, it can be determined that at least one application and approval policy corresponding to the digital seal has approved the application and approval of the digital seal. If there are multiple application and approval parties corresponding to the above-mentioned digital seal, then when all application and approval policies have approved the application and approval of the digital seal, it can be determined that at least one application and approval policy corresponding to the digital seal has approved the application and approval of the digital seal, or when a preset number of application and approval policies have approved the application and approval of the digital seal, it can be determined that at least one application and approval policy corresponding to the digital seal has approved the application and approval of the digital seal; wherein, the preset number can be pre-set by technical personnel according to actual needs.

[0220] For example, suppose there are 5 applicants and reviewers corresponding to the digital seal, and the technicians have pre-set that 3 applicants and reviewers are required to approve the application. In this case, if any 3 of the 5 applicants and reviewers approve the application for the digital seal, it can be determined that the 5 applicants and reviewers corresponding to the digital seal have approved the application for the digital seal.

[0221] In one embodiment shown, the created digital seal may specifically include: a pattern image of the digital seal and an identifier assigned to the digital seal. The identifier may be used to find the digital seal later.

[0222] Furthermore, in one embodiment shown, the pattern image of the digital seal can be visually integrated with the identity information of the party applying for the digital seal. Figure 6 Taking the sample image of the digital seal shown as an example, the "SFA" in the sample image is the watermark information of the identity information A of the enterprise A that applies for the digital seal. In this way, an informed person can view the identity information A of the enterprise A through the watermark information.

[0223] In one embodiment shown, after creating the above-mentioned digital seal for the above-mentioned digital seal applicant, a creation record corresponding to the digital seal can be generated, and the generated creation record can be published to the above-mentioned blockchain for evidence storage; wherein, the creation record can record relevant information of the digital seal applicant, relevant information of the digital seal, creation time and creation location (for example: positioning location information submitted by the digital seal applicant) and other information; the specific information can be pre-set by technical personnel according to actual needs.

[0224] In one embodiment shown, in the first aspect, the digital seal application transaction may carry the identity information of the digital seal applicant. In this case, the identity information of the digital seal applicant carried in the digital seal application transaction may be directly obtained, and the obtained identity information may be bound to the created digital seal.

[0225] On the second aspect, referring to the event mechanism of the aforementioned smart contract, when the above-mentioned smart contract is called and the above-mentioned digital seal is created, the smart contract can generate an event corresponding to the digital seal (called a creation completion event); wherein the creation completion event is used to indicate that the digital seal has been created. In this case, when the above-mentioned digital seal applicant obtains the creation completion event, it can respond to the creation completion event and submit the identity information to the smart contract through the Oracle oracle, so that the smart contract obtains the identity information through the Oracle oracle, and binds the obtained identity information to the created digital seal.

[0226] Specifically, when the client used by the digital seal applicant obtains the creation completion event, it can output the following information to the user who is the digital seal applicant: Figure 7 The user registration interface is shown. Figure 7As shown, the user of the digital seal applicant can enter the identity information of the user who is allowed to use the digital seal in the usage registration interface, and after completing the input, click the "Confirm" button in the usage registration interface; when the client detects the click operation on the "Confirm" button, it can submit the identity information of the user entered by the user of the digital seal applicant to the smart contract through the Oracle oracle.

[0227] It should be noted that the identity information of the digital seal applicant may be obtained by only using the first aspect or the second aspect, or by using both the first aspect and the second aspect at the same time, and this manual does not impose any restrictions on this.

[0228] In order to ensure the authenticity of the data, the digital seal applicant can use the private key in the CA certificate held by the digital seal applicant to sign the identity information when submitting the identity information to the smart contract; when the smart contract obtains the signed identity information, it can use the public key in the CA certificate held by the digital seal applicant to verify the signature to verify the authenticity of the identity information.

[0229] In actual applications, there may be multiple identity information of the digital seal applicant bound to the created digital seal. For example, assuming that the digital seal applicant holds multiple CA certificates, the public keys in multiple CA certificates can be used as the identity information of the digital seal applicant, and the identity information can be bound to the digital seal.

[0230] In the above technical solution, the node device in the blockchain can respond to the digital seal application transaction initiated by the digital seal applicant, call the application approval logic in the smart contract deployed on the blockchain, determine at least one application approval party corresponding to the digital seal, and instruct at least one application approval policy to apply for and approve the digital seal. If at least one application approval policy approves the application of the digital seal, the digital seal creation logic in the smart contract can be further called to create a digital seal for the digital seal applicant, and the binding relationship between the created digital seal and the identity information of the digital seal applicant can be published to the blockchain for evidence storage.

[0231] In this way, on the one hand, since the digital seal applicant can create the digital seal after the digital seal applicant's application is approved, the security and reliability of the digital seal creation can be guaranteed;

[0232] On the other hand, after a digital seal is created for the digital seal applicant, the digital seal and the identity information of the digital seal applicant are published to the blockchain for evidence storage. Therefore, when the digital seal is used later, the user's identity can be authenticated based on the corresponding binding relationship, thereby ensuring the security and reliability of the use of the digital seal.

[0233] Please refer to Figure 8 , Figure 8 It is a schematic diagram of another blockchain-based digital seal application system shown in an exemplary embodiment of this specification.

[0234] In such Figure 8 In the blockchain-based digital seal application system shown, a smart contract can be deployed on the blockchain. The smart contract may include a smart contract code for creating a digital seal for the digital seal applicant; specifically, the smart contract code of the smart contract may include a smart contract code corresponding to the digital seal creation logic, etc. In practical applications, by executing the smart contract code corresponding to the digital seal creation logic in the smart contract, the digital seal creation logic can be implemented to create a digital seal for the digital seal applicant.

[0235] It should be noted that the specific process of creating and calling a smart contract can refer to the creation and calling process of the aforementioned smart contract, and this manual will not go into details here.

[0236] In a specific implementation, a user can initiate a digital seal application request through a client that establishes a connection with the Baas platform; wherein the Baas platform can establish a connection with the client and the node device in the above-mentioned blockchain respectively. When the Baas platform receives the digital seal application request, it can first determine at least one application approval party corresponding to the digital seal, and instruct at least one application approval policy to apply for and approve the digital seal, and then send a transaction for calling the above-mentioned smart contract deployed on the blockchain to the node device in the blockchain when at least one application approval policy approves the application for the digital seal. When the node device in the blockchain receives the transaction, it can send the transaction to other node devices in the blockchain to perform consensus processing on the transaction, and after the consensus on the transaction is passed, execute the smart contract code in the smart contract to create a digital seal for the digital seal applicant.

[0237] In actual applications, the above-mentioned client can be deployed on an electronic device, which can be a server, computer, mobile phone, tablet device, laptop computer, PDA (Personal Digital Assistants), etc.; the above-mentioned Baas platform can be deployed on an electronic device, which can be a server, computer, etc.; the electronic device added to the above-mentioned blockchain as a node device can be a server, computer, mobile phone, tablet device, laptop computer, PDA, etc.; this manual does not limit this.

[0238] Please refer to Fig. 9 , Fig. 9 It is a flowchart of another method for applying for a digital seal based on blockchain as shown in an exemplary embodiment of this specification.

[0239] Combined with Figure 8 The blockchain-based digital seal application system shown in the figure, the blockchain-based digital seal application method can be applied to Figure 8 The Baas platform shown; the blockchain-based digital seal application method may include the following steps:

[0240] Step 901, receiving a digital seal application request initiated by a digital seal applicant;

[0241] Step 902: In response to the digital seal application request, determine at least one application and approval party corresponding to the digital seal, and instruct the at least one application and approval party to perform application and approval for the digital seal;

[0242] Step 903: If at least one of the applicants approves the application for the digital seal, a smart contract call transaction is sent to the node device, so that the node device responds to the smart contract call transaction, calls the digital seal creation logic corresponding to the smart contract code in the smart contract, creates a digital seal for the digital seal applicant, and publishes the binding relationship between the created digital seal and the identity information of the digital seal applicant to the blockchain for evidence storage.

[0243] In this embodiment, a smart contract can be deployed on the blockchain. A user who needs to apply for a digital seal (referred to as a digital seal applicant) can initiate a digital seal application request through a client that establishes a connection with the Baas platform.

[0244] In this embodiment, the Baas platform can determine at least one application and approval party corresponding to the digital seal that the digital seal applicant needs to apply for in response to the digital seal application transaction, and instruct the at least one application and approval policy to approve the application for the digital seal.

[0245] In this embodiment, when at least one application approval policy corresponding to the digital seal that the digital seal applicant needs to apply for is used to apply for and approve the digital seal, if at least one application approval policy approves the application for the digital seal, the Baas platform can send a smart contract call transaction for calling the smart contract deployed on the blockchain to the node device in the blockchain. The node device in the blockchain can respond to the smart contract call transaction, call the digital seal creation logic corresponding to the smart contract code in the smart contract, that is, execute the smart contract code corresponding to the digital seal creation logic in the smart contract, create the digital seal for the digital seal applicant, and publish the binding relationship between the created digital seal and the identity information of the digital seal applicant to the blockchain for evidence storage.

[0246] In one embodiment shown, the Baas platform may determine at least one applicant and approver corresponding to the digital seal based on the type of the digital seal applied for; and / or the Baas platform may determine at least one applicant and approver corresponding to the digital seal based on the identity information of the digital seal applicant.

[0247] In an illustrated implementation, the Baas platform may send an approval instruction message to the at least one applicant and approver, so that the at least one applicant and approver approves the application for the digital seal in response to the application approval message.

[0248] In one embodiment shown, the Baas platform can obtain the application and approval result of the digital seal by the at least one applicant and approver before sending the smart contract call transaction to the node device, and determine whether the application and approval of the digital seal by the at least one applicant and approver is passed based on the obtained application and approval result.

[0249] In one embodiment shown, the Baas platform may generate an application and approval record for the digital seal by the at least one application and approval party, and publish the generated application and approval record to the blockchain for evidence storage.

[0250] It should be noted that the specific method for the Baas platform to perform the above steps 901 to 903 can be referred to as follows Figure 5 The specific manner in which the node devices in the blockchain execute the above steps 501 to 503 in the blockchain-based digital seal application method shown will not be repeated in this specification.

[0251] In the above technical solution, the Baas platform can respond to the digital seal application request initiated by the digital seal applicant, determine at least one application approval party corresponding to the digital seal, and instruct at least one application approval policy to approve the application for the digital seal. If at least one application approval policy approves the application for the digital seal, a smart contract call transaction can be further sent to the node device in the blockchain, so that the node device in the blockchain calls the digital seal creation logic in the smart contract, creates a digital seal for the digital seal applicant, and publishes the binding relationship between the created digital seal and the identity information of the digital seal applicant to the blockchain for evidence storage.

[0252] In this way, on the one hand, since the digital seal applicant can create the digital seal after the digital seal applicant's application is approved, the security and reliability of the digital seal creation can be guaranteed;

[0253] On the other hand, after a digital seal is created for the digital seal applicant, the digital seal and the identity information of the digital seal applicant are published to the blockchain for evidence storage. Therefore, when the digital seal is used later, the user's identity can be authenticated based on the corresponding binding relationship, thereby ensuring the security and reliability of the use of the digital seal.

[0254] Corresponding to the aforementioned embodiment of the method for applying for a digital seal based on blockchain, this specification also provides an embodiment of a device for applying for a digital seal based on blockchain.

[0255] The embodiments of the digital seal application device based on blockchain in this specification can be applied to electronic devices. The device embodiments can be implemented through software, hardware, or a combination of software and hardware. Taking software implementation as an example, as a device in a logical sense, it is formed by the processor of the electronic device in which it is located reading the corresponding computer program instructions in the non-volatile memory into the memory and running them. From the hardware level, if Fig.10 The following is a hardware structure diagram of the electronic device where the blockchain-based digital seal application device is located. Fig.10 In addition to the processor, memory, network interface, and non-volatile memory shown, the electronic device where the device in the embodiment is located may also include other hardware according to the actual function of the blockchain-based digital seal application, which will not be described in detail.

[0256] Please refer to Fig.11 , Fig.11 This is a block diagram of a digital seal application device based on blockchain as shown in an exemplary embodiment of this specification. The digital seal application device based on blockchain 110 can be applied to Fig.10The electronic device shown can be used as a node device in the blockchain, and a smart contract for creating a digital seal for a digital seal applicant is deployed in the blockchain; the device 110 may include:

[0257] Receiving module 1101, receiving a digital seal application transaction initiated by a digital seal applicant;

[0258] The approval module 1102, in response to the digital seal application transaction, calls the application approval logic corresponding to the smart contract code in the smart contract, determines at least one application approval party corresponding to the digital seal, and instructs the at least one application approval party to perform application approval for the digital seal;

[0259] Creation module 1103, if at least one of the applicants approves the application for the digital seal, further calls the digital seal creation logic corresponding to the smart contract code in the smart contract, creates a digital seal for the digital seal applicant, and publishes the binding relationship between the created digital seal and the identity information of the digital seal applicant to the blockchain for evidence storage.

[0260] In this embodiment, the approval module 1102:

[0261] Based on the type of the digital seal applied for, at least one applicant and approver corresponding to the digital seal is determined; and / or based on the identity information of the digital seal applicant, at least one applicant and approver corresponding to the digital seal is determined.

[0262] In this embodiment, the approval module 1102:

[0263] A claim approval event corresponding to the at least one claim approval party is generated, so that when the at least one claim approval party obtains the claim approval event, it responds to the claim approval event and performs claim approval for the digital seal.

[0264] In this embodiment, the device 110 further includes:

[0265] Determination module 1104, the digital seal creation logic corresponding to the smart contract code in the smart contract is called, before creating a digital seal for the digital seal applicant, the approval management logic corresponding to the smart contract code in the smart contract is called to obtain the application approval result of the digital seal by at least one applicant and approver, and determine whether the application approval of the digital seal by at least one applicant and approver is passed based on the obtained application approval result.

[0266] In this embodiment, the device 110 further includes:

[0267] The first generating module 1105 generates an application and approval record for the digital seal by the at least one application and approval party, and publishes the generated application and approval record to the blockchain for evidence storage.

[0268] In this embodiment, the device further includes:

[0269] The second generation module 1106, after creating a digital seal for the digital seal applicant, generates a creation record corresponding to the digital seal, and publishes the generated creation record to the blockchain for evidence storage.

[0270] In this embodiment, the device 110 further includes:

[0271] The binding module 1107 obtains the identity information of the digital seal applicant carried in the digital seal application transaction before publishing the binding relationship between the created digital seal and the identity information of the digital seal applicant to the blockchain for evidence storage, and binds the obtained identity information to the created digital seal; and / or

[0272] The binding relationship between the created digital seal and the identity information of the digital seal applicant is generated before being published to the blockchain for evidence storage, and the identity information of the digital seal applicant submitted to the smart contract in response to the creation completion event when the creation completion event is obtained, and the obtained identity information is bound to the created digital seal.

[0273] In this embodiment, the identity information includes the public key in the CA certificate held by the digital seal applicant.

[0274] In this embodiment, the identity information further includes one or more combinations of the following:

[0275] The identity of the party applying for the digital seal;

[0276] The blockchain account identifier of the party applying for the digital seal;

[0277] Image information of the physical seal held by the digital seal applicant.

[0278] In this embodiment, the party applying for the digital seal is an enterprise; and the digital seal is the official seal of the enterprise.

[0279] In this embodiment, the digital seal created for the digital seal applicant includes a sample image of the digital seal and an identifier assigned to the digital seal.

[0280] In this embodiment, the pattern image of the digital seal visualizes and integrates the identity information of the digital seal applicant.

[0281] Please refer to Fig.12 , Fig.12 is a block diagram of another digital seal application device based on blockchain shown in an exemplary embodiment of this specification. The digital seal application device 120 based on blockchain can be applied to Fig.10 The electronic device shown can be used as a Baas platform connected to the node device in the blockchain; the blockchain is deployed with a smart contract for creating a digital seal for the digital seal applicant; the device 120 may include:

[0282] Receiving module 1201, receiving a digital seal application request initiated by a digital seal applicant;

[0283] The approval module 1202 determines at least one application and approval party corresponding to the digital seal in response to the digital seal application request, and instructs the at least one application and approval party to perform application and approval for the digital seal;

[0284] Creation module 1203, if at least one of the applicants and approvers approves the application for the digital seal, sends a smart contract call transaction to the node device, so that the node device responds to the smart contract call transaction, calls the digital seal creation logic corresponding to the smart contract code in the smart contract, creates a digital seal for the digital seal applicant, and publishes the binding relationship between the created digital seal and the identity information of the digital seal applicant to the blockchain for evidence storage.

[0285] In this embodiment, the approval module 1202:

[0286] Based on the type of the digital seal applied for, at least one applicant and approver corresponding to the digital seal is determined; and / or based on the identity information of the digital seal applicant, at least one applicant and approver corresponding to the digital seal is determined.

[0287] In this embodiment, the approval module 1202:

[0288] An approval instruction message is sent to the at least one application and approval party respectively, so that the at least one application and approval party performs application and approval for the digital seal in response to the application and approval message.

[0289] In this embodiment, the device 120 further includes:

[0290] Determination module 1204, before sending the smart contract call transaction to the node device, obtains the application and approval result of the at least one application and approval party for the digital seal, and determines whether the application and approval of the digital seal by the at least one application and approval party is passed based on the obtained application and approval result.

[0291] In this embodiment, the device 120 further includes:

[0292] The generation module 1205 generates an application and approval record for the digital seal by at least one application and approval party, and publishes the generated application and approval record to the blockchain for evidence storage.

[0293] In this embodiment, the identity information includes the public key in the CA certificate held by the digital seal applicant.

[0294] In this embodiment, the identity information further includes one or more combinations of the following:

[0295] The identity of the party applying for the digital seal;

[0296] The blockchain account identifier of the party applying for the digital seal;

[0297] Image information of the physical seal held by the digital seal applicant.

[0298] In this embodiment, the party applying for the digital seal is an enterprise; and the digital seal is the official seal of the enterprise.

[0299] In this embodiment, the digital seal created for the digital seal applicant includes a sample image of the digital seal and an identifier assigned to the digital seal.

[0300] In this embodiment, the pattern image of the digital seal visualizes and integrates the identity information of the digital seal applicant.

[0301] The implementation process of the functions and effects of each module in the above-mentioned device is specifically described in the implementation process of the corresponding steps in the above-mentioned method, which will not be repeated here.

[0302] For the device embodiment, since it basically corresponds to the method embodiment, the relevant parts can refer to the partial description of the method embodiment. The device embodiment described above is only schematic, wherein the modules described as separate components may or may not be physically separated, and the components displayed as modules may or may not be physical modules, that is, they may be located in one place, or they may be distributed on multiple network modules. Some or all of the modules may be selected according to actual needs to achieve the purpose of the scheme of this specification. A person of ordinary skill in the art can understand and implement it without paying creative labor.

[0303] The systems, devices, modules or units described in the above embodiments may be implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer, which may be in the form of a personal computer, a laptop computer, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email transceiver, a game console, a tablet computer, a wearable device or a combination of any of these devices.

[0304] In a typical configuration, a computer includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0305] The memory may include non-permanent storage in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM. The memory is an example of a computer-readable medium.

[0306] Computer-readable media include permanent and non-permanent, removable and non-removable media that can be used to store information by any method or technology. Information can be computer-readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical storage, magnetic cassettes, disk storage, quantum memory, graphene-based storage media or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer-readable media does not include temporary computer-readable media (transitory media), such as modulated data signals and carrier waves.

[0307] It should also be noted that the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, commodity or device. In the absence of more restrictions, the elements defined by the sentence "comprises a ..." do not exclude the existence of other identical elements in the process, method, commodity or device including the elements.

[0308] The above is a description of a specific embodiment of the specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recorded in the claims can be performed in an order different from that in the embodiments and still achieve the desired results. In addition, the processes depicted in the drawings do not necessarily require the specific order or continuous order shown to achieve the desired results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0309] The terms used in one or more embodiments of this specification are only for the purpose of describing specific embodiments, and are not intended to limit one or more embodiments of this specification. The singular forms of "a", "said" and "the" used in one or more embodiments of this specification and the appended claims are also intended to include plural forms, unless the context clearly indicates other meanings. It should also be understood that the term "and / or" used herein refers to and includes any or all possible combinations of one or more associated listed items.

[0310] It should be understood that although the terms first, second, third, etc. may be used to describe various information in one or more embodiments of this specification, these information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other. For example, without departing from the scope of one or more embodiments of this specification, the first information may also be referred to as the second information, and similarly, the second information may also be referred to as the first information. Depending on the context, the word "if" as used herein may be interpreted as "at the time of" or "when" or "in response to determining".

[0311] The above description is merely a preferred embodiment of one or more embodiments of the present specification and is not intended to limit one or more embodiments of the present specification. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of one or more embodiments of the present specification shall be included in the scope of protection of one or more embodiments of the present specification.

Claims

1. A digital seal application method based on blockchain, applied to a node device in the blockchain; a smart contract for creating a digital seal for a digital seal applicant is deployed in the blockchain; the method comprises: Receive digital seal application transactions initiated by digital seal applicants; In response to the digital seal application transaction, calling the application approval logic corresponding to the smart contract code in the smart contract, determining at least one application approval party corresponding to the digital seal, and instructing the at least one application approval party to apply for and approve the digital seal; The approval management logic corresponding to the smart contract code in the smart contract is called to obtain the application approval result of the digital seal by the at least one applicant and approver, and determine whether the application approval of the digital seal by the at least one applicant and approver is passed based on the obtained application approval result; if the application approval of the digital seal by the at least one applicant and approver is passed, the digital seal creation logic corresponding to the smart contract code in the smart contract is further called to create a digital seal for the digital seal applicant, and the binding relationship between the created digital seal and the identity information of the digital seal applicant is published to the blockchain for evidence storage.

2. According to the method of claim 1, the step of determining at least one applicant and approver corresponding to the digital seal comprises: Based on the type of the digital seal applied for, determining at least one application and approval party corresponding to the digital seal; And / or, based on the identity information of the digital seal applicant, determining at least one applicant and approver corresponding to the digital seal.

3. According to the method of claim 1, the step of instructing the at least one applicant and approving party to apply for and approve the digital seal comprises: A claim approval event corresponding to the at least one claim approval party is generated, so that when the at least one claim approval party obtains the claim approval event, it responds to the claim approval event and performs claim approval for the digital seal.

4. The method according to claim 1, further comprising: Generate an application and approval record for the digital seal by the at least one application and approval party, and publish the generated application and approval record to the blockchain for evidence storage.

5. The method according to claim 1, further comprising: After creating a digital seal for the digital seal applicant, a creation record corresponding to the digital seal is generated, and the generated creation record is published to the blockchain for evidence storage.

6. The method according to claim 1, before publishing the binding relationship between the created digital seal and the identity information of the digital seal applicant to the blockchain for evidence storage, further comprises: Acquire the identity information of the digital seal applicant carried in the digital seal application transaction, and bind the acquired identity information with the created digital seal; and / or, Generate a creation completion event corresponding to the digital seal, obtain the identity information of the digital seal applicant submitted to the smart contract in response to the creation completion event when the creation completion event is obtained, and bind the obtained identity information with the created digital seal.

7. The method according to claim 1 or 6, wherein the identity information includes a public key in a CA certificate held by the digital seal applicant.

8. The method according to claim 7, wherein the identity information further comprises a combination of one or more of the following: The identity of the party applying for the digital seal; The blockchain account identifier of the party applying for the digital seal; Image information of the physical seal held by the digital seal applicant.

9. According to the method of claim 1, the party applying for the digital seal is an enterprise; and the digital seal is the official seal of the enterprise.

10. The method according to claim 1, wherein the digital seal created for the digital seal claimant comprises a sample image of the digital seal and an identifier assigned to the digital seal.

11. The method according to claim 10, wherein the pattern image of the digital seal is visualized and integrated with the identity information of the party applying for the digital seal.

12. A digital seal application method based on blockchain, applied to a Baas platform connected to a node device in the blockchain; a smart contract for creating a digital seal for a digital seal applicant is deployed in the blockchain; the method comprises: Receive a digital seal application request initiated by a digital seal applicant; In response to the digital seal application request, determining at least one application and approval party corresponding to the digital seal, and instructing the at least one application and approval party to perform application and approval for the digital seal; Obtain the application and approval result of the digital seal by the at least one applicant and approver, and determine whether the application and approval of the digital seal by the at least one applicant and approver is passed based on the obtained application and approval result; if the application and approval of the digital seal by the at least one applicant and approver is passed, send a smart contract call transaction to the node device, so that the node device responds to the smart contract call transaction, calls the digital seal creation logic corresponding to the smart contract code in the smart contract, creates a digital seal for the digital seal applicant, and publishes the binding relationship between the created digital seal and the identity information of the digital seal applicant to the blockchain for evidence storage.

13. The method according to claim 12, wherein determining at least one applicant and approver corresponding to the digital seal comprises: Based on the type of the digital seal applied for, determining at least one application and approval party corresponding to the digital seal; And / or, based on the identity information of the digital seal applicant, determining at least one applicant and approver corresponding to the digital seal.

14. The method according to claim 12, wherein the step of instructing the at least one applicant to approve the digital seal comprises: An approval instruction message is sent to the at least one application and approval party respectively, so that the at least one application and approval party performs application and approval for the digital seal in response to the application and approval message.

15. The method according to claim 12, further comprising: Generate an application and approval record for the digital seal by the at least one application and approval party, and publish the generated application and approval record to the blockchain for evidence storage.

16. The method according to claim 12, wherein the identity information comprises a public key in a CA certificate held by the digital seal applicant.

17. The method according to claim 16, wherein the identity information further comprises a combination of one or more of the following: The identity of the party applying for the digital seal; The blockchain account identifier of the party applying for the digital seal; Image information of the physical seal held by the digital seal applicant.

18. According to the method of claim 12, the party applying for the digital seal is an enterprise; and the digital seal is the official seal of the enterprise.

19. The method according to claim 12, wherein the digital seal created for the digital seal claimant comprises a sample image of the digital seal and an identifier assigned to the digital seal.

20. The method according to claim 19, wherein the pattern image of the digital seal is visualized and integrated with the identity information of the party applying for the digital seal.

21. A digital seal application device based on blockchain, applied to a node device in the blockchain; a smart contract for creating a digital seal for a digital seal applicant is deployed in the blockchain; the device comprises: A receiving module receives a digital seal application transaction initiated by a digital seal applicant; An approval module, in response to the digital seal application transaction, calls the application approval logic corresponding to the smart contract code in the smart contract, determines at least one application approval party corresponding to the digital seal, and instructs the at least one application approval party to perform application approval for the digital seal; A determination module calls the approval management logic corresponding to the smart contract code in the smart contract, obtains the application approval result of the at least one application approval party for the digital seal, and determines whether the application approval of the at least one application approval party for the digital seal is passed based on the obtained application approval result; The creation module further calls the digital seal creation logic corresponding to the smart contract code in the smart contract if the at least one applicant and approver approves the application for the digital seal, creates a digital seal for the digital seal applicant, and publishes the binding relationship between the created digital seal and the identity information of the digital seal applicant to the blockchain for evidence storage.

22. The device according to claim 21, wherein the approval module: Based on the type of the digital seal applied for, at least one applicant and approver corresponding to the digital seal is determined; and / or based on the identity information of the digital seal applicant, at least one applicant and approver corresponding to the digital seal is determined.

23. The device according to claim 21, wherein the approval module: A claim approval event corresponding to the at least one claim approval party is generated, so that when the at least one claim approval party obtains the claim approval event, it responds to the claim approval event and performs claim approval for the digital seal.

24. The apparatus according to claim 21, further comprising: The first generation module generates an application and approval record for the digital seal by at least one application and approval party, and publishes the generated application and approval record to the blockchain for evidence storage.

25. The apparatus according to claim 21, further comprising: The second generation module, after creating a digital seal for the digital seal applicant, generates a creation record corresponding to the digital seal, and publishes the generated creation record to the blockchain for evidence storage.

26. The apparatus according to claim 21, further comprising: A binding module, which obtains the identity information of the digital seal applicant carried in the digital seal application transaction before publishing the binding relationship between the created digital seal and the identity information of the digital seal applicant to the blockchain for evidence storage, and binds the obtained identity information to the created digital seal; and / or, The binding relationship between the created digital seal and the identity information of the digital seal applicant is generated before being published to the blockchain for evidence storage, and the identity information of the digital seal applicant submitted to the smart contract in response to the creation completion event when the creation completion event is obtained, and the obtained identity information is bound to the created digital seal.

27. The device according to claim 21 or 26, wherein the identity information comprises a public key in a CA certificate held by the digital seal applicant.

28. The apparatus according to claim 27, wherein the identity information further comprises a combination of one or more of the following: The identity of the party applying for the digital seal; The blockchain account identifier of the party applying for the digital seal; Image information of the physical seal held by the digital seal applicant.

29. The device according to claim 21, wherein the party applying for the digital seal is an enterprise; and the digital seal is the official seal of the enterprise.

30. The apparatus according to claim 21, wherein the digital seal created for the digital seal claimant comprises a sample image of the digital seal and an identifier assigned to the digital seal.

31. The device according to claim 30, wherein the pattern image of the digital seal is visualized by integrating the identity information of the party applying for the digital seal.

32. A digital seal application device based on blockchain, applied to a Baas platform connected to a node device in the blockchain; a smart contract for creating a digital seal for a digital seal applicant is deployed in the blockchain; the device comprises: A receiving module receives a digital seal application request initiated by a digital seal applicant; An approval module, in response to the digital seal application request, determines at least one application and approval party corresponding to the digital seal, and instructs the at least one application and approval party to perform application and approval for the digital seal; A determination module, which obtains the application and approval result of the at least one application and approval party for the digital seal, and determines whether the application and approval of the digital seal by the at least one application and approval party is passed based on the obtained application and approval result; The creation module sends a smart contract call transaction to the node device if at least one of the applicants and approves the application for the digital seal, so that the node device responds to the smart contract call transaction, calls the digital seal creation logic corresponding to the smart contract code in the smart contract, creates a digital seal for the digital seal applicant, and publishes the binding relationship between the created digital seal and the identity information of the digital seal applicant to the blockchain for evidence storage.

33. The apparatus according to claim 32, wherein the approval module: Based on the type of the digital seal applied for, at least one applicant and approver corresponding to the digital seal is determined; and / or based on the identity information of the digital seal applicant, at least one applicant and approver corresponding to the digital seal is determined.

34. The apparatus according to claim 32, wherein the approval module: An approval instruction message is sent to the at least one application and approval party respectively, so that the at least one application and approval party performs application and approval for the digital seal in response to the application and approval message.

35. The apparatus of claim 32, further comprising: A generation module generates an application and approval record for the digital seal by at least one application and approval party, and publishes the generated application and approval record to the blockchain for evidence storage.

36. The apparatus according to claim 32, wherein the identity information comprises a public key in a CA certificate held by the digital seal claimant.

37. The apparatus according to claim 36, wherein the identity information further comprises a combination of one or more of the following: The identity of the party applying for the digital seal; The blockchain account identifier of the party applying for the digital seal; Image information of the physical seal held by the digital seal applicant.

38. According to the device of claim 32, the party applying for the digital seal is an enterprise; and the digital seal is the official seal of the enterprise.

39. The apparatus according to claim 32, wherein the digital seal created for the digital seal claimant comprises a sample image of the digital seal and an identifier assigned to the digital seal.

40. The device according to claim 39, wherein the pattern image of the digital seal is visualized and integrated with the identity information of the party applying for the digital seal.

41. An electronic device comprising: processor; a memory for storing processor-executable instructions; The processor implements the method as described in any one of claims 1-11 or 12-20 by running the executable instructions.

42. A computer-readable storage medium having computer instructions stored thereon, which, when executed by a processor, implement the method according to any one of claims 1-11 or 12-20.