CN112003694B - License issuing method, system, electronic equipment and medium based on blockchain - Google Patents
License issuing method, system, electronic equipment and medium based on blockchain Download PDFInfo
- Publication number
- CN112003694B CN112003694B CN202010795641.6A CN202010795641A CN112003694B CN 112003694 B CN112003694 B CN 112003694B CN 202010795641 A CN202010795641 A CN 202010795641A CN 112003694 B CN112003694 B CN 112003694B
- Authority
- CN
- China
- Prior art keywords
- license
- issuing
- signing
- issuers
- public
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 94
- 230000005484 gravity Effects 0.000 claims abstract description 16
- 238000012790 confirmation Methods 0.000 claims description 20
- 230000000694 effects Effects 0.000 claims description 11
- 230000008569 process Effects 0.000 description 24
- 238000010586 diagram Methods 0.000 description 13
- 238000010200 validation analysis Methods 0.000 description 9
- 230000005540 biological transmission Effects 0.000 description 5
- 238000012545 processing Methods 0.000 description 5
- 238000005516 engineering process Methods 0.000 description 4
- 238000004519 manufacturing process Methods 0.000 description 4
- KAICRBBQCRKMPO-UHFFFAOYSA-N phosphoric acid;pyridine-3,4-diamine Chemical compound OP(O)(O)=O.NC1=CC=NC=C1N KAICRBBQCRKMPO-UHFFFAOYSA-N 0.000 description 4
- 230000007547 defect Effects 0.000 description 3
- 230000006870 function Effects 0.000 description 2
- 230000006872 improvement Effects 0.000 description 2
- 230000002093 peripheral effect Effects 0.000 description 2
- 238000012546 transfer Methods 0.000 description 2
- 238000003491 array Methods 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 238000004590 computer program Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 238000011022 operating instruction Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/08—Key distribution or management, e.g. generation, sharing or updating, of cryptographic keys or passwords
- H04L9/0861—Generation of secret information including derivation or calculation of cryptographic keys or passwords
- H04L9/0869—Generation of secret information including derivation or calculation of cryptographic keys or passwords involving random numbers or seeds
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/10—Protecting distributed programs or content, e.g. vending or licensing of copyrighted material ; Digital rights management [DRM]
- G06F21/12—Protecting executable software
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/04—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks
- H04L63/0407—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks wherein the identity of one or more communicating identities is hidden
- H04L63/0421—Anonymous communication, i.e. the party's identifiers are hidden from the other party or parties, e.g. using an anonymizer
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/08—Key distribution or management, e.g. generation, sharing or updating, of cryptographic keys or passwords
- H04L9/0816—Key establishment, i.e. cryptographic processes or cryptographic protocols whereby a shared secret becomes available to two or more parties, for subsequent use
- H04L9/0819—Key transport or distribution, i.e. key establishment techniques where one party creates or otherwise obtains a secret value, and securely transfers it to the other(s)
- H04L9/0822—Key transport or distribution, i.e. key establishment techniques where one party creates or otherwise obtains a secret value, and securely transfers it to the other(s) using key encryption key
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/50—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols using hash chains, e.g. blockchains or hash trees
Landscapes
- Engineering & Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Signal Processing (AREA)
- Computer Networks & Wireless Communication (AREA)
- Theoretical Computer Science (AREA)
- Software Systems (AREA)
- Computer Hardware Design (AREA)
- General Engineering & Computer Science (AREA)
- Technology Law (AREA)
- General Physics & Mathematics (AREA)
- Physics & Mathematics (AREA)
- Multimedia (AREA)
- Computing Systems (AREA)
- Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
Abstract
One or more embodiments of the present specification disclose a blockchain-based license issuing method, system, electronic device, and medium. The license issuing method based on the blockchain is suitable for a license issuing system with license issuing contracts deployed on a blockchain network, wherein the license issuing contracts comprise the number of issuing parties and/or the proportion of the issuing parties to the signing rights, and the method comprises the following steps: after receiving a license application submitted by a user, generating a corresponding random key for an issuer; determining whether the number of issuers signing the license based on the random key reaches a first threshold value and/or whether the sum of the specific gravities of the signing rights reaches a second threshold value; if so, determining that the license is valid, and that the random key is invalidated after the license is valid; after encrypting the validated license using the public key of the client public-private key pair, uploading the encrypted license to the blockchain network so that the user views the license using the private key of the client public-private key pair.
Description
Technical Field
The present document relates to the field of blockchain technologies, and in particular, to a blockchain-based license issuing method, a blockchain-based license issuing system, an electronic device, and a medium.
Background
The commercial version of the software needs to be issued to the user by the owner of the copyright before the user can use the software, and the premise of the issue of the owner of the copyright is that the user purchases a license, such as a common Windows legal serial number, a legal serial number of Xmini software, a VIP account number of a hundred-degree cloud disk and the like, otherwise, the license only needs 14 days of trial time.
The person who needs to have the issuing authority can issue a license to the user, and the person who needs to have the authority can operate the generation of the Windows original serial number, and the person is the issuing party. The traditional issuing authority needs to generate a private key for an issuing party, and the private key generation process and storage mode are as follows: 1. the developer designs the code and designates the corresponding public key in the code, and the developer informs the issuer of the private key corresponding to the public key in the code library, so that the problem is that the developer and the issuer know the private key, and the risk of leakage of the private key exists, so that the property loss of the company can be influenced. 2. After the user initiates payment, the issuer signs the license, and the step has the defect that most private keys belong to confidential documents and can be required to be stored on the book offline by the issuer, so that the license is easy to lose, and the license cannot be retrieved after the license is lost, thereby causing loss. How to improve the security of license issuance and avoid the risk of issuing file leakage becomes a technical problem to be solved.
Disclosure of Invention
An object of one or more embodiments of the present disclosure is to provide a blockchain-based license issuing method, system, electronic device and medium, which can improve security of license issuing and avoid risk of issuing file leakage.
To solve the above technical problems, one or more embodiments of the present specification are implemented as follows:
in a first aspect, a blockchain-based license issuing method is provided, which is applicable to a license issuing system in which a license issuing contract is deployed on a blockchain network, wherein the license issuing contract includes the number of issuers and/or the proportion of the issuers to the signing rights, and the method includes: after receiving a license application submitted by a user, generating a corresponding random key for the issuer, wherein the license application carries a public key in a client public-private key pair corresponding to the user; determining whether the number of issuers signing a license based on the random key reaches a first threshold and/or whether the sum of the specific gravities of signing rights reaches a second threshold; if so, determining that the license is valid and that the random key is revoked after the license is valid; and after encrypting the effective license by using the public key in the public-private key pair of the client, uploading the encrypted license to a blockchain network so that the user can check the license by using the private key in the public-private key pair of the client.
In a second aspect, a blockchain-based license issuing system is provided, including a blockchain network and an issuing module, where a license issuing contract is deployed on the blockchain network, where the license issuing contract includes the number of issuing parties and/or the specific weight of the issuing parties in the signing rights, and the issuing module is configured to: after receiving a license application submitted by a user, generating a corresponding random key for the issuer, wherein the license application carries a public key in a client public-private key pair corresponding to the user; determining whether the number of issuers signing a license based on the random key reaches a first threshold and/or whether the sum of the specific gravities of signing rights reaches a second threshold; if so, determining that the license is valid and that the random key is revoked after the license is valid; and after encrypting the effective license by using the public key in the public-private key pair of the client, uploading the encrypted license to the blockchain network so that the user can check the license by using the private key in the public-private key pair of the client.
In a third aspect, an electronic device is provided, comprising: a processor; and a memory arranged to store computer executable instructions that, when executed, cause the processor to perform a blockchain-based license issuing method as described above.
In a fourth aspect, a storage medium is provided storing one or more programs that, when executed by an electronic device comprising a plurality of application programs, cause the electronic device to perform a blockchain-based license issuing method as described above.
As can be seen from the technical solutions provided in one or more embodiments of the present disclosure, in the blockchain-based license issuing method provided in the present disclosure is applicable to a license issuing system in which license issuing contracts are deployed on a blockchain network, the number of license issuing contract issuers and/or the proportion of signing rights occupied by the issuers are/is determined, after receiving a license application submitted by a user, a corresponding random key is generated for the issuers, the issuers may be multiple persons, a corresponding random key is generated for each of the issuers, the random keys of the issuers may be the same, or may be different, the issuers may take effect and fail the random keys after signing the licenses of the corresponding license application based on the corresponding random keys, the different license applications respectively correspond to different licenses, and after the issuers sign the licenses, it is determined whether the number of license issuing contract issuers and/or the proportion of signing rights reaches a set threshold; if the sum of the number of issuers and/or the specific gravity of the signing authority reaches a set threshold, the license is validated and the random key is invalidated. The corresponding random key is invalid after the signer signs the license each time, the signer needs to generate the corresponding random key again and immediately for the signer when signing the next license, and the generation of the random key is to automatically generate the key which is not known by other persons except the signer who knows the corresponding key, so that the security of signing the license by the signer is ensured, and the risk of leakage of the signed file is avoided. The license application submitted by the user comprises a public key in a client public-private key pair corresponding to the user, and finally, the validated license is encrypted by the public key and then uploaded to the blockchain network, the user uses the private key in the client public-private key pair to check the license, the blockchain network is a decentralization protocol, and the whole process from the validation of the license to the checking of the user is traceable and can not be tampered, so that the risk of leakage of the issued file is avoided.
Drawings
For a clearer description of one or more embodiments of the present description or of the solutions of the prior art, reference will be made below to the accompanying drawings which are used in the description of one or more embodiments or of the prior art, it being apparent that the drawings in the description below are only some of the embodiments described in the description, from which, without inventive faculty, other drawings can also be obtained for a person skilled in the art.
Fig. 1 is a schematic architecture diagram of a blockchain-based license issuing system in accordance with embodiments of the present description.
Fig. 2 is a schematic diagram of steps of a blockchain-based license issuing method according to an embodiment of the present disclosure.
FIG. 3 is a schematic diagram illustrating steps of another blockchain-based license issuing method according to an embodiment of the present disclosure.
FIG. 4 is a schematic diagram illustrating steps of another blockchain-based license issuing method according to an embodiment of the present disclosure.
FIG. 5 is a schematic diagram illustrating steps of another blockchain-based license issuing method according to an embodiment of the present disclosure.
FIG. 6 is a schematic diagram illustrating steps of another blockchain-based license issuing method according to an embodiment of the present disclosure.
FIG. 7 is a schematic diagram illustrating steps of another blockchain-based license issuing method according to an embodiment of the present disclosure.
FIG. 8 is a schematic diagram illustrating steps of another blockchain-based license issuing method according to an embodiment of the present disclosure.
Fig. 9 is a schematic structural diagram of a blockchain-based license issuing system according to an embodiment of the present disclosure.
Fig. 10 is a schematic structural diagram of another blockchain-based license issuing system according to an embodiment of the present disclosure.
Fig. 11 is a schematic structural diagram of yet another blockchain-based license issuing system provided in an embodiment of the present disclosure.
Fig. 12 is a schematic structural diagram of an electronic device according to an embodiment of the present disclosure.
Detailed Description
In order that those skilled in the art will better understand the technical solutions in this specification, a clear and complete description of the technical solutions in one or more embodiments of this specification will be provided below with reference to the accompanying drawings in one or more embodiments of this specification, and it is apparent that the one or more embodiments described are only a part of embodiments of this specification, not all embodiments. All other embodiments, which can be made by one or more embodiments of the present disclosure without inventive faculty, are intended to be within the scope of the present disclosure.
First, referring to fig. 1, a system architecture according to an embodiment of the present specification will be described. The blockchain-based license issuing system provided in the embodiments of the present specification may include: an issue module 100, a blockchain network 110, a management module 120, and an application module 130. In this application, the operation body of the issuing module 100 may be an issuing party, the operation body of the management module 120 may be an administrator, and the operation body of the application module 130 may be a user. The emphasis is on the improvement made by the issuing module 100, in combination with the blockchain network, to increase the security of license issuing. The blockchain network is a novel decentralization protocol, can safely store transaction data or other data, and can ensure that information cannot be counterfeited and tampered.
It can be understood that, the issuing module 100, the management module 120 and the application module 130 which can perform information transmission with the blockchain network shown in fig. 1 are authorized by the blockchain network authentication, so that the whole process from the generation of the random key and the checking of the license from the effectiveness to the user is traceable and can not be tampered, the security of issuing the license is ensured, and the risk of leakage of the issued file is avoided.
It should be noted that, in this specification, the issuing module 100, the management module 120, and the application module 130 may exist in the form of DAPPs, or may be different modules in the same DAPP, which is not limited herein. Further, the license issuance referred to in this specification may include two steps of license signing and transmitting the license to the user.
Example 1
Referring to fig. 2, a schematic diagram of steps of a blockchain-based license issuing method according to an embodiment of the present disclosure is shown. The license issuing method is suitable for a license issuing system in which a license issuing contract is deployed on a blockchain network, the license issuing contract comprises the number of issuing parties and/or the proportion of signing rights occupied by the issuing parties, the generation of a random key and the whole process of checking the license from an effectively-generated license to a user can be traced back based on the blockchain network, the license cannot be tampered, and the safety of the license issuing is ensured. The license issuing method based on the blockchain comprises the following steps:
step 10: generating a corresponding random key for an issuer after receiving a license application submitted by a user, wherein the license application carries a public key in a client public-private key pair corresponding to the user;
When a user purchases a certain software, the user needs to submit a license application for purchasing the software, wherein the license is a common Windows legal serial number, an Xmini software legal serial number, a hundred-degree cloud-disk VIP account number and the like, and the user can normally use the software only after taking the license.
The normal use of the software may be charged or may be free, for which the user needs to fill out an application form for the software to be purchased, and for which the user also needs to pay a fee for use, so that the license application mentioned in the embodiments of the present specification may contain information about the two operations performed by the user. The licenses of different software can be different, so that the application form filled by the user comprises application information such as software names, version numbers and the like, and the corresponding license can be signed based on the software information.
The random key is generated for the issuer enjoying the signing authority after receiving the license application submitted by the user, wherein the signing authority is the right to sign the license, the number of the issuers can be one or a plurality, and the signing authority can be distributed among the issuers according to percentages in the case of a plurality of issuers. In this step, a random key is generated for an issuer who enjoys the signing authority, and an issuer who does not hold the random key does not have the signing authority for an issuer who holds the random key can exercise the signing authority.
The random key is generated for the issuer after each time the license application submitted by the user is received, and therefore the random key is generated for the issuer after each time the license application submitted by the user is received, all the random keys generated for the issuer can be the same or different, and are not applied to the next license signing. And the issuer may be indeterminate or randomly select the issuer that enjoys the signing authority each time in a predetermined list.
It will be appreciated that the random key may be a string of characters, numbers, and special symbols, or may be in other forms, not limited herein.
The license application carries a public key of a client public-private key pair corresponding to the user, after the user registers application information of the license, the client public-private key pair is generated for the user, and the public key of the client public-private key pair is placed in the license application so that the effective license can be encrypted by the public key of the client public-private key pair and then sent to the blockchain network. The private key in the public-private key pair of the client is reserved by the user, and the license can be checked after the private key in the public-private key pair of the client is adopted for decryption later.
Step 20: determining whether the number of issuers signing the license based on the random key reaches a first threshold value and/or whether the sum of the specific gravities of the signing rights reaches a second threshold value;
before generating a random key for an issuer, a license issuing contract is deployed, wherein the number of the issuer and the proportion of the issuer to the signing rights are agreed, the number of the issuer can be more than two, and the signing rights of each issuer can be the same or different.
Corresponding random secret keys can be generated for different issuers in a DAPP mode, and the method that a plurality of issuers sign licenses is adopted, so that the risk that signing rights are concentrated in one person's hand, so that rights are too concentrated and technical loopholes of a license issuing system and economic losses of software companies exist is avoided.
In the case of multiple issuers, the condition for the license to be validated may be that the number of issuers reaches a first threshold, or whether the sum of the weights of the signing weights occupied by the issuers signing the license based on the random key reaches a second threshold, and the above two conditions may be a union or intersection determination manner, so that the number of issuers is not necessarily required to be in a state of being all in good order in the case of multiple issuers, or the sum of the weights of the signing weights occupied by the issuers signing the license based on the random key is not necessarily required to be a percentage, and the license can be validated as long as the number of the signers reaches the first threshold and/or the weight of the signing weights reaches a value. This is to take into account that the signing time does not necessarily allow someone to sign the license in time.
Step 30: if so, determining that the license is valid, and that the random key is invalidated after the license is valid;
after receiving the random key, the issuing party completes the license signing corresponding to the license application based on the random key, then the license takes effect, the signing of the license is completed, the random key is immediately invalid and cannot be used for signing the next license, and therefore the random key cannot be stolen and cannot be lost.
The embodiment of the specification combines the production of the random key and the signing of the license with the blockchain network, realizes the processes of the production, the use and the invalidation of the random key by utilizing the technical advantages of the blockchain network, ensures that the signing and the validation processes of the license are traceable and untampered, ensures the normal and safe use of the random key, and can not be stolen or lost.
Step 40: after encrypting the validated license using the public key of the client public-private key pair, the encrypted license is uploaded to the blockchain network to enable the user to view the license using the private key of the client public-private key pair.
And after the license is validated, encrypting and transmitting the validated license to the blockchain network by adopting a public key in a client public-private key pair, and after the validated license is monitored by a user, decrypting the encrypted license by adopting a private key in the client public-private key pair reserved by the user and checking the license. The encrypted transmission of the validated license to the blockchain may ensure that only the user can view the license, and no other person, including the issuer, can view the license.
The effective license is sent to the blockchain network, the license can be checked after the user monitors the effective license, and the issuing process of the license can be traceable and non-tamperable by combining the issuing of the license with the blockchain network through the blockchain network, so that the effective license is ensured to be safely sent to the user. The method overcomes the defect that in the traditional technical scheme, the issuing party is directly sent to the user, or forwarded to the user by the transfer person, or directly sent to the client through the traditional webpage version management software, so that leakage wind of the effective license is avoided.
Referring to FIG. 3, in some embodiments, step 10: before generating a random key for an issuer after receiving a license application submitted by a user, the license issuing method provided by the embodiment of the present specification further includes:
step 50: deploying a license issuing contract with respect to the issuing of the license, wherein the license issuing contract comprises the number of issuers and/or the proportion of the signing authority occupied by the issuers;
correspondingly, when the number of the issuing parties is more than two, step 10: random keys are generated for the issuers respectively.
When the intelligent contract agrees with more than two issuers, corresponding random keys are respectively generated for each issuer, the random keys of the issuers can be the same or different, the security of the license issuing system is improved, and the loss caused by the leakage of the random keys is avoided.
Referring to fig. 4, in some embodiments, step 10: after receiving a license application submitted by a user, before generating a corresponding random key for the issuer, the license issuing method provided in the embodiments of the present disclosure further includes:
step 60: sending a signing authority confirmation instruction to the blockchain network;
after the intelligent contract deployment is completed, a signing right confirmation instruction is sent to the blockchain network, so that an issuer can prove the signing right of the issuer, for example, identity information which is agreed with the signing right for the issuer in the intelligent contract such as a name, an identity card, a work number and the like. The issuer judges whether the issuer enjoys the signing authority or not by adopting zero knowledge to prove the signing authority of the issuer according to the identity information of the issuer.
The signing authority confirmation instruction is sent to the blockchain network, and the signing authority confirmation instruction aims to realize traceability and non-falsification of the signing authority confirmation process by utilizing the technical advantages of the blockchain network and improve the public confidence of the signing authority confirmation process.
Step 70: after the signing party monitors the signing right confirmation instruction, the signing right of the signing party is proved by adopting zero knowledge.
After hearing the signing authority confirmation instruction, the signing authority Fang Zaijian adopts zero knowledge to prove the signing authority of the signing party, and only the management module is proved that the signing authority is enjoyed by the signing party, namely the signing authority is available or unavailable, but the relevant identity information of the signing party is not displayed, the outside does not know who is the signing party, and the signing parties do not know whether the opposite party is the signing party.
Referring to fig. 5, in some embodiments, in the license issuing method provided in the embodiments of the present disclosure, when the number of issuing parties is more than two, step 30: determining that the license is valid and before the random key expires after the license is valid, the method further comprising:
step 80: the method and the device have the advantages that the number of the signed issuers which are not finished in the issuers is checked by the signed issuers, and the respective identities of the issuers are mutually hidden.
The issuer who has completed the signature can view the number of issuers that have not completed the signature, with the emphasis being only the number of issuers that have not completed the signature, and the respective identities are mutually hidden between the issuers, so that the identity outsiders of the issuers that have not completed the signature are not known.
Referring to fig. 6, in some embodiments, in the license issuing method provided in the embodiments of the present disclosure, when the number of issuing parties is more than two, step 30: determining that the license is valid and before the random key expires after the license is valid, the method further comprising:
step 300: when the signer which does not sign the license in the signer does not sign, the random key corresponding to the signer which does not sign in the signer is disabled.
If the issuer that does not sign the license in the license signing process, the random key corresponding to the issuer that does not sign the license in the issuer fails, and the step of signing the license by the issuer can be finished if the license takes effect or does not take effect.
Referring to fig. 7, in some embodiments, a license issuing method provided in the embodiments of the present disclosure, step 10: the method for generating the random key for the issuer specifically comprises the following steps:
step 100: randomly generating a public and private key pair of an issuer;
when issuing a license based on a blockchain, a public and private key pair of an issuer can be randomly generated for the issuer at each license issuing time, a private key in the public and private key pair is selected as a random key, and different issuers can adopt corresponding private keys to sign the license.
Step 110: and selecting a private key in the public and private key pair of the issuing party as a secret key.
The private key in the public-private key pair of the issuing party is only owned by the corresponding issuing party, and other people can obtain the private key differently, so that the security of the key is ensured.
Referring to fig. 8, in some embodiments, step 10: before receiving a license application submitted by a user, the license issuing method provided by the embodiment of the specification further includes:
Step 90: and generating a client public and private key pair for the user after the user registers the application information of the license.
The user needs to fill out the application form of the software to be purchased when buying the software, and the user also needs to pay the use fee for the charged software, so the license application mentioned in the embodiment of the present specification can contain the related information related to the purchase of the software by the user. The licenses of different software can be different, so that the application form filled by the user comprises software information such as a software name, a version number and the like, and the corresponding license can be signed based on the application information.
After the user registers the application information of the license, a client public-private key pair is generated for the user, and the public key in the client public-private key pair is placed in the license application so that the effective license can be encrypted by the public key in the client public-private key pair and then sent to the blockchain network. The private key in the public-private key pair of the client is reserved by the user, and the license can be checked after the private key in the public-private key pair of the client is adopted for decryption later.
Through the technical scheme, the license issuing method based on the blockchain is suitable for a license issuing system with license issuing contracts deployed on a blockchain network, the number of license issuing contract issuing parties and/or the proportion of signing rights occupied by the issuing parties are/is used for generating corresponding random keys for the issuing parties after receiving license applications submitted by users, the issuing parties can generate corresponding random keys for each issuing party, the random keys of the issuing parties can be the same or different, the issuing parties can take effect after signing the licenses of the corresponding license applications based on the corresponding random keys and the random keys are invalid, different license applications correspond to different licenses respectively, and after the issuing parties sign the licenses, whether the number of the license issuing contract issuing parties and/or the proportion of signing rights reach a set threshold value is judged; if the sum of the number of issuers and/or the specific gravity of the signing authority reaches a set threshold, the license is validated and the random key is invalidated. The corresponding random key is invalid after the signer signs the license each time, the signer needs to generate the corresponding random key again and immediately for the signer when signing the next license, and the generation of the random key is to automatically generate the key which is not known by other persons except the signer who knows the corresponding key, so that the security of signing the license by the signer is ensured, and the risk of leakage of the signed file is avoided. The license application submitted by the user comprises a public key in a client public-private key pair corresponding to the user, and finally, the validated license is encrypted by the public key and then uploaded to the blockchain network, the user uses the private key in the client public-private key pair to check the license, the blockchain network is a decentralization protocol, and the whole process from the validation of the license to the checking of the user is traceable and can not be tampered, so that the risk of leakage of the issued file is avoided.
Example two
Referring to FIG. 9, a blockchain-based license issuing system 10 is provided in an embodiment of the present description. The blockchain-based license issuing system 10 can realize the security of license issuing by combining a blockchain technology, the traceability and the authenticity of the whole process from the effective generation of a secret key to the checking of a user can be realized, and the risk of issuing a file leakage can be avoided. The blockchain-based license issuing system comprises an issuing module 100 and a blockchain network 110, wherein a license issuing contract is deployed on the blockchain network 110, the license issuing contract comprises the number of issuing parties and/or the proportion of the issuing parties to the signing rights, and the issuing module 100 is used for:
after receiving a license application submitted by a user, generating a corresponding random key for an issuer, wherein the license application carries a public key in a client public-private key pair corresponding to the user;
when a user purchases a certain software, the user needs to submit a license application for purchasing the software, wherein the license is a common Windows legal serial number, an Xmini software legal serial number, a hundred-degree cloud-disk VIP account number and the like, and the user can normally use the software only after taking the license.
The normal use of the software may be charged or may be free, for which the user needs to fill out an application form for the software to be purchased, and for which the user also needs to pay a fee for use, so that the license application mentioned in the embodiments of the present specification may contain information about the two operations performed by the user. The licenses of different software can be different, so that the application form filled by the user comprises software information such as a software name, a version number and the like, and the corresponding license can be signed based on the software information.
The random key is generated for the issuer enjoying the signing authority after receiving the license application submitted by the user, wherein the signing authority is the right to sign the license, the number of the issuers can be one or a plurality, and the signing authority can be distributed among the issuers according to percentages in the case of a plurality of issuers. In this step, a random key is generated for an issuer who enjoys the signing authority, and an issuer who does not hold the random key does not have the signing authority for an issuer who holds the random key can exercise the signing authority.
The random key is generated for the issuer after each time the license application submitted by the user is received, and therefore the random key is generated for the issuer after each time the license application submitted by the user is received, all the random keys generated for the issuer can be the same or different, and are not applied to the next license signing. And the issuer may be indeterminate or randomly select the issuer that enjoys the signing authority each time in a predetermined list.
It will be appreciated that the random key may be a string of characters, numbers, and special symbols, or may be in other forms, not limited herein. After signing the license corresponding to the license application based on the random key, the issuing party realizes the license validation and the key is invalid after the license validation;
the license application carries a public key of a client public-private key pair corresponding to the user, after the user registers application information of the license, the client public-private key pair is generated for the user, and the public key of the client public-private key pair is placed in the license application so that the effective license can be encrypted by the public key of the client public-private key pair and then sent to the blockchain network. The private key in the public-private key pair of the client is reserved by the user, and the license can be checked after the private key in the public-private key pair of the client is adopted for decryption later.
Determining whether the number of issuers signing the license based on the random key reaches a first threshold value and/or whether the sum of the specific gravities of the signing rights reaches a second threshold value;
before generating a random key for an issuer, a license issuing contract is deployed, wherein the number of the issuer and the proportion of the issuer to the signing rights are agreed, the number of the issuer can be more than two, and the signing rights of each issuer can be the same or different.
Corresponding random secret keys can be generated for different issuers in a DAPP mode, and the method that a plurality of issuers sign licenses is adopted, so that the risk that signing rights are concentrated in one person's hand, so that rights are too concentrated and technical loopholes of a license issuing system and economic losses of software companies exist is avoided.
In the case of multiple issuers, the condition that the license is validated may be that the number of issuers reaches a first threshold value, or that the sum of the specific gravities of the signing rights occupied by the issuers signing the license based on the random key reaches a second threshold value, and the above two judgment conditions may be a union or intersection judgment manner, so that the number of issuers is not necessarily required to be in a state of being all in good order in the case of multiple issuers, or the specific gravity of the signing rights is not necessarily required to be in a percentage, and the license may be as long as the number of signers reaches the first threshold value and/or the specific gravity of the signing rights is validated reaches a value. This is to take into account that the signing time does not necessarily allow someone to sign the license in time.
If so, determining that the license is valid, and that the random key is invalidated after the license is valid;
after receiving the random key, the issuing party completes the license signing corresponding to the license application based on the random key, then the license takes effect, the signing of the license is completed, the random key is immediately invalid and cannot be used for signing the next license, and therefore the random key cannot be stolen and cannot be lost.
The embodiment of the specification combines the production of the random key and the signing of the license with the blockchain network, realizes the processes of the production, the use and the invalidation of the random key by utilizing the technical advantages of the blockchain network, ensures that the signing and the validation processes of the license are traceable and untampered, ensures the normal and safe use of the random key, and can not be stolen or lost.
After encrypting the validated license using the public key of the client public-private key pair, uploading the encrypted license to the blockchain network so that the user views the license using the private key of the client public-private key pair.
Thus, the license is validated and then encrypted using the public key of the client public-private key pair to send the validated license to the blockchain network, and the user checks the license after hearing the validated license and decrypting the encrypted license using the private key of the client public-private key pair maintained by the user. The encrypted transmission of the validated license to the blockchain may ensure that only the user can view the license, and no other person, including the issuer, can view the license.
The effective license is issued to the blockchain network, after the user monitors the effective license, the user can check the license after decrypting by using the private key in the public and private key pair of the client, and the issuing process of the license can be traceable and non-tamperable by combining the issuing of the license with the blockchain network and realizing the issuing process of the license through the blockchain network, so that the effective license is ensured to be safely delivered to the user. The method overcomes the defect that in the traditional technical scheme, the issuing party is directly sent to the user, or forwarded to the user by the transfer person, or directly sent to the client through the traditional webpage version management software, so that leakage wind of the effective license is avoided.
Referring to fig. 10, in some embodiments, the license issuing system provided in the embodiments of the present disclosure further includes a management module 120, after receiving a license application submitted by a user, before generating a random key for an issuer, the management module 120 is configured to:
deploying a license issuing contract with respect to the issuing of the license, wherein the license issuing contract agrees with the number of issuers and/or the proportion of the signing authority occupied by the issuers;
before generating a random key for an issuer, deploying a license issuing contract, wherein the number of the contracted issuers and the proportion of the issuers to the signing rights are agreed, the number of the issuers can be more than two, and the signing rights of each issuer can be the same or different.
Corresponding random secret keys can be generated for different issuers in a DAPP mode, and the method that a plurality of issuers sign licenses is adopted, so that the risk that signing rights are concentrated in one person's hand, so that rights are too concentrated and technical loopholes of a license issuing system and economic losses of software companies exist is avoided.
Correspondingly, when the number of the issuing parties is greater than or equal to two, the issuing module 100 is specifically configured to:
random keys are generated for the issuers respectively.
When the intelligent contract agrees with more than two issuers, corresponding random keys are respectively generated for each issuer, the random keys of the issuers can be the same or different, the security of the license issuing system is improved, and the loss caused by the leakage of the random keys is avoided.
In some embodiments, in the license issuing system provided in the embodiments of the present disclosure, the management module 120 is configured to:
sending a signing authority confirmation instruction to the blockchain network;
after the intelligent contract deployment is completed, a signing right confirmation instruction is sent to the blockchain network, so that an issuer can prove the signing right of the issuer, for example, identity information which is agreed with the signing right for the issuer in the intelligent contract such as a name, an identity card, a work number and the like. The issuer judges whether the issuer enjoys the signing authority or not by adopting zero knowledge to prove the signing authority of the issuer according to the identity information of the issuer.
The signing authority confirmation instruction is sent to the blockchain network, and the signing authority confirmation instruction aims to realize traceability and non-falsification of the signing authority confirmation process by utilizing the technical advantages of the blockchain network and improve the public confidence of the signing authority confirmation process.
Correspondingly, the issuing module 100 is further configured to:
after the signing party monitors the signing right confirmation instruction, the signing right of the signing party is proved by adopting zero knowledge.
After hearing the signing authority confirmation instruction, the signing authority Fang Zaijian adopts zero knowledge to prove the signing authority of the signing party, and only the management module is proved that the signing authority is enjoyed by the signing party, namely the signing authority is available or unavailable, but the relevant identity information of the signing party is not displayed, the outside does not know who is the signing party, and the signing parties do not know whether the opposite party is the signing party.
In some embodiments, in the license issuing system provided in the embodiments of the present disclosure, when the number of issuing parties is more than two, the issuing module 100 is further configured to:
the method and the device have the advantages that the number of the signed issuers which are not finished in the issuers is checked by the signed issuers, and the respective identities of the issuers are mutually hidden.
The issuer who has completed the signature can view the number of issuers that have not completed the signature, with the emphasis being only the number of issuers that have not completed the signature, and the respective identities are mutually hidden between the issuers, so that the identity outsiders of the issuers that have not completed the signature are not known.
In some embodiments, the license issuing system provided in the embodiments of the present disclosure, when the number of issuing parties is more than two, the issuing module 100 is further configured to:
when the signer which does not sign the license in the signer does not sign, the random key corresponding to the signer which does not sign in the signer is disabled.
If the signer with incomplete signing does not sign the license in the license signing process, the random key corresponding to the signer with incomplete signing in the signer is invalid, the license signing time can be contracted, the random key corresponding to the signer with incomplete signing is invalid after the license signing time is finished, the step of signing the license by the signer is finished, and the method is suitable for the condition that the license is valid or invalid.
In some embodiments, in the license issuing system provided in the embodiments of the present disclosure, the issuing module 100 is further configured to:
randomly generating a public and private key pair of an issuer;
when issuing a license based on a blockchain, a public and private key pair of an issuer can be randomly generated for the issuer at each license issuing time, a private key in the public and private key pair is selected as a random key, and different issuers can adopt corresponding private keys to sign the license.
And selecting a private key in the public and private key pair of the issuing party as a secret key.
The private key in the public-private key pair of the issuing party is only owned by the corresponding issuing party, and other people can obtain the private key differently, so that the security of the key is ensured.
In some embodiments, the license issuing system provided in the embodiments of the present disclosure further includes an application module 130, where the application module 130 is configured to:
and generating a client public and private key pair for the user after the user registers the application information of the license.
The user needs to fill out the application form of the software to be purchased when buying the software, and the user also needs to pay the use fee for the charged software, so the license application mentioned in the embodiment of the present specification can contain the related information related to the purchase of the software by the user. The licenses of different software can be different, so that the application form filled by the user comprises software information such as a software name, a version number and the like, and the corresponding license can be signed based on the application information.
After the user registers the application information of the license, a client public-private key pair is generated for the user, and the public key in the client public-private key pair is placed in the license application so that the effective license can be encrypted by the public key in the client public-private key pair and then sent to the blockchain network. The private key in the public-private key pair of the client is reserved by the user, and the license can be checked after the private key in the public-private key pair of the client is adopted for decryption later.
Through the technical scheme, the license issuing method based on the blockchain is suitable for a license issuing system with license issuing contracts deployed on a blockchain network, the number of license issuing contract issuing parties and/or the proportion of signing rights occupied by the issuing parties are/is used for generating corresponding random keys for the issuing parties after receiving license applications submitted by users, the issuing parties can generate corresponding random keys for each issuing party, the random keys of the issuing parties can be the same or different, the issuing parties can take effect after signing the licenses of the corresponding license applications based on the corresponding random keys and the random keys are invalid, different license applications respectively correspond to different licenses, and after the issuing parties sign the licenses, whether the sum of the number of the license issuing contract issuing parties and/or the proportion of signing rights reaches a set threshold value is judged; if the sum of the number of issuers and/or the specific gravity of the signing authority reaches a set threshold, the license is validated and the random key is invalidated. The corresponding random key is invalid after the signer signs the license each time, the signer needs to generate the corresponding random key again and immediately for the signer when signing the next license, and the generation of the random key is to automatically generate the key which is not known by other persons except the signer who knows the corresponding key, so that the security of signing the license by the signer is ensured, and the risk of leakage of the signed file is avoided. The license application submitted by the user comprises a public key in a client public-private key pair corresponding to the user, and finally, the validated license is encrypted by the public key and then uploaded to the blockchain network, the user uses the private key in the client public-private key pair to check the license, the blockchain network is a decentralization protocol, and the whole process from the validation of the license to the checking of the user is traceable and can not be tampered, so that the risk of leakage of the issued file is avoided.
Example III
Fig. 12 is a schematic structural view of an electronic device according to an embodiment provided in the present specification. At the hardware level, the electronic device comprises a processor, optionally an internal bus, a network interface, a memory. The Memory may include a Memory, such as a Random-Access Memory (RAM), and may further include a non-volatile Memory (non-volatile Memory), such as at least 1 disk Memory. Of course, the electronic device may also include hardware required for other services.
The processor, network interface, and memory may be interconnected by an internal bus, which may be an ISA (Industry Standard Architecture ) bus, a PCI (Peripheral Component Interconnect, peripheral component interconnect standard) bus, or EISA (Extended Industry Standard Architecture ) bus, among others. The buses may be classified as address buses, data buses, control buses, etc. For ease of illustration, only one bi-directional arrow is shown in FIG. 12, but not only one bus or type of bus.
And the memory is used for storing programs. In particular, the program may include program code including computer-operating instructions. The memory may include memory and non-volatile storage and provide instructions and data to the processor.
The processor reads the corresponding computer program from the nonvolatile memory into the memory and then runs to form the block chain consensus device on a logic level. The processor executes the program stored in the memory, and is specifically configured to execute the method steps corresponding to each execution body in the embodiments of the present disclosure.
The methods disclosed in the embodiments shown in fig. 2 to 8 of the present specification may be applied to a processor or implemented by a processor. The processor may be an integrated circuit chip having signal processing capabilities. In implementation, the steps of the above method may be performed by integrated logic circuits of hardware in a processor or by instructions in the form of software. The processor may be a general-purpose processor, including a central processing unit (Central Processing Unit, CPU), a network processor (Network Processor, NP), etc.; but also digital signal processors (Digital Signal Processor, DSP), application specific integrated circuits (Application Specific Integrated Circuit, ASIC), field programmable gate arrays (Field-Programmable Gate Array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components. The methods, steps, and logic blocks disclosed in one or more embodiments of the present description may be implemented or performed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of a method disclosed in connection with one or more embodiments of the present disclosure may be embodied directly in a hardware decoding processor or in a combination of hardware and software modules in a decoding processor. The software modules may be located in a random access memory, flash memory, read only memory, programmable read only memory, or electrically erasable programmable memory, registers, etc. as well known in the art. The storage medium is located in a memory, and the processor reads the information in the memory and, in combination with its hardware, performs the steps of the above method.
The electronic device may also execute the method of the embodiment shown in fig. 2 to 8 and implement the functions of the corresponding apparatus in the embodiment shown in fig. 9 to 11, which are not described herein again.
Of course, in addition to the software implementation, the electronic device of the embodiments of the present disclosure does not exclude other implementations, such as a logic device or a combination of software and hardware, that is, the execution subject of the following processing flow is not limited to each logic unit, but may also be hardware or a logic device.
Through the technical scheme, the license issuing method based on the blockchain is suitable for a license issuing system with license issuing contracts deployed on a blockchain network, the number of license issuing contract issuing parties and/or the proportion of signing rights occupied by the issuing parties are/is used for generating corresponding random keys for the issuing parties after receiving license applications submitted by users, the issuing parties can generate corresponding random keys for each issuing party, the random keys of the issuing parties can be the same or different, the issuing parties can take effect after signing the licenses of the corresponding license applications based on the corresponding random keys and the random keys are invalid, different license applications respectively correspond to different licenses, and after the issuing parties sign the licenses, whether the sum of the number of the license issuing contract issuing parties and/or the proportion of signing rights reaches a set threshold value is judged; if the sum of the number of issuers and/or the specific gravity of the signing authority reaches a set threshold, the license is validated and the random key is invalidated. The corresponding random key is invalid after the signer signs the license each time, the signer needs to generate the corresponding random key again and immediately for the signer when signing the next license, and the generation of the random key is to automatically generate the key which is not known by other persons except the signer who knows the corresponding key, so that the security of signing the license by the signer is ensured, and the risk of leakage of the signed file is avoided. The license application submitted by the user comprises a public key in a client public-private key pair corresponding to the user, and finally, the validated license is encrypted by the public key and then uploaded to the blockchain network, the user uses the private key in the client public-private key pair to check the license, the blockchain network is a decentralization protocol, and the whole process from the validation of the license to the checking of the user is traceable and can not be tampered, so that the risk of leakage of the issued file is avoided.
Example IV
The present description also proposes a computer-readable storage medium storing one or more programs, the one or more programs comprising instructions, which when executed by an electronic device comprising a plurality of application programs, enable the electronic device to perform the methods of the embodiments shown in fig. 2-8.
Through the technical scheme, the license issuing method based on the blockchain is suitable for a license issuing system with license issuing contracts deployed on a blockchain network, the number of license issuing contract issuing parties and/or the proportion of signing rights occupied by the issuing parties are/is used for generating corresponding random keys for the issuing parties after receiving license applications submitted by users, the issuing parties can generate corresponding random keys for each issuing party, the random keys of the issuing parties can be the same or different, the issuing parties can take effect after signing the licenses of the corresponding license applications based on the corresponding random keys and the random keys are invalid, different license applications respectively correspond to different licenses, and after the issuing parties sign the licenses, whether the sum of the number of the license issuing contract issuing parties and/or the proportion of signing rights reaches a set threshold value is judged; if the sum of the number of issuers and/or the specific gravity of the signing authority reaches a set threshold, the license is validated and the random key is invalidated. The corresponding random key is invalid after the signer signs the license each time, the signer needs to generate the corresponding random key again and immediately for the signer when signing the next license, and the generation of the random key is to automatically generate the key which is not known by other persons except the signer who knows the corresponding key, so that the security of signing the license by the signer is ensured, and the risk of leakage of the signed file is avoided. The license application submitted by the user comprises a public key in a client public-private key pair corresponding to the user, and finally, the validated license is encrypted by the public key and then uploaded to the blockchain network, the user uses the private key in the client public-private key pair to check the license, the blockchain network is a decentralization protocol, and the whole process from the validation of the license to the checking of the user is traceable and can not be tampered, so that the risk of leakage of the issued file is avoided.
In summary, the foregoing description is only a preferred embodiment of the present invention and is not intended to limit the scope of the present invention. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present specification should be included in the protection scope of the present specification.
The systems, devices, modules, or units illustrated in one or more of the embodiments described above may be implemented in particular by a computer chip or entity, or by a product having some function. One typical implementation is a computer. In particular, the computer may be, for example, a personal computer, a laptop computer, a cellular telephone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.
Computer readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of storage media for a computer include, but are not limited to, phase change memory (PRAM), static Random Access Memory (SRAM), dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), read Only Memory (ROM), electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium, which can be used to store information that can be accessed by a computing device. Computer-readable media, as defined herein, does not include transitory computer-readable media (transmission media), such as modulated data signals and carrier waves.
It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article or apparatus that comprises the element.
In this specification, each embodiment is described in a progressive manner, and identical and similar parts of each embodiment are all referred to each other, and each embodiment mainly describes differences from other embodiments. In particular, for system embodiments, since they are substantially similar to method embodiments, the description is relatively simple, as relevant to see a section of the description of method embodiments.
The foregoing describes specific embodiments of the present disclosure. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims can be performed in a different order than in the embodiments and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.
Claims (12)
1. A blockchain-based license issuing method suitable for use in a license issuing system having a license issuing contract deployed on a blockchain network, the license issuing contract including a number of issuers and/or a specific gravity of signing rights occupied by the issuers, the method comprising:
after receiving a license application submitted by a user, generating a corresponding random key for the issuer, wherein the license application carries a public key in a client public-private key pair corresponding to the user;
determining whether the number of issuers signing a license based on the random key reaches a first threshold and/or whether the sum of the specific gravities of signing rights reaches a second threshold;
if so, determining that the license is valid and that the random key is revoked after the license is valid;
and after encrypting the effective license by using the public key in the public-private key pair of the client, uploading the encrypted license to a blockchain network so that the user can check the license by using the private key in the public-private key pair of the client.
2. The license issuing method according to claim 1, before generating a corresponding random key for the issuer after receiving a license application submitted by a user, the method further comprising:
Sending a signing authority confirmation instruction to the blockchain network;
after the issuer monitors the signing right confirmation instruction, zero knowledge is adopted to prove the signing right of the issuer.
3. The license issuing method according to claim 1, wherein when the number of issuing parties is two or more, the license is determined to be in effect, and before the random key is invalidated after the license is in effect, the method further comprising:
the method comprises the steps that the signed issuers in the issuers are checked to see the number of the issuers which do not complete signing in the issuers, and the respective identities of the issuers are mutually hidden.
4. A license issuing method according to any one of claims 1 to 3, wherein when the number of issuing parties is two or more, the license is determined to be validated, and before the random key is invalidated after the license is validated, the method further comprising:
and when the signer which does not sign the license in the signer does not sign the license, the random key corresponding to the signer which does not sign in the signer is disabled.
5. The license issuing method according to claim 1, wherein the generating of the random key for the issuer specifically comprises:
Randomly generating a public and private key pair of an issuer;
and selecting a private key in the public and private key pair of the issuer as the random key.
6. The license issuing system based on the blockchain comprises a blockchain network and an issuing module, wherein license issuing contracts are deployed on the blockchain network, the license issuing contracts comprise the number of issuing parties and/or the proportion of the issuing parties to the signing rights, and the issuing module is used for:
after receiving a license application submitted by a user, generating a corresponding random key for the issuer, wherein the license application carries a public key in a client public-private key pair corresponding to the user;
determining whether the number of issuers signing a license based on the random key reaches a first threshold and/or whether the sum of the specific gravities of signing rights reaches a second threshold;
if so, determining that the license is valid and that the random key is revoked after the license is valid;
and after encrypting the effective license by using the public key in the public-private key pair of the client, uploading the encrypted license to the blockchain network so that the user can check the license by using the private key in the public-private key pair of the client.
7. The license issuing system according to claim 6, further comprising a management module for:
sending a signing authority confirmation instruction to the blockchain network;
correspondingly, the issuing module is further configured to:
after the issuer monitors the signing right confirmation instruction, zero knowledge is adopted to prove the signing right of the issuer.
8. The license issuing system according to claim 6, wherein the issuing module is further configured to, in a case where the number of issuing parties is two or more:
the method comprises the steps that the signed issuers in the issuers are checked to see the number of the issuers which do not complete signing in the issuers, and the respective identities of the issuers are mutually hidden.
9. The license issuing system according to any one of claims 6 to 8, wherein the issuing module is further configured to, in a condition that the number of issuing parties is two or more:
and when the signer which does not sign the license in the signer does not sign the license, the random key corresponding to the signer which does not sign in the signer is disabled.
10. The license issuing system according to claim 6, the issuing module further being configured to:
randomly generating a public and private key pair of an issuer;
And selecting a private key in the public and private key pair of the issuer as the random key.
11. An electronic device, comprising:
a processor; and
a memory arranged to store computer executable instructions that when executed cause the processor to perform the blockchain-based license issuing method of any of claims 1 to 5.
12. A storage medium storing one or more programs that, when executed by an electronic device comprising a plurality of application programs, cause the electronic device to perform the blockchain-based license issuing method of any of claims 1-5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010795641.6A CN112003694B (en) | 2020-08-10 | 2020-08-10 | License issuing method, system, electronic equipment and medium based on blockchain |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010795641.6A CN112003694B (en) | 2020-08-10 | 2020-08-10 | License issuing method, system, electronic equipment and medium based on blockchain |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112003694A CN112003694A (en) | 2020-11-27 |
| CN112003694B true CN112003694B (en) | 2023-06-23 |
Family
ID=73463231
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010795641.6A Active CN112003694B (en) | 2020-08-10 | 2020-08-10 | License issuing method, system, electronic equipment and medium based on blockchain |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112003694B (en) |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101694685A (en) * | 2009-10-12 | 2010-04-14 | 南京联创科技集团股份有限公司 | Safety product license management method based on XML encryption and digital certificate |
| WO2019034951A1 (en) * | 2017-08-15 | 2019-02-21 | nChain Holdings Limited | Threshold digital signature method and system |
| CN110601848A (en) * | 2019-09-10 | 2019-12-20 | 北京清红微谷技术开发有限责任公司 | Appointment information processing method, device and system based on block chain and electronic equipment |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| IL121550A (en) * | 1997-08-14 | 2003-07-31 | Diversinet Corp | System and method for handling permits |
| CN108600272B (en) * | 2018-05-10 | 2020-08-04 | 阿里巴巴集团控股有限公司 | Block chain data processing method, device, processing equipment and system |
-
2020
- 2020-08-10 CN CN202010795641.6A patent/CN112003694B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101694685A (en) * | 2009-10-12 | 2010-04-14 | 南京联创科技集团股份有限公司 | Safety product license management method based on XML encryption and digital certificate |
| WO2019034951A1 (en) * | 2017-08-15 | 2019-02-21 | nChain Holdings Limited | Threshold digital signature method and system |
| CN110601848A (en) * | 2019-09-10 | 2019-12-20 | 北京清红微谷技术开发有限责任公司 | Appointment information processing method, device and system based on block chain and electronic equipment |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112003694A (en) | 2020-11-27 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11443368B2 (en) | Resource transfer and capital transfer method and apparatus | |
| US20220277307A1 (en) | Systems and methods for personal identification and verification | |
| CN107086909B (en) | Identity information generation method and device and identity verification method and device | |
| CN108681853B (en) | Logistics information transmission method, system and device based on block chain | |
| TWI736705B (en) | Business processing method and device | |
| CN112215601B (en) | Service processing method, device and equipment based on block chain | |
| CN113255005B (en) | Block chain-based data asset circulation method, device and equipment | |
| KR100868121B1 (en) | Method for using trusted, hardware-based identity credentials in runtime package signature to secure mobile communications and high-value transaction execution | |
| JP2020512779A (en) | Method and apparatus for processing transaction requests | |
| CN111770199B (en) | Information sharing method, device and equipment | |
| CN111814195B (en) | Data management method, device and equipment based on trusted hardware | |
| JP3731867B2 (en) | Access control for computers | |
| US20230080322A1 (en) | User id codes for online verification | |
| JP2000222362A (en) | Method and device for realizing multiple security check point | |
| CN109388957B (en) | Block chain-based information transfer method, device, medium and electronic equipment | |
| CN101395625A (en) | Identity theft mitigation | |
| CN111461852A (en) | Data processing method and device based on block chain and readable storage medium | |
| CN113704775B (en) | Service processing method and related device based on distributed digital identity | |
| CN111770112B (en) | Information sharing method, device and equipment | |
| CN109858911A (en) | Qualification verification method, device, system, equipment and readable storage medium storing program for executing | |
| TWI623904B (en) | Confirmation system based on blockchain smart contract and method thereof | |
| CN113574828A (en) | Security chip, security processing method and related equipment | |
| US20180218363A1 (en) | Payment instrument management with key tokenization | |
| CN112003694B (en) | License issuing method, system, electronic equipment and medium based on blockchain | |
| CN113507432B (en) | Alliance chain authority management method and device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |