CN114844629A - Verification method, device, computer equipment and storage medium for blockchain account - Google Patents

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

Verification method, device, computer equipment and storage medium for blockchain account

technical field

The present application relates to the field of computer technology, and in particular to a method, device, computer equipment and storage medium for verifying a blockchain account.

Background technique

With the continuous development of the Internet, blockchain technology has emerged as the times require. Specifically, the essence of blockchain technology is a decentralized and distributed data storage, transmission and proof method, replacing the current Internet with data blocks. The reliance on the central server enables all data changes or transaction items to be recorded on a cloud system. Blockchain technology is an Internet database technology with the characteristics of decentralization, openness and transparency. For example, the Decentralized Identifiers (DID) technology of technical digital identity in the field of blockchain has the characteristics of distributed, autonomous and controllable, and cross-chain reuse.

At present, in the existing blockchain account system, a public-private key pair is usually used. Based on the algorithm, the public key is derived from the private key, and then the address is derived from the public key. The blockchain account is controlled only by the private key, and the private key is controlled by the private key. is the only proof of account verification. Therefore, when the user's private key is lost, the user cannot retrieve his own blockchain account, thus losing all rights and interests under the current account, resulting in low reliability when using the blockchain.

SUMMARY OF THE INVENTION

The embodiments of the present application provide a method, device, computer equipment and storage medium for verifying a blockchain account. By using the DID contract as the underlying system contract and the user using the DID contract account as the underlying blockchain account, it is possible to reset the private key, solve the problem of private key loss, and improve the reliability of the blockchain.

The embodiment of the present application provides a method for verifying a blockchain account, and the method includes:

Receive a transaction request initiated by the controller to be verified corresponding to the target user, wherein the transaction request carries a transaction body, and the transaction body includes transaction data, the target DID account number, the signature information of the controller to be verified, and the controller to be verified. private key information;

Obtain the controller public key information of multiple account controllers in the DID account contract corresponding to the target DID account, and obtain multiple controller public key information;

Determine 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;

Find out whether there is controller public key information matching the to-be-verified public key information from the plurality of controller public keys, and determine the verification result;

If the verification result is that the verification is successful, it is determined that the transaction is valid, and the transaction is performed in the blockchain network based on the transaction body.

Correspondingly, an embodiment of the present application also provides a verification device for a blockchain account, the device comprising:

The receiving unit is configured to receive a transaction request initiated by the controller to be verified corresponding to the target user, wherein the transaction request carries a transaction body, and the transaction body includes transaction data, the target DID account number, and the signature information of the controller to be verified. And the private key information of the controller to be verified;

an obtaining unit, configured to obtain the controller public key information of multiple account controllers in the DID account contract corresponding to the target DID account, and obtain multiple controller public key information;

a first determining unit, configured to determine 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;

a second determining unit, configured to search whether there is controller public key information matching the public key information to be verified from the plurality of controller public keys, and determine the verification result;

The third determining unit is 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 includes:

The first receiving subunit is configured to receive an account registration request sent by a first controller corresponding to the target user, where the account registration request carries attribute information of the first controller, and the attribute information of the first controller includes the first The first private key information of the controller, the first public key information of the first controller, and the first controller address of the first controller;

a first generating unit, configured to generate a target contract address in the account system contract deployed by the blockchain network based on the attribute information of the first controller, wherein the account system contract is used to manage the DID account;

A second generating unit, configured to generate a target DID account based on the target contract address and preset identification information;

The first processing unit is used to save the target DID account in the account system contract, and send the target DID account to the target user, so that the controller corresponding to the target user obtains the target DID Account control permissions.

In some embodiments, the apparatus further includes:

A creation unit for creating a DID account contract in the account system contract;

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 includes:

The fourth generating unit is used for splicing the DID prefix, the DID method identifier and the target contract address in sequence to generate a target DID account.

In some embodiments, the apparatus further includes:

The second receiving subunit is configured to receive an adding request of a controller to be added from among the multiple candidate controllers of the target user, wherein the adding request carries the target DID account of the target user and second controller attribute information of the controller to be added, the second controller attribute information includes the second public key information of the controller to be added and the address of the second controller of the controller to be added;

The adding unit is configured to add the controller to be added as the target controller of the target DID account based on the target DID account and the attribute information of the second controller, wherein the target controller has all Describe the control authority of the target DID account.

In some embodiments, the apparatus further includes:

The second processing unit is configured to save the attribute information of the second controller into the DID account contract corresponding to the target DID account, so as to add the controller to be added as the target controller of the target DID account.

In some embodiments, the apparatus further includes:

a judging unit for judging whether the initiating controller is the controller of the target DID account;

A third processing unit for:

If so, save the attribute information of the second controller into the DID account contract corresponding to the target DID account;

If not, the controller to be added is not added as the controller of the DID account.

In some embodiments, the apparatus further includes:

The third receiving subunit is configured to receive a deletion request of the controller to be deleted from the initiating controller among the multiple candidate controllers of the target user, wherein the deletion request carries the target DID corresponding to the initiating controller Account number and the controller address of the controller to be deleted;

A deletion unit, configured to delete 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 includes:

The fourth receiving subunit is used to receive the DID account statistics request sent by the target user;

A statistical unit, configured to count the number of accounts of all DID accounts through the deployed account system contract of the blockchain network based on the DID account statistics request;

The returning unit is configured to return the account number to the target user.

Correspondingly, an embodiment of the present application further provides 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 is executed by the processor When implementing any of the steps of the verification method for the blockchain account as described above.

In addition, the embodiments of the present application also provide a computer-readable storage medium, where a computer program is stored on the computer-readable storage medium, and when the computer program is executed by a processor, any method for verifying a blockchain account as described above is implemented. a step.

The embodiments of the present application provide a method, device, computer equipment and storage medium for verifying a blockchain account, receive a transaction request initiated by a controller to be verified corresponding to a target user; obtain the DID account contract corresponding to the target DID account. The controller public key information of each account controller is obtained, and multiple controller public key information is obtained; based on the signature information of the controller to be verified and the private key information of the controller to be verified, the public key information of the controller to be verified is determined. key information; find out whether there is controller public key information that matches the public key information to be verified from the plurality of controller public keys, and determine the verification result; if the verification result is successful, the transaction is determined to be valid. The transaction body conducts transactions in the blockchain network. By using the DID contract as the underlying system contract and the user using the DID contract account as the underlying blockchain account in the embodiment of this application, the private key can be reset, the problem of private key loss can be solved, and the reliability of the blockchain can be improved.

Description of drawings

In order to illustrate the technical solutions in the embodiments of the present application more clearly, the following briefly introduces the drawings that are used in the description of the embodiments. Obviously, the drawings in the following description are only some embodiments of the present application. For those skilled in the art, other drawings can also be obtained from these drawings without creative effort.

FIG. 1 is a schematic flowchart of a distributed identity identification and verifiable claim model provided by an embodiment of the present application.

FIG. 2 is a schematic flowchart of a method for verifying a blockchain account provided by an embodiment of the present application.

FIG. 3 is a schematic diagram of a scenario of a method for verifying a blockchain account provided by an embodiment of the present application.

FIG. 4 is a schematic structural diagram of a verification device for a blockchain account provided by an embodiment of the present application.

FIG. 5 is a schematic structural diagram of a computer device provided by an embodiment of the present application.

Detailed ways

The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, but not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those skilled in the art without creative work fall within the protection scope of the present application.

In the prior art, the user first needs to perform account registration on the platform. First, the user generates a pair of public key and private key, and generates a corresponding address account according to the public key, and the user submits the address account to initiate the account registration process. The blockchain system A random account will be automatically generated, bound to the address account corresponding to the public key, and stored on the blockchain. In the account registration process, the private key is generated off-chain and kept by the user himself. During the registration process, only the public key will be uploaded to the chain. When the user's private key is lost, the user cannot retrieve his own blockchain account. Lose all the rights and interests under the current account, resulting in low reliability when using the blockchain.

Based on this, embodiments of the present application provide a method, device, computer device, and storage medium for verifying a blockchain account. Specifically, the embodiments of the present application provide a method for verifying a blockchain account that is suitable for a verification device for a blockchain account. The verification device for a blockchain account can be integrated in computer equipment. The blockchain account in the embodiments of the present application The verification method can be performed by a computer device. Wherein, the computer device may be a terminal or a server and other devices. The terminal may be a smart phone, a tablet computer, a notebook computer, a touch screen, a game console, a personal computer (PC, Personal Computer), a personal digital assistant (Personal Digital Assistant, PDA) and other terminal devices. The server can be an independent physical server, a server cluster or a distributed system composed of multiple physical servers, or a cloud service, cloud database, cloud computing, cloud function, cloud storage, network service, cloud communication, Cloud servers for basic cloud computing services such as middleware services, domain name services, security services, CDN, and big data and artificial intelligence platforms, but not limited to this.

Please refer to FIG. 1. FIG. 1 is a schematic flowchart of a distributed identity identification and a Verifiable Credential (VC) model provided by an embodiment of the present application. In the distributed identity and Verifiable Credential (VC) model provided by the embodiments of the present application, there are three types of participants: holder, issuer and verifier. Among them, the holder can register the distributed identity, and query the distributed identity, and can also become the issuer by registering the distributed identity. The holder user can apply for a verifiable claim and send the application to the issuer, and the issuer can verify the holder's distributed identity to determine whether to issue a verifiable claim. The holder user provides the verifiable statement to the verifier, and the verifier can verify whether the user, issuer or signature information is legal, and the verifier may also call the issuer to check the status of the verifiable statement.

Specifically, Verifiable Credential provides a specification to describe certain attributes of an entity and realizes evidence-based trust. DID holders can prove to other entities (individuals, organizations, specific things, etc.) that certain attributes of themselves are credible through verifiable claims. At the same time, combined with cryptographic technologies such as digital signatures and zero-knowledge proofs, the statement can be made more secure and credible, and user privacy can be further protected from being violated.

Among them, the embodiment of the present application can be applied to a verifiable claim (VC) verifiable system. In the verifiable claim system, there are three types of participants: an issuer (Issuer), which has user data and can issue a verifiable claim. Entity, such as government, bank, university and other institutions and organizations; Holder, the holder is the user, the entity that the user requests, receives and holds the verifiable statement from the issuer, and presents the verifiable statement to the verifier , the verifiable statement issued can be self-saved and used again later, for example, in the wallet, and the user may also transfer one or more VCs to others; verifier (Verifier), receive the verifiable statement and verify it, verify After passing, a certain type of service can be provided to users who present a verifiable claim; an identifier registry (Verifiable Data Registry) maintains a database of distributed identities (DIDs), such as a certain blockchain or a distributed ledger. In the verifiable claim system, the verifier can verify the user's verifiable claim, and can also verify the self-signed verifiable claim, that is, the verifiable representation (VP). Verify the validity of the claim. Among them, publishers have different categories, and different categories of publishers have different permission levels.

For example, taking the three-level issuer structure as an example, issuers can be divided into root issuers, first-level issuers, and common issuers. The root issuer can directly add a first-level issuer, and authorize the first-level issuer to issue specified certificates. The root issuer can be a member of the alliance organization in the alliance chain. The first-level issuer can directly add common issuers, and authorize the common issuers to issue designated certificates. , public blockchain platforms, industrial and commercial institutions, China Banking Regulatory Commission, government organizations, general first-level institutions, etc.). After being authorized by the first-level issuer, a network entity can become a common issuer. Common issuers have the authority to issue designated certificates. Common issuers can be subordinate branches of various institutions/associations/organizations/alliances, such as companies (industrial and commercial certification bodies). ), various universities (issued by the Education Bureau), various general issuers (ticket issuers), etc.

In the embodiments of the present application, the distributed digital identities are not only people, but also organizations, and even objects in the future. These people, organizations, and items do not simply rely on the original centralized authority, and cannot be taken or deleted, but are identities that they carry for life. The distributed identities (Decentralized Identifiers, DID) mentioned in the embodiments of this application are decentralized and verifiable digital identifiers, and have the characteristics of being distributed, autonomously controllable, and reusable across chains. The entity can independently complete the registration, resolution, update or revocation of DID. DID is specifically parsed into DIDDocument. DID Document includes the unique identification code of DID, the public key list and the detailed information of the public key (holder, encryption algorithm, key state, etc.), and other attribute descriptions of the DID holder.

The embodiments of the present application provide a method, device, computer equipment, and storage medium for verifying a blockchain account, which will be described in detail below. It should be noted that the description order of the following 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. The embodiments of the present application will be described from the perspective of a verification device for a blockchain account. The verification device for a blockchain account may specifically be integrated in a computer device.

Please refer to FIG. 2 and FIG. 3 together. FIG. 2 is a schematic flowchart of a method for verifying a blockchain account provided by an embodiment of the present application. The specific process may be as follows from step 101 to step 105:

101. Receive a transaction request initiated by the controller to be verified corresponding to the target user, wherein the transaction request carries a transaction body, and the transaction body includes transaction data, the target DID account number, the signature information of the controller to be verified, and the signature information of the controller to be verified. The controller's private key information.

The transaction data may be the original transaction data, and the target DID account may be the user's DID (for example: did:future:0x8688f14154d2ab5E05229a7C3FB2393d02e68E06). The signature information can be calculated by the signature algorithm. Optionally, the signature algorithm provided in this embodiment of the present application may be an elliptic curve signature algorithm (Secp256k1 signature algorithm).

Specifically, before registering a DID account, an account system contract that supports the DID account controller contract can be deployed at the bottom of the blockchain. The core functions of the account system contract include: DID account creation, adding a DID controller, deleting A DID controller, query all controllers of a DID account, query the number of DID accounts, and other functions that DID accounts need, such as changing services, changing authorization, etc. Among them, the reference code example of the DID account controller contract is as follows:

Further, the reference code example of the DID account contract is as follows:

In one embodiment, before the step "receive the transaction request initiated by the controller to be verified corresponding to the target user", the method may include:

Receive an account registration request sent by the first controller corresponding to the target user, where the account registration request carries attribute information of the first controller, and the attribute information of the first controller includes the first private key information of the first controller , the first public key information of the first controller, and the first controller address of the first controller;

Based on the attribute information of the first controller, a target contract address is generated in the account system contract deployed by the blockchain network, wherein the account system contract is used to manage the DID account;

Generate a target DID account based on the target contract address and preset identification information;

The target DID account is saved in the account system contract, and the target DID account is sent to the target user, so that the controller corresponding to the target user obtains the control authority of the target DID account.

For example, a user can generate an initial private key off-chain, and use the private key to initiate an account creation transaction on the blockchain to create a DID contract account (the account creation transaction is in the same format as the existing Ethereum transaction), where , the blockchain will create a contract account that can be used as the user's DID account. For example: the initial private key can be:

4c0883a69102937d6231471b5dbb6204fe5129617082792ae468d01a3f362318;

The public key can be:

(4e3b81af9c2234cad09d679ce6035ed1392347ce64ce405f5dcd36228a25de6e47fd35c4215d1edf53e6f83de344615ce719bdb0fd878f6ed76f06dd277956de);

The controller address can be:

0x2c7536e3605d9c16a7a3d7b1898e529396a65c23;

Users can initiate transactions with the initial private key, enter the default controller address, default controller public key, otherParams and other DID-related parameters, and call the DID account controller contract to create a DID account.

Among them, the reference code example for creating a DID account on the user side is as follows:

Among them, the reference code example for creating a DID account by the blockchain network is as follows:

In a specific embodiment, the step of "generating a target contract address in the account system contract deployed by the blockchain network based on the attribute information of the first controller", the method may include:

Create a DID account contract in the account system contract;

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.

Specifically, the preset identification information may include a DID prefix and a DID method identification. The step "generate a target DID account number based on the target contract address and preset identification information", the method may include:

The DID prefix, the DID method identifier and the target contract address are sequentially spliced to generate a target DID account.

Among them, the DID prefix is fixed, indicating that the string is a DID identification string; the DID method identification represents the DID method, which is used to indicate the method by which the DID identification is defined and operated.

For example, the DidAccount contract address can 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's did account, the controller's public key, and the creation time may be returned.

In one embodiment, after the step "save the target DID account number in the account system contract, and send the target DID account number to the target user", the method may include:

Receive an addition request of the controller to be added from among the multiple candidate controllers of the target user, wherein the addition request carries the target DID account of the target user and the second control of the controller to be added. attribute information of the controller, the attribute information of the second controller includes the second public key information of the controller to be added and the address of the second controller of the controller to be added;

Based on the target DID account and the attribute information of the second controller, the controller to be added is added as the target controller of the target DID account, wherein the target controller has the property of the target DID account Control permissions.

Specifically, the step of "adding the controller to be added as the target controller of the target DID account based on the target DID account and the attribute information of the second controller", the method may include:

The attribute information of the second controller is saved in the DID account contract corresponding to the target DID account, so that the controller to be added is added as the target controller of the target DID account.

Further, before the step "save the attribute information of the second controller in the DID account contract corresponding to the target DID account", the method may include:

Determine whether the initiating controller is the controller of the target DID account;

If so, save the attribute information of the second controller into the DID account contract corresponding to the target DID account;

If not, the controller to be added is not added as the controller of the DID account.

Among them, the reference code example of the controller of the newly added DID account on the user side is as follows:

//Add a controller to a did account

//did target did; newController new controller address; newControllerPublicKey new controller public key

function addController(string did,address newController,stringnewControllerPublicKey)public{

DIDAccount(did).addController(did);

}

Among them, the reference code example of the controller of the newly added DID account in the blockchain network is as follows:

In order to manage the controller corresponding to the DID account, after the step "add the controller to be added as the target controller of the target DID account based on the target DID account and the attribute information of the second controller", Methods can include:

Receive the deletion request of the controller to be deleted from the initiating controller among the multiple candidate controllers of the target user, wherein the deletion request carries the target DID account corresponding to the initiating controller and the control of the controller to be deleted. address;

The controller address of the controller to be deleted is 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.

Among them, the reference code example for deleting the controller of the DID account on the user side is as follows:

//Delete the controller for a did account

//did target did; controller controller address

function delController(string did,address controller)public{

DIDAccount(did).delController(did);

}

Among them, the reference code example for the controller of the blockchain to delete the DID account is as follows:

To count the number of accounts in the blockchain network, methods can include:

Receive the DID account statistics request sent by the target user;

Based on the DID account statistics request, count the number of accounts of all DID accounts through the account system contract deployed by the blockchain network;

Return the account number to the target user.

Among them, the reference code example for the blockchain to query all DID accounts is as follows:

102. Obtain controller public key information of multiple account controllers in the DID account contract corresponding to the target DID account, and obtain multiple controller public key information.

103. Determine 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. Find out whether there is controller public key information matching the public key information to be verified from the plurality of controller public keys, and determine a verification result.

105. If the verification result is that the verification is successful, it is determined that the transaction is valid, and the transaction is performed in the blockchain network based on the transaction body.

To sum up, the embodiments of the present application provide a method for verifying a blockchain account, by receiving a transaction request initiated by a controller to be verified corresponding to a target user; obtaining multiple accounts in the DID account contract corresponding to the target DID account The controller public key information of the controller is obtained, and multiple controller public key information is obtained; based on the signature information of the controller to be verified and the private key information of the controller to be verified, the public key information to be verified of the controller to be verified is determined ; Find out whether there is controller public key information matching the public key information to be verified from the plurality of controller public keys, and determine the verification result; if the verification result is that the verification is successful, then determine that the transaction is valid, based on the transaction The entity conducts transactions in the blockchain network. In the embodiment of the present application, by using the DID contract as the underlying system contract and the user using the DID contract account as the underlying blockchain account, the private key can be reset, the problem of private key loss can be solved, and the reliability of the blockchain can be improved.

According to the above-mentioned content, the following examples will be used to further illustrate the verification method of the blockchain account of the present application. Referring to FIG. 3, a verification method for a blockchain account provided by another embodiment of the present application, the specific method is as follows:

(1) By deploying a DID account system contract at the bottom of the blockchain, the DID account system contract includes functions such as creating a DID account, resetting the private key of the DID account, querying the DID account, and counting the number of accounts.

(2) The user can generate an initial private key off-chain, and use the private key to initiate a transaction to create a DID contract account on the blockchain, and the blockchain will create a contract account based on the transaction, that is, the user's DID account. Specifically, write the default controller address, default controller public key, otherParams and other DID-related parameters (services, etc.) into the DID account system contract, and call the DID account controller contract to create a DID account.

(3) The user can set one or more controllers for the DID account (each controller has a corresponding private key), and each controller can control the DID account, so the user does not need to worry about the loss of the private key, Either can be resolved by resetting the controller.

(4) In addition, when a user initiates a blockchain transaction, the DID account address can be added at the end of the original transaction body, and the transaction can be sent to the blockchain by signing the transaction body with the private key of one of the controllers in the DID account. Blockchain: Before the blockchain receives the transaction and enters the queue, it first obtains the DID account from the end of the transaction body, and queries the public key of the controller in the contract through the DID account address; at the same time, the public key of the signer of the transaction body is recovered, and the blockchain verifies The signature of the transaction body; the blockchain also verifies whether the public key of the controller of the transaction is one of the controllers of the DID account.

(5) The blockchain can also count the specific number of registered users of the blockchain account through the DID account system contract. Specifically, the blockchain can query the number of accounts of did, so as to count the specific number of registered users of the blockchain account.

In order to facilitate better implementation of 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 above-mentioned blockchain account. The meanings of the nouns are the same as those in the verification method of the blockchain account above, and the specific implementation details can refer to the description in the method embodiment.

Please refer to FIG. 4. FIG. 4 is a schematic structural diagram of a verification device for a blockchain account provided by an embodiment of the present application. The device includes:

The receiving unit 201 is configured to receive 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 includes transaction data, the target DID account number, and the signature of the controller to be verified. information and the private key information of the controller to be verified;

The obtaining unit 202 is configured to obtain the controller public key information of multiple account controllers in the DID account contract corresponding to the target DID account, and obtain multiple controller public key information;

a first determining unit 203, configured to determine 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 204 is configured to search from the plurality of controller public keys whether there is controller public key information matching the to-be-verified public key information, and determine the verification result;

The third determining unit 205 is configured to determine that the transaction is valid if the verification result is that the verification is successful, and conduct the transaction in the blockchain network based on the transaction body.

In some embodiments, the apparatus further includes:

The first receiving subunit is configured to receive an account registration request sent by a first controller corresponding to the target user, where the account registration request carries attribute information of the first controller, and the attribute information of the first controller includes the first The first private key information of the controller, the first public key information of the first controller, and the first controller address of the first controller;

a first generating unit, configured to generate a target contract address in the account system contract deployed by the blockchain network based on the attribute information of the first controller, wherein the account system contract is used to manage the DID account;

A second generating unit, configured to generate a target DID account based on the target contract address and preset identification information;

The first processing unit is used to save the target DID account in the account system contract, and send the target DID account to the target user, so that the controller corresponding to the target user obtains the target DID Account control permissions.

In some embodiments, the apparatus further includes:

A creation unit for creating a DID account contract in the account system contract;

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 includes:

The fourth generating unit is used for splicing the DID prefix, the DID method identifier and the target contract address in sequence to generate a target DID account.

In some embodiments, the apparatus further includes:

The second receiving subunit is configured to receive an adding request of a controller to be added from among the multiple candidate controllers of the target user, wherein the adding request carries the target DID account of the target user and second controller attribute information of the controller to be added, the second controller attribute information includes the second public key information of the controller to be added and the address of the second controller of the controller to be added;

The adding unit is configured to add the controller to be added as the target controller of the target DID account based on the target DID account and the attribute information of the second controller, wherein the target controller has all Describe the control authority of the target DID account.

In some embodiments, the apparatus further includes:

The second processing unit is configured to save the attribute information of the second controller into the DID account contract corresponding to the target DID account, so as to add the controller to be added as the target controller of the target DID account.

In some embodiments, the apparatus further includes:

a judging unit for judging whether the initiating controller is the controller of the target DID account;

A third processing unit for:

If so, save the attribute information of the second controller into the DID account contract corresponding to the target DID account;

If not, the controller to be added is not added as the controller of the DID account.

In some embodiments, the apparatus further includes:

The third receiving subunit is configured to receive a deletion request of the controller to be deleted from the initiating controller among the multiple candidate controllers of the target user, wherein the deletion request carries the target DID corresponding to the initiating controller Account number and the controller address of the controller to be deleted;

A deletion unit, configured to delete 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 includes:

The fourth receiving subunit is used to receive the DID account statistics request sent by the target user;

A statistical unit, configured to count the number of accounts of all DID accounts through the deployed account system contract of the blockchain network based on the DID account statistics request;

The returning unit is configured to return the account number to the target user.

The embodiment of the present application provides a verification device for a blockchain account. The receiving unit 201 receives 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 includes transaction data, target DID account number, signature information of the controller to be verified, and private key information of the controller to be verified; acquisition unit 202 acquires the controller public key information of multiple account controllers in the DID account contract corresponding to the target DID account , to obtain a plurality of controller public key information; the first determining unit 203 determines the to-be-verified public key information of the to-be-verified controller based on the to-be-verified controller's signature information and the to-be-verified controller's private key information; the second The determining unit 204 searches the plurality of controller public keys for whether there is controller public key information that matches the public key information to be verified, and determines the verification result; the third determining unit 205 determines if the verification result is that the verification is successful. The transaction is valid, and the transaction is carried out in the blockchain network based on the transaction body. In the embodiment of the present application, by using the DID contract as the underlying system contract and the user using the DID contract account as the underlying blockchain account, the private key can be reset, the problem of private key loss can be solved, and the reliability of the blockchain can be improved.

Correspondingly, an 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 smart phone, a tablet computer, a notebook computer, a touch screen, a game console, a personal computer (PC, Personal Computer) ), personal digital assistant (Personal Digital Assistant, PDA) and other terminal equipment. As shown in FIG. 5 , FIG. 5 is a schematic structural diagram of a computer device provided by an embodiment of the present application. The computer device 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 can understand that the computer device structure shown in the figures does not constitute a limitation on the computer device, and may include more or less components than the one shown, or combine some components, or arrange different components.

The processor 301 is the control center of the computer device 300, and uses various interfaces and lines to connect various parts of the entire computer device 300, by running or loading the software programs and/or modules stored in the memory 302, and calling the software programs and/or modules stored in the memory 302. to perform various functions of the computer device 300 and process data, so as to monitor the computer device 300 as a whole.

In this embodiment of the present application, the processor 301 in the computer device 300 loads the instructions corresponding to the processes of one or more application programs into the memory 302 according to the following steps, and the processor 301 executes the instructions stored in the memory. 302 application in order to achieve various functions:

Receive a transaction request initiated by the controller to be verified corresponding to the target user, wherein the transaction request carries a transaction body, and the transaction body includes transaction data, the target DID account number, the signature information of the controller to be verified, and the controller to be verified. private key information;

Obtain the controller public key information of multiple account controllers in the DID account contract corresponding to the target DID account, and obtain multiple controller public key information;

Determine 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;

Find out whether there is controller public key information matching the to-be-verified public key information from the plurality of controller public keys, and determine the verification result;

If the verification result is that the verification is successful, it is determined that the transaction is valid, and the transaction is performed in the blockchain network based on the transaction body.

For the specific implementation of the above operations, reference may be made to the foregoing embodiments, and details are not described herein again.

Optionally, as shown in FIG. 5 , the computer device 300 further includes: a touch display screen 303 , a radio frequency circuit 304 , an audio circuit 305 , an input unit 306 and a power supply 307 . The processor 301 is electrically connected to the touch display screen 303 , the radio frequency circuit 304 , the audio circuit 305 , the input unit 306 and the power supply 307 respectively. Those skilled in the art can understand that the computer device structure shown in FIG. 5 does not constitute a limitation on the computer device, and may include more or less components than the one shown, or combine some components, or arrange different components.

The touch screen 303 can be used to display a graphical user interface and receive operation instructions generated by the user acting on the graphical user interface. The touch display 303 may include a display panel and a touch panel. Among them, the display panel can be used to display the information input by the user or the information provided to the user and various graphical user interfaces of the computer equipment, and these graphical user interfaces can be composed of graphics, text, icons, videos and any combination thereof. Optionally, the display panel may be configured in the form of a liquid crystal display (LCD, Liquid Crystal Display), an organic light-emitting diode (OLED, Organic Light-Emitting Diode), and the like. The touch panel can be used to collect the user's touch operations on or near it (such as the user's operations on or near the touch panel using a finger, stylus, etc., any suitable object or accessory), and generate corresponding operations instruction, and the operation instruction executes the corresponding program. Optionally, the touch panel may include two parts, a touch detection device and a touch controller. Among them, the touch detection device detects the user's touch orientation, detects the signal brought by the touch operation, and transmits the signal to the touch controller; the touch controller receives the touch information from the touch detection device, converts it into contact coordinates, and then sends it to the touch controller. To the processor 301, and can receive the command sent by the processor 301 and execute it. The touch panel can cover the display panel, and when the touch panel detects a touch operation on or near it, it is transmitted to the processor 301 to determine the type of the touch event, and then the processor 301 provides the display panel according to the type of the touch event. Corresponding visual output. In this embodiment of the present application, the touch panel and the display panel may be integrated into the touch display screen 303 to implement input and output functions. However, in some embodiments, the touch panel and the touch panel may be used as two independent components to implement input and output functions. That is, the touch display screen 303 can also be used as a part of the input unit 306 to realize the input function.

The radio frequency circuit 304 can be used for transmitting and receiving radio frequency signals, so as to establish wireless communication with network equipment or other computer equipment through wireless communication, and send and receive signals with network equipment or other computer equipment.

Audio circuitry 305 may be used to provide an audio interface between the user and computer equipment through speakers, microphones. The audio circuit 305 can transmit the electrical signal converted from the received audio data to the speaker, and the speaker converts it into a sound signal for output; on the other hand, the microphone converts the collected sound signal into an electrical signal, which is converted after being received by the audio circuit 305 In the form of audio data, the audio data is output to the processor 301 for processing, and then sent to, for example, another computer device via the radio frequency circuit 304, or the audio data is output to the memory 302 for further processing. Audio circuitry 305 may also include an ear jack to provide for communication of peripheral headphones with computer equipment.

The input unit 306 can be used to receive input numbers, character information or user characteristic information (such as fingerprint, iris, facial information, etc.), and generate keyboard, mouse, joystick, optical or trackball signal input related to user settings and function control .

Power supply 307 is used to power various components of computer device 300 . Optionally, the power supply 307 may be logically connected to the processor 301 through a power management system, so that functions such as charging, discharging, and power consumption management are implemented through the power management system. The power source 307 may also include one or more DC or AC power sources, recharging systems, power failure detection circuits, power converters or inverters, power status indicators, and any other components.

Although not shown in FIG. 5 , the computer device 300 may further include a camera, a sensor, a Wi-Fi module, a Bluetooth module, and the like, which will not be repeated here.

In the above-mentioned embodiments, the description of each embodiment has its own emphasis. For parts that are not described in detail in a certain embodiment, reference may be made to the relevant descriptions of other embodiments.

It can be seen from the above that the computer equipment provided in this embodiment can use the DID contract as the underlying system contract, and the user can use the DID contract account as the underlying blockchain account, which can reset the private key, solve the problem of private key loss, and improve the block chain. chain reliability.

Those of ordinary skill in the art can understand that all or part of the steps in the various methods of the above-mentioned embodiments can be completed by instructions, or by instructions that control relevant hardware, and the instructions can be stored in a computer-readable storage medium, and loaded and executed by the processor.

To this end, the embodiments of the present application provide a computer-readable storage medium, in which a plurality of computer programs are stored, and the computer programs can be loaded by a processor to execute any blockchain account provided by the embodiments of the present application. steps in the verification method. For example, the computer program may perform the following steps:

Receive a transaction request initiated by the controller to be verified corresponding to the target user, wherein the transaction request carries a transaction body, and the transaction body includes transaction data, the target DID account number, the signature information of the controller to be verified, and the controller to be verified. private key information;

Obtain the controller public key information of multiple account controllers in the DID account contract corresponding to the target DID account, and obtain multiple controller public key information;

Determine 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;

Find out whether there is controller public key information matching the to-be-verified public key information from the plurality of controller public keys, and determine the verification result;

If the verification result is that the verification is successful, it is determined that the transaction is valid, and the transaction is performed in the blockchain network based on the transaction body.

For the specific implementation of the above operations, reference may be made to the foregoing embodiments, and details are not described herein again.

Wherein, the storage medium may include: a read only memory (ROM, Read Only Memory), a random access memory (RAM, Random Access Memory), a magnetic disk or an optical disk, and the like.

Since the computer program stored in the storage medium can execute the steps in any blockchain account verification method provided by the embodiments of the present application, any block chain account provided by the embodiments of the present application can be implemented. The beneficial effects that can be achieved by the verification method of the chain account can be seen in the previous embodiments, which will not be repeated here.

In the above-mentioned embodiments, the description of each embodiment has its own emphasis. For parts that are not described in detail in a certain embodiment, reference may be made to the relevant descriptions of other embodiments.

The verification method, device, computer equipment and storage medium for a blockchain account provided by the embodiments of the present application have been described above in detail. The principles and implementations of the present application are described with specific examples in this article. The descriptions of the examples are only used to help understand the technical solutions of the present application and their core ideas; those of ordinary skill in the art should understand that they can still modify the technical solutions described in the foregoing embodiments, or modify some of the technical features. Equivalent replacement; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the scope of the technical solutions of the embodiments of the present application.

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.

Images