A Domain Name Registration Method, Device, Equipment and Storage Medium Based on Blockchain

Abstract

The present application provides a blockchain-based domain name registration method, apparatus, device, and storage medium. The domain name registration method includes: in response to any user terminal completing the registration of a domain name on a first blockchain, the target network stores the domain name registered by the user terminal on the first blockchain in a local database; in response to a first domain name registration request sent by a first user terminal, the target network verifies, according to the first user signature carried in the first domain name registration request and the local database, whether the target domain name requested by the first user terminal to be registered on a second blockchain belongs to the domain name already registered by the first user terminal on the first blockchain; when it is determined that the target domain name belongs to the domain name already registered by the first user terminal on the first blockchain, the target network allows the first user terminal to register the target domain name on the second blockchain. In this way, the present application enables the same user to use the same decentralized domain name across blockchains.

Description

Technical Field

[0001] This application relates to the field of blockchain technology. Specifically, it relates to a domain name registration method, device, equipment, and storage medium based on blockchain. Background Art

[0002] In the field of blockchain, existing DID (Decentralized Identity) domain name registration project parties are usually located on only one blockchain, making the DID domain names registered by users on this blockchain unable to be used across blockchains.

[0003] Specifically, taking the DID domain name registered by a user on Ethereum as tom.eth as an example, at this time, the DID domain name tom.eth registered by the user on Ethereum can only represent the user on Ethereum, while on other blockchains other than Ethereum, the same DID domain name tom.eth may have been registered by other users, resulting in the user being unable to use the same DID domain name across blockchains, which is likely to cause confusion in user identity recognition during cross-chain interaction and is not conducive to the development of cross-chain technology. Summary of the Invention

[0004] In view of this, the purpose of this application is to provide a domain name registration method, device, equipment, and storage medium based on blockchain, enabling the same user to use the same decentralized domain name (i.e., DID domain name) across blockchains, effectively improving the accuracy of user identity recognition during cross-chain interaction, and being conducive to the development of cross-chain technology.

[0005] To make the above objects, features, and advantages of this application more obvious and understandable, the following specifically gives preferred embodiments and, in conjunction with the attached drawings, makes a detailed description as follows.

[0006] In a first aspect, an embodiment of this application provides a domain name registration method based on blockchain. The domain name registration method includes:

[0007] In response to any user terminal completing the registration of a domain name on the first blockchain, the target network stores the domain name registered by the user terminal on the first blockchain in the local database;

[0008] In response to a first domain name registration request sent by the first user terminal, the target network verifies whether the target domain name requested by the first user terminal to be registered on the second blockchain belongs to the domain name already registered by the first user terminal on the first blockchain according to the first user signature carried in the first domain name registration request and the local database; wherein, the first user signature is determined according to the first blockchain address corresponding to the first user terminal on the first blockchain;

[0009] When it is determined that the target domain name belongs to the domain names registered by the first user terminal on the first blockchain, the target network allows the first user terminal to register the target domain name on the second blockchain.

[0010] In a second aspect, an embodiment of the present application provides a blockchain-based domain name registration device, where the domain name registration device includes:

[0011] A recording module, configured to store, in a local database, the domain names registered by any user terminal on the first blockchain in response to the completion of domain name registration on the first blockchain by the target network;

[0012] A first verification module, configured to verify, in response to a first domain name registration request sent by a first user terminal through the target network, whether the target domain name requested by the first user terminal to be registered on the second blockchain belongs to the domain names registered by the first user terminal on the first blockchain according to the first user signature carried in the first domain name registration request and the local database; wherein, the first user signature is determined according to the first blockchain address corresponding to the first user terminal on the first blockchain;

[0013] A second verification module, configured to allow the first user terminal to register the target domain name on the second blockchain through the target network when it is determined that the target domain name belongs to the domain names registered by the first user terminal on the first blockchain.

[0014] In a third aspect, an embodiment of the present application provides a blockchain-based domain name registration system, where the domain name registration system includes: a target network and multiple user terminals; wherein, the target network is configured to:

[0015] Store, in a local database, the domain names registered by any user terminal on the first blockchain in response to the completion of domain name registration on the first blockchain by the user terminal;

[0016] Verify, in response to a first domain name registration request sent by a first user terminal, whether the target domain name requested by the first user terminal to be registered on the second blockchain belongs to the domain names registered by the first user terminal on the first blockchain according to the first user signature carried in the first domain name registration request and the local database; wherein, the first user signature is determined according to the first blockchain address corresponding to the first user terminal on the first blockchain;

[0017] Allow the first user terminal to register the target domain name on the second blockchain when it is determined that the target domain name belongs to the domain names registered by the first user terminal on the first blockchain.

[0018] Fourthly, an embodiment of the present application provides a computer device, including a memory, a processor, and a computer program stored on the memory and executable on the processor. When the processor executes the computer program, the steps of the above-mentioned blockchain-based domain name registration method are implemented.

[0019] Fifthly, an embodiment of the present application provides a computer-readable storage medium, on which a computer program is stored. When the computer program is run by a processor, the steps of the above-mentioned blockchain-based domain name registration method are executed.

[0020] The technical solutions provided by the embodiments of the present application may include the following beneficial effects:

[0021] A blockchain-based domain name registration method, device, equipment, and storage medium provided by an embodiment of the present application. In response to any user terminal completing domain name registration on a first blockchain, the target network stores the domain name registered by the user terminal on the first blockchain in a local database; in response to a first domain name registration request sent by a first user terminal, the target network verifies whether the target domain name requested by the first user terminal to be registered on a second blockchain belongs to the domain name already registered by the first user terminal on the first blockchain according to the first user signature carried in the first domain name registration request and the local database; when it is determined that the target domain name belongs to the domain name already registered by the first user terminal on the first blockchain, the target network allows the first user terminal to register the target domain name on the second blockchain. In this way, the present application enables the same user to use the same decentralized domain name across blockchains, and can effectively improve the accuracy of user identity recognition during cross-chain interaction, which is beneficial to the development of cross-chain technology. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] To more clearly illustrate the technical solutions of the embodiments of the present application, the following will briefly introduce the drawings required for the embodiments. It should be understood that the following drawings only show some embodiments of the present application, and thus should not be regarded as limiting the scope. For those of ordinary skill in the art, other related drawings can be obtained based on these drawings without creative efforts.

[0023] Figure 1 Shows a schematic flowchart of a blockchain-based domain name registration method provided by an embodiment of the present application;

[0024] Figure 2 Shows a schematic flowchart of a method for obtaining node signatures of different nodes in a target network provided by an embodiment of the present application;

[0025] Figure 3 Shows a schematic flowchart of a method for registering a target domain name on a second blockchain provided by an embodiment of the present application;

[0026] Figure 4 It shows a schematic flowchart of the first method provided by the embodiments of the present application for verifying whether an aggregated signature meets the signature validity condition;

[0027] Figure 5 It shows a schematic flowchart of the second method provided by the embodiments of the present application for verifying whether an aggregated signature meets the signature validity condition;

[0028] Figure 6 It shows a schematic structural diagram of a blockchain-based domain name registration device provided by the embodiments of the present application;

[0029] Figure 7 It shows a schematic structural diagram of a blockchain-based domain name registration system provided by the embodiments of the present application;

[0030] Figure 8 It is a schematic structural diagram of an electronic device 800 provided by the embodiments of the present application. Detailed implementation manners

[0031] To make the objectives, technical solutions, and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present application. It should be understood that the accompanying drawings in the present application are only for the purposes of illustration and description, and are not used to limit the protection scope of the present application. In addition, it should be understood that the schematic drawings are not drawn to actual scale. The flowcharts used in the present application show the operations implemented according to some embodiments of the present application. It should be understood that the operations in the flowchart may not be implemented in sequence, and steps without a logical context relationship may be reversed in order or implemented simultaneously. In addition, those skilled in the art can add one or more other operations to the flowchart or remove one or more operations from the flowchart under the guidance of the content of the present application.

[0032] In addition, the described embodiments are only some embodiments of the present application, rather than all of the embodiments. The components of the embodiments of the present application described and illustrated in the accompanying drawings here can be arranged and designed in various different configurations. Therefore, the following detailed description of the embodiments of the present application provided in the accompanying drawings is not intended to limit the scope of the present application claimed, but only represents selected embodiments of the present application. All other embodiments obtained by those skilled in the art based on the embodiments of the present application without creative efforts fall within the protection scope of the present application.

[0033] It should be noted that the term "including" will be used in the embodiments of the present application to indicate the existence of the features stated hereinafter, but does not exclude the addition of other features.

[0034] It should be noted that the "domain name" and "target domain name" involved in the embodiments of the present application both belong to decentralized domain names (i.e., DID domain names); among them, in the field of blockchain, the standard DID identity identifier (i.e., decentralized identity identifier) of a user consists of three parts: a fixed prefix + a blockchain identifier + a custom suffix; the fixed prefix represents a fixed string, the blockchain identifier is determined according to the specific blockchain actually accessed by the user, and the DID domain name is equivalent to the custom suffix in the above standard DID identity identifier; that is to say, the "domain name" and "target domain name" involved in the embodiments of the present application are not equivalent to the user's DID identity identifier, but are equivalent to one of the components belonging to the custom suffix in the DID identity identifier.

[0035] Currently, in the field of blockchain, the existing DID (Decentralized Identity) domain name registration project parties are usually located on only one blockchain, so that the DID domain names registered by users on this blockchain cannot be used across chains.

[0036] Based on this, the embodiments of the present application provide a blockchain-based domain name registration method, device, equipment and storage medium, enabling the same user to use the same decentralized domain name across chains, effectively improving the accuracy of user identity recognition during cross-chain interaction, and being beneficial to the development of cross-chain technology.

[0037] Next, a blockchain-based domain name registration method, device, equipment and storage medium provided by the embodiments of the present application will be introduced in detail.

[0038] Refer to Figure 1 As shown Figure 1 shows a schematic flowchart of a blockchain-based domain name registration method provided by the embodiments of the present application. The domain name registration method includes steps S101 - S103; specifically:

[0039] S101, in response to any user terminal completing the registration of a domain name on the first blockchain, the target network stores the domain name registered by the user terminal on the first blockchain in the local database.

[0040] S102, in response to a first domain name registration request sent by the first user terminal, the target network verifies whether the target domain name requested by the first user terminal to be registered on the second blockchain belongs to the domain name already registered by the first user terminal on the first blockchain according to the first user signature carried in the first domain name registration request and the local database.

[0041] S103. When it is determined that the target domain name belongs to the domain names already registered by the first user terminal on the first blockchain, the target network allows the first user terminal to register the target domain name on the second blockchain.

[0042] In the domain name registration method based on blockchain provided in the embodiments of the present application, in response to any user terminal completing the registration of a domain name on the first blockchain, the target network stores the domain name registered by the user terminal on the first blockchain in the local database; in response to the first domain name registration request sent by the first user terminal, the target network verifies, according to the first user signature carried in the first domain name registration request and the local database, whether the target domain name requested by the first user terminal to be registered on the second blockchain belongs to the domain names already registered by the first user terminal on the first blockchain; when it is determined that the target domain name belongs to the domain names already registered by the first user terminal on the first blockchain, the target network allows the first user terminal to register the target domain name on the second blockchain. In this way, the present application enables the same user to use the same decentralized domain name across blockchains, and can effectively improve the accuracy of user identity recognition during cross-chain interaction, which is beneficial to the development of cross-chain technology.

[0043] In the embodiments of the present application, the above domain name registration method based on blockchain can be applied to a domain name registration system, which includes: a target network and multiple user terminals; wherein, each user terminal can first register a domain name on a benchmark blockchain (i.e., the above first blockchain) deployed with a target DID protocol (a DID protocol for implementing the domain name registration method provided in the embodiments of the present application). Based on the deployment of the target DID protocol, the target network can record and store (store in the above local database) the domain name registration events completed by each user terminal on the benchmark blockchain. When a user terminal wants to register the same domain name (i.e., the domain name already registered by the user terminal on the first blockchain) on a member blockchain (i.e., the above second blockchain) deployed with the same target DID protocol, the user terminal can send a domain name registration request (i.e., the above first domain name registration request) to the target network. In response to the received domain name registration request, when the target network determines that the domain name requested by the user terminal to be registered on the second blockchain is the domain name already registered by the user terminal on the first blockchain, it can allow the user terminal to register the same domain name on the second blockchain, so that the same user can use the same decentralized domain name across blockchains.

[0044] Taking the application to the above domain name registration system as an example, the following is an exemplary description of each step in the above domain name registration method based on blockchain provided in the embodiments of the present application:

[0045] S101. In response to any user terminal completing the registration of a domain name on the first blockchain, the target network stores the domain name registered by the user terminal on the first blockchain in its local database.

[0046] Here, the first blockchain represents the reference blockchain used by user terminals for domain name registration. In terms of underlying technical implementation, the project party implementing the cross-chain domain name registration service can select one blockchain from the existing multiple blockchains in advance as the reference blockchain (i.e., the above-mentioned first blockchain), and select other blockchains except the reference blockchain as member blockchains. At this time, the project party can deploy the target DID protocol (the DID protocol for implementing the domain name registration method provided in the embodiments of the present application) on the reference blockchain and each member blockchain simultaneously, so as to realize data communication between the reference blockchain, member blockchains, and the target network based on the deployment of the target DID protocol, enabling the target network to record domain name registration events occurring on the reference blockchain and / or member blockchains.

[0047] It should be noted that the above-mentioned first blockchain as the reference blockchain can be determined according to the actual development needs of the project party. As a preferred embodiment, Ethereum, which is relatively well-known in the blockchain field (with a wide user group and frequent domain name registration events), can be preferentially selected as the first blockchain; in addition, other blockchains except Ethereum (such as the polygon blockchain, etc.) can also be selected; the specific blockchain represented by the above-mentioned first blockchain is not limited in the embodiments of the present application.

[0048] Specifically, taking the first blockchain as Ethereum as an example, when user terminal a successfully registers the domain name Alice on Ethereum (i.e., the first blockchain), based on the deployment of the target DID protocol on Ethereum, Ethereum will, after the user's domain name registration is successful, package the registered domain name Alice and the registered blockchain address (i.e., the blockchain address corresponding to user terminal a on the first blockchain Ethereum) as a domain name registration event and send it to the target network, so that the target network can, in response to any user terminal completing the registration of a domain name on the first blockchain, store the domain name registered by the user terminal on the first blockchain in its local database.

[0049] It should be noted that the above-mentioned target network can be a weakly associated network (such as an Oracle network, an arbitration committee network, etc.), or a strongly associated network with more complex functions (such as a blockchain network); the specific network type corresponding to the above-mentioned target network is not limited in the embodiments of the present application.

[0050] S102. The target network responds to the first domain name registration request sent by the first user terminal, and based on the first user signature carried in the first domain name registration request and the local database, verifies whether the target domain name requested by the first user terminal to be registered on the second blockchain belongs to the domain names already registered by the first user terminal on the first blockchain.

[0051] Here, the second blockchain is the member blockchain described in step S101 above, that is, the second blockchain represents a member blockchain that deploys the same target DID protocol as the first blockchain.

[0052] Here, the above first domain name registration request represents a domain name registration request for registering a target domain name on the second blockchain. At this time, to verify whether the target domain name requested by the first user terminal to be registered is a domain name that the first user terminal has already registered on the first blockchain (equivalent to verifying whether the first user terminal has the registration authority to register the target domain name on the second blockchain), the above first domain name registration request at least includes: the target domain name requested to be registered, the second blockchain identifier (used to indicate the request to register the target domain name on the second blockchain), the second blockchain address corresponding to the first user terminal on the second blockchain (used to clarify the specific blockchain address for registering the target domain name on the second blockchain), the first blockchain address corresponding to the first user terminal on the first blockchain, and the first user signature; among them, the first user signature can be determined according to the first blockchain address.

[0053] Specifically, combining the relevant description content in step S101 above, in the local database within the target network, all the domain names already registered by each user terminal on the first blockchain are stored; on this basis, after the target network receives the above first domain name registration request sent by the first user terminal, it can first verify the identity of the first user terminal according to the first blockchain address and the first user signature in the first domain name registration request; after the verification is passed, the target network can obtain from the local database the domain names already registered by the first user terminal on the first blockchain; and then verify whether the target domain name requested by the first user terminal to be registered on the second blockchain belongs to the domain names already registered by the first user terminal on the first blockchain according to the obtained all domain names.

[0054] S103. When it is determined that the target domain name belongs to the domain names already registered by the first user terminal on the first blockchain, the target network allows the first user terminal to register the target domain name on the second blockchain.

[0055] Here, when it is determined that the target domain name belongs to the domain names registered by the first user terminal on the first blockchain, the target network determines that the first user terminal has the permission to register the target domain name on the second blockchain, and allows the first user terminal to send a domain name registration request for the target domain name to the second blockchain, so as to support the first user terminal to register the same target domain name on the second blockchain as on the first blockchain according to the second blockchain address.

[0056] On this basis, since the local database also stores the historical domain names registered by other user terminals (user terminals other than the first user terminal) on the first blockchain, therefore, as an optional implementation manner, when it is determined that the above-mentioned target domain name does not belong to the domain names registered by the first user terminal on the first blockchain, it is also possible to verify whether the target domain name has been registered by other user terminals on the first blockchain according to the domain names registered by each user terminal on the first blockchain stored in the local database; when it is determined that the target domain name has been registered by other user terminals on the first blockchain (that is, the target domain name appears repeatedly with the domain names registered by other user terminals stored in the local database), the target network can reject the first domain name registration request sent by the first user terminal, and reserve the permission for the user terminal that has originally registered the target domain name on the first blockchain to register the target domain name on the second blockchain in the future, reducing the phenomenon of cross-chain domain name squatting for the same domain name, so as to effectively improve the accuracy of user identity recognition during cross-chain interaction, which is beneficial to the development of cross-chain technology.

[0057] Regarding the domain name registration method described in the above steps S101 - S103, it should be noted that the above domain name registration method provided by the embodiments of the present application is mainly to solve the problem of user terminals registering the same domain name on different blockchains; on this basis, for the problem of different user terminals registering domain names on the same blockchain, according to the existing domain name registration method, when a user terminal registers a domain name, it can search for the domain name to be registered on the blockchain. When the search result shows that the domain name has been registered by other user terminals, the user terminal naturally cannot register the domain name on this blockchain; that is, in the embodiments of the present application, when the first user terminal requests to register the target domain name on the second blockchain, the target network does not involve searching for whether the target domain name appears repeatedly among all the domain names already registered on the second blockchain. This search step can be performed by the target DID protocol deployed on the second blockchain for implementing domain name registration services to search and verify when the first user terminal sends a domain name registration request for the target domain name to the second blockchain.

[0058] The following will respectively describe in detail the specific implementation processes of the above steps in the embodiments of the present application:

[0059] For the domain name registration method described in the above steps S101 - S103, except for the two situations that occur in step S103 (one situation is that the target domain name is a domain name registered by the first user terminal on the first blockchain, and the other situation is that the target domain name is a domain name registered by other user terminals on the first blockchain), in the actual application process, considering that the target domain name may also be a brand - new domain name that has not been registered by any user terminal on the first blockchain. In this case, the embodiments of the present application also provide the following two different optional implementation manners according to the specific network type of the target network (that is, the above - mentioned target network can be a weakly associated network or a strongly associated network). Specifically:

[0060] Optional implementation manner 1: When the target network belongs to a strongly associated network and the target domain name does not belong to the domain name already registered by the first user terminal on the first blockchain, the first user terminal can be continuously verified whether it can register the target domain name on the second blockchain according to the manner described in the following steps a1 - a2. Specifically:

[0061] Step a1: When it is determined that the target domain name does not belong to the domain name already registered by the first user terminal on the first blockchain, verify whether the target domain name has not been registered on the first blockchain according to the domain names registered by each user terminal on the first blockchain stored in the local database.

[0062] Here, combined with the relevant description content in step S101 above, all domain names successfully registered by each user terminal on the first blockchain are stored in the local database of the target network. Based on this, after it is determined that the target domain name has not been registered by the first user terminal on the first blockchain, the target network can verify whether the target domain name has been registered by other user terminals (that is, user terminals other than the first user terminal) on the first blockchain according to the domain names registered by other user terminals stored in the local data, so as to determine whether the first user terminal has the permission to register the target domain name on the second blockchain according to the verification result.

[0063] Step a2: When it is determined that the target domain name has not been registered on the first blockchain, the target network allows the first user terminal to register the target domain name on the second blockchain.

[0064] Specifically, when it is determined that the target domain name has not been registered on the first blockchain, the target network can determine that there is no conflict between the target domain name and the domain names already registered by other user terminals on the first blockchain. Therefore, the first user terminal can be allowed to register the target domain name on the second blockchain.

[0065] Here, as an optional embodiment, after the first user terminal completes the registration of the target domain name on the second blockchain, since the target DID protocol is also deployed on the second blockchain, therefore, similar to the first blockchain, the second blockchain can also send the domain name registration event of the first user terminal for the target domain name to the target network. At this time, in response to the first user terminal completing the registration of the target domain name on the second blockchain, the target network can store the target domain name registered by the first user terminal on the second blockchain in its local database, so that when other user terminals want to register the same target domain name on the first blockchain, the target network can reject the other user terminals that try to register first, and reserve the registration permission of the first user terminal for the target domain name on the first blockchain in the future, enabling the same user to use the same decentralized domain name across different blockchains.

[0066] Specifically, in the specific implementation process of the above optional implementation manner 1, since the target network can receive domain name registration events sent from different blockchains (such as the above-mentioned first blockchain and the second blockchain) at the same time (that is, both the first blockchain and the second blockchain can send the domain name registration event of a user terminal for a certain domain name to the target network), therefore, in a relatively extreme case, due to the fact that there is usually a certain time delay in information transmission, the target network may receive domain name registration events of different user terminals for the same domain name on different blockchains within a very short time interval (the time difference is less than the preset threshold) (for example, within a short period of time, the target network simultaneously receives the domain name registration event A1 of user terminal A for the domain name Bob on the first blockchain and the domain name registration event B1 of user terminal B for the domain name Bob on the second blockchain). At this time, based on the characteristic that the strongly associated network can participate in consensus, taking the simultaneous receipt of the above domain name registration events A1 and B1 within a short time as an example, the following steps b1 - b3 can be used to specifically solve the above extreme situation and maintain the normal operation of the target network:

[0067] Step b1: Based on the predetermined consensus rules, initiate a consensus for the above domain name registration events A1 and B1 within the target network, and obtain the number of nodes a in the target network that approve the domain name registration event A1 and the number of nodes b that approve the domain name registration event B1.

[0068] Step b2: From the obtained number of nodes a and number of nodes b, determine the target number of nodes whose proportion in the total number of all nodes (that is, all nodes in the target network) is greater than or equal to the target threshold.

[0069] Step b3: Store the domain name registration event corresponding to the target number of nodes in the local database.

[0070] Exemplary illustration, taking the number of all nodes in the target network as N and the above target threshold as For example, if it is determined that the proportion of the number of nodes a in the total number of nodes N is greater than Then it can be determined that the above domain name registration event A1 passes the consensus, and the domain name registration event A1 is stored in the local database. At this time, the target network can also send a prompt message for the domain name registration event A1 to the first blockchain and the second blockchain respectively, to prompt the first blockchain to allow the user terminal A to register the domain name Bob, and to prompt the second blockchain to reject the user terminal B to register the domain name Bob.

[0071] Optional implementation method 2: When the target network belongs to a weakly associated network, considering that a weakly associated network cannot participate in consensus like a strongly associated network (such as a blockchain network), at this time, if it can receive domain name registration events sent from different blockchains simultaneously like the above strongly associated network, the weakly associated network is prone to fork problems (that is, it cannot obtain a unified result for the specific domain name registration event allowed to pass) due to receiving multiple similar domain name registration events (such as domain name registration events for the same domain name by different user terminals on different blockchains) within a similar time. Based on this, different from the method described in the above optional implementation method 1, when the target domain name does not belong to the domain name already registered by the first user terminal on the first blockchain, the following steps c1 - c2 can be used to continue to verify whether the first user terminal can register the target domain name on the second blockchain. Specifically:

[0072] Step c1: When it is determined that the target domain name does not belong to the domain name already registered by the first user terminal on the first blockchain, verify whether the target domain name has not been registered on the first blockchain according to the domain names registered by each user terminal on the first blockchain stored in the local database.

[0073] Here, the specific verification method of step c1 is the same as step a1 above, and the repeated parts will not be elaborated here.

[0074] Step c2: When it is determined that the target domain name has not been registered on the first blockchain, the target network sends a target prompt message to the first user terminal.

[0075] Here, the above target prompt message is used to prompt the first user terminal to preferentially complete the registration of the target domain name on the first blockchain. That is, the first user terminal can confirm that it can currently register the target domain name on the first blockchain according to the received target prompt message, so that after the first user terminal completes the registration of the target domain name on the first blockchain, it can continue to complete the registration of the target domain name on the second blockchain according to the domain name registration method described in the above steps S101 - S103.

[0076] On this basis, regarding the weakly associated network in the above optional implementation 2, it should be noted that when the above target network belongs to a weakly associated network, according to the specific implementation process of the above optional implementation 2, the target network only needs to be able to record and store the domain name registration events occurring on the first blockchain online, and does not need to participate in consensus; at this time, the target network only needs to ensure that: the number of nodes in the target network is determined and the nodes can identify their respective node identities clearly to enable inter-node communication; for example, the target network can specifically be an Oracle network, an arbitration committee network, etc.; for the specific network corresponding to the above weakly associated network, the embodiments of the present application also do not make any limitations.

[0077] Regarding the domain name registration method described in the above steps S101 - S103, combining the relevant description content at step S101 above, it can be seen that in terms of underlying technical implementation, the data transmission between the first blockchain, the target network, and the second blockchain is based on the same target DID protocol deployed by the same project party on the first blockchain and the second blockchain respectively; on this basis, considering that the first blockchain can represent the reference blockchain (equivalent to the number of user terminals that first register domain names on the first blockchain being higher than the number of user terminals that first register domain names on member blockchains such as the second blockchain), the specific contract content of the target DID protocol deployed by the project party on the first blockchain and the second blockchain can be different; for example, in the target DID protocol deployed on the first blockchain, only the functions related to the registration and query of domain names in the first blockchain can be retained (equivalent to enabling user terminals to query registered domain names on the first blockchain, so as to select unregistered domain names for registration), while in the target DID protocol deployed on the second blockchain, in addition to the above functions related to registration and query, the signature verification function can be further retained to verify the validity of the aggregated signature sent by the target network to the first user terminal (equivalent to a signature certificate proving that the first user terminal has the permission to register the target domain name on the second blockchain) after the target network allows the first user terminal to register the target domain name, effectively improving the accuracy of user identity recognition during cross-chain interaction.

[0078] Based on this, in an optional implementation Figure 2 shows a schematic flow diagram of a method for obtaining node signatures of different nodes in the target network provided by the embodiments of the present application, as Figure 2 shown, after step S103 is executed, the method further includes steps S201 - S202; specifically:

[0079] S201, the target network extracts nodes greater than or equal to a first preset number from all nodes in the network as nodes to be signed.

[0080] Here, there can be N nodes in the target network, and the specific number of nodes included in the target network is not limited in any way in the embodiments of the present application.

[0081] Here, the first preset quantity can be set according to actual signature requirements. For example, the first preset quantity can be (i.e., 50% of all nodes in the target network), and the first preset quantity can also be Regarding the specific value of the above first preset quantity, the embodiments of the present application do not make any limitations.

[0082] S202, the target network obtains the node signature of each to-be-signed node for the target registration event, and sends each obtained node signature to the first user terminal.

[0083] Here, the target registration event represents the registration event of the first user terminal registering the target domain name on the second blockchain.

[0084] Exemplarily, taking the target registration event as (B address, Alice, solana) as an example; where the address B represents the second blockchain address corresponding to the first user terminal on the second blockchain, Alice represents the target domain name to be registered, and solana represents the blockchain identifier corresponding to the second blockchain. At this time, the target network can obtain the node signature of each to-be-signed node for the above target registration event.

[0085] It should be noted that the embodiments of the present application do not make any limitations on the specific signature algorithm used by each to-be-signed node.

[0086] In the embodiments of the present application, after obtaining the node signatures of different nodes in the target network, in an alternative implementation Figure 3 shows a schematic flowchart of a method for registering a target domain name on the second blockchain provided by the embodiments of the present application. As Figure 3 shown, based on the obtained above node signatures, the first user terminal can register the target domain name on the second blockchain according to the method described in the following steps S301 - S303; specifically:

[0087] S301, the first user terminal sends a second domain name registration request to the second blockchain.

[0088] Here, the second domain name registration request includes: the second blockchain address corresponding to the first user terminal on the second blockchain, the target domain name, the blockchain identifier of the second blockchain, and the aggregated signature; where the parties participating in the aggregated signature are the nodes in the target network.

[0089] S302. The second blockchain, in response to the second domain name registration request sent by the first user terminal, verifies whether the aggregated signature meets the signature validity condition according to multiple network node signatures included in the aggregated signature.

[0090] Here, the participants in the aggregated signature are nodes within the target network. Therefore, the aggregated signature includes multiple network node signatures. In the specific implementation process, there may also be network node signatures corresponding to nodes outside the target network in the aggregated signature (such as forged node signatures, etc.). Therefore, after receiving the second domain name registration request sent by the first user terminal, the second blockchain also needs to verify the aggregated signature in the second domain name registration request according to the definition of the validity of the aggregated signature in the target DID protocol (i.e., the above signature validity condition), so as to register the target domain name for the registration request of the first user terminal on the basis of determining that the aggregated signature meets the signature validity condition.

[0091] S303. When it is determined that the aggregated signature meets the signature validity condition, it is determined that the first user terminal has completed the registration of the target domain name on the second blockchain.

[0092] Here, when performing the above steps S302 - S303, the embodiments of the present application provide the following two optional signature validity condition verification methods:

[0093] In the first optional implementation manner, Figure 4 shows a schematic flowchart of the first method provided by the embodiments of the present application for verifying whether the aggregated signature meets the signature validity condition. As Figure 4 shown, when performing the above steps S302 - S303, the method further includes steps S401 - S402; specifically:

[0094] S401. Determine the number of first node signatures whose signers belong to nodes within the target network from the multiple network node signatures.

[0095] Here, in the first optional implementation manner, when the target DID protocol stipulates that as long as the signer belongs to a node within the target network, it is a valid signature, the second blockchain can first determine the number of first node signatures whose signers belong to nodes within the target network from the multiple network node signatures included in the aggregated signature, so as to determine that the aggregated signature is valid when the number of the determined first node signatures reaches a credible number (i.e., greater than or equal to a preset number).

[0096] S402. When it is determined that the number of the first node signatures is greater than or equal to a second preset number, it is determined that the aggregated signature meets the signature validity condition.

[0097] It should be noted that the second preset quantity can also be set according to actual verification requirements. For example, the second preset quantity can be n, or the second preset quantity can be m. For the specific value of the above-mentioned second preset quantity, the embodiments of the present application do not make any limitations either.

[0098] In the second alternative implementation manner, Figure 5 FIG. shows a schematic flowchart of the second method for verifying whether an aggregated signature meets the signature validity condition provided by the embodiments of the present application. As Figure 5 shown, when performing the above steps S302-S303, the method further includes steps S501-S502; specifically:

[0099] S501, obtain the number of second node signatures whose signers belong to valid signature nodes within the target network from the multiple network node signatures.

[0100] Here, in the second alternative implementation manner, different from the above step S401, the target DID protocol may also stipulate that only part of the valid signature nodes within the target network whose signers belong to are valid signatures; at this time, the valid signature nodes may be part of the target nodes within the target network. For the specific number of the valid signature nodes, the embodiments of the present application do not make any limitations.

[0101] S502, when determining that the number of the second node signatures is greater than or equal to a third preset quantity, determine that the aggregated signature meets the signature validity condition.

[0102] It should be noted that the third preset quantity can also be set according to actual verification requirements. For example, the third preset quantity can be n, or the third preset quantity can be m. For the specific value of the above-mentioned third preset quantity, the embodiments of the present application do not make any limitations either.

[0103] Based on the above-mentioned blockchain-based domain name registration method provided by the embodiments of the present application, in response to any user terminal completing the registration of a domain name on the first blockchain, the target network stores the domain name registered by the user terminal on the first blockchain in the local database; in response to a first domain name registration request sent by the first user terminal, the target network verifies whether the target domain name requested by the first user terminal to be registered on the second blockchain belongs to the domain name already registered by the first user terminal on the first blockchain according to the first user signature carried in the first domain name registration request and the local database; when determining that the target domain name belongs to the domain name already registered by the first user terminal on the first blockchain, the target network allows the first user terminal to register the target domain name on the second blockchain. In this way, the present application enables the same user to use the same decentralized domain name across blockchains, and can effectively improve the accuracy of user identity recognition during cross-chain interaction, which is beneficial to the development of cross-chain technology.

[0104] Based on the same inventive concept, this application also provides a domain name registration device corresponding to the above-mentioned blockchain-based domain name registration method. Since the principle of solving problems by the domain name registration device in the embodiments of this application is similar to that of the above-mentioned blockchain-based domain name registration method in the embodiments of this application, the implementation of the domain name registration device can refer to the implementation of the above-mentioned domain name registration method, and the repeated parts will not be elaborated.

[0105] Referring to Figure 6 as shown, Figure 6 The figure shows a schematic structural diagram of a blockchain-based domain name registration device provided by an embodiment of this application. The domain name registration device includes:

[0106] A recording module 601, configured to store, in a local database, the domain name registered by the user terminal on the first blockchain in response to any user terminal completing the registration of the domain name on the first blockchain through the target network;

[0107] A first verification module 602, configured to verify, in response to a first domain name registration request sent by a first user terminal through the target network, whether the target domain name requested by the first user terminal to be registered on the second blockchain belongs to the domain name already registered by the first user terminal on the first blockchain according to the first user signature carried in the first domain name registration request and the local database; wherein, the first user signature is determined according to the first blockchain address corresponding to the first user terminal on the first blockchain;

[0108] A second verification module 603, configured to allow the first user terminal to register the target domain name on the second blockchain through the target network when it is determined that the target domain name belongs to the domain name already registered by the first user terminal on the first blockchain.

[0109] In an optional implementation manner, when it is determined that the target domain name belongs to the domain name already registered by the first user terminal on the first blockchain, the second verification module 603 is further configured to:

[0110] Extract, from all nodes in the network through the target network, nodes greater than or equal to a first preset number as nodes to be signed;

[0111] Obtain, through the target network, the node signature of each of the nodes to be signed for the target registration event, and send each of the obtained node signatures to the first user terminal; wherein, the target registration event represents the registration event of the first user terminal registering the target domain name on the second blockchain.

[0112] In an alternative embodiment, the domain name registration device further includes: a registration module; wherein, the registration module is configured to:

[0113] Send a second domain name registration request to the second blockchain through the first user terminal; wherein, the second domain name registration request includes: the second blockchain address corresponding to the first user terminal on the second blockchain, the target domain name, the blockchain identifier of the second blockchain, and an aggregated signature;

[0114] Respond to the second domain name registration request sent by the first user terminal through the second blockchain, and verify whether the aggregated signature meets the signature validity condition according to the multiple network node signatures included in the aggregated signature;

[0115] When it is determined that the aggregated signature meets the signature validity condition, determine that the first user terminal has completed the registration of the target domain name on the second blockchain.

[0116] In an alternative embodiment, when verifying whether the aggregated signature meets the signature validity condition according to the multiple network node signatures included in the aggregated signature, the registration module is configured to:

[0117] Determine the number of the first node signatures of the signature parties belonging to the nodes within the target network from the multiple network node signatures;

[0118] When it is determined that the number of the first node signatures is greater than or equal to a second preset number, determine that the aggregated signature meets the signature validity condition.

[0119] In an alternative embodiment, when verifying whether the aggregated signature meets the signature validity condition according to the multiple network node signatures included in the aggregated signature, the registration module is configured to:

[0120] Obtain the number of the second node signatures of the signature parties belonging to the valid signature nodes within the target network from the multiple network node signatures;

[0121] When it is determined that the number of the second node signatures is greater than or equal to a third preset number, determine that the aggregated signature meets the signature validity condition.

[0122] In an alternative embodiment, the domain name registration device further includes: a third verification module; wherein, when the target network belongs to a strongly associated network, the third verification module is configured to:

[0123] When it is determined that the target domain name does not belong to the domain names registered by the first user terminal on the first blockchain, verify whether the target domain name has not been registered on the first blockchain according to the domain names registered by each user terminal stored in the local database on the first blockchain;

[0124] When it is determined that the target domain name has not been registered on the first blockchain, allow the first user terminal to register the target domain name on the second blockchain through the target network.

[0125] In an optional implementation manner, after allowing the first user terminal to register the target domain name on the second blockchain through the target network, the third verification module is further configured to:

[0126] Responding to the first user terminal completing the registration of the target domain name on the second blockchain through the target network, store the target domain name registered by the first user terminal on the second blockchain in the local database.

[0127] In an optional implementation manner, when the target network belongs to a weakly associated network, the third verification module is configured to:

[0128] When it is determined that the target domain name does not belong to the domain names registered by the first user terminal on the first blockchain, verify whether the target domain name has not been registered on the first blockchain according to the domain names registered by each user terminal stored in the local database on the first blockchain;

[0129] When it is determined that the target domain name has not been registered on the first blockchain, the target network sends target prompt information to the first user terminal; wherein, the target prompt information is used to prompt the first user terminal to preferentially complete the registration of the target domain name on the first blockchain.

[0130] In an optional implementation manner, the third verification module is further configured to:

[0131] When it is determined that the target domain name does not belong to the domain names registered by the first user terminal on the first blockchain, verify whether the target domain name has been registered by other user terminals on the first blockchain according to the domain names registered by each user terminal stored in the local database on the first blockchain;

[0132] When it is determined that the target domain name has been registered by the other user terminals on the first blockchain, the target network rejects the first user terminal from registering the target domain name on the second blockchain.

[0133] Based on the above-mentioned blockchain-based domain name registration device provided by the embodiments of the present application, when the target network responds to any user terminal completing the registration of a domain name on the first blockchain, it stores the domain name registered by the user terminal on the first blockchain in the local database; when the target network responds to a first domain name registration request sent by the first user terminal, it verifies whether the target domain name requested by the first user terminal to be registered on the second blockchain belongs to the domain name already registered by the first user terminal on the first blockchain according to the first user signature carried in the first domain name registration request and the local database; when it is determined that the target domain name belongs to the domain name already registered by the first user terminal on the first blockchain, the target network allows the first user terminal to register the target domain name on the second blockchain. In this way, the present application enables the same user to use the same decentralized domain name across blockchains, and can effectively improve the accuracy of user identity recognition during cross-chain interaction, which is beneficial to the development of cross-chain technology.

[0134] Based on the same inventive concept, the present application also provides a domain name registration system corresponding to the above-mentioned blockchain-based domain name registration method. Since the principle of solving problems by the domain name registration system in the embodiments of the present application is similar to that of the above-mentioned domain name registration method in the embodiments of the present application, the implementation of the domain name registration system can refer to the implementation of the above-mentioned domain name registration method, and the repeated parts will not be described again.

[0135] Refer to Figure 7 as shown in Figure 7 FIG. shows a schematic structural diagram of a blockchain-based domain name registration system provided by an embodiment of the present application. The domain name registration system includes: a target network 700 and multiple user terminals 701; wherein, the target network 700 is used for:

[0136] When responding to any user terminal 701 completing the registration of a domain name on the first blockchain, store the domain name registered by the user terminal 701 on the first blockchain in the local database;

[0137] When responding to a first domain name registration request sent by the first user terminal 710, verify whether the target domain name requested by the first user terminal 710 to be registered on the second blockchain belongs to the domain name already registered by the first user terminal 710 on the first blockchain according to the first user signature carried in the first domain name registration request and the local database; wherein, the first user signature is determined according to the first blockchain address corresponding to the first user terminal 710 on the first blockchain;

[0138] When it is determined that the target domain name belongs to the domain name already registered by the first user terminal 710 on the first blockchain, allow the first user terminal 710 to register the target domain name on the second blockchain.

[0139] In an alternative implementation, when it is determined that the target domain name belongs to the domain names registered by the first user terminal on the first blockchain, the target network 700 is further configured to:

[0140] Select, from all nodes in the network, a number of nodes greater than or equal to a first preset number as nodes to be signed;

[0141] Obtain the node signature of each node to be signed for the target registration event, and send each obtained node signature to the first user terminal 710; wherein, the target registration event represents the registration event of the first user terminal 710 registering the target domain name on the second blockchain.

[0142] In an alternative implementation, after the target network 700 allows the first user terminal 710 to register the target domain name on the second blockchain, the first user terminal 710 is configured to register the target domain name on the second blockchain by the following method:

[0143] The first user terminal 710 is configured to send a second domain name registration request to the second blockchain; wherein, the second domain name registration request includes: the second blockchain address corresponding to the first user terminal 710 on the second blockchain, the target domain name, the blockchain identifier of the second blockchain, and the aggregated signature.

[0144] The second blockchain is configured to, in response to the second domain name registration request sent by the first user terminal 710, verify whether the aggregated signature meets the signature validity condition according to the multiple network node signatures included in the aggregated signature.

[0145] When it is determined that the aggregated signature meets the signature validity condition, it is determined that the first user terminal 710 has completed the registration of the target domain name on the second blockchain.

[0146] In an alternative implementation, when verifying whether the aggregated signature meets the signature validity condition according to the multiple network node signatures included in the aggregated signature, the second blockchain is configured to:

[0147] Determine the number of first node signatures whose signers belong to the nodes in the target network from the multiple network node signatures.

[0148] When it is determined that the number of the first node signatures is greater than or equal to a second preset number, it is determined that the aggregated signature meets the signature validity condition.

[0149] In an alternative implementation, when verifying whether the aggregated signature meets the signature validity condition according to the multiple network node signatures included in the aggregated signature, the second blockchain is further configured to:

[0150] Obtain the number of second node signatures whose signers belong to valid signature nodes within the target network from the multiple network node signatures;

[0151] When it is determined that the number of the second node signatures is greater than or equal to a third preset number, determine that the aggregated signature meets the signature validity condition.

[0152] In an alternative embodiment, when the target network 700 belongs to a strongly associated network, the target network 700 is further configured to:

[0153] When it is determined that the target domain name does not belong to the domain names registered by the first user terminal 710 on the first blockchain, verify whether the target domain name has not been registered on the first blockchain according to the domain names registered by each user terminal 701 stored in the local database;

[0154] When it is determined that the target domain name has not been registered on the first blockchain, allow the first user terminal 710 to register the target domain name on the second blockchain.

[0155] In an alternative embodiment, after allowing the first user terminal 710 to register the target domain name on the second blockchain, the target network 700 is further configured to:

[0156] In response to the first user terminal 710 completing the registration of the target domain name on the second blockchain, store the target domain name registered by the first user terminal 710 on the second blockchain in the local database.

[0157] In an alternative embodiment, when the target network 700 belongs to a weakly associated network, the target network 700 is further configured to:

[0158] When it is determined that the target domain name does not belong to the domain names registered by the first user terminal 710 on the first blockchain, verify whether the target domain name has not been registered on the first blockchain according to the domain names registered by each user terminal 701 stored in the local database;

[0159] When it is determined that the target domain name has not been registered on the first blockchain, the target network 700 sends a target prompt message to the first user terminal 710; wherein, the target prompt message is used to prompt the first user terminal 710 to preferentially complete the registration of the target domain name on the first blockchain.

[0160] In an alternative embodiment, the target network 700 is further configured to:

[0161] When it is determined that the target domain name does not belong to the domain names registered by the first user terminal 710 on the first blockchain, verify whether the target domain name has been registered by other user terminals on the first blockchain according to the domain names registered by each user terminal stored in the local database;

[0162] When it is determined that the target domain name has been registered by the other user terminals on the first blockchain, the target network 700 rejects the first user terminal 710 from registering the target domain name on the second blockchain.

[0163] Based on the above blockchain-based domain name registration system provided by the embodiments of the present application, when the target network responds to any user terminal completing the registration of a domain name on the first blockchain, it stores the domain name registered by the user terminal on the first blockchain in the local database; when the target network responds to the first domain name registration request sent by the first user terminal, it verifies whether the target domain name requested by the first user terminal to be registered on the second blockchain belongs to the domain names registered by the first user terminal on the first blockchain according to the first user signature carried in the first domain name registration request and the local database; when it is determined that the target domain name belongs to the domain names registered by the first user terminal on the first blockchain, the target network allows the first user terminal to register the target domain name on the second blockchain. In this way, the present application enables the same user to use the same decentralized domain name across blockchains, which can effectively improve the accuracy of user identity recognition during cross-chain interaction and is beneficial to the development of cross-chain technology.

[0164] Based on the same inventive concept, Figure 8 FIG. is a schematic structural diagram of an electronic device 800 provided by an embodiment of the present application, including: a processor 801, a memory 802, and a bus 803. The memory 802 stores machine-readable instructions executable by the processor 801. When the electronic device 800 runs a blockchain-based domain name registration method as in the embodiment, the processor 801 communicates with the memory 802 through the bus 803, and the processor 801 executes the machine-readable instructions. Among them, when the processor 801 executes the machine-readable instructions, the following steps are implemented, specifically:

[0165] When the target network responds to any user terminal completing the registration of a domain name on the first blockchain, store the domain name registered by the user terminal on the first blockchain in the local database;

[0166] The target network responds to a first domain name registration request sent by a first user terminal, and verifies whether the target domain name requested by the first user terminal to be registered on a second blockchain belongs to the domain names already registered by the first user terminal on a first blockchain according to the first user signature carried in the first domain name registration request and the local database; wherein, the first user signature is determined according to the first blockchain address corresponding to the first user terminal on the first blockchain;

[0167] When it is determined that the target domain name belongs to the domain names already registered by the first user terminal on the first blockchain, the target network allows the first user terminal to register the target domain name on the second blockchain.

[0168] In an optional implementation manner, when it is determined that the target domain name belongs to the domain names already registered by the first user terminal on the first blockchain, the processor 801 is further configured to:

[0169] Extract, from all nodes in the network through the target network, nodes greater than or equal to a first preset number as nodes to be signed;

[0170] Obtain, through the target network, the node signatures of each of the nodes to be signed for a target registration event, and send each of the obtained node signatures to the first user terminal; wherein, the target registration event represents the registration event of the first user terminal registering the target domain name on the second blockchain.

[0171] In an optional implementation manner, the processor 801 is further configured to:

[0172] Send a second domain name registration request to the second blockchain through the first user terminal; wherein, the second domain name registration request includes: the second blockchain address corresponding to the first user terminal on the second blockchain, the target domain name, the blockchain identifier of the second blockchain, and an aggregated signature;

[0173] The second blockchain responds to the second domain name registration request sent by the first user terminal, and verifies whether the aggregated signature meets the signature validity condition according to the multiple network node signatures included in the aggregated signature;

[0174] When it is determined that the aggregated signature meets the signature validity condition, it is determined that the first user terminal has completed the registration of the target domain name on the second blockchain.

[0175] In an optional implementation manner, when verifying whether the aggregated signature meets the signature validity condition according to the multiple network node signatures included in the aggregated signature, the processor 801 is configured to:

[0176] Determine the number of the first node signatures whose signers belong to the nodes within the target network from the multiple network node signatures;

[0177] When it is determined that the number of the first node signatures is greater than or equal to a second preset number, determine that the aggregated signature meets the signature validity condition.

[0178] In an alternative embodiment, when verifying whether the aggregated signature meets the signature validity condition according to the multiple network node signatures included in the aggregated signature, the processor 801 is configured to:

[0179] Obtain the number of the second node signatures whose signers belong to the valid signature nodes within the target network from the multiple network node signatures;

[0180] When it is determined that the number of the second node signatures is greater than or equal to a third preset number, determine that the aggregated signature meets the signature validity condition.

[0181] In an alternative embodiment, when the target network belongs to a strongly associated network, the processor 801 is further configured to:

[0182] When it is determined that the target domain name does not belong to the domain names registered by the first user terminal on the first blockchain, verify whether the target domain name has not been registered on the first blockchain according to the domain names registered by each user terminal stored in the local database on the first blockchain;

[0183] When it is determined that the target domain name has not been registered on the first blockchain, allow the first user terminal to register the target domain name on the second blockchain through the target network.

[0184] In an alternative embodiment, after allowing the first user terminal to register the target domain name on the second blockchain through the target network, the processor 801 is further configured to:

[0185] Responding to the first user terminal completing the registration of the target domain name on the second blockchain through the target network, store the target domain name registered by the first user terminal on the second blockchain into the local database.

[0186] In an alternative embodiment, when the target network belongs to a weakly associated network, the processor 801 is further configured to:

[0187] When it is determined that the target domain name does not belong to the domain names registered by the first user terminal on the first blockchain, verify whether the target domain name has not been registered on the first blockchain according to the domain names registered by each user terminal stored in the local database on the first blockchain;

[0188] When it is determined that the target domain name has not been registered on the first blockchain, the target network sends a target prompt message to the first user terminal; wherein, the target prompt message is used to prompt the first user terminal to preferentially complete the registration of the target domain name on the first blockchain.

[0189] In an alternative embodiment, the processor 801 is further configured to:

[0190] When it is determined that the target domain name does not belong to the domain names registered by the first user terminal on the first blockchain, verify whether the target domain name has been registered by other user terminals on the first blockchain according to the domain names registered by each user terminal stored in the local database on the first blockchain;

[0191] When it is determined that the target domain name has been registered by the other user terminals on the first blockchain, the target network rejects the first user terminal from registering the target domain name on the second blockchain.

[0192] Based on the above electronic device 800 provided in the embodiments of the present application, when the target network responds to the completion of the registration of a domain name by any user terminal on the first blockchain, it stores the domain name registered by the user terminal on the first blockchain in the local database; when the target network responds to the first domain name registration request sent by the first user terminal, it verifies whether the target domain name requested by the first user terminal to be registered on the second blockchain belongs to the domain names registered by the first user terminal on the first blockchain according to the first user signature carried in the first domain name registration request and the local database; when it is determined that the target domain name belongs to the domain names registered by the first user terminal on the first blockchain, the target network allows the first user terminal to register the target domain name on the second blockchain. In this way, the present application enables the same user to use the same decentralized domain name across blockchains, and can effectively improve the accuracy of user identity recognition during cross-chain interaction, which is beneficial to the development of cross-chain technology.

[0193] Based on the same inventive concept, an embodiment of the present application further provides a computer-readable storage medium, on which a computer program is stored, and when the computer program is run by a processor, the processor executes the following steps:

[0194] Upon the target network storing the domain name registered by any user terminal on the first blockchain into the local database in response to the completion of the domain name registration on the first blockchain by the user terminal;

[0195] Upon the target network receiving a first domain name registration request sent by a first user terminal, verifying, based on the first user signature carried in the first domain name registration request and the local database, whether the target domain name requested by the first user terminal to be registered on the second blockchain belongs to the domain name already registered by the first user terminal on the first blockchain; wherein the first user signature is determined according to the first blockchain address corresponding to the first user terminal on the first blockchain;

[0196] When it is determined that the target domain name belongs to the domain name already registered by the first user terminal on the first blockchain, allowing, through the target network, the first user terminal to register the target domain name on the second blockchain.

[0197] In an alternative embodiment, when it is determined that the target domain name belongs to the domain name already registered by the first user terminal on the first blockchain, the processor is further configured to:

[0198] Extracting, from all nodes within the network through the target network, nodes greater than or equal to a first preset number as nodes to be signed;

[0199] Obtaining, through the target network, the node signature of each of the nodes to be signed for the target registration event, and sending each of the obtained node signatures to the first user terminal; wherein the target registration event represents the registration event of the first user terminal registering the target domain name on the second blockchain.

[0200] In an alternative embodiment, the processor is further configured to:

[0201] Sending, through the first user terminal, a second domain name registration request to the second blockchain; wherein the second domain name registration request includes: the second blockchain address corresponding to the first user terminal on the second blockchain, the target domain name, the blockchain identifier of the second blockchain, and the aggregated signature;

[0202] Upon the second blockchain receiving the second domain name registration request sent by the first user terminal, verifying, based on the multiple network node signatures included in the aggregated signature, whether the aggregated signature meets the signature validity condition;

[0203] When it is determined that the aggregated signature meets the signature validity condition, determining that the first user terminal has completed the registration of the target domain name on the second blockchain.

[0204] In an alternative embodiment, when verifying whether the aggregated signature meets the signature validity condition based on the multiple network node signatures included in the aggregated signature, the processor is configured to:

[0205] Determine the number of first node signatures whose signers belong to the nodes within the target network from the multiple network node signatures;

[0206] When determining that the number of the first node signatures is greater than or equal to a second preset number, determine that the aggregated signature meets the signature validity condition.

[0207] In an alternative embodiment, when verifying whether the aggregated signature meets the signature validity condition based on the multiple network node signatures included in the aggregated signature, the processor is configured to:

[0208] Obtain the number of second node signatures whose signers belong to the valid signature nodes within the target network from the multiple network node signatures;

[0209] When determining that the number of the second node signatures is greater than or equal to a third preset number, determine that the aggregated signature meets the signature validity condition.

[0210] In an alternative embodiment, when the target network belongs to a strongly associated network, the processor is further configured to:

[0211] When determining that the target domain name does not belong to the domain names registered by the first user terminal on the first blockchain, verify whether the target domain name has not been registered on the first blockchain according to the domain names registered by each user terminal stored in the local database on the first blockchain;

[0212] When determining that the target domain name has not been registered on the first blockchain, allow the first user terminal to register the target domain name on the second blockchain through the target network.

[0213] In an alternative embodiment, after allowing the first user terminal to register the target domain name on the second blockchain through the target network, the processor is further configured to:

[0214] Responding to the first user terminal completing the registration of the target domain name on the second blockchain through the target network, store the target domain name registered by the first user terminal on the second blockchain in the local database.

[0215] In an alternative embodiment, when the target network belongs to a weakly associated network, the processor is further configured to:

[0216] When it is determined that the target domain name does not belong to the domain names registered by the first user terminal on the first blockchain, verify whether the target domain name has not been registered on the first blockchain according to the domain names registered by each user terminal stored in the local database on the first blockchain;

[0217] When it is determined that the target domain name has not been registered on the first blockchain, the target network sends a target prompt message to the first user terminal; wherein, the target prompt message is used to prompt the first user terminal to preferentially complete the registration of the target domain name on the first blockchain.

[0218] In an alternative embodiment, the processor is further configured to:

[0219] When it is determined that the target domain name does not belong to the domain names registered by the first user terminal on the first blockchain, verify whether the target domain name has been registered by other user terminals on the first blockchain according to the domain names registered by each user terminal stored in the local database on the first blockchain;

[0220] When it is determined that the target domain name has been registered by the other user terminals on the first blockchain, the target network rejects the first user terminal from registering the target domain name on the second blockchain.

[0221] Based on the above computer-readable storage medium provided by the embodiments of the present application, when the target network responds to any user terminal completing the registration of a domain name on the first blockchain, it stores the domain name registered by the user terminal on the first blockchain in the local database; when the target network responds to the first domain name registration request sent by the first user terminal, it verifies whether the target domain name requested by the first user terminal to be registered on the second blockchain belongs to the domain names registered by the first user terminal on the first blockchain according to the first user signature carried in the first domain name registration request and the local database; when it is determined that the target domain name belongs to the domain names registered by the first user terminal on the first blockchain, the target network allows the first user terminal to register the target domain name on the second blockchain. In this way, the present application enables the same user to use the same decentralized domain name across blockchains, which can effectively improve the accuracy of user identity recognition during cross-chain interaction and is beneficial to the development of cross-chain technology.

[0222] In the embodiments of the present application, when the computer program is run by the processor, it may also execute other machine-readable instructions to execute the domain name registration method based on the blockchain as described in other parts of the embodiments. For the specific method steps and principles of execution, refer to the description of the embodiments and will not be elaborated in detail here.

[0223] In the embodiments provided in the present application, it should be understood that the disclosed devices and methods can be implemented in other ways. The device embodiments described above are merely illustrative. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods. For another example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the displayed or discussed couplings or direct couplings or communication connections between each other can be through some communication interfaces. The indirect couplings or communication connections of the devices or units can be in electrical, mechanical or other forms.

[0224] The units described as separate components may or may not be physically separated. The components displayed as units may or may not be physical units, that is, they can be located in one place or distributed to multiple network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0225] In addition, each functional unit in the embodiments provided in the present application can be integrated into one processing unit, or each unit can exist physically alone, or two or more units can be integrated into one unit.

[0226] If the functions are implemented in the form of software function units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on such an understanding, the technical solution of the present application, in essence, or the part that contributes to the prior art, or a part of this technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to enable a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in various embodiments of the present application. The foregoing storage medium includes: various media such as USB flash drives, mobile hard disks, read-only memories (ROMs), random access memories (RAMs), magnetic disks, or optical discs that can store program codes.

[0227] It should be noted that similar reference numerals and letters represent similar items in the following drawings. Therefore, once an item is defined in one drawing, it does not need to be further defined and explained in subsequent drawings. In addition, the terms "first", "second", "third", etc. are only used for descriptive distinction and cannot be understood as indicating or implying relative importance.

[0228] Finally, it should be noted that the above-described embodiments are only specific implementation manners of the present application, used to illustrate the technical solutions of the present application, rather than limiting it. The protection scope of the present application is not limited thereto. Although the present application has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that any person skilled in the art within the technical scope disclosed by the present application can still modify the technical solutions recorded in the foregoing embodiments or can easily think of changes, or perform equivalent replacements on some of the technical features; and these modifications, changes or replacements do not make the essence of the corresponding technical solutions deviate from the spirit and scope of the technical solutions of the embodiments of the present application. All should be covered within the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.

Claims

1. A domain name registration method based on blockchain, characterized in that, the domain name registration method includes: In response to any user terminal completing the registration of a domain name on the first blockchain, the target network stores the domain name registered by the user terminal on the first blockchain in the local database; In response to a first domain name registration request sent by a first user terminal, the target network verifies whether the target domain name requested by the first user terminal to be registered on the second blockchain belongs to the domain name already registered by the first user terminal on the first blockchain according to the first user signature carried in the first domain name registration request and the local database; wherein, the first user signature is determined according to the first blockchain address corresponding to the first user terminal on the first blockchain; When it is determined that the target domain name belongs to the domain name already registered by the first user terminal on the first blockchain, the target network allows the first user terminal to register the target domain name on the second blockchain; When it is determined that the target domain name does not belong to the domain name already registered by the first user terminal on the first blockchain, the target network verifies whether the target domain name has been registered by other user terminals on the first blockchain according to the domain names registered by each user terminal on the first blockchain stored in the local database; When it is determined that the target domain name has been registered by the other user terminals on the first blockchain, the target network rejects the first user terminal from registering the target domain name on the second blockchain.

2. The domain name registration method according to claim 1, characterized in that, when it is determined that the target domain name belongs to the domain name already registered by the first user terminal on the first blockchain, the domain name registration method further includes: The target network extracts a node number greater than or equal to a first preset number of nodes from all nodes in the network as nodes to be signed; The target network obtains the node signatures of each of the nodes to be signed for the target registration event, and sends each of the obtained node signatures to the first user terminal; wherein, the target registration event represents the registration event of the first user terminal registering the target domain name on the second blockchain.

3. The domain name registration method according to claim 1, characterized in that, after the target network allows the first user terminal to register the target domain name on the second blockchain, the first user terminal registers the target domain name on the second blockchain by the following method: The first user terminal sends a second domain name registration request to the second blockchain; wherein, the second domain name registration request includes: the second blockchain address corresponding to the first user terminal on the second blockchain, the target domain name, the blockchain identifier of the second blockchain, and an aggregated signature; In response to the second domain name registration request sent by the first user terminal, the second blockchain verifies whether the aggregated signature meets the signature validity condition according to the multiple network node signatures included in the aggregated signature; When it is determined that the aggregated signature meets the signature validity condition, it is determined that the first user terminal completes the registration of the target domain name on the second blockchain.

4. The domain name registration method according to claim 3, wherein, verifying whether the aggregated signature meets the signature validity condition according to the multiple network node signatures included in the aggregated signature includes: determining the number of first node signatures of which the signatory belongs to the nodes within the target network from the multiple network node signatures; when it is determined that the number of the first node signatures is greater than or equal to a second preset number, determining that the aggregated signature meets the signature validity condition.

5. The domain name registration method according to claim 3, wherein, verifying whether the aggregated signature meets the signature validity condition according to the multiple network node signatures included in the aggregated signature further includes: obtaining the number of second node signatures of which the signatory belongs to the valid signature nodes within the target network from the multiple network node signatures; when it is determined that the number of the second node signatures is greater than or equal to a third preset number, determining that the aggregated signature meets the signature validity condition.

6. The domain name registration method according to claim 1, wherein, when the target network belongs to a strongly associated network, after verifying whether the target domain name requested by the first user terminal to register on the second blockchain belongs to the domain name already registered by the first user terminal on the first blockchain, the domain name registration method further includes: when it is determined that the target domain name does not belong to the domain name already registered by the first user terminal on the first blockchain, verifying whether the target domain name has not been registered on the first blockchain according to the domain names registered by each user terminal stored in the local database; when it is determined that the target domain name has not been registered on the first blockchain, the target network allows the first user terminal to register the target domain name on the second blockchain.

7. The domain name registration method according to claim 6, wherein, after the target network allows the first user terminal to register the target domain name on the second blockchain, the domain name registration method further includes: the target network stores the target domain name registered by the first user terminal on the second blockchain into the local database in response to the first user terminal completing the registration of the target domain name on the second blockchain.

8. The domain name registration method according to claim 1, wherein, when the target network belongs to a weakly associated network, after verifying whether the target domain name requested by the first user terminal to register on the second blockchain belongs to the domain name already registered by the first user terminal on the first blockchain, the domain name registration method further includes: When it is determined that the target domain name does not belong to the domain names registered by the first user terminal on the first blockchain, verify whether the target domain name has not been registered on the first blockchain according to the domain names registered by each user terminal stored in the local database; When it is determined that the target domain name has not been registered on the first blockchain, the target network sends target prompt information to the first user terminal; wherein, the target prompt information is used to prompt the first user terminal to preferentially complete the registration of the target domain name on the first blockchain.

9. A domain name registration device based on blockchain, characterized in that, the domain name registration device includes: a recording module, configured to store, in the local database, the domain name registered by a user terminal on the first blockchain in response to any user terminal completing the registration of a domain name on the first blockchain through the target network; a first verification module, configured to verify, in response to a first domain name registration request sent by a first user terminal through the target network, whether the target domain name requested by the first user terminal to be registered on the second blockchain belongs to the domain names registered by the first user terminal on the first blockchain according to the first user signature carried in the first domain name registration request and the local database; wherein, the first user signature is determined according to the first blockchain address corresponding to the first user terminal on the first blockchain; a second verification module, configured to allow the first user terminal to register the target domain name on the second blockchain through the target network when it is determined that the target domain name belongs to the domain names registered by the first user terminal on the first blockchain; wherein, the domain name registration device further includes a third verification module, and the third verification module is configured to: when it is determined that the target domain name does not belong to the domain names registered by the first user terminal on the first blockchain, verify whether the target domain name has been registered by other user terminals on the first blockchain according to the domain names registered by each user terminal stored in the local database; when it is determined that the target domain name has been registered by the other user terminals on the first blockchain, the target network rejects the first user terminal from registering the target domain name on the second blockchain.

10. A domain name registration system based on blockchain, characterized in that, the domain name registration system includes: a target network and multiple user terminals; wherein, the target network is configured to: store, in the local database, the domain name registered by a user terminal on the first blockchain in response to any one of the user terminals completing the registration of a domain name on the first blockchain; In response to a first domain name registration request sent by a first user terminal, verify whether the target domain name requested by the first user terminal to be registered on a second blockchain belongs to the domain names already registered by the first user terminal on a first blockchain according to the first user signature carried in the first domain name registration request and the local database; wherein, the first user signature is determined according to the first blockchain address corresponding to the first user terminal on the first blockchain. When it is determined that the target domain name belongs to the domain names already registered by the first user terminal on the first blockchain, allow the first user terminal to register the target domain name on the second blockchain. When it is determined that the target domain name does not belong to the domain names already registered by the first user terminal on the first blockchain, verify whether the target domain name has been registered by other user terminals on the first blockchain according to the domain names registered by each user terminal on the first blockchain stored in the local database. When it is determined that the target domain name has been registered by the other user terminals on the first blockchain, the target network rejects the first user terminal from registering the target domain name on the second blockchain.

11. An electronic device characterized in that it includes: a processor, a memory, and a bus, where the memory stores machine-readable instructions executable by the processor. When the electronic device runs, the processor communicates with the memory through the bus. When the machine-readable instructions are executed by the processor, the steps of the domain name registration method according to any one of claims 1 to 8 are executed.

12. A computer-readable storage medium characterized in that a computer program is stored on the computer-readable storage medium, and when the computer program is run by a processor, the steps of the domain name registration method according to any one of claims 1 to 8 are executed.

Images