Blockchain-based registration method and device, electronic equipment and readable storage medium
By verifying the uniqueness of user identifiers and obtaining signature information on the registered blockchain, the problem of inconsistent user identifiers on different blockchains is solved, and the portability of user account management on different blockchains is improved.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2023-02-22
- Publication Date
- 2026-04-07
Smart Images
Figure CN116233130B_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of blockchain technology, and more specifically to a blockchain-based registration method, apparatus, electronic device, and computer-readable storage medium. Background Technology
[0002] With the rise of the internet, blockchain technology is being used more and more widely in people's lives. Decentralized Identity (DID), which has emerged under this blockchain technology, is a trust invention that combines blockchain technology. It is an identity credential in the future decentralized society, which is owned and controlled by one person.
[0003] However, since different blockchains are independent of each other, the user identifier corresponding to a user's DID account registration on a certain blockchain can only be held by that user on the currently registered blockchain. As a result, other users can register DID accounts on another blockchain based on the same user identifier. This leads to a situation where users can only register DID accounts on another blockchain based on different user identifiers, which is not conducive to managing the same user's accounts on different blockchains. Summary of the Invention
[0004] This application provides a blockchain-based registration method, apparatus, electronic device, and computer-readable storage medium, which can improve the portability of managing the same user's accounts on different blockchains.
[0005] In a first aspect, embodiments of this application provide a blockchain-based registration method applied to a registration blockchain, where DID accounts on at least two business blockchains need to register DID accounts based on registered user identifiers on the aforementioned registration blockchain. The method includes:
[0006] Receive a registration request, which includes the identifier of the first user to be registered;
[0007] If the first user identifier is not among the registered user identifiers on the aforementioned registration blockchain, then the first user identifier is registered on the aforementioned registration blockchain so that the first user identifier becomes a registered user identifier on the aforementioned registration blockchain.
[0008] Obtain the signature information of at least one blockchain node on the aforementioned registration blockchain regarding the registered status of the aforementioned first user identifier;
[0009] The aforementioned signature information is sent to the sender of the aforementioned registration request. The aforementioned signature information is used for DID account registration on any of the aforementioned business blockchains.
[0010] Secondly, embodiments of this application provide a blockchain-based registration method applied to a target business blockchain. DID accounts on at least two business blockchains need to register based on registered user identifiers on the registration blockchain. The target business blockchain is one of the aforementioned at least two business blockchains. The method includes:
[0011] Receive a DID account registration request sent by a user, wherein the DID account registration request includes a second user identifier that needs to register a DID account;
[0012] Obtain the signature information of at least one blockchain node on the aforementioned registration blockchain regarding the registered status of the aforementioned second user identifier;
[0013] Verify the validity of the signature information corresponding to at least one of the above blockchain nodes;
[0014] If the above signature validity verification passes, then DID account registration will be performed for the above user on the above target business blockchain based on the above second user identifier.
[0015] Thirdly, this application also provides a blockchain-based registration device for registering a blockchain, where DID accounts on at least two business blockchains need to register DID accounts based on the registered user identifiers on the aforementioned registration blockchain. The device includes:
[0016] The first receiving module is used to receive a registration request, wherein the registration request includes a first user identifier to be registered;
[0017] The first registration module is used to register the first user identifier on the registration blockchain if the first user identifier does not exist among the registered user identifiers on the registration blockchain, so that the first user identifier becomes a registered user identifier on the registration blockchain.
[0018] The first acquisition module is used to acquire the signature information of at least one blockchain node on the aforementioned registration blockchain regarding the registered status of the aforementioned first user identifier.
[0019] The sending module is used to send the aforementioned signature information to the sender of the aforementioned registration request. The aforementioned signature information is used for DID account registration on any of the aforementioned business blockchains.
[0020] Fourthly, embodiments of this application also provide a blockchain-based registration device applied to a target business blockchain. DID accounts on at least two business blockchains need to register their DID accounts based on registered user identifiers on the registration blockchain. The target business blockchain is one of the aforementioned at least two business blockchains. The device includes:
[0021] The second receiving module is used to receive a DID account registration request sent by a user, wherein the DID account registration request includes a second user identifier that needs to register a DID account;
[0022] The second acquisition module is used to acquire the signature information of at least one blockchain node on the aforementioned registration blockchain regarding the registered status of the aforementioned second user identifier.
[0023] The verification module is used to verify the signature validity of the signature information corresponding to at least one of the above blockchain nodes;
[0024] The second registration module is used to register a DID account for the user on the target business blockchain based on the second user identifier if the above signature validity verification passes.
[0025] Fifthly, embodiments of this application also provide an electronic device, including a memory storing multiple instructions; the processor loads instructions from the memory to execute steps in any of the blockchain-based registration methods provided in embodiments of this application.
[0026] Sixthly, embodiments of this application also provide a computer-readable storage medium storing a plurality of instructions adapted for loading by a processor to execute steps in any of the blockchain-based registration methods provided in embodiments of this application.
[0027] In this embodiment, DID accounts are applied to a registration blockchain, and at least two business blockchains require DID account registration based on registered user identifiers on the aforementioned registration blockchain. The registration blockchain receives a registration request including a first user identifier to be registered, and determines whether the first user identifier is present in the existing registered user identifiers on the registration blockchain. If the first user identifier is not present in the existing registered user identifiers on the registration blockchain, then the first user identifier is registered on the registration blockchain, making it a registered user identifier on the registration blockchain. This allows the user who triggered the registration request to possess the first user identifier on the registration blockchain and obtain the aforementioned registration information. At least one blockchain node on the registration blockchain signs the registered status of the aforementioned first user identifier, and sends the signed information to the sender of the registration request. This signed information is used for DID account registration on any of the aforementioned business blockchains. Thus, when registering a DID account based on a user identifier on a business blockchain, the signature information can be used to determine whether the user who triggered the DID account registration is qualified to hold the first user identifier. This achieves the uniqueness of the user identifier of the same user on different blockchains, avoids the situation where the same user identifier is held by different users on different blockchains, and improves the portability of account management for the same user on different blockchains. Attached Figure Description
[0028] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.
[0029] Figure 1 This is a schematic diagram illustrating a scenario of the blockchain-based registration method provided in this application embodiment;
[0030] Figure 2 This is a schematic flowchart of one embodiment of the blockchain-based registration method provided in this application.
[0031] Figure 3 This is a schematic flowchart of another embodiment of the blockchain-based registration method provided in this application.
[0032] Figure 4 This is a schematic diagram of a blockchain-based registration device provided in an embodiment of this application;
[0033] Figure 5 This is another schematic diagram of the structure of the blockchain-based registration device provided in the embodiments of this application;
[0034] Figure 6 This is a schematic diagram of the structure of the electronic device provided in the embodiments of this application. Detailed Implementation
[0035] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.
[0036] Before providing a detailed explanation of the embodiments of this application, some terms involved in the embodiments of this application will be explained.
[0037] In the description of the embodiments of this application, the terms "first," "second," etc., may be used herein to describe various concepts, but unless specifically stated otherwise, these concepts are not limited by these terms. These terms are used only to distinguish one concept from another. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or device that includes a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to these processes, methods, products, or devices.
[0038] Blockchain, in particular, is a decentralized, distributed database composed of blocks. Each block stores specific information, and these blocks are linked together in chronological order of their creation.
[0039] In this context, a blockchain node refers to a device that participates in building the blockchain, such as a personal computer, web server, database server, or smartphone. There are no specific limitations; for example, blockchain nodes can be deployed on a single server or on different servers. Any two blockchain nodes can communicate peer-to-peer to conduct transactions, such as deploying smart contracts, updating stored data, or generating new stored data. Furthermore, the consensus mechanism of the blockchain ensures the consistency of the stored content across all blockchain nodes, enabling block synchronization operations, such as updating a block of data stored on a blockchain node.
[0040] Among them, the consensus mechanism of blockchain is to complete the verification and confirmation of transactions in a very short time through voting by blockchain nodes. It includes, but is not limited to, the Proof of Work (POW) mechanism, the Proof of Stake (POS) mechanism, or the Delegated Proof of Stake (DPOS) mechanism.
[0041] It should be noted that the blockchain-based registration method provided in this application embodiment can generally be executed by a blockchain node. Correspondingly, the blockchain-based registration device provided in this application embodiment can also generally be set in a blockchain node.
[0042] Decentralized Identity (DID) features distributed, autonomous, controllable, and cross-chain reusable characteristics. Accounts that register this DID include a unique identifier for the DID, a list of public keys, detailed information about the public keys (e.g., holder, encryption algorithm, key status), and other attribute descriptions of the DID holder.
[0043] It should be noted that because different blockchains are independent of each other, the user identifiers used by users to register decentralized identity accounts on different blockchains may be different, resulting in poor portability in managing the same user's identity accounts on different blockchains. To address this, this embodiment further establishes a registration blockchain. This registration blockchain consists of blockchain nodes that store user identifiers for at least one user and can issue signature information regarding the registration status of user identifiers. By setting up this registration blockchain, the uniqueness of the user identifier when a user wants to register a DID account can be verified, that is, whether the user identifier corresponding to the DID account the user currently wants to register is already held by another user, or whether it is held by the current user.
[0044] Among them, the user identifier of the user stored in the blockchain node on the aforementioned registration blockchain is the registered user identifier on the registration blockchain.
[0045] The aforementioned registered blockchain is an anchored blockchain. Its consensus mechanism can be configured according to requirements, such as a Proof-of-Stake (PoS) mechanism, which is not limited here. Node operators can be recruited for the blockchain nodes on the registered blockchain. The amount of collateral pledged by each node operator on the registered blockchain must meet a preset collateral threshold. Furthermore, as transactions proceed, the collateral of each node operator can be deducted or increased based on the participation status of each blockchain node in the transaction.
[0046] The participation status of the transaction includes whether the participant is participating in the transaction and whether the current transaction method is compliant. For example, if a blockchain node participates in the transaction and the transaction method is compliant, the collateral amount of the node operator to which the blockchain node belongs will be increased by a preset amount.
[0047] The business blockchain is a blockchain where users register DID accounts based on their user identifiers. Users can register DID accounts on this business blockchain and participate in corresponding transactions based on their registered DID accounts. These business blockchains include, but are not limited to, Ethereum, the Polygon public chain, or Binance Smart Chain (BSC).
[0048] Understandably, in order to achieve the uniqueness of DID accounts on multiple business blockchains, in this embodiment, when a user wants to register a DID account for another user on a business blockchain based on a certain user identifier, the registration blockchain must first verify whether the user can hold that user identifier. Then, the business blockchain determines whether the user is qualified based on the verification result of the registration blockchain, and decides whether to register a DID account for the user based on that user identifier.
[0049] This application provides a blockchain-based registration method, apparatus, electronic device, and computer-readable storage medium. Specifically, the blockchain-based registration method of this application can be executed by a blockchain node, which can be an electronic device, such as a terminal or server. The terminal can be a smartphone, tablet, laptop, touchscreen, game console, personal computer (PC), personal digital assistant (PDA), or other terminal device. The terminal can also include a client, which can be a game application client, a browser client carrying a game program, or an instant messaging client. The server can be an independent physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server providing basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, CDN, and big data and artificial intelligence platforms.
[0050] Please see Figure 1 , Figure 1 This is a schematic diagram illustrating an application scenario of the blockchain-based registration method provided in this application embodiment. Figure 1The system may include at least one terminal 1000, a registration blockchain 2000, and at least one business blockchain 3000. A user-held terminal 1000 can send a request to either the registration blockchain 2000 or the business blockchain 3000 to respond and perform a corresponding operation. In some scenarios, the business blockchain 3000 can send a request to the registration blockchain 2000 to perform a corresponding operation; conversely, the registration blockchain 2000 can also send a request to the business blockchain 3000 to perform a corresponding operation. The terminal 1000 can be any device with computing hardware. Additionally, the terminal 1000 has one or more multi-touch screens for sensing and acquiring user input through touch or swipe operations performed by the user at multiple points on one or more touch displays. Furthermore, when multiple terminals 1000 and multiple business blockchains 3000 exist in a scenario, different terminals 1000 can request to register a DID account with different business blockchains 3000.
[0051] The following is a detailed description in conjunction with the accompanying drawings. It should be noted that the order of description of the following embodiments is not intended to limit the preferred order of the embodiments. Although a logical order is shown in the flowcharts, in some cases, the steps shown or described may be performed in a different order than that shown in the drawings.
[0052] Example 1
[0053] In this embodiment, the application to a registration blockchain is used as an example. At least two business blockchains require DID accounts to register based on the registered user identifiers on the aforementioned registration blockchain. This embodiment provides a blockchain-based registration method, such as... Figure 2 As shown, the specific process of this blockchain-based registration method can be as follows:
[0054] 201. Receive a registration request, which includes the identifier of the first user to be registered.
[0055] In this embodiment, the above-mentioned registration request is used to request the registration of the first user identifier on the registration blockchain, so that after the first user identifier is successfully registered, the user who triggered the registration request can occupy the first user identifier, thereby preventing other users from registering DID accounts based on the same first user identifier on the business blockchain where the current user has not registered.
[0056] The aforementioned first user identifier is used to identify the user's identity, and this first user identifier can be composed of characters. It should be noted that this first user identifier is the unique identifier of the aforementioned DID. For example, the first user identifier can be a domain name such as tom.eth or jack.eth, or it can be a username such as Tom.
[0057] In some embodiments, since the registration blockchain consists of multiple blockchain nodes, and when new data is generated on the registration blockchain, i.e., when registering the first user identifier, it needs to be processed based on the consensus mechanism of multiple blockchain nodes, each blockchain node on the registration blockchain needs to receive the registration request.
[0058] Specifically, receiving the registration request may include: receiving the registration request through at least one blockchain node on the registration blockchain and broadcasting the registration request to other blockchain nodes on the registration blockchain so that other blockchain nodes receive the registration request, thereby ensuring that all blockchain nodes on the registration blockchain receive the registration request.
[0059] In some embodiments, the sender of the registration request may be the user terminal held by the user, i.e. Figure 1 In the case of terminal 1000, the registration request received by the registration blockchain 2000 includes the request sent by the user terminal.
[0060] Alternatively, the sender of the aforementioned registration request could also be the business blockchain, i.e. Figure 1 In the business blockchain 3000, the corresponding registration blockchain 2000 receives registration requests including requests sent by the business blockchain based on received DID account registration requests. Specifically, when the business blockchain receives a DID account registration request containing a first user identifier, it generates a registration request based on the DID account registration request and sends it to the registration blockchain. This allows the registration blockchain to register the first user identifier in the registration request, thereby enabling the user who triggered the registration request—that is, the user who sent the DID account registration request to the business blockchain—to occupy the user identifier. Here, the first user identifier is the user identifier in the aforementioned DID account registration request.
[0061] Understandably, if the registration request is sent by the user terminal, it is solely for the purpose of allowing the user to possess the user identifier, regardless of whether the user has registered the user identifier on at least one business blockchain. However, if the registration request is sent by the business blockchain, it indicates that the request is intended to register the user's DID account on the sending party (i.e., the business blockchain that sent the request) based on the user identifier possessed by the user, after the user has possessed the user identifier.
[0062] 202. If the first user identifier does not exist among the registered user identifiers on the aforementioned registration blockchain, then the first user identifier shall be registered on the aforementioned registration blockchain so that the first user identifier becomes a registered user identifier on the aforementioned registration blockchain.
[0063] The aforementioned registered user identifiers are user identifiers stored in the DID database corresponding to each blockchain node on the registration blockchain.
[0064] Understandably, once a user identifier is registered on the registration blockchain, each blockchain node on the registration blockchain stores the registered user identifier. Thus, when faced with a new user identifier to be registered, the registered user identifier on the registration blockchain can be compared with the new user identifier to determine whether the new user identifier needs to be registered.
[0065] In this embodiment, if the first user identifier is not among the registered user identifiers, it means that the first user identifier is not held by any user. Therefore, the first user identifier can be registered on the registration blockchain for the user who currently triggered the registration request. This makes the first user identifier a registered user identifier on the registration blockchain and held by the user who currently triggered the registration request. Then, regardless of whether the user who currently triggered the registration request registers a DID account based on this user identifier on the business blockchain, other users cannot register a DID account based on this user identifier. This ensures that the same user identifier on each business blockchain can only be held by one user, achieving user identifier uniformity.
[0066] It is understandable that a user can hold at least one user identifier on the registration blockchain, meaning that a user can use different user identifiers to register a DID account on the business blockchain.
[0067] Accordingly, if a first user identifier exists among the registered user identifiers, it means that the first user identifier has already been held by a user. In order to ensure the uniqueness of user identifiers, the first user identifier cannot be registered again.
[0068] In some embodiments, since the registered user identifier on the aforementioned registration blockchain is the user identifier stored in each blockchain node on the registration blockchain, it is possible to determine whether to register the first user identifier based on the consensus mechanism of the blockchain.
[0069] Understandably, since different consensus mechanisms correspond to different consensus methods, the number of blockchain nodes required to reach consensus varies. Therefore, the number of nodes required for a consensus mechanism can be determined based on the consensus mechanism adopted by the registration blockchain. When the corresponding number of blockchain nodes reach the consensus, the first user identifier is registered on the registration blockchain. After registration, the first user identifier is stored by each blockchain node on the registration blockchain.
[0070] Specifically, if the first user identifier is not among the registered user identifiers on the aforementioned registration blockchain, then registering the first user identifier on the aforementioned registration blockchain may include: querying the blockchain nodes on the aforementioned registration blockchain to see if the first user identifier exists among the registered user identifiers stored by the blockchain nodes; if the first user identifier is not among the registered user identifiers corresponding to the aforementioned blockchain nodes, then registering the first user identifier on the aforementioned registration blockchain.
[0071] Specifically, if the first user identifier is not among the registered user identifiers on the aforementioned registration blockchain, then registering the first user identifier on the aforementioned registration blockchain may include: querying the blockchain nodes on the aforementioned registration blockchain to see if the first user identifier exists among the registered user identifiers stored by the blockchain nodes; determining the node consensus data corresponding to the consensus mechanism on the registration blockchain; if there are a corresponding number of blockchain nodes with the same number of consensus nodes as the node, and the first user identifier is not among the registered user identifiers of the corresponding nodes, then registering the first user identifier on the aforementioned registration blockchain.
[0072] 203. Obtain the signature information of at least one blockchain node on the aforementioned registration blockchain regarding the registered status of the aforementioned first user identifier.
[0073] In this embodiment, after the registration blockchain completes the registration of the first user identifier for the user, the registration blockchain can obtain the signature information of at least one blockchain node on the registration blockchain regarding the registered status of the first user identifier, which can be used as proof that the first user identifier is held by the user who currently triggers the registration request. This allows the business blockchain to determine whether the user who triggered the registration request is qualified based on the proof.
[0074] Understandably, a blockchain node will only sign when it determines that the first user identifier is registered and is held by the user who triggered the registration request. That is, the blockchain node will sign the registered status of the first user identifier.
[0075] Specifically, since there are multiple blockchain nodes on the registered blockchain, the block-producing node can be obtained from each blockchain node on the registered blockchain, and the block-producing node can summarize the signature information corresponding to each node.
[0076] In some embodiments, a preset number of blockchain nodes to which the signature information of the registered state of the first user identifier belongs can be preset. That is, the signature information is only fed back when the number of signature information of the blockchain nodes obtained is greater than or equal to the preset number. Correspondingly, if the number of signature information of the blockchain nodes obtained within a preset time is less than the preset number, it can be determined whether to feed back the signature information according to the needs. The preset number can be set according to the needs, and is generally 2 / 3 of the total number.
[0077] In some embodiments, the registration request may also include the registration address of the business blockchain, and the signature information is the signature of the blockchain node on the first user identifier and the registration address.
[0078] Optionally, if the registration request carries the registration address of the business blockchain, and the registration request is sent by the user terminal or the business blockchain, then after the registration blockchain obtains the signature information of at least one blockchain node on the registration blockchain regarding the registered status of the first user identifier, it can send the signature information to the business blockchain based on the registration address of the business blockchain in the registration request, so that after the business blockchain verifies the validity of the signature information, it can register a DID account for the user based on the first user identifier.
[0079] Optionally, if the registration request carries the registration address of the business blockchain and the registration request is sent by the user terminal, then after the registration blockchain obtains the signature information of at least one blockchain node on the registration blockchain regarding the registered status of the first user identifier, it can send a DID account registration request to the business blockchain based on the registration address of the business blockchain in the registration request. The DID account registration request includes signature information and the first user identifier, so that after the business blockchain verifies the validity of the signature information, it can register a DID account for the user based on the first user identifier.
[0080] In some embodiments, the acquisition of the signature information of the registered status of the first user identifier by at least one blockchain node on the aforementioned registration blockchain can be automatic or triggered.
[0081] Specifically, obtaining the signature information of at least one blockchain node on the registration blockchain regarding the registered status of the first user identifier may include: after the registration blockchain completes the registration of the first user identifier, the blockchain nodes can automatically sign the registered status of the first user identifier to obtain the signature information of at least one blockchain node on the registration blockchain regarding the registered status of the first user identifier.
[0082] Specifically, obtaining the signature information of at least one blockchain node on the registration blockchain regarding the registered status of the first user identifier may include: receiving a request from the sender to obtain the signature information of the first user identifier, wherein the request includes the first user identifier; and, based on the request, obtaining the signature information of at least one blockchain node on the registration blockchain regarding the registered status of the first user identifier. The sender may be a user terminal or a business blockchain.
[0083] It is understandable that if the registration request is sent by the user's terminal, then the signature information in this embodiment may be that the user terminal sends a signature information acquisition request when needed to prove that the user to which the user terminal belongs has the qualification to hold the user identifier, so as to obtain the signature information of at least one blockchain node on the registered status of the first user identifier; or it may be that when the business blockchain receives the DID account registration request, it sends a signature information acquisition request to verify whether the user who triggered the DID account registration request has the qualification to hold the corresponding user identifier, so as to obtain the signature information of at least one blockchain node on the registered status of the first user identifier.
[0084] If the above registration request is sent by the business blockchain, then since this scenario shows that the current business blockchain has a need to verify whether the user holds a user identifier based on the signature information, the signature information in this application embodiment is automatically obtained directly for subsequent steps.
[0085] 204. Send the aforementioned signature information to the sender of the aforementioned registration request. The aforementioned signature information is used for DID account registration on any of the aforementioned business blockchains.
[0086] In this embodiment, after obtaining the aforementioned signature information from the registered blockchain, the signature information is sent to the sender of the registration request. This signature information is used to provide proof for the user when registering a DID account on any business blockchain, thereby proving the user's eligibility to hold the first user identifier.
[0087] Understandably, if the sender is a user terminal, the registered blockchain sends the signature information to the user terminal, which then stores the signature information so that the user can use it when needed, i.e., send the signature information to the business blockchain for verification.
[0088] If the sender is a business blockchain, the registration blockchain will send the signature information to the business blockchain, which will then verify the signature information to determine if the user is qualified to hold the first user identifier. Furthermore, either the registration blockchain or the business blockchain can send the signature information to the user's terminal, allowing the user to send the signature information to the corresponding business blockchain when needed.
[0089] Specifically, since there are multiple blockchain nodes on the registration blockchain, the block-producing node can be obtained from each blockchain node on the registration blockchain. Therefore, the block-producing node can aggregate the signature information corresponding to each blockchain node to obtain aggregated signature information, and send the aggregated signature information to the sender of the above registration request.
[0090] In some embodiments, the blockchain-based registration method may further include: if the first user identifier exists among the registered user identifiers on the registration blockchain, and the first user identifier is held by the user who triggered the registration request, then obtain signature information of at least one blockchain node on the registration blockchain regarding the registered status of the first user identifier; and send the signature information to the sender of the registration request, wherein the signature information is used for DID account registration on any of the aforementioned business blockchains.
[0091] As can be seen from the above, by applying to the registration blockchain, and requiring DID accounts on at least two business blockchains to register based on the registered user identifiers on the aforementioned registration blockchain, and the registration blockchain receiving a registration request including a first user identifier to be registered, and judging the first user identifier, if the first user identifier does not exist among the registered user identifiers on the aforementioned registration blockchain, then the first user identifier is registered on the aforementioned registration blockchain, so that the first user identifier becomes a registered user identifier on the aforementioned registration blockchain, thereby enabling the user who triggered the registration request to possess the first user identifier on the registration blockchain and obtain the aforementioned... At least one blockchain node on the registered blockchain signs the registration status of the aforementioned first user identifier, and sends the signature information to the sender of the registration request. This signature information is used for DID account registration on any of the aforementioned business blockchains. Thus, when registering a DID account based on a user identifier on a business blockchain, the signature information can be used to determine whether the user who triggered the DID account registration is qualified to hold the first user identifier. This achieves the uniqueness of the user identifier of the same user on different blockchains, avoids the situation where the same user identifier is held by different users on different blockchains, and improves the portability of account management for the same user on different blockchains.
[0092] Example 2
[0093] In this embodiment, the application to a target business blockchain is used as an example. DID accounts on at least two business blockchains need to be registered based on the registered user identifier on the registration blockchain. The target business blockchain is one of the aforementioned at least two business blockchains. This embodiment provides a blockchain-based registration method, such as... Figure 3 As shown, the specific process of this blockchain-based registration method can be as follows:
[0094] 301. Receive a DID account registration request sent by a user, wherein the DID account registration request includes a second user identifier that needs to be registered for a DID account.
[0095] In this embodiment, the aforementioned DID account registration request is used to request the registration of a second user identifier on the target business blockchain, that is, to perform DID account registration on the target business blockchain based on the second user identifier, so as to verify the user's eligibility to hold the second user identifier. When the verification is successful, DID account registration is performed for the user on the target business blockchain based on the second user identifier.
[0096] The aforementioned second user identifier is used to identify the user's identity, and this second user identifier can be composed of characters. It should be noted that this second user identifier is the unique identifier of the aforementioned DID. For example, the second user identifier can be the domain name tom.eth, jack.eth, or the username Tom.
[0097] In some embodiments, since the business blockchain also consists of multiple blockchain nodes, for the purpose of distinguishing description, in this embodiment, the blockchain nodes of the business blockchain are referred to as business blockchain nodes, and the blockchain nodes of the aforementioned registration blockchain are still referred to as blockchain nodes.
[0098] Furthermore, when generating new data on the business blockchain, i.e., registering a DID account based on the second user identifier, it needs to be processed based on the consensus mechanism of multiple business blockchain nodes. Therefore, each business blockchain node on the business blockchain needs to receive the registration request.
[0099] Specifically, receiving the DID account registration request sent by the user may include: receiving the DID account registration request sent by the user through at least one business blockchain node on the aforementioned business blockchain, and broadcasting the DID account registration request to other business blockchain nodes on the aforementioned business blockchain, so that other business blockchain nodes receive the DID account registration request, thereby realizing that all business blockchain nodes on the business blockchain receive the DID account registration request.
[0100] In some embodiments, the sender of the DID account registration request may be the user's user terminal, i.e. Figure 1 In the terminal 1000, the corresponding business blockchain 3000 receives the DID account registration request, which includes the DID account registration request sent by the user terminal.
[0101] Alternatively, the sender of the aforementioned DID account registration request could also be the registering blockchain, i.e. Figure 1 In the registration blockchain 2000, the business blockchain 3000 receives the DID account registration request, which includes the DID account registration request sent by the registration blockchain based on the registration address of the business blockchain in the received registration request.
[0102] 302. Obtain the signature information of at least one blockchain node on the aforementioned registration blockchain regarding the registered status of the aforementioned second user identifier.
[0103] In this embodiment, the business blockchain can obtain the signature information of at least one blockchain node on the registration blockchain regarding the registered status of the second user identifier, which can be used as proof that the second user identifier is held by the user who currently triggers the DID account registration request. This allows the business blockchain to determine whether the user who triggered the DID account registration request is qualified based on the proof.
[0104] Understandably, a blockchain node will only sign a second user identifier when it confirms that the second user identifier is registered and is held by the user who triggered the DID account registration request. This signature information is the blockchain node's signature of the second user identifier's registered status. Therefore, the user who triggered the DID account registration request can be judged based on this signature information.
[0105] In some embodiments, the acquisition of the signature information of the registered status of the second username user identifier by at least one blockchain node on the aforementioned registration blockchain may be automatic or triggered.
[0106] Specifically, obtaining the signature information of at least one blockchain node on the registration blockchain regarding the registered status of the second user identifier may include: the business blockchain obtaining the signature information of at least one blockchain node on the registration blockchain regarding the registered status of the second user identifier from the DID account registration request.
[0107] It is understandable that if the aforementioned DID account registration request is sent by a user terminal, the DID account registration request may include signature information, meaning that the signature information has been obtained by the user terminal. In addition, if the aforementioned DID account registration request is sent by the registration blockchain based on the registration address of the business blockchain in the registration request, and the business blockchain in the registration request is the aforementioned target business blockchain, then the DID account registration request includes signature information, meaning that the signature information is generated by the registration blockchain after successfully registering the second user identifier.
[0108] Specifically, obtaining the signature information of at least one blockchain node on the registration blockchain regarding the registered status of the second user identifier may include: generating a request to obtain the signature information of the registered status of the second user identifier based on the second user identifier; sending the request to the registration blockchain so that the registration blockchain receives the request and, based on the request, signs the registered status of the second user identifier through at least one blockchain node on the registration blockchain to obtain signature information; and obtaining the signature information of at least one blockchain node on the registration blockchain regarding the registered status of the second user identifier sent by the registration blockchain.
[0109] It is understandable that if the aforementioned DID account registration request is sent by the user terminal, the DID account registration request may not include signature information. If it does not include signature information, the business blockchain needs to send a request to the registration blockchain to obtain the signature information of the second user identifier. The request includes the second user identifier, so that the registration blockchain can obtain the signature information of at least one blockchain node on the registration blockchain regarding the registered status of the second user identifier based on the request, and then feed it back to the business blockchain, so that the business blockchain can obtain the signature information of at least one blockchain node on the registration blockchain regarding the registered status of the second user identifier.
[0110] 303. Verify the signature validity of the signature information corresponding to at least one of the above blockchain nodes.
[0111] In this embodiment, the above-mentioned validity verification is used to verify whether the blockchain node to which the signature information belongs is a valid node, and whether the number of signature information corresponding to the blockchain node is greater than or equal to a preset number. That is, if the blockchain node is a valid node, it means that the identity validity verification of the blockchain node has passed. Furthermore, if the number of signature information is greater than or equal to the preset number, it is determined that the above-mentioned signature validity verification has passed. The preset number can be set according to the needs, and is generally 2 / 3 of the total number.
[0112] Among them, the aforementioned valid nodes are blockchain nodes stored in the target business blockchain that can perform signing to generate signature information in the registered blockchain.
[0113] Specifically, DID smart contracts can be deployed on each business blockchain node of the aforementioned business blockchain to enable the DID smart contracts on each business blockchain node to verify the signature validity of the signature information corresponding to at least one blockchain node.
[0114] In some embodiments, the target business blockchain includes first node information of blockchain nodes on the registration blockchain. The signature validity verification of the signature information corresponding to the at least one blockchain node may include: obtaining second node information of the blockchain node that signed based on the second user identifier from the signature information; performing node signature verification based on the first node information and the second node information, that is, determining whether each blockchain node in the second node information is consistent with one blockchain node in the first node information. If all blockchain nodes in the second node information are consistent, the node signature verification is considered to be successful. Accordingly, if the node signature verification is successful and the number of nodes in the second node information is greater than or equal to a preset number, the signature validity verification is determined to be successful.
[0115] The aforementioned first node information refers to the node information of blockchain nodes on the registered blockchain that are capable of signing; generally, it includes the node information of all blockchain nodes on the registered blockchain. When a blockchain node needs to be removed from the registered blockchain due to some factors, other blockchain nodes on the registered blockchain will sign the removal information, obtaining removal signature information, and send this removal signature information to the business blockchain. After verifying the validity of the removal signature information, the business blockchain updates its stored first node information, i.e., the node information of the aforementioned valid nodes. Similarly, when a new blockchain node is added to the registered blockchain, the same method is followed: the registered blockchain obtains the new signature information and sends it to the business blockchain. After verifying the validity of the new signature information, the business blockchain updates its stored first node information, i.e., the node information of the aforementioned valid nodes.
[0116] For example, if the first node information is set to N1, N2, ..., Nm, and the second node information is set to S1, S2, ..., Sn, and the preset number is 7, where m is greater than or equal to n, then by comparing the nodes, if all the nodes from S1 to Sn are consistent with one of the blockchain nodes from N1 to Nm, and n is 8, then it means that the number of nodes in the second node information is greater than or equal to the preset number, and the above signature validity verification is confirmed to be successful.
[0117] Optionally, if some of the blockchain nodes in the second node information are not consistent with the blockchain nodes in the first node information, the number of other blockchain nodes in the second node information excluding the inconsistent blockchain nodes is calculated. If the number of nodes is greater than or equal to the preset number, the above signature validity verification is still considered to be successful.
[0118] Optionally, if some of the blockchain nodes in the second node information are not consistent with the blockchain nodes in the first node information, the number of other blockchain nodes in the second node information excluding the inconsistent blockchain nodes is calculated. If the number of nodes is less than a preset number, the above signature validity verification is considered to have failed.
[0119] 304. If the above signature validity verification passes, then DID account registration will be performed for the above user on the above target business blockchain based on the above second user identifier.
[0120] In this embodiment, to ensure the uniqueness of DID accounts across multiple business blockchains, the uniqueness of the second user identifier required for DID account registration is verified. Specifically, the signature information of this second user identifier is validated on the registration blockchain. If the validation passes, the signature information is deemed valid, and the business blockchain can then provide a certain type of service to the user presenting the signature information, i.e., registering a DID account for that user based on the second user identifier. This DID account registration can be performed via a smart contract deployed on the target business blockchain.
[0121] In some embodiments, the DID account registration request further includes the registration address on the target business blockchain, and the DID account registration for the user on the target business blockchain based on the second user identifier includes: registering the DID account for the user on the target business blockchain based on the second user identifier and the registration address.
[0122] For example, if the above registration address is set as A1 and the user identifier is Tom, then based on A1 and Tom, an account named Tom can be registered on the target business blockchain for the registration address A1.
[0123] As can be seen from the above, by applying to the target business blockchain, and requiring DID accounts on at least two business blockchains to register based on registered user identifiers on the registration blockchain, the target business blockchain is one of the at least two business blockchains. This target business blockchain receives DID account registration requests from users, including a second user identifier to be registered. It obtains signature information from at least one blockchain node on the registration blockchain regarding the registered status of the second user identifier, and then verifies the signature validity of the signature information corresponding to the at least one blockchain node. Based on this signature information, it determines whether the user triggering the DID account registration is qualified to hold the second user identifier. If the signature validity verification passes, it indicates that the user triggering the DID account registration is qualified to hold the second user identifier. Therefore, based on the second user identifier, DID account registration is performed for the user on the target business blockchain. This achieves the uniqueness of the user identifier for the same user on different blockchains, avoiding the situation where a user identifier is held by different users on different blockchains, and improving the portability of account management for the same user on different blockchains.
[0124] To better implement the above methods, this application also provides a blockchain-based registration device, which can be integrated into an electronic device, such as a computer device, which can be a terminal, server, or other device.
[0125] The terminal can be a mobile phone, tablet computer, smart Bluetooth device, laptop computer, personal computer, etc.; the server can be a single server or a server cluster composed of multiple servers.
[0126] Example 3
[0127] In this embodiment, taking the integration of a blockchain-based registration device into a terminal as an example, the method of this application embodiment will be described in detail. This embodiment provides a blockchain-based registration device, which is applied to a registration blockchain. At least two business blockchains require DID accounts to register based on the registered user identifiers on the aforementioned registration blockchain. Figure 4 As shown, the blockchain-based registration device may include:
[0128] The first receiving module 401 is used to receive a registration request, wherein the registration request includes a first user identifier to be registered;
[0129] The first registration module 402 is used to register the first user identifier on the registration blockchain if the first user identifier does not exist among the registered user identifiers on the registration blockchain, so that the first user identifier becomes a registered user identifier on the registration blockchain.
[0130] The first acquisition module 403 is used to acquire the signature information of at least one blockchain node on the above-mentioned registration blockchain regarding the registered status of the above-mentioned first user identifier.
[0131] The sending module 404 is used to send the aforementioned signature information to the sender of the aforementioned registration request. The aforementioned signature information is used for DID account registration on any of the aforementioned business blockchains.
[0132] In some embodiments, the registration request may also include the registration address of the business blockchain, and the signature information is the signature of the blockchain node on the first user identifier and the registration address.
[0133] In some embodiments, the first acquisition module 403 is specifically used for:
[0134] Receive a request from the sender to obtain the signature information of the first user identifier, wherein the request includes the first user identifier;
[0135] Based on the above request, obtain the signature information of at least one blockchain node on the above-mentioned registration blockchain regarding the registered status of the first user identifier.
[0136] In some embodiments, the first registration module 402 is specifically used for:
[0137] By checking the blockchain nodes on the aforementioned registration blockchain, we can determine whether the aforementioned first user identifier exists among the registered user identifiers stored on the aforementioned blockchain nodes.
[0138] If the first user identifier is not among the registered user identifiers corresponding to the aforementioned blockchain node, then the first user identifier will be registered on the aforementioned registration blockchain.
[0139] In some embodiments, the sending module 404 is further configured to:
[0140] If the first user identifier exists among the registered user identifiers on the aforementioned registration blockchain, and the first user identifier is held by the user who triggered the aforementioned registration request, then the signature information of at least one blockchain node on the aforementioned registration blockchain regarding the registered status of the first user identifier is obtained.
[0141] Send the aforementioned signature information to the sender of the aforementioned registration request.
[0142] In some embodiments, the registration request includes a request sent by a user terminal; or a request sent by the business blockchain based on a received DID account registration request, wherein the first user identifier is the user identifier in the DID account registration request.
[0143] As can be seen from the above, the blockchain-based registration device of this embodiment is applied to the registration blockchain, and DID accounts on at least two business blockchains need to register DID accounts based on the registered user identifiers on the registration blockchain. The registration blockchain receives a registration request including a first user identifier to be registered through the first receiving module 401, and judges the first user identifier through the first registration module 402. If the first user identifier does not exist among the registered user identifiers on the registration blockchain, the first user identifier is registered on the registration blockchain, so that the first user identifier becomes a registered user identifier on the registration blockchain, thereby realizing the possession of the first user identifier by the user who triggered the registration request on the registration blockchain. The system obtains signature information of at least one blockchain node on the registration blockchain regarding the registered status of the first user identifier through the first acquisition module 403, and sends the signature information to the sender of the registration request through the sending module 404. This signature information is used for DID account registration on any of the aforementioned business blockchains. Thus, when registering a DID account based on a user identifier on a business blockchain, the signature information can be used to determine whether the user who triggered the DID account registration is qualified to hold the first user identifier. This achieves the uniqueness of the user identifier of the same user on different blockchains, avoids the situation where the same user identifier is held by different users on different blockchains, and improves the portability of account management for the same user on different blockchains.
[0144] Example 4
[0145] In this embodiment, the method of this application embodiment will be described in detail using the example of a blockchain-based registration device specifically integrated into a terminal. This embodiment provides a blockchain-based registration device, which is applied to a target business blockchain. DID accounts on at least two business blockchains need to register DID accounts based on the registered user identifiers on the registration blockchain. The target business blockchain is one of the at least two business blockchains, such as... Figure 5 As shown, the blockchain-based registration device may include:
[0146] The second receiving module 501 is used to receive a DID account registration request sent by a user, wherein the DID account registration request includes a second user identifier that needs to register a DID account.
[0147] The second acquisition module 502 is used to acquire the signature information of at least one blockchain node on the above-mentioned registration blockchain regarding the registered status of the above-mentioned second user identifier.
[0148] Verification module 503 is used to verify the signature validity of the signature information corresponding to at least one of the above blockchain nodes;
[0149] The second registration module 504 is used to register a DID account for the user on the target business blockchain based on the second user identifier if the above signature validity verification passes.
[0150] In some embodiments, the second acquisition module 502 is specifically used for:
[0151] Obtain the signature information of at least one blockchain node on the aforementioned registration blockchain regarding the registered status of the aforementioned second user identifier from the aforementioned DID account registration request.
[0152] In some embodiments, the second acquisition module 502 is specifically used for:
[0153] Based on the aforementioned second user identifier, a request is generated to obtain signature information regarding the registered status of the aforementioned second user identifier;
[0154] The above-mentioned acquisition request is sent to the above-mentioned registration blockchain so that the above-mentioned registration blockchain receives the above-mentioned acquisition request and, based on the above-mentioned acquisition request, signs the registered status of the above-mentioned second user identifier through at least one blockchain node on the above-mentioned registration blockchain to obtain signature information;
[0155] Obtain the signature information of at least one blockchain node on the aforementioned registration blockchain regarding the registered status of the aforementioned second user identifier, sent by the aforementioned registration blockchain.
[0156] In some embodiments, the DID account registration request further includes a registration address on the target business blockchain, and the second registration module 504 is specifically used for:
[0157] Based on the aforementioned second user identifier and the aforementioned registration address, DID account registration is performed for the aforementioned user on the aforementioned target business blockchain.
[0158] In some embodiments, the target business blockchain includes first node information of the blockchain node on the registration blockchain, and the verification module 503 is specifically used for:
[0159] Obtain the second node information of the blockchain node that signed based on the second user identifier from the above signature information;
[0160] Based on the first node information and the second node information mentioned above, node signature verification is performed;
[0161] If the above node signature verification passes, and the number of nodes in the above second node information is greater than or equal to the preset number, then the above signature validity verification is determined to be successful.
[0162] As can be seen from the above, the blockchain-based registration device of this embodiment is applied to a target business blockchain, and DID accounts on at least two business blockchains need to register DID accounts based on registered user identifiers on the registration blockchain. The target business blockchain is one of the at least two business blockchains, and the target business blockchain receives the DID account registration request sent by the user through the second receiving module 501. The DID account registration request includes the second user identifier that needs to be registered for DID account registration, and obtains the signature information of at least one blockchain node on the registration blockchain regarding the registered status of the second user identifier through the second obtaining module 502. Then, the verification module 503 verifies the signature information of the at least one blockchain node on the registration blockchain regarding the registered status of the second user identifier. The signature information corresponding to each blockchain node is used to verify the validity of the signature. Based on this signature information, it is determined whether the user who triggered the DID account registration is qualified to hold the second user identifier. Finally, the second registration module 504 judges the validity verification result. If the above signature validity verification passes, it means that the user who triggered the DID account registration is qualified to hold the second user identifier. Then, based on the second user identifier, the DID account is registered for the user on the target business blockchain. This realizes the uniqueness of the user identifier of the same user on different blockchains, avoids the situation where the same user identifier is held by different users on different blockchains, and improves the portability of account management for the same user on different blockchains.
[0163] Example 5
[0164] Accordingly, this application also provides an electronic device, which can be a terminal, such as a smartphone, tablet computer, laptop computer, touch screen, game console, personal computer (PC), personal digital assistant (PDA), or other terminal device. Figure 6 As shown, Figure 6 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. The electronic device 600 includes a processor 601 with one or more processing cores, a memory 602 with one or more computer-readable storage media, and a computer program stored on the memory 602 and executable on the processor. The processor 601 and the memory 602 are electrically connected. Those skilled in the art will understand that the electronic device structure shown in the figure does not constitute a limitation on the electronic device, and may include more or fewer components than shown, or combine certain components, or have different component arrangements.
[0165] The processor 601 is the control center of the electronic device 600. It connects various parts of the electronic device 600 through various interfaces and lines. By running or loading software programs and / or modules stored in the memory 602, and calling data stored in the memory 602, it performs various functions of the electronic device 600 and processes data, thereby monitoring the electronic device 600 as a whole.
[0166] In this embodiment, the processor 601 in the electronic device 600 loads the instructions corresponding to the processes of one or more applications into the memory 602 according to the following steps, and the processor 601 runs the applications stored in the memory 602 to achieve various functions:
[0167] Receive a registration request, which includes the identifier of the first user to be registered;
[0168] If the first user identifier is not among the registered user identifiers on the aforementioned registration blockchain, then the first user identifier is registered on the aforementioned registration blockchain so that the first user identifier becomes a registered user identifier on the aforementioned registration blockchain.
[0169] Obtain the signature information of at least one blockchain node on the aforementioned registration blockchain regarding the registered status of the aforementioned first user identifier;
[0170] The aforementioned signature information is sent to the sender of the aforementioned registration request. The aforementioned signature information is used for DID account registration on any of the aforementioned business blockchains.
[0171] In some embodiments, the registration request may also include the registration address of the business blockchain, and the signature information is the signature of the blockchain node on the first user identifier and the registration address.
[0172] In some embodiments, obtaining the signature information of at least one blockchain node on the registration blockchain regarding the registered status of the first user identifier includes:
[0173] Receive a request from the sender to obtain the signature information of the first user identifier, wherein the request includes the first user identifier;
[0174] Based on the above request, obtain the signature information of at least one blockchain node on the above-mentioned registration blockchain regarding the registered status of the first user identifier.
[0175] In some embodiments, if the first user identifier is not among the registered user identifiers on the registration blockchain, then registering the first user identifier on the registration blockchain includes:
[0176] By checking the blockchain nodes on the aforementioned registration blockchain, we can determine whether the aforementioned first user identifier exists among the registered user identifiers stored on the aforementioned blockchain nodes.
[0177] If the first user identifier is not among the registered user identifiers corresponding to the aforementioned blockchain node, then the first user identifier will be registered on the aforementioned registration blockchain.
[0178] In some embodiments, it also includes:
[0179] If the first user identifier exists among the registered user identifiers on the aforementioned registration blockchain, and the first user identifier is held by the user who triggered the aforementioned registration request, then the signature information of at least one blockchain node on the aforementioned registration blockchain regarding the registered status of the first user identifier is obtained.
[0180] Send the aforementioned signature information to the sender of the aforementioned registration request.
[0181] In some embodiments, the registration request includes a request sent by a user terminal; or a request sent by the business blockchain based on a received DID account registration request, wherein the first user identifier is the user identifier in the DID account registration request.
[0182] In addition, the following functions can also be achieved:
[0183] Receive a DID account registration request sent by a user, wherein the DID account registration request includes a second user identifier that needs to register a DID account;
[0184] Obtain the signature information of at least one blockchain node on the aforementioned registration blockchain regarding the registered status of the aforementioned second user identifier;
[0185] Verify the validity of the signature information corresponding to at least one of the above blockchain nodes;
[0186] If the above signature validity verification passes, then DID account registration will be performed for the above user on the above target business blockchain based on the above second user identifier.
[0187] In some embodiments, obtaining the signature information of at least one blockchain node on the registration blockchain regarding the registered status of the second user identifier includes:
[0188] Obtain the signature information of at least one blockchain node on the aforementioned registration blockchain regarding the registered status of the aforementioned second user identifier from the aforementioned DID account registration request.
[0189] In some embodiments, obtaining the signature information of at least one blockchain node on the registration blockchain regarding the registered status of the second user identifier includes:
[0190] Based on the aforementioned second user identifier, a request is generated to obtain signature information regarding the registered status of the aforementioned second user identifier;
[0191] The above-mentioned acquisition request is sent to the above-mentioned registration blockchain so that the above-mentioned registration blockchain receives the above-mentioned acquisition request and, based on the above-mentioned acquisition request, signs the registered status of the above-mentioned second user identifier through at least one blockchain node on the above-mentioned registration blockchain to obtain signature information;
[0192] Obtain the signature information of at least one blockchain node on the aforementioned registration blockchain regarding the registered status of the aforementioned second user identifier, sent by the aforementioned registration blockchain.
[0193] In some embodiments, the DID account registration request further includes a registration address on the target business blockchain, and the DID account registration for the user on the target business blockchain based on the second user identifier includes:
[0194] Based on the aforementioned second user identifier and the aforementioned registration address, DID account registration is performed for the aforementioned user on the aforementioned target business blockchain.
[0195] In some embodiments, the target business blockchain includes first node information of blockchain nodes on the registration blockchain, and the signature validity verification of the signature information corresponding to the at least one blockchain node includes:
[0196] Obtain the second node information of the blockchain node that signed based on the second user identifier from the above signature information;
[0197] Based on the first node information and the second node information mentioned above, node signature verification is performed;
[0198] If the above node signature verification passes, and the number of nodes in the above second node information is greater than or equal to the preset number, then the above signature validity verification is determined to be successful.
[0199] Therefore, the electronic device 600 provided in this embodiment can bring the following technical effects: improve the portability of managing the same user's accounts on different blockchains.
[0200] For details on the implementation of each of the above operations, please refer to the previous examples, which will not be repeated here.
[0201] Optional, such as Figure 6As shown, the electronic device 600 also includes: a touch display screen 603, a radio frequency circuit 604, an audio circuit 605, an input unit 606, and a power supply 607. The processor 601 is electrically connected to the touch display screen 603, the radio frequency circuit 604, the audio circuit 605, the input unit 606, and the power supply 607. Those skilled in the art will understand that... Figure 6 The electronic device structure shown does not constitute a limitation on the electronic device and may include more or fewer components than shown, or combine certain components, or have different component arrangements.
[0202] The touch display screen 603 can be used to display a graphical user interface (GUI) and receive operation commands generated by the user interacting with the GUI. The touch display screen 603 may include a display panel and a touch panel. The display panel can be used to display information input by the user or information provided to the user, as well as various graphical user interfaces of the electronic device. These graphical user interfaces can be composed of graphics, text, icons, video, and any combination thereof. Optionally, the display panel can be configured using a liquid crystal display (LCD), organic light-emitting diode (OLED), or other similar technologies. The touch panel can be used to collect touch operations performed by the user on or near it (such as operations performed by the user using a finger, stylus, or any suitable object or accessory on or near the touch panel), generate corresponding operation commands, and execute the corresponding program according to the operation commands. Optionally, the touch panel may include two parts: a touch detection device and a touch controller. The touch detection device detects the user's touch location and the signal generated by the touch operation, transmitting the signal to the touch controller. The touch controller receives touch information from the touch detection device, converts it into touch point coordinates, and sends it to the processor 601. It can also receive and execute commands from the processor 601. The touch panel can cover the display panel. When the touch panel detects a touch operation on or near it, it transmits the information to the processor 601 to determine the type of touch event. Subsequently, the processor 601 provides corresponding visual output on the display panel based on the type of touch event. In this embodiment, the touch panel and the display panel can be integrated into the touch display screen 603 to achieve input and output functions. However, in some embodiments, the touch panel and the touch display screen 603 can be implemented as two independent components to achieve input and output functions. That is, the touch display screen 603 can also be used as part of the input unit 606 to achieve input functions.
[0203] The radio frequency circuit 604 can be used to transmit and receive radio frequency signals to establish wireless communication with network devices or other electronic devices, and to transmit and receive signals with network devices or other electronic devices.
[0204] Audio circuit 605 can be used to provide an audio interface between a user and an electronic device via a speaker and a microphone. Audio circuit 605 can convert received audio data into electrical signals and transmit them to the speaker, where the speaker converts them into sound signals for output. Conversely, the microphone converts collected sound signals into electrical signals, which are then received by audio circuit 605, converted back into audio data, and then processed by processor 601 before being transmitted via radio frequency circuit 604 to, for example, another electronic device, or output to memory 602 for further processing. Audio circuit 605 may also include an earphone jack to provide communication between peripheral headphones and electronic devices.
[0205] The input unit 606 can be used to receive input numbers, characters, or user characteristic information (such as fingerprints, iris, facial information, etc.), and to generate keyboard, mouse, joystick, optical, or trackball signal inputs related to user settings and function control.
[0206] Power supply 607 is used to supply power to various components of electronic device 600. Optionally, power supply 607 can be logically connected to processor 601 through a power management system, thereby enabling functions such as charging, discharging, and power consumption management through the power management system. Power supply 607 may also include one or more DC or AC power supplies, recharging systems, power fault detection circuits, power converters or inverters, power status indicators, and other arbitrary components.
[0207] although Figure 6 As not shown in the diagram, the electronic device 600 may also include a camera, sensor, wireless fidelity module, Bluetooth module, etc., which will not be described in detail here.
[0208] In the above embodiments, the descriptions of each embodiment have different focuses. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions in other embodiments.
[0209] Those skilled in the art will understand that all or part of the steps in the various methods of the above embodiments can be performed by instructions, or by instructions controlling related hardware. These instructions can be stored in a computer-readable storage medium and loaded and executed by a processor.
[0210] Therefore, embodiments of this application provide a computer-readable storage medium storing multiple computer programs that can be loaded by a processor to execute steps in any of the blockchain-based registration methods provided in embodiments of this application. For example, the computer program can execute the following steps:
[0211] Receive a registration request, which includes the identifier of the first user to be registered;
[0212] If the first user identifier is not among the registered user identifiers on the aforementioned registration blockchain, then the first user identifier is registered on the aforementioned registration blockchain so that the first user identifier becomes a registered user identifier on the aforementioned registration blockchain.
[0213] Obtain the signature information of at least one blockchain node on the aforementioned registration blockchain regarding the registered status of the aforementioned first user identifier;
[0214] The aforementioned signature information is sent to the sender of the aforementioned registration request. The aforementioned signature information is used for DID account registration on any of the aforementioned business blockchains.
[0215] In some embodiments, the registration request may also include the registration address of the business blockchain, and the signature information is the signature of the blockchain node on the first user identifier and the registration address.
[0216] In some embodiments, obtaining the signature information of at least one blockchain node on the registration blockchain regarding the registered status of the first user identifier includes:
[0217] Receive a request from the sender to obtain the signature information of the first user identifier, wherein the request includes the first user identifier;
[0218] Based on the above request, obtain the signature information of at least one blockchain node on the above-mentioned registration blockchain regarding the registered status of the first user identifier.
[0219] In some embodiments, if the first user identifier is not among the registered user identifiers on the registration blockchain, then registering the first user identifier on the registration blockchain includes:
[0220] By checking the blockchain nodes on the aforementioned registration blockchain, we can determine whether the aforementioned first user identifier exists among the registered user identifiers stored on the aforementioned blockchain nodes.
[0221] If the first user identifier is not among the registered user identifiers corresponding to the aforementioned blockchain node, then the first user identifier will be registered on the aforementioned registration blockchain.
[0222] In some embodiments, it also includes:
[0223] If the first user identifier exists among the registered user identifiers on the aforementioned registration blockchain, and the first user identifier is held by the user who triggered the aforementioned registration request, then the signature information of at least one blockchain node on the aforementioned registration blockchain regarding the registered status of the first user identifier is obtained.
[0224] Send the aforementioned signature information to the sender of the aforementioned registration request.
[0225] In some embodiments, the registration request includes a request sent by a user terminal; or a request sent by the business blockchain based on a received DID account registration request, wherein the first user identifier is the user identifier in the DID account registration request.
[0226] Alternatively, the following steps can be performed:
[0227] Receive a DID account registration request sent by a user, wherein the DID account registration request includes a second user identifier that needs to register a DID account;
[0228] Obtain the signature information of at least one blockchain node on the aforementioned registration blockchain regarding the registered status of the aforementioned second user identifier;
[0229] Verify the validity of the signature information corresponding to at least one of the above blockchain nodes;
[0230] If the above signature validity verification passes, then DID account registration will be performed for the above user on the above target business blockchain based on the above second user identifier.
[0231] In some embodiments, obtaining the signature information of at least one blockchain node on the registration blockchain regarding the registered status of the second user identifier includes:
[0232] Obtain the signature information of at least one blockchain node on the aforementioned registration blockchain regarding the registered status of the aforementioned second user identifier from the aforementioned DID account registration request.
[0233] In some embodiments, obtaining the signature information of at least one blockchain node on the registration blockchain regarding the registered status of the second user identifier includes:
[0234] Based on the aforementioned second user identifier, a request is generated to obtain signature information regarding the registered status of the aforementioned second user identifier;
[0235] The above-mentioned acquisition request is sent to the above-mentioned registration blockchain so that the above-mentioned registration blockchain receives the above-mentioned acquisition request and, based on the above-mentioned acquisition request, signs the registered status of the above-mentioned second user identifier through at least one blockchain node on the above-mentioned registration blockchain to obtain signature information;
[0236] Obtain the signature information of at least one blockchain node on the aforementioned registration blockchain regarding the registered status of the aforementioned second user identifier, sent by the aforementioned registration blockchain.
[0237] In some embodiments, the DID account registration request further includes a registration address on the target business blockchain, and the DID account registration for the user on the target business blockchain based on the second user identifier includes:
[0238] Based on the aforementioned second user identifier and the aforementioned registration address, DID account registration is performed for the aforementioned user on the aforementioned target business blockchain.
[0239] In some embodiments, the target business blockchain includes first node information of blockchain nodes on the registration blockchain, and the signature validity verification of the signature information corresponding to the at least one blockchain node includes:
[0240] Obtain the second node information of the blockchain node that signed based on the second user identifier from the above signature information;
[0241] Based on the first node information and the second node information mentioned above, node signature verification is performed;
[0242] If the above node signature verification passes, and the number of nodes in the above second node information is greater than or equal to the preset number, then the above signature validity verification is determined to be successful.
[0243] As can be seen, the computer program can be loaded by the processor to execute the steps in any of the blockchain-based registration methods provided in the embodiments of this application, thereby bringing the following technical effects: improving the portability of account management for the same user on different blockchains.
[0244] For details on the implementation of each of the above operations, please refer to the previous examples, which will not be repeated here.
[0245] The computer-readable storage medium may include: read-only memory (ROM), random access memory (RAM), disk or optical disk, etc.
[0246] Since the computer program stored in the computer-readable storage medium can execute the steps of any of the blockchain-based registration methods provided in the embodiments of this application, the beneficial effects that any of the blockchain-based registration methods provided in the embodiments of this application can achieve can be realized, as detailed in the preceding embodiments, and will not be repeated here.
[0247] The foregoing has provided a detailed description of a blockchain-based registration method, apparatus, electronic device, and computer-readable storage medium provided in the embodiments of this application. Specific examples have been used to illustrate the principles and implementation methods of this application. The descriptions of the embodiments above are only for the purpose of helping to understand the method and core ideas of this application. At the same time, for those skilled in the art, there will be changes in the specific implementation methods and application scope based on the ideas of this application. Therefore, the content of this specification should not be construed as a limitation of this application.
Claims
1. A blockchain-based registration method, characterized in that, The method is applied to a registration blockchain, which consists of blockchain nodes that store at least one registered user identifier and issue signature information for the registration status of the user identifier. At least two independent business blockchains require DID accounts to register based on the registered user identifiers on the registration blockchain. The method includes: Receive a registration request, the registration request including a first user identifier to be registered; If the first user identifier is not among the registered user identifiers on the registration blockchain, then the first user identifier is registered on the registration blockchain so that the first user identifier becomes a registered user identifier on the registration blockchain, and other users cannot register a DID account on the business blockchain where the first user identifier is not registered, and the other users are users other than the user who triggered the registration request; Obtain the signature information of at least one blockchain node on the registration blockchain regarding the registered status of the first user identifier; The signature information is sent to the sender of the registration request, and the signature information is used for DID account registration on any of the business blockchains; If the first user identifier exists among the registered user identifiers on the registration blockchain, and the first user identifier is held by the user who triggered the registration request, then the signature information of at least one blockchain node on the registration blockchain regarding the registered status of the first user identifier is obtained. The signature information is sent to the sender of the registration request.
2. The blockchain-based registration method as described in claim 1, characterized in that, The registration request also includes the registration address of the business blockchain, and the signature information is the signature made by the blockchain node on the first user identifier and the registration address.
3. The blockchain-based registration method as described in claim 1, characterized in that, The step of obtaining the signature information of at least one blockchain node on the registration blockchain regarding the registered status of the first user identifier includes: Receive the sender's request to obtain the signature information of the first user identifier, wherein the request includes the first user identifier; Based on the acquisition request, acquire the signature information of at least one blockchain node on the registration blockchain regarding the registered status of the first user identifier.
4. The blockchain-based registration method as described in claim 1, characterized in that, If the first user identifier is not among the registered user identifiers on the registration blockchain, then registering the first user identifier on the registration blockchain includes: By querying the blockchain nodes on the registration blockchain, we can determine whether the first user identifier exists among the registered user identifiers stored on the blockchain nodes. If the first user identifier is not among the registered user identifiers corresponding to the blockchain node, then the first user identifier is registered on the registration blockchain.
5. The blockchain-based registration method as described in any one of claims 1 to 4, characterized in that, The registration request includes a request sent by a user terminal; or a request sent by the business blockchain based on a received DID account registration request, wherein the first user identifier is the user identifier in the DID account registration request.
6. A blockchain-based registration method, characterized in that, Applied to a target business blockchain, DID accounts on at least two independent business blockchains need to register DID accounts based on registered user identifiers on a registration blockchain. The target business blockchain is one of the at least two business blockchains. The registration blockchain consists of blockchain nodes that store at least one registered user identifier and issue signature information for the registration status of the user identifier. Other users cannot register DID accounts on the business blockchain where the registered user identifier is not registered, based on the registered user identifier. The other users are users other than the user corresponding to the registered user identifier. When a registration request containing a first user identifier with registration is received, and the first user identifier exists among the registered user identifiers on the registration blockchain, and the first user identifier is held by the user who triggered the registration request, the signature information of the blockchain node on the registration blockchain for the registration status of the first user identifier is obtained, and the signature information is sent to the sender of the registration request. The method includes: Receive a DID account registration request sent by a user, wherein the DID account registration request includes a second user identifier that needs to register a DID account; Obtain the signature information of at least one blockchain node on the registration blockchain regarding the registered status of the second user identifier; Verify the validity of the signature information corresponding to the at least one blockchain node; If the signature validity verification passes, then the user is registered for a DID account on the target business blockchain based on the second user identifier.
7. The blockchain-based registration method as described in claim 6, characterized in that, The step of obtaining the signature information of at least one blockchain node on the registration blockchain regarding the registered status of the second user identifier includes: Obtain the signature information of at least one blockchain node on the registration blockchain regarding the registered status of the second user identifier from the DID account registration request.
8. The blockchain-based registration method as described in claim 6, characterized in that, The step of obtaining the signature information of at least one blockchain node on the registration blockchain regarding the registered status of the second user identifier includes: Based on the second user identifier, a request is generated to obtain signature information regarding the registered status of the second user identifier; The acquisition request is sent to the registration blockchain so that the registration blockchain receives the acquisition request and, based on the acquisition request, signs the registered status of the second user identifier through at least one blockchain node on the registration blockchain to obtain signature information; Obtain the signature information of at least one blockchain node on the registration blockchain regarding the registered status of the second user identifier, sent by the registration blockchain.
9. The blockchain-based registration method as described in claim 6, characterized in that, The DID account registration request also includes a registration address on the target business blockchain, and the step of registering the user's DID account on the target business blockchain based on the second user identifier includes: Based on the second user identifier and the registration address, a DID account is registered for the user on the target business blockchain.
10. The blockchain-based registration method as described in any one of claims 6 to 9, characterized in that, The target business blockchain includes the first node information of the blockchain nodes on the registration blockchain. The signature validity verification of the signature information corresponding to the at least one blockchain node includes: Obtain the second node information of the blockchain node that signed based on the second user identifier from the signature information; Based on the first node information and the second node information, node signature verification is performed; If the node signature verification passes and the number of nodes in the second node information is greater than or equal to a preset number, then the signature validity verification is determined to be successful.
11. A blockchain-based registration device, characterized in that, The device is applied to a registration blockchain, which consists of blockchain nodes that store at least one registered user identifier and issue signature information for the registration status of the user identifier. At least two independent business blockchains require DID accounts to register based on the registered user identifiers on the registration blockchain. The device includes: The first receiving module is used to receive a registration request, the registration request including a first user identifier to be registered; The first registration module is used to register the first user identifier on the registration blockchain if the first user identifier does not exist among the registered user identifiers on the registration blockchain, so that the first user identifier becomes a registered user identifier on the registration blockchain, and other users cannot register DID accounts on the business blockchain where the first user identifier is not registered based on the first user identifier. The other users are users other than the user who triggered the registration request. The first acquisition module is used to acquire the signature information of at least one blockchain node on the registration blockchain regarding the registered status of the first user identifier; A sending module is used to send the signature information to the sender of the registration request, wherein the signature information is used for DID account registration on any of the business blockchains; The sending module is further configured to, if the first user identifier exists among the registered user identifiers on the registration blockchain and the first user identifier is held by the user who triggered the registration request, obtain signature information of the registered status of the first user identifier from at least one blockchain node on the registration blockchain; and send the signature information to the sender of the registration request.
12. A blockchain-based registration device, characterized in that, Applied to a target business blockchain, DID accounts on at least two independent business blockchains need to register DID accounts based on registered user identifiers on a registration blockchain. The target business blockchain is one of the at least two business blockchains. The registration blockchain consists of blockchain nodes that store at least one registered user identifier and issue signature information for the registration status of the user identifier. Other users cannot register DID accounts on the business blockchain where the registered user identifier is not registered, based on the registered user identifier. The other users are users other than the user corresponding to the registered user identifier. When a registration request containing a first user identifier with registration is received, and the first user identifier exists among the registered user identifiers on the registration blockchain, and the first user identifier is held by the user who triggered the registration request, the signature information of the blockchain node on the registration blockchain for the registration status of the first user identifier is obtained, and the signature information is sent to the sender of the registration request. The device includes: The second receiving module is used to receive a DID account registration request sent by a user, wherein the DID account registration request includes a second user identifier that needs to register a DID account; The second acquisition module is used to acquire the signature information of at least one blockchain node on the registration blockchain regarding the registered status of the second user identifier; The verification module is used to verify the signature validity of the signature information corresponding to the at least one blockchain node; The second registration module is used to register a DID account for the user on the target business blockchain based on the second user identifier if the signature validity verification passes.
13. An electronic device, characterized in that, It includes a processor and a memory, the memory storing multiple instructions; the processor loads instructions from the memory to perform the steps in the blockchain-based registration method as described in any one of claims 1 to 10.
14. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a plurality of instructions adapted for loading by a processor to perform the steps of the blockchain-based registration method according to any one of claims 1 to 10.
Citation Information
Patent Citations
Account registration method and device based on block chain and electronic equipment
CN110009353A
Data right confirmation method and system based on block chain technology
CN112651052A