CN114844629A - Verification method and device of block chain account, computer equipment and storage medium - Google Patents
Verification method and device of block chain account, computer equipment and storage medium Download PDFInfo
- Publication number
- CN114844629A CN114844629A CN202210344237.6A CN202210344237A CN114844629A CN 114844629 A CN114844629 A CN 114844629A CN 202210344237 A CN202210344237 A CN 202210344237A CN 114844629 A CN114844629 A CN 114844629A
- Authority
- CN
- China
- Prior art keywords
- controller
- account
- target
- verified
- contract
- 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.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 63
- 238000012795 verification Methods 0.000 title claims abstract description 51
- 230000000977 initiatory effect Effects 0.000 claims description 16
- 238000004590 computer program Methods 0.000 claims description 12
- 238000012217 deletion Methods 0.000 claims description 8
- 230000037430 deletion Effects 0.000 claims description 8
- 230000006870 function Effects 0.000 description 12
- 238000012545 processing Methods 0.000 description 10
- 238000005516 engineering process Methods 0.000 description 8
- 230000008569 process Effects 0.000 description 5
- 238000004891 communication Methods 0.000 description 4
- 238000010586 diagram Methods 0.000 description 4
- 238000001514 detection method Methods 0.000 description 3
- 238000007726 management method Methods 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 230000005236 sound signal Effects 0.000 description 2
- 238000013459 approach Methods 0.000 description 1
- 238000013473 artificial intelligence Methods 0.000 description 1
- 238000013475 authorization Methods 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 238000007599 discharging Methods 0.000 description 1
- 230000001815 facial effect Effects 0.000 description 1
- 238000012905 input function Methods 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 230000008520 organization Effects 0.000 description 1
- 230000002093 peripheral effect Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
- 230000000007 visual 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/088—Usage controlling of secret information, e.g. techniques for restricting cryptographic keys to pre-authorized uses, different access levels, validity of crypto-period, different key- or password length, or different strong and weak cryptographic algorithms
-
- 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/0825—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 asymmetric-key encryption or public key infrastructure [PKI], e.g. key signature or public key certificates
-
- 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/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
Landscapes
- Engineering & Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
Abstract
The embodiment of the application discloses a verification method, a verification device, computer equipment and a storage medium for a block chain account, wherein the verification method comprises the following steps: receiving a transaction request initiated by a controller to be verified corresponding to a target user; acquiring controller public key information of a plurality of account controllers in a DID account contract corresponding to the target DID account to obtain a plurality of controller public key information; determining the public key information to be verified of the controller to be verified based on the signature information of the controller to be verified and the private key information of the controller to be verified; searching whether controller public key information matched with the public key information to be verified exists in the plurality of controller public keys, and determining a verification result; if the verification result is successful, determining that the transaction is effective, and performing the transaction in the block chain network based on the transaction body; by using the DID contract as the bottom layer system contract, the private key can be reset, the problem of private key loss is solved, and the reliability of the block chain is improved.
Description
Technical Field
The present application relates to the field of computer technologies, and in particular, to a method and an apparatus for verifying a blockchain account, a computer device, and a storage medium.
Background
With the continuous development of the internet, the blockchain technology is brought forward, and particularly, the blockchain technology is an approach of data storage, transmission and certification which is decentralized and is built in a distributed structure, and replaces the current dependence of the internet on a central server by data blocks, so that all data changes or transaction items are recorded on a cloud system. The block chain technology is an internet database technology and has the characteristics of decentralization and open transparency. For example, technology digital identity Distributed Identifiers (DID) technology appearing in the field of block chaining has the characteristics of distribution, autonomous control, cross-chain multiplexing and the like.
At present, in an existing block chain account system, a public-private key pair is generally adopted, a public key is derived from a private key based on an algorithm, an address is derived from the public key, the block chain account is controlled by a unique private key, and the private key is a unique certificate for account verification. Therefore, when the private key of the user is lost, the user cannot retrieve the own blockchain account number, so that the ownership of the current account is lost, and the reliability of the blockchain in use is low.
Disclosure of Invention
The embodiment of the application provides a verification method and device for a block chain account, computer equipment and a storage medium, and the user can reset a private key by taking a DID contract as a bottom layer system contract and taking a DID contract account as a bottom layer block chain account, so that the problem of private key loss is solved, and the reliability of the block chain is improved.
The embodiment of the application provides a verification method of a block chain account, which comprises the following steps:
receiving a transaction request initiated by a controller to be verified corresponding to a target user, wherein the transaction request carries a transaction body, and the transaction body comprises transaction data, a target DID account number, signature information of the controller to be verified and private key information of the controller to be verified;
acquiring controller public key information of a plurality of account controllers in a DID account contract corresponding to the target DID account to obtain a plurality of controller public key information;
determining the public key information to be verified of the controller to be verified based on the signature information of the controller to be verified and the private key information of the controller to be verified;
searching whether controller public key information matched with the public key information to be verified exists in the plurality of controller public keys, and determining a verification result;
And if the verification result is successful, determining that the transaction is effective, and performing the transaction in the block chain network based on the transaction body.
Correspondingly, an embodiment of the present application further provides a device for verifying a blockchain account, where the device includes:
the system comprises a receiving unit, a verification unit and a verification unit, wherein the receiving unit is used for receiving a transaction request initiated by a controller to be verified corresponding to a target user, the transaction request carries a transaction body, and the transaction body comprises transaction data, a target DID account number, signature information of the controller to be verified and private key information of the controller to be verified;
the acquisition unit is used for acquiring controller public key information of a plurality of account controllers in a DID account contract corresponding to the target DID account to obtain a plurality of controller public key information;
the first determining unit is used for determining the public key information to be verified of the controller to be verified based on the signature information of the controller to be verified and the private key information of the controller to be verified;
the second determining unit is used for searching whether the controller public key information matched with the public key information to be verified exists in the plurality of controller public keys and determining a verification result;
and the third determining unit is used for determining that the transaction is effective if the verification result is successful, and performing the transaction in the block chain network based on the transaction body.
In some embodiments, the apparatus further comprises:
a first receiving subunit, configured to receive an account registration request sent by a first controller corresponding to the target user, where the account registration request carries first controller attribute information, and the first controller attribute information includes first private key information of a first controller, first public key information of the first controller, and a first controller address of the first controller;
a first generating unit, configured to generate a target contract address in an account system contract deployed in the blockchain network based on the first controller attribute information, where the account system contract is used to manage a DID account;
the second generation unit is used for generating a target DID account based on the target contract address and preset identification information;
and the first processing unit is used for storing the target DID account in the account system contract and sending the target DID account to the target user so that a controller corresponding to the target user can acquire the control authority of the target DID account.
In some embodiments, the apparatus further comprises:
a creating unit, configured to create a DID account contract in the account system contract;
And a third generating unit, configured to write the first controller attribute information into the DID account contract, and generate a target contract address corresponding to the DID account contract based on the first controller attribute information.
In some embodiments, the apparatus further comprises:
and the fourth generating unit is used for sequentially splicing the DID prefix, the DID method identifier and the target contract address to generate a target DID account.
In some embodiments, the apparatus further comprises:
a second receiving subunit, configured to receive an addition request of an initiating controller to a controller to be added from among multiple candidate controllers of the target user, where the addition request carries a target DID account of the target user and second controller attribute information of the controller to be added, and the second controller attribute information includes second public key information of the controller to be added and a second controller address of the controller to be added;
and the adding unit is used for adding the controller to be added as a target controller of the target DID account based on the target DID account and the second controller attribute information, wherein the target controller has the control authority of the target DID account.
In some embodiments, the apparatus further comprises:
and the second processing unit is used for storing the second controller attribute information into a DID account contract corresponding to the target DID account so as to add the controller to be added as a target controller of the target DID account.
In some embodiments, the apparatus further comprises:
the judging unit is used for judging whether the initiating controller is a controller of the target DID account;
a third processing unit to:
if yes, the second controller attribute information is stored in a DID account contract corresponding to the target DID account;
and if not, not adding the controller to be added as the controller of the DID account.
In some embodiments, the apparatus further comprises:
a third receiving subunit, configured to receive a deletion request from an initiating controller to a controller to be deleted, where the deletion request carries a target DID account corresponding to the initiating controller and a controller address of the controller to be deleted;
and the deleting unit is used for deleting the controller address of the controller to be deleted from the DID account contract corresponding to the target DID account so as to release the control authority of the controller to be deleted on the DID account.
In some embodiments, the apparatus further comprises:
the fourth receiving subunit is configured to receive a DID account statistics request sent by the target user;
a counting unit, configured to count, based on the DID account counting request, the number of accounts of all DID accounts through an account system contract deployed in the block chain network;
and the returning unit is used for returning the account number to the target user.
Accordingly, embodiments of the present application further provide a computer device, including a processor, a memory, and a computer program stored on the memory and capable of running on the processor, where the computer program, when executed by the processor, implements the steps of any one of the methods for verifying a blockchain account as described above.
Furthermore, an embodiment of the present application further provides a computer-readable storage medium, on which a computer program is stored, where the computer program, when executed by a processor, implements the steps of any one of the verification methods for blockchain accounts as described above.
The embodiment of the application provides a verification method and device for a block chain account, computer equipment and a storage medium, and the method comprises the steps of receiving a transaction request initiated by a controller to be verified corresponding to a target user; acquiring controller public key information of a plurality of account controllers in a DID account contract corresponding to the target DID account to obtain a plurality of controller public key information; determining the public key information to be verified of the controller to be verified based on the signature information of the controller to be verified and the private key information of the controller to be verified; searching whether controller public key information matched with the public key information to be verified exists in the plurality of controller public keys, and determining a verification result; and if the verification result is successful, determining that the transaction is effective, and performing the transaction in the block chain network based on the transaction body. According to the method and the device, the DID contract is used as the bottom layer system contract, the user uses the DID contract account as the bottom layer block chain account, the private key can be reset, the problem that the private key is lost is solved, and the reliability of the block chain is improved.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.
Fig. 1 is a schematic flowchart of a distributed identity and verifiable claims model provided in an embodiment of the present application.
Fig. 2 is a flowchart illustrating a method for verifying a blockchain account according to an embodiment of the present disclosure.
Fig. 3 is a schematic view of a scenario of a verification method for a blockchain account according to an embodiment of the present disclosure.
Fig. 4 is a schematic structural diagram of an apparatus for verifying a blockchain account according to an embodiment of the present disclosure.
Fig. 5 is a schematic structural diagram of a computer device provided in an embodiment of the present application.
Detailed Description
The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application. It is to be understood that the embodiments described are only a few embodiments of the present application and not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
In the prior art, a user firstly needs to register an account on a platform, firstly, the user generates a pair of a public key and a private key, and generates a corresponding address account according to the public key, the user submits the address account to initiate an account registration process, and a block chain system automatically generates a random account, binds the random account with the address account corresponding to the public key, and stores the random account on a block chain. In the account registration process, the private key generation is completed under the chain and is kept by the user, the public key is only linked up in the registration process, and when the private key of the user is lost, the user cannot find the own block chain account number, so that the ownership of the current account is lost, and the reliability of the block chain in use is low.
Based on this, the embodiment of the application provides a method and an apparatus for verifying a blockchain account, a computer device and a storage medium. Specifically, the present application provides a method for verifying a blockchain account, which is applicable to a device for verifying a blockchain account, where the device for verifying a blockchain account may be integrated in a computer device, and the method for verifying a blockchain account according to the present application may be executed by the computer device. The computer device may be a terminal or a server. The terminal may be a terminal device such as a smart phone, a tablet Computer, a notebook Computer, a touch screen, a game machine, a Personal Computer (PC), a Personal Digital Assistant (PDA), and the like. The server may be an independent physical server, a server cluster or a distributed system formed by a plurality of physical servers, or a cloud server providing basic cloud computing services such as a cloud service, a cloud database, cloud computing, a cloud function, cloud storage, a network service, cloud communication, middleware service, a domain name service, a security service, a CDN, and a big data and artificial intelligence platform, but is not limited thereto.
Referring to fig. 1, fig. 1 is a schematic flowchart of a distributed identity and Verifiable assertion (VC) model according to an embodiment of the present application. In the distributed identity and Verifiable statement (VC) model provided in the embodiments of the present application, 3 kinds of participants are included: a holder, a publisher, and a verifier. The holder can perform distributed identity registration and query distributed identity, and can also become an issuer by registering the distributed identity. The holder user can apply for the verifiable claims and send the application to the issuer, who can verify the distributed identity of the holder and then determine whether to issue the verifiable claims. The holder user provides the verifiable claim to a verifier who can verify whether the user, the issuer, or the signature information, etc., are legitimate, or which can invoke the issuer to check the status of the verifiable claim.
In particular, a Verifiable assertion (Verifiable trust) provides a specification to describe certain attributes that an entity has, enabling evidence-based trust. The DID holder, through a verifiable claim, can prove to other entities (individuals, organizations, things, etc.) that certain attributes of himself are trustworthy. Meanwhile, by combining the cryptographic technologies such as digital signature and zero knowledge proof, the statement can be safer and more credible, and the privacy of the user can be further guaranteed against being invaded.
The embodiment of the application can be applied to a verifiable system of a verifiable statement (VC), and the verifiable statement system comprises 3 participants: issuers (issuers) who possess user data and can issue verifiable claims to entities such as government, bank, university, etc. organizations and organizations; holder (Holder), i.e. user, who requests, receives and holds the verifiable statement from the issuer, presents the verifiable statement to a verifier, who can save itself, for example in a wallet, and who may also transfer one or more VCs to others; the Verifier (Verifier) receives the verifiable statement and verifies the verifiable statement, and after the verification is passed, the Verifier can provide a certain type of service for the user who shows the verifiable statement; an identifier Registry (veriable Data Registry) maintains a database of Distributed Identities (DID), such as a block chain, distributed ledger. In the verifiable statement system, a verifier can verify the verifiable statement of a user, and also can verify the verifiable statement after self-signature, namely, the verifiable statement (VP), and after the verification is passed, the validity of the verifiable statement held by the user can be determined. Where issuers have different categories, with different categories of issuers having different levels of permission.
For example, taking a three-tier issuer architecture as an example, issuers may be classified as root issuers, primary issuers, and common issuers. The root issuer may directly add and authorize the issuance of the specified credentials to the primary issuer, which may be a member of a federation organization within a federation chain. The primary issuer can directly increase the common issuers and authorize the common issuers to issue the designated certificates, and the primary issuer can be various broad primary institutions (such as education bureaus, public block chain platforms, industrial and commercial institutions, banking and supervision agencies, government organizations, general primary institutions and the like) such as authorities, authority associations, authority organizations, alliances and the like. The network entity can become a common issuer after being authorized by the primary issuer, the common issuer has the authority of issuing the designated certificate, and the common issuer can be various subordinate branches of organizations/associations/organizations/alliances, such as companies (industrial and commercial certification organizations), various universities (issued by educational bureaus), various common issuers (ticket issuers), and the like.
In embodiments of the present application, distributed digital identities include not only humans, but also organizations and even future items. These people, organizations, and items simply do not rely on an original centralized authority, cannot be removed or deleted, and are life-long identities. The Distributed Identities (DID) mentioned in the embodiments of the present application are Decentralized verifiable digital Identifiers, and have the characteristics of being distributed, autonomously controllable, and multiplexed across chains. The entity can autonomously complete the registration, parsing, updating or revocation operations of the DID. The DID is specifically resolved into a DID Document that includes the unique id of the DID, a list of public keys and detailed information of the public keys (holder, encryption algorithm, key status, etc.), and other attribute descriptions of the DID holder.
Embodiments of the present application provide a method and an apparatus for verifying a blockchain account, a computer device, and a storage medium, which are described in detail below. It should be noted that the following description of the embodiments is not intended to limit the preferred order of the embodiments.
The embodiments of the present application provide a method for verifying a blockchain account, which will be described in terms of a device for verifying a blockchain account, where the device for verifying a blockchain account may be specifically integrated in a computer device.
Referring to fig. 2 and fig. 3 together, fig. 2 is a schematic flow chart of a verification method for a blockchain account according to an embodiment of the present application, and a specific flow may include the following steps 101 to 105:
101. receiving a transaction request initiated by a controller to be verified corresponding to a target user, wherein the transaction request carries a transaction body, and the transaction body comprises transaction data, a target DID account, signature information of the controller to be verified and private key information of the controller to be verified.
The transaction data can be transaction original data, and the target DID account number can be a DID of the user (for example: DID: future:0x8688f14154d2ab5E05229a7C3FB2393d02E68E 06). The signature information may be calculated by a signature algorithm. Alternatively, the signature algorithm provided by the embodiment of the present application may be an elliptic curve signature algorithm (Secp256k1 signature algorithm).
Specifically, before performing DID account registration, an account system contract supporting a DID account controller contract may be deployed at a bottom layer of a block chain, and core functions of the account system contract include: the method comprises the steps of creating a DID account, adding a DID controller, deleting a DID controller, inquiring all controllers of a DID account, inquiring the number of DID accounts and other functions required by the DID account, such as changing service, changing authorization and the like. Wherein, the reference code of the DID account controller contract is as follows:
further, an example of the reference code of the DID account contract is as follows:
in an embodiment, before the step "receiving a transaction request initiated by a controller to be authenticated corresponding to a target user", the method may include:
receiving an account registration request sent by a first controller corresponding to the target user, wherein the account registration request carries first controller attribute information, and the first controller attribute information comprises first private key information of the first controller, first public key information of the first controller and a first controller address of the first controller;
generating a target contract address in an account system contract deployed in the block chain network based on the first controller attribute information, wherein the account system contract is used for managing a DID account;
Generating a target DID account based on the target contract address and preset identification information;
and storing the target DID account in the account system contract, and sending the target DID account to the target user so that a controller corresponding to the target user can acquire the control authority of the target DID account.
For example, a user may generate an initial private key down the chain and use the private key to initiate an account creation transaction on the blockchain to create a DID contract account (the transaction for creating the account is consistent with the existing etherhouse transaction format), where the blockchain may be used as the DID account of the user by creating the contract account. For example: the initial private key may be:
4c0883a69102937d6231471b5dbb6204fe5129617082792ae468d01a3f362318；
the public key may be:
(4e3b81af9c2234cad09d679ce6035ed1392347ce64ce405f5dcd36228a25de6e47fd35c4215d1edf53e6f83de344615ce719bdb0fd878f6ed76f06dd277956de)；
the controller address may be:
0x2c7536e3605d9c16a7a3d7b1898e529396a65c23；
the user can initiate a transaction by using an initial private key, input other DID related parameters such as a default controller address, a default controller public key, otherParams and the like, and call a DID account controller contract to create a DID account.
The reference code for creating the DID account at the user side is as follows:
the reference code of the block chain network for creating the DID account is as follows:
in a specific embodiment, the step "generating a target contract address in an account system contract deployed in the blockchain network based on the first controller attribute information", may include:
Creating a DID account contract in the account system contract;
and writing the first controller attribute information into the DID account contract, and generating a target contract address corresponding to the DID account contract based on the first controller attribute information.
Specifically, the preset identification information may include a DID prefix and a DID method identification. The step of generating the target DID account based on the target contract address and the preset identification information may include:
and sequentially splicing the DID prefix, the DID method identification and the target contract address to generate a target DID account.
Wherein, the DID prefix is fixed, which indicates that the character string is a DID identification character string; the DID method identification represents a DID method for indicating in what way this DID identification is defined and operated.
For example, a DidAccount contract address may be:
0x8688f14154d2ab5E05229a7C3FB2393d02e68E06
the final did account is:
did:future:0x8688f14154d2ab5E05229a7C3FB2393d02e68E06。
optionally, after the DID account is created, a DID change event may be sent to the user, and information such as the user DID account, the controller public key, the creation time, and the like may be returned.
In one embodiment, after the step of saving the target DID account in the account system contract and sending the target DID account to the target user, the method may include:
Receiving an addition request of an initiating controller to a controller to be added from a plurality of candidate controllers of the target user, wherein the addition request carries a target DID account of the target user and second controller attribute information of the controller to be added, and the second controller attribute information comprises second public key information of the controller to be added and a second controller address of the controller to be added;
and adding the controller to be added as a target controller of the target DID account based on the target DID account and the second controller attribute information, wherein the target controller has the control authority of the target DID account.
Specifically, the step of adding the to-be-added controller as the target controller of the target DID account based on the target DID account and the second controller attribute information may include:
and storing the second controller attribute information into a DID account contract corresponding to the target DID account so as to add the controller to be added as a target controller of the target DID account.
Further, before the step of "saving the second controller attribute information in the DID account contract corresponding to the target DID account", the method may include:
Judging whether the initiating controller is a controller of the target DID account;
if yes, the second controller attribute information is stored in a DID account contract corresponding to the target DID account;
and if not, not adding the controller to be added as the controller of the DID account.
The reference code of the controller with the added DID account at the user side is as follows:
novel controller for a certain did account
// did target did; newController new controller address; new controller public key of newControllerPublicKey
function addController(string did,address newController,string newControllerPublicKey)public{
DIDAccount(did).addController(did)；
}
The reference code of the controller of the block chain network with the added DID account is as follows:
in order to manage a controller corresponding to a DID account, after the step "add the controller to be added as a target controller of the target DID account based on the target DID account and the second controller attribute information", the method may include:
receiving a deletion request of an initiating controller to a controller to be deleted from a plurality of candidate controllers of the target user, wherein the deletion request carries a target DID account corresponding to the initiating controller and a controller address of the controller to be deleted;
and deleting the controller address of the controller to be deleted from the DID account contract corresponding to the target DID account so as to release the control authority of the controller to be deleted on the DID account.
The reference code of the controller for deleting the DID account at the user side is as follows:
// controller for deleting a given did account
// did target did; controller address
function delController(string did,address controller)public{
DIDAccount(did).delController(did)；
}
Reference codes of controllers of block chain deleted DID accounts are as follows:
to account number in a blockchain network, a method may include:
receiving a DID account number counting request sent by the target user;
counting the account number of all DID accounts through the deployed account system contract of the block chain network based on the DID account counting request;
and returning the account number to the target user.
The reference codes of all DID accounts for block chain query are as follows:
102. and acquiring controller public key information of a plurality of account controllers in a DID account contract corresponding to the target DID account to obtain the plurality of controller public key information.
103. And determining the public key information to be verified of the controller to be verified based on the signature information of the controller to be verified and the private key information of the controller to be verified.
104. And searching whether the controller public key information matched with the public key information to be verified exists or not from the plurality of controller public keys, and determining a verification result.
105. And if the verification result is successful, determining that the transaction is effective, and performing the transaction in the block chain network based on the transaction body.
In summary, the embodiment of the present application provides a method for verifying a blockchain account, which receives a transaction request initiated by a controller to be verified corresponding to a target user; acquiring controller public key information of a plurality of account controllers in a DID account contract corresponding to the target DID account to obtain a plurality of controller public key information; determining the public key information to be verified of the controller to be verified based on the signature information of the controller to be verified and the private key information of the controller to be verified; searching whether controller public key information matched with the public key information to be verified exists in the plurality of controller public keys, and determining a verification result; and if the verification result is successful, determining that the transaction is effective, and performing the transaction in the block chain network based on the transaction body. According to the method and the device, the DID contract can be used as the bottom layer system contract, the user uses the DID contract account as the bottom layer block chain account, the private key can be reset, the problem that the private key is lost is solved, and the reliability of the block chain is improved.
Based on the above description, the method for verifying the blockchain account of the present application will be further described by way of example. Referring to fig. 3, a method for verifying a blockchain account according to another embodiment of the present application includes the following steps:
(1) A DID account system contract is deployed at the bottom layer of a block chain, and the DID account system contract comprises functions of creating a DID account, resetting a DID account private key, querying the DID account, counting the number of accounts and the like.
(2) The user can generate an initial private key under the chain, and use the private key to initiate a transaction for creating a DID contract account number to the blockchain, and the blockchain creates a contract account number, namely the user DID account number according to the transaction. Specifically, a default controller address, a default controller public key and other DID related parameters (such as services) of otherParams are written into a DID account system contract, and a DID account controller contract is called to create a DID account.
(3) The user can set one to more controllers (wherein each controller has a corresponding private key) for the DID account, and each controller can control the DID account, so that the user can solve the problem by resetting the controllers without worrying about the loss of the private key.
(4) In addition, when a user initiates a block chain transaction, a DID account address can be added at the tail of an original transaction body, and the transaction body is signed by a private key of one controller in the DID account number, so that the transaction can be sent to the block chain; before the block link receives and enqueues the transaction, firstly, a DID account is obtained from the end of a transaction body, and a controller public key in a contract is inquired through a DID account address; meanwhile, the public key of the transaction body signer is recovered, and the signature of the transaction body is verified by the block chain; and simultaneously verifying whether the public key of the controller of the transaction is one of the controllers of the DID account by the blockchain, and if so, determining that the transaction is real and effective and can be queued for transaction.
(5) The block chain can also count the specific number of registered users of the block chain account through a DID account system contract. Specifically, the blockchain may query the number of the account numbers of the did, so as to count the specific number of registered users of the blockchain account numbers.
In order to better implement the verification method for the blockchain account provided by the embodiment of the present application, the embodiment of the present application further provides a verification device based on the blockchain account. The meaning of the noun is the same as that in the verification method of the blockchain account, and specific implementation details can refer to the description in the method embodiment.
Referring to fig. 4, fig. 4 is a schematic structural diagram of a verification apparatus for a blockchain account according to an embodiment of the present disclosure, where the apparatus includes:
the system comprises a receiving unit 201, a processing unit and a processing unit, wherein the receiving unit is used for receiving a transaction request initiated by a controller to be verified corresponding to a target user, the transaction request carries a transaction body, and the transaction body comprises transaction data, a target DID account number, signature information of the controller to be verified and private key information of the controller to be verified;
an obtaining unit 202, configured to obtain controller public key information of multiple account controllers in a DID account contract corresponding to the target DID account, to obtain multiple controller public key information;
A first determining unit 203, configured to determine public key information to be verified of the controller to be verified based on the signature information of the controller to be verified and the private key information of the controller to be verified;
a second determining unit 204, configured to search, from the multiple controller public keys, whether controller public key information matching the public key information to be verified exists, and determine a verification result;
a third determining unit 205, configured to determine that the transaction is valid if the verification result is that the verification is successful, and perform the transaction in the blockchain network based on the transaction body.
In some embodiments, the apparatus further comprises:
a first receiving subunit, configured to receive an account registration request sent by a first controller corresponding to the target user, where the account registration request carries first controller attribute information, and the first controller attribute information includes first private key information of a first controller, first public key information of the first controller, and a first controller address of the first controller;
a first generation unit, configured to generate a target contract address in an account system contract deployed in the blockchain network based on the first controller attribute information, where the account system contract is used to manage a DID account;
The second generation unit is used for generating a target DID account based on the target contract address and preset identification information;
and the first processing unit is used for storing the target DID account in the account system contract and sending the target DID account to the target user so that a controller corresponding to the target user can acquire the control authority of the target DID account.
In some embodiments, the apparatus further comprises:
a creating unit, configured to create a DID account contract in the account system contract;
and a third generating unit, configured to write the first controller attribute information into the DID account contract, and generate a target contract address corresponding to the DID account contract based on the first controller attribute information.
In some embodiments, the apparatus further comprises:
and the fourth generating unit is used for sequentially splicing the DID prefix, the DID method identifier and the target contract address to generate a target DID account.
In some embodiments, the apparatus further comprises:
a second receiving subunit, configured to receive an addition request of an initiating controller to a controller to be added from among multiple candidate controllers of the target user, where the addition request carries a target DID account of the target user and second controller attribute information of the controller to be added, and the second controller attribute information includes second public key information of the controller to be added and a second controller address of the controller to be added;
And the adding unit is used for adding the controller to be added as a target controller of the target DID account based on the target DID account and the second controller attribute information, wherein the target controller has the control authority of the target DID account.
In some embodiments, the apparatus further comprises:
and the second processing unit is configured to store the second controller attribute information in a DID account contract corresponding to the target DID account, so as to add the controller to be added as a target controller of the target DID account.
In some embodiments, the apparatus further comprises:
the judging unit is used for judging whether the initiating controller is a controller of the target DID account;
a third processing unit to:
if yes, the second controller attribute information is stored in a DID account contract corresponding to the target DID account;
and if not, not adding the controller to be added as the controller of the DID account.
In some embodiments, the apparatus further comprises:
a third receiving subunit, configured to receive a deletion request from an initiating controller to a controller to be deleted, where the deletion request carries a target DID account corresponding to the initiating controller and a controller address of the controller to be deleted;
And the deleting unit is used for deleting the controller address of the controller to be deleted from the DID account contract corresponding to the target DID account so as to release the control authority of the controller to be deleted on the DID account.
In some embodiments, the apparatus further comprises:
the fourth receiving subunit is configured to receive a DID account statistics request sent by the target user;
a counting unit, configured to count, based on the DID account counting request, the number of accounts of all DID accounts through an account system contract deployed in the block chain network;
and the returning unit is used for returning the account number to the target user.
The embodiment of the application provides a verification device for a block chain account, which receives a transaction request initiated by a controller to be verified corresponding to a target user through a receiving unit 201, wherein the transaction request carries a transaction body, and the transaction body comprises transaction data, a target DID account number, signature information of the controller to be verified and private key information of the controller to be verified; the obtaining unit 202 obtains controller public key information of a plurality of account controllers in a DID account contract corresponding to the target DID account to obtain a plurality of controller public key information; the first determining unit 203 determines public key information to be verified of the controller to be verified based on the signature information of the controller to be verified and the private key information of the controller to be verified; the second determining unit 204 searches whether the controller public key information matched with the public key information to be verified exists in the plurality of controller public keys, and determines a verification result; if the verification result is successful, the third determining unit 205 determines that the transaction is valid, and performs the transaction in the blockchain network based on the transaction body. According to the method and the device, the DID contract can be used as the bottom layer system contract, the user uses the DID contract account as the bottom layer block chain account, the private key can be reset, the problem that the private key is lost is solved, and the reliability of the block chain is improved.
Correspondingly, the embodiment of the present application further provides a Computer device, where the Computer device may be a terminal or a server, and the terminal may be a terminal device such as a smart phone, a tablet Computer, a notebook Computer, a touch screen, a game machine, a Personal Computer (PC), a Personal Digital Assistant (PDA), and the like. As shown in fig. 5, fig. 5 is a schematic structural diagram of a computer device according to an embodiment of the present application. The computer apparatus 300 includes a processor 301 having one or more processing cores, a memory 302 having one or more computer-readable storage media, and a computer program stored on the memory 302 and executable on the processor. The processor 301 is electrically connected to the memory 302. Those skilled in the art will appreciate that the computer device configurations illustrated in the figures are not meant to be limiting of computer devices and may include more or fewer components than those illustrated, or some components may be combined, or a different arrangement of components.
The processor 301 is a control center of the computer apparatus 300, connects various parts of the entire computer apparatus 300 by various interfaces and lines, performs various functions of the computer apparatus 300 and processes data by running or loading software programs and/or modules stored in the memory 302, and calling data stored in the memory 302, thereby monitoring the computer apparatus 300 as a whole.
In the embodiment of the present application, the processor 301 in the computer device 300 loads instructions corresponding to processes of one or more application programs into the memory 302, and the processor 301 executes the application programs stored in the memory 302 according to the following steps, so as to implement various functions:
receiving a transaction request initiated by a controller to be verified corresponding to a target user, wherein the transaction request carries a transaction body, and the transaction body comprises transaction data, a target DID account number, signature information of the controller to be verified and private key information of the controller to be verified;
acquiring controller public key information of a plurality of account controllers in a DID account contract corresponding to the target DID account to obtain a plurality of controller public key information;
determining the public key information to be verified of the controller to be verified based on the signature information of the controller to be verified and the private key information of the controller to be verified;
searching whether controller public key information matched with the public key information to be verified exists in the plurality of controller public keys, and determining a verification result;
and if the verification result is successful, determining that the transaction is effective, and performing the transaction in the block chain network based on the transaction body.
The above operations can be implemented in the foregoing embodiments, and are not described in detail herein.
Optionally, as shown in fig. 5, the computer device 300 further includes: a touch display 303, a radio frequency circuit 304, an audio circuit 305, an input unit 306, and a power source 307. The processor 301 is electrically connected to the touch display 303, the radio frequency circuit 304, the audio circuit 305, the input unit 306, and the power source 307. Those skilled in the art will appreciate that the computer device configuration illustrated in FIG. 5 does not constitute a limitation of computer devices, and may include more or fewer components than those illustrated, or some components may be combined, or a different arrangement of components.
The touch display screen 303 may be used for displaying a graphical user interface and receiving operation instructions generated by a user acting on the graphical user interface. The touch display screen 303 may include a display panel and a touch panel. The display panel may be used, among other things, to display information entered by or provided to a user and various graphical user interfaces of the computer device, which may be made up of graphics, text, icons, video, and any combination thereof. Alternatively, the Display panel may be configured in the form of a Liquid Crystal Display (LCD), an Organic Light-Emitting Diode (OLED), or the like. The touch panel may be used to collect touch operations of a user on or near the touch panel (for example, operations of the user on or near the touch panel using any suitable object or accessory such as a finger, a stylus pen, and the like), and generate corresponding operation instructions, and the operation instructions execute corresponding programs. Alternatively, the touch panel may include two parts, a touch detection device and a touch controller. The touch detection device detects the touch direction of a user, detects a signal brought by touch operation and transmits the signal to the touch controller; the touch controller receives touch information from the touch sensing device, converts the touch information into touch point coordinates, sends the touch point coordinates to the processor 301, and can receive and execute commands sent by the processor 301. The touch panel may overlay the display panel, and when the touch panel detects a touch operation thereon or nearby, the touch panel transmits the touch operation to the processor 301 to determine the type of the touch event, and then the processor 301 provides a corresponding visual output on the display panel according to the type of the touch event. In the embodiment of the present application, the touch panel and the display panel may be integrated into the touch display screen 303 to realize input and output functions. However, in some embodiments, the touch panel and the touch panel can be implemented as two separate components to perform the input and output functions. That is, the touch display screen 303 may also be used as a part of the input unit 306 to implement an input function.
The rf circuit 304 may be used for transceiving rf signals to establish wireless communication with a network device or other computer device via wireless communication, and for transceiving signals with the network device or other computer device.
The audio circuit 305 may be used to provide an audio interface between the user and the computer device through speakers, microphones. The audio circuit 305 may transmit the electrical signal converted from the received audio data to a speaker, and convert the electrical signal into a sound signal for output; on the other hand, the microphone converts the collected sound signal into an electric signal, which is received by the audio circuit 305 and converted into audio data, which is then processed by the audio data output processor 301, and then transmitted to, for example, another computer device via the radio frequency circuit 304, or output to the memory 302 for further processing. The audio circuit 305 may also include an earbud jack to provide communication of a peripheral headset with the computer device.
The input unit 306 may be used to receive input numbers, character information, or user characteristic information (e.g., fingerprint, iris, facial information, etc.), and to generate keyboard, mouse, joystick, optical, or trackball signal inputs related to user settings and function control.
The power supply 307 is used to power the various components of the computer device 300. Optionally, the power supply 307 may be logically connected to the processor 301 through a power management system, so as to implement functions of managing charging, discharging, and power consumption through the power management system. Power supply 307 may also include any component of one or more dc or ac power sources, recharging systems, power failure detection circuitry, power converters or inverters, power status indicators, and the like.
Although not shown in fig. 5, the computer device 300 may further include a camera, a sensor, a wireless fidelity module, a bluetooth module, etc., which are not described in detail herein.
In the foregoing embodiments, the descriptions of the respective embodiments have respective emphasis, and for parts that are not described in detail in a certain embodiment, reference may be made to related descriptions of other embodiments.
As can be seen from the above, the computer device provided in this embodiment can use the DID contract as the underlying system contract, and the user uses the DID contract account as the underlying blockchain account, so that the private key can be reset, the problem of private key loss is solved, and the reliability of the blockchain is improved.
It will be understood by those skilled in the art that all or part of the steps of the methods of the above embodiments may be performed by instructions or by associated hardware controlled by the instructions, which may be stored in a computer readable storage medium and loaded and executed by a processor.
To this end, the present application provides a computer-readable storage medium, in which a plurality of computer programs are stored, where the computer programs can be loaded by a processor to execute the steps in any one of the verification methods for blockchain accounts provided in the present application. For example, the computer program may perform the steps of:
receiving a transaction request initiated by a controller to be verified corresponding to a target user, wherein the transaction request carries a transaction body, and the transaction body comprises transaction data, a target DID account number, signature information of the controller to be verified and private key information of the controller to be verified;
acquiring controller public key information of a plurality of account controllers in a DID account contract corresponding to the target DID account to obtain a plurality of controller public key information;
determining the public key information to be verified of the controller to be verified based on the signature information of the controller to be verified and the private key information of the controller to be verified;
searching whether controller public key information matched with the public key information to be verified exists in the plurality of controller public keys, and determining a verification result;
and if the verification result is successful, determining that the transaction is effective, and performing the transaction in the block chain network based on the transaction body.
The above operations can be implemented in the foregoing embodiments, and are not described in detail herein.
Wherein the storage medium may include: read Only Memory (ROM), Random Access Memory (RAM), magnetic or optical disks, and the like.
Since the computer program stored in the storage medium may execute the steps in any block chain account verification method provided in the embodiment of the present application, beneficial effects that can be achieved by any block chain account verification method provided in the embodiment of the present application may be achieved, for details, see the foregoing embodiment, and are not described herein again.
In the foregoing embodiments, the descriptions of the respective embodiments have respective emphasis, and for parts that are not described in detail in a certain embodiment, reference may be made to related descriptions of other embodiments.
The method, the apparatus, the computer device, and the storage medium for verifying the blockchain account provided in the embodiments of the present application are described in detail above, and a specific example is applied in the description to explain the principle and the implementation of the present application, and the description of the embodiments is only used to help understanding the technical solution and the core idea of the present application; those of ordinary skill in the art will understand that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; such modifications or substitutions do not depart from the spirit and scope of the present disclosure as defined by the appended claims.
Claims (12)
1. A method for verifying a blockchain account, comprising:
receiving a transaction request initiated by a controller to be verified corresponding to a target user, wherein the transaction request carries a transaction body, and the transaction body comprises transaction data, a target DID account number, signature information of the controller to be verified and private key information of the controller to be verified;
acquiring controller public key information of a plurality of account controllers in a DID account contract corresponding to the target DID account to obtain a plurality of controller public key information;
determining the public key information to be verified of the controller to be verified based on the signature information of the controller to be verified and the private key information of the controller to be verified;
searching whether controller public key information matched with the public key information to be verified exists in the plurality of controller public keys, and determining a verification result;
and if the verification result is successful, determining that the transaction is effective, and performing the transaction in the block chain network based on the transaction body.
2. The method for verifying the blockchain account according to claim 1, before receiving the transaction request initiated by the controller to be verified corresponding to the target user, further comprising:
receiving an account registration request sent by a first controller corresponding to the target user, wherein the account registration request carries first controller attribute information, and the first controller attribute information comprises first private key information of the first controller, first public key information of the first controller and a first controller address of the first controller;
Generating a target contract address in an account system contract deployed in the block chain network based on the first controller attribute information, wherein the account system contract is used for managing a DID account;
generating a target DID account based on the target contract address and preset identification information;
and storing the target DID account in the account system contract, and sending the target DID account to the target user so that a controller corresponding to the target user can acquire the control authority of the target DID account.
3. The method for validating a blockchain account according to claim 2, wherein the generating a target contract address in the account system contract deployed in the blockchain network based on the first controller attribute information comprises:
creating a DID account contract in the account system contract;
and writing the first controller attribute information into the DID account contract, and generating a target contract address corresponding to the DID account contract based on the first controller attribute information.
4. The method of claim 3, wherein the predetermined identification information comprises a DID prefix and a DID method identification;
Generating a target DID account based on the target contract address and preset identification information comprises the following steps:
and sequentially splicing the DID prefix, the DID method identification and the target contract address to generate a target DID account.
5. The method for validating a blockchain account according to claim 3, further comprising, after saving the target DID account in the account system contract and sending the target DID account to the target user:
receiving an addition request of an initiating controller to a controller to be added from a plurality of candidate controllers of the target user, wherein the addition request carries a target DID account of the target user and second controller attribute information of the controller to be added, and the second controller attribute information comprises second public key information of the controller to be added and a second controller address of the controller to be added;
and adding the controller to be added as a target controller of the target DID account based on the target DID account and the second controller attribute information, wherein the target controller has the control authority of the target DID account.
6. The method for verifying the blockchain account according to claim 5, wherein the adding the to-be-added controller as the target controller of the target DID account based on the target DID account and the second controller attribute information includes:
And storing the second controller attribute information into a DID account contract corresponding to the target DID account so as to add the controller to be added as a target controller of the target DID account.
7. The method for validating a blockchain account according to claim 6, before saving the second controller attribute information to the DID account contract corresponding to the target DID account, further comprising:
judging whether the initiating controller is a controller of the target DID account;
if yes, the second controller attribute information is stored in a DID account contract corresponding to the target DID account;
and if not, not adding the controller to be added as the controller of the DID account.
8. The method of verifying a blockchain account according to claim 5, further comprising, after adding the to-be-added controller as a target controller of the target DID account based on the target DID account and the second controller attribute information:
receiving a deletion request of an initiating controller to a controller to be deleted from a plurality of candidate controllers of the target user, wherein the deletion request carries a target DID account corresponding to the initiating controller and a controller address of the controller to be deleted;
And deleting the controller address of the controller to be deleted from the DID account contract corresponding to the target DID account so as to release the control authority of the controller to be deleted on the DID account.
9. The method of validating a blockchain account of claim 2, further comprising:
receiving a DID account number counting request sent by the target user;
counting the account number of all DID accounts through the deployed account system contract of the block chain network based on the DID account counting request;
and returning the account number to the target user.
10. An apparatus for validating blockchain accounts, the apparatus comprising:
the system comprises a receiving unit, a verification unit and a verification unit, wherein the receiving unit is used for receiving a transaction request initiated by a controller to be verified corresponding to a target user, the transaction request carries a transaction body, and the transaction body comprises transaction data, a target DID account number, signature information of the controller to be verified and private key information of the controller to be verified;
the acquisition unit is used for acquiring controller public key information of a plurality of account controllers in a DID account contract corresponding to the target DID account to obtain a plurality of controller public key information;
the first determining unit is used for determining the public key information to be verified of the controller to be verified based on the signature information of the controller to be verified and the private key information of the controller to be verified;
The second determining unit is used for searching whether the controller public key information matched with the public key information to be verified exists in the plurality of controller public keys and determining a verification result;
and the third determining unit is used for determining that the transaction is effective if the verification result is successful, and performing the transaction in the block chain network based on the transaction body.
11. A computer device comprising a processor, a memory and a computer program stored on the memory and executable on the processor, the computer program when executed by the processor implementing the steps of the method of authentication of blockchain accounts according to any one of claims 1 to 9.
12. A computer-readable storage medium, on which a computer program is stored which, when being executed by a processor, carries out the steps of the method of authentication of blockchain accounts according to any one of claims 1 to 9.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210344237.6A CN114844629A (en) | 2022-03-31 | 2022-03-31 | Verification method and device of block chain account, computer equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210344237.6A CN114844629A (en) | 2022-03-31 | 2022-03-31 | Verification method and device of block chain account, computer equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114844629A true CN114844629A (en) | 2022-08-02 |
Family
ID=82563729
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210344237.6A Pending CN114844629A (en) | 2022-03-31 | 2022-03-31 | Verification method and device of block chain account, computer equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114844629A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116074126A (en) * | 2023-03-31 | 2023-05-05 | 天聚地合(苏州)科技股份有限公司 | Identity management method and device based on intelligent contract |
| CN117952605A (en) * | 2022-10-28 | 2024-04-30 | 花瓣云科技有限公司 | Processing method and processing device for verifiable statement |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110688679A (en) * | 2019-09-30 | 2020-01-14 | 湖南天河国云科技有限公司 | Account locking/unlocking method and device based on block chain |
| CN111213350A (en) * | 2019-07-02 | 2020-05-29 | 阿里巴巴集团控股有限公司 | System and method for creating decentralized identity |
| CN111241533A (en) * | 2020-01-08 | 2020-06-05 | 深圳壹账通智能科技有限公司 | Block chain-based password management method and device and computer-readable storage medium |
| CN111277577A (en) * | 2020-01-14 | 2020-06-12 | 北京百度网讯科技有限公司 | Digital identity verification method, device, equipment and storage medium |
| CN112702346A (en) * | 2020-12-24 | 2021-04-23 | 国网浙江省电力有限公司电力科学研究院 | Distributed identity authentication method and system based on alliance chain |
| EP3822894A1 (en) * | 2019-11-13 | 2021-05-19 | Telefonica Digital España, S.L.U. | Secure electronic messaging guaranteeing integrity and non-repudation |
| CN113452516A (en) * | 2020-03-27 | 2021-09-28 | 山东浪潮质量链科技有限公司 | Block chain-based asymmetric key generation and distribution method, equipment and medium |
| CN113610528A (en) * | 2021-08-24 | 2021-11-05 | 上海点融信息科技有限责任公司 | Block chain-based management system, method, device and storage medium |
-
2022
- 2022-03-31 CN CN202210344237.6A patent/CN114844629A/en active Pending
Patent Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111213350A (en) * | 2019-07-02 | 2020-05-29 | 阿里巴巴集团控股有限公司 | System and method for creating decentralized identity |
| CN110688679A (en) * | 2019-09-30 | 2020-01-14 | 湖南天河国云科技有限公司 | Account locking/unlocking method and device based on block chain |
| EP3822894A1 (en) * | 2019-11-13 | 2021-05-19 | Telefonica Digital España, S.L.U. | Secure electronic messaging guaranteeing integrity and non-repudation |
| CN111241533A (en) * | 2020-01-08 | 2020-06-05 | 深圳壹账通智能科技有限公司 | Block chain-based password management method and device and computer-readable storage medium |
| CN111277577A (en) * | 2020-01-14 | 2020-06-12 | 北京百度网讯科技有限公司 | Digital identity verification method, device, equipment and storage medium |
| US20210218574A1 (en) * | 2020-01-14 | 2021-07-15 | Beijing Baidu Netcom Science And Technology Co., Ltd. | Method and apparatus for verifying digital identity, device and storage medium |
| CN113452516A (en) * | 2020-03-27 | 2021-09-28 | 山东浪潮质量链科技有限公司 | Block chain-based asymmetric key generation and distribution method, equipment and medium |
| CN112702346A (en) * | 2020-12-24 | 2021-04-23 | 国网浙江省电力有限公司电力科学研究院 | Distributed identity authentication method and system based on alliance chain |
| CN113610528A (en) * | 2021-08-24 | 2021-11-05 | 上海点融信息科技有限责任公司 | Block chain-based management system, method, device and storage medium |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN117952605A (en) * | 2022-10-28 | 2024-04-30 | 花瓣云科技有限公司 | Processing method and processing device for verifiable statement |
| CN116074126A (en) * | 2023-03-31 | 2023-05-05 | 天聚地合(苏州)科技股份有限公司 | Identity management method and device based on intelligent contract |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20220058655A1 (en) | Authentication system | |
| US11665006B2 (en) | User authentication with self-signed certificate and identity verification | |
| CN110598482B (en) | Digital certificate management method, device, equipment and storage medium based on blockchain | |
| US9064257B2 (en) | Mobile device transaction using multi-factor authentication | |
| US12041189B2 (en) | Method for storing and recovering key for blockchain-based system, and device therefor | |
| CN109558106A (en) | The information processing terminal and method, system and storage medium for information processing | |
| TW201836322A (en) | Certificate management method and system | |
| CA2945703A1 (en) | Systems, apparatus and methods for improved authentication | |
| CN113343208A (en) | Certificate authorization method, device, terminal and storage medium | |
| US11233897B1 (en) | Secure call center communications | |
| CN110601858B (en) | Certificate management method and device | |
| CN109766677B (en) | Management system and control method thereof | |
| CN106778295B (en) | File storage method, file display method, file storage device, file display device and terminal | |
| WO2019010669A1 (en) | Method, apparatus and system for identity validity verification | |
| CN114844629A (en) | Verification method and device of block chain account, computer equipment and storage medium | |
| CN104954132A (en) | Information processing apparatus, information processing method, and recording medium | |
| KR20230020262A (en) | Method and apparatus for managing non-fungible token for digital content | |
| US20230261886A1 (en) | Electronic device and method for sharing data using blockchain network | |
| CN111212074B (en) | Blockchain-based qualification identification method, device, equipment and storage medium | |
| CN113506108A (en) | Account management method, device, terminal and storage medium | |
| CN117501656A (en) | Decentralised identity with user biometric | |
| CN113746640B (en) | Digital certificate using method, device, computer equipment and storage medium | |
| CN113935072B (en) | Issuer registration method, issuer registration device, computer device, and storage medium | |
| CN114282270B (en) | Method, device, terminal and storage medium for managing certificates in block chain | |
| CN114418573A (en) | Certificate issuing method and certificate verifying method in block chain |
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 |