Decentralized domain name management method and system based on block chain, and electronic equipment

Abstract

The invention provides a decentralized domain name management method and system based on a block chain and an electronic device, the method deploys a first smart contract, the first smart contract is deployed on a public chain node of a source block chain and is used for managing target information, the target information comprises domain name information and analysis record information, then a browser plug-in is deployed, and the browser plug-in is used for managing the domain name information and the analysis record information. The browser plug-in is used for interacting with the first smart contract; and in response to a request of a user for obtaining target information, calling the first smart contract through the browser plug-in to obtain the target information, the target information being information stored in the target block chain and obtained by the source block chain through interaction between the source block chain and the target block chain. According to the method, a user can initiate a request through a browser plug-in and automatically obtain domain name information and an analysis record through an intelligent contract so as to improve the efficiency, and through a decentralized architecture, the domain name of the user does not depend on a single service provider, so that the risk caused by the problem of the service provider is reduced, and the safety is improved.

Description

Technical Field

[0001] The present application relates to the field of communication technology, and in particular to a decentralized domain name management method, system and electronic device based on blockchain. Background Art

[0002] The Domain Name System (DNS) is a system used on the Internet to convert domain names into corresponding IP addresses. The domain name system includes domain name resolution, IP address management, load balancing, fault tolerance and failure recovery, domain name management and maintenance, etc. Users purchase and manage domain names through registrars. The resolution service provides the conversion from domain names to IP addresses. Users can choose to use the resolution service provided by the registrar or a third-party resolution service.

[0003] Although users have the right to use domain names, these rights are subject to the control of the registrar and the policy restrictions of the domain name system. When changing domain name service providers or resolution service providers, users need to go through a series of complicated processes, including logging in to the old service provider's website, exporting domain name and resolution records, logging in to the new service provider's website, and importing these records.

[0004] However, users need to manually handle a large number of domain names and DNS records when changing domain name service providers, and the centralized nature of domain name services makes users' domain name assets highly dependent on a single service provider. If there is a problem with the service provider, such as system failure, security vulnerabilities, policy changes, etc., the user's domain name may be affected, resulting in low efficiency and low security in obtaining domain names and DNS records. Summary of the invention

[0005] The present application provides a decentralized domain name management method, system and electronic device based on blockchain to solve the problems of low efficiency and low security in obtaining domain names and DNS records.

[0006] In a first aspect, the present application provides a decentralized domain name management method based on blockchain, comprising:

[0007] Deploy a first smart contract, where the first smart contract is deployed on a public chain node of a source blockchain and is used to manage target information, where the target information includes domain name information and resolution record information;

[0008] Deploy a browser plug-in, where the browser plug-in is used to interact with the first smart contract;

[0009] In response to a user's request to obtain the target information, the first smart contract is called through the browser plug-in to obtain the target information, where the target information is information stored in the target blockchain and obtained by the source blockchain through interaction with the target blockchain.

[0010] In some feasible embodiments, before deploying the first smart contract, the steps include:

[0011] Define an interface, where the interface is used to implement a first smart contract;

[0012] An abstraction layer is established, where the abstraction layer is used to interact with the browser plug-in and call the interface to interact with the first smart contract through the interface.

[0013] In some feasible embodiments, in response to the user's request to obtain the target information, before calling the first smart contract through the browser plug-in to obtain the target information, the process includes:

[0014] Creating an identity identifier that performs identity authentication using a public key and a private key;

[0015] Registering the public key to the first smart contract through the browser plug-in;

[0016] Calling the first smart contract, and verifying the signature through the first smart contract, where the signature is a signature made by the user using the private key through the browser plug-in;

[0017] If the signatures match, in response to a request sent by the user to enter the domain name information and the resolution record, the target information is received and stored in the target blockchain.

[0018] In some feasible embodiments, the acquiring the target information includes:

[0019] In response to a user's request for obtaining the target information, sending an instruction to the browser plug-in to control the browser plug-in to obtain the private key and generate signed request data;

[0020] Obtain the public key, and control the first smart contract to verify the signature in the signed request data through the public key;

[0021] If the signatures match, the target information is obtained through the first smart contract.

[0022] In some feasible embodiments, if the signatures match, obtaining target information through the first smart contract includes:

[0023] If the signature matches, obtain the permission record, where the permission record is the permission information of the user defined by the permission model;

[0024] If the permission record includes obtaining the target information, the target information is obtained through the first smart contract.

[0025] In some feasible embodiments, storing the target information in the target blockchain includes:

[0026] Obtaining a backup blockchain connected to the target blockchain;

[0027] Send an instruction to the target blockchain so that the target blockchain synchronizes the target information to the backup blockchain through a cross-chain bridge or a relay chain.

[0028] In some feasible embodiments, in response to the user's request to obtain the target information, calling the first smart contract through the browser plug-in to obtain the target information further includes:

[0029] Deploy a second smart contract, where the second smart contract is deployed on a public chain node of the target blockchain;

[0030] In response to a first query request initiated by a user, the first smart contract sends a request to a target blockchain through a cross-chain bridge or a relay chain to retrieve the target information through the second smart contract, wherein the first query request is a request initiated by the browser plug-in interacting with the first smart contract;

[0031] The target information is sent to the first smart contract through a cross-chain bridge or a relay chain, and the target information is displayed through the browser plug-in.

[0032] In some feasible embodiments, the request for obtaining the target information includes a source service provider, a target service provider, and target information;

[0033] The method further comprises:

[0034] generating migration options based on the request for the target information;

[0035] Calling the first smart contract through the browser plug-in to obtain the target information;

[0036] According to the migration option, the target information of the source service provider is migrated to the target service provider.

[0037] In the second aspect, the present application provides a decentralized domain name management system based on blockchain, including:

[0038] A smart contract deployment unit, used to deploy a first smart contract, where the first smart contract is deployed on a public chain node of a source blockchain and is used to manage target information, where the target information includes domain name information and resolution record information;

[0039] A browser plug-in deployment unit, used to deploy a browser plug-in, where the browser plug-in is used to interact with the first smart contract;

[0040] An execution unit is used to respond to a user's request to obtain the target information, call the first smart contract through the browser plug-in to obtain the target information, wherein the target information is information stored in the target blockchain obtained by the source blockchain through interaction with the target blockchain.

[0041] In a third aspect, the present application provides an electronic device, including:

[0042] Memory for storing computer programs;

[0043] A processor is used to execute the computer program, wherein the computer program is specifically used to implement the decentralized domain name management method based on blockchain.

[0044] As can be seen from the above technical solutions, the present application provides a decentralized domain name management method, system and electronic device based on blockchain, wherein the method deploys a first smart contract, wherein the first smart contract is deployed on the public chain node of the source blockchain, and is used to manage target information, the target information including domain name information and resolution record information, and then deploys a browser plug-in, the browser plug-in is used to interact with the first smart contract; in response to a user's request to obtain the target information, the first smart contract is called through the browser plug-in to obtain the target information, the target information is the information stored in the target blockchain obtained by the source blockchain through the interaction with the target blockchain. In the method, the user can initiate a request through the browser plug-in, and the smart contract automatically obtains the domain name information and resolution record to improve efficiency, and through a decentralized architecture, the user's domain name does not rely on a single service provider, reducing the risk caused by service provider problems to improve security. BRIEF DESCRIPTION OF THE DRAWINGS

[0045] In order to more clearly illustrate the technical solution of the present application, the drawings required for use in the embodiments are briefly introduced below. Obviously, for ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0046] Figure 1 A flowchart of a decentralized domain name management method based on blockchain provided in an embodiment of the present application;

[0047] Figure 2 A schematic diagram of creating or importing a private key provided in an embodiment of the present application;

[0048] Figure 3A schematic diagram of a user entering target information provided in an embodiment of the present application;

[0049] Figure 4 A schematic diagram of obtaining target information provided in an embodiment of the present application;

[0050] Figure 5 A schematic diagram of a decentralized domain name management system based on blockchain provided in an embodiment of the present application. DETAILED DESCRIPTION

[0051] The following embodiments are described in detail, and examples thereof are shown in the accompanying drawings. When the following description refers to the drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The implementations described in the following embodiments do not represent all implementations consistent with the present application. They are only examples of systems and methods consistent with some aspects of the present application as detailed in the claims.

[0052] Users purchase and manage domain names through domain name registrars, such as GoDaddy, DNS Pod, and Alibaba Cloud. Users purchase domain names through domain name registrars, and can configure the DNS records of the domain names through the control panel provided by the service provider to point to their own servers or hosting services. Users can change the registration information, renew, transfer, and other operations of the domain name, all of which need to be completed through the interface provided by the service provider. In other words, the service provider acts as a medium between the user and the domain name registrar, and the user's personal information is stored on the service provider's server. If the service provider is attacked or the data is leaked, the user's privacy information may be exposed. In addition, sensitive information related to the domain name, such as DNS records and resolution records, may also be abused or tampered with.

[0053] To make it easier for users to remember domain names, domain name resolution can be used. Users enter a domain name in a browser or other client application. The client first checks the local cache to see if there is a record of the domain name. If not, it sends a query request to the local DNS server. After receiving the request, if the local DNS server has a record of the domain name in its cache, it will return it directly; if not, it will start a recursive query. First, the root DNS server is contacted. The root DNS server does not directly save the specific IP address of the domain name, but knows the location of the top-level domain name, such as .com, .org, etc. The root DNS server will tell the local DNS server where to find the top-level domain name server. The top-level domain name server also does not save the specific IP address, but knows the location of the corresponding authoritative DNS server. The top-level domain name server will tell the local DNS server where to find the authoritative DNS server. The authoritative DNS server is responsible for managing the records of a specific domain name and will return the IP address corresponding to the domain name. After obtaining the IP address, the local DNS server returns the result to the client and may cache the record for a period of time so that future requests can respond faster. The client accesses the target server based on the returned IP address.

[0054] It can be seen that domain name resolution involves multiple levels of DNS servers, from root servers to top-level domain name servers to authoritative servers. The process is relatively complicated, increasing delays and potential failure points. Centralized servers become targets of attacks. If they are attacked by DDoS or data leaks, it will affect user privacy and data security. In addition, users need to rely on third-party service providers to manage and resolve domain names, which increases the complexity of management and maintenance.

[0055] Although users have the right to use domain names, these rights are subject to the control of the registrar and the policy restrictions of the domain name system. The replacement of domain name registrar is completed in the following way. In some embodiments, the domain name is first unlocked, and the authorization code is obtained, and a domain name transfer request is submitted to the newly registered service provider to complete the replacement. The replacement of domain name resolution service provider is completed in the following way. In some embodiments, the domain name resolution record is first exported, and then the new resolution service provider is logged in, the DNS record is imported, and the NS (Name Server) record is updated to complete the replacement.

[0056] In summary, in the above process, the process of obtaining domain names and DNS records not only affects efficiency but also leads to low security.

[0057] To solve the above problems, Figure 1As shown, some embodiments of the present application provide a decentralized domain name management method based on blockchain. Users can initiate requests through browser plug-ins with one click, and smart contracts automatically handle the migration process, reducing the tediousness of manual operations and improving the efficiency of obtaining domain names and DNS records. And through a decentralized architecture, users' domain name assets no longer rely on a single service provider, which can reduce the risks caused by service provider problems. All operations are recorded on the blockchain to ensure that the data is open, transparent and cannot be tampered with, thereby improving the security of the system.

[0058] The method comprises:

[0059] S100: Deploy the first smart contract.

[0060] Smart Contracts are computer programs that automatically execute contract terms. They run on blockchain technology and use the characteristics of distributed ledgers to ensure that the terms of the contract can be automatically and reliably executed. Blockchain platforms may include Ethereum, Polkadot, Cosmos, etc.

[0061] Use the technology and features of the public blockchain to build and run applications or services. In this context, the public blockchain is used to provide a decentralized, transparent, secure and tamper-proof basic platform. Use the technical support provided by the public blockchain, such as smart contracts and distributed ledgers, to implement application functions and services. Applications and services do not rely on a single centralized server, but are distributed on nodes around the world, which can improve the reliability and fault resistance of the system.

[0062] The first smart contract is deployed on the public chain node of the source blockchain (Source Chain), where the source blockchain refers to the blockchain platform that initially hosts the domain name information. The source blockchain is used to store and manage the user's domain name information and resolution record information, which can ensure its decentralization and transparency, and is used to manage the target information. Specifically, the first smart contract is used to receive user requests, verify user identities, perform corresponding operations, such as query, update, migration, etc., and record all related events. In this embodiment, the first smart contract can be modularized so that each module is responsible for a specific function. For example: an account management module and a domain name management module. The account management module is used for operations such as account creation, login, and logout. The domain name management module is used for operations such as domain name registration, renewal, and transfer.

[0063] The target information includes domain name information and resolution record information. The resolution record is a DNS resolution record, which is a record that maps a domain name to an IP address or other resources. When a user enters the domain name of a website in a browser, the device sends a request to the DNS server to convert the domain name into the corresponding IP address. The DNS resolution record is a database used to complete this mapping. DNS resolution records can include multiple types, such as A records (Address Record) and AAAA records (IPv6 Address Record).

[0064] In some embodiments, before deploying the first smart contract, an interface is first defined, and the interface is used to implement the first smart contract; then an intermediate layer (Provider) is established, for example, an abstraction layer (Cross-platform Abstraction Layer), and the abstraction layer is used to interact with the browser plug-in and call the interface to interact with the first smart contract through the interface.

[0065] These interfaces include but are not limited to domain name registration, domain name renewal, domain name transfer, domain name information query, DNS record management, etc. Domain name registration allows users to register new domain names, domain name renewal allows users to extend the validity period of a domain name, domain name transfer allows users to transfer the ownership of a domain name to another address, domain name information query allows users to query the status of a domain name and other related information, and DNS record management allows users to add, delete or modify the DNS resolution record of a domain name.

[0066] After setting the interface, deploy the smart contract. The first smart contract is deployed first. The first smart contract is the smart contract of the source blockchain. Deploy smart contracts for the blockchain and ensure that they all follow the standardized interface. Compile the smart contract through the compiler, deploy the compiled smart contract on the blockchain platform, and record the address of the smart contract on the blockchain platform for subsequent calls.

[0067] In order to achieve consistent operation logic on different blockchain platforms, the cross-platform abstraction layer can be used to make the implementation details of the first smart contract on different blockchain platforms transparent to the end user. The abstraction layer is used for interface mapping, error handling, state synchronization, and DNS record management. Interface mapping maps the unified interface to the specific implementation of each blockchain platform. Error handling uniformly handles error codes and abnormal situations on different platforms. State synchronization ensures state consistency between different platforms. DNS record management is used for operations such as adding, deleting, and modifying DNS records.

[0068] For example, if a user needs to register a domain name across platforms, a register Domain interface can be defined, which accepts the domain name and registration period as parameters. Write an adapter for each supported blockchain platform (e.g., Ethereum, Polkadot, Cosmos, etc.), map the register Domain interface to the smart contract call of the platform, and then write specific smart contract code for each platform to implement the domain name registration function.

[0069] S200: Deploy a browser plug-in.

[0070] A browser plug-in (Signer) refers to an extension installed on the user's browser for interacting with the first smart contract. The browser plug-in can provide a user-friendly interface, allowing users to easily initiate requests, view status, manage domain name information, etc.

[0071] When a user requests to perform an operation through a browser plug-in, the browser plug-in will call the corresponding smart contract method and process the returned result. In some embodiments, the browser plug-in receives the user's request, calls the corresponding smart contract method according to the request, processes the result returned by the smart contract, and displays the result to the user. This ensures that users can perform consistent operations on different blockchain platforms without having to learn different operation logics, which can simplify the user experience and improve efficiency.

[0072] It is understandable that browser plug-ins, as the front end for interacting with users, can also interact with smart contracts on different blockchain platforms. Browser plug-ins can support cross-platform calls and can call corresponding smart contracts according to user choices.

[0073] The user can query and migrate the target information through the interface of the browser plug-in, and the browser plug-in can obtain the target information through the first smart contract. However, in order to allow users to independently control identity authentication and data operations to improve security, in some embodiments, an identity identifier can be created, and the identity identifier performs identity authentication through a public key and a private key; then the public key is registered to the first smart contract through the browser plug-in; the first smart contract is called, and the signature is verified through the first smart contract. The signature is the signature of the user through the browser plug-in using the private key; if the signature matches, then respond to the user's request to enter, query or migrate information.

[0074] Among them, the identity identifier can be a decentralized identity (Decentralized Identifier, DID), which does not rely on a centralized registration agency and allows users to independently manage and control their own identity information. DID can be combined with a public-private key mechanism to achieve identity authentication.

[0075] like Figure 2 As shown, in some embodiments, the user's identity is first created, allowing the user to generate public and private keys, and register the public key in the smart contract, and then the user's signature is verified so that the user has the correct private key, and the user's authority information is managed, and the authority information includes authorized users and authorized operations.

[0076] Before responding to a user's request to enter, query or migrate information, the authentication logic is implemented in the smart contract on each blockchain platform, and only users with the correct private key can perform specific operations. To make the cross-chain authentication mechanism effective, in some embodiments, the user's permission information is transmitted through a cross-chain communication mechanism, such as the cross-chain messaging protocol CMP.

[0077] For user permissions, a user permission model can be defined so that users can only perform authorized operations. Permissions may include read permissions and write permissions. Read permissions allow users to read target information, and write permissions allow users to modify target information.

[0078] For example, first create a DID, generate a pair of public and private keys, and register the public key to the smart contract through a browser plug-in. Users can assign permissions to themselves or others. For example, users can assign read permissions to themselves. For another example, users can assign read permissions to other users so that other users can also obtain target information.

[0079] When a user requests to obtain target information through a browser plug-in, the browser plug-in signs the request with the user's private key and sends the signature and the request to the smart contract. The browser plug-in calls the smart contract. After receiving the request, the smart contract verifies whether the signature in the request is correct and checks whether the requester has read permission. If the verification is successful and the requester has permission, the smart contract returns the target information.

[0080] Verifying user identities through public and private keys ensures security. Users can independently control their own identity authentication and data operations, and can independently manage domain names and DNS records on different blockchain platforms without relying on third parties.

[0081] After registering the public key to the smart contract through the browser plug-in, you can enter the domain name information and resolution record information. For example, Figure 3 As described above, the user uses a private key to sign the request through a browser plug-in to prove the legitimacy of the request. The browser plug-in carries the signature and request to call the smart contract. The browser plug-in interacts with the services of Alchemy and Infura. These two services provide API interfaces for developers to use, making it easier to communicate with the blockchain network.

[0082] Provider interacts with the virtual machine, which is one of the core components of the blockchain network and is responsible for executing smart contracts. In the Ethereum blockchain, the virtual machine is called EVM (Ethereum Virtual Machine). The system can include multiple smart contracts, each responsible for different tasks, such as domain name registration, resolution record management, etc. These smart contracts are deployed on the blockchain and can be called by other smart contracts or external entities. The operations of smart contracts will be recorded on the blockchain to form blocks. The blockchain is formed by a series of ordered blocks connected together, and each block contains the hash value of the previous block to ensure the integrity and immutability of the data.

[0083] The smart contract verifies the signature and performs the corresponding operation, and checks whether the user has the corresponding authority to enter the information. If the verification is passed and the authority is available, the smart contract performs the entry operation and returns the result to the browser plug-in.

[0084] When storing or entering the target information into the blockchain, the management of the target information is not centralized in a single centralized server or system, but can be collaboratively managed and verified through multiple different blockchain platforms and their respective node networks. In some embodiments, a backup blockchain connected to the target blockchain is first obtained, and then an instruction is sent to the target blockchain so that the target blockchain synchronizes the target information to the backup blockchain through a cross-chain bridge or a relay chain.

[0085] Different blockchain platforms have node networks that are distributed in different locations. Each node stores a copy of part or all of the data. Distributed networks can reduce the risk of single point failures. Even if some nodes fail or are attacked, other nodes can continue to work normally.

[0086] Multiple blockchain platforms jointly manage target information, share and synchronize it through multiple blockchain platforms. Each blockchain platform can exchange and communicate data through cross-chain technology to ensure the consistency and integrity of data between different chains.

[0087] The target information can also be distributed and stored on multiple blockchain nodes. This distributed storage method can improve data redundancy and increase data reliability and security.

[0088] For example, when user A wants to register a new domain name abcd.com, user A sends a registration request through a browser plug-in. The smart contract writes the domain name information into the blockchain and synchronizes it to other blockchain platforms through cross-chain technology. The node networks of multiple blockchain platforms copy and store the domain name information on their respective nodes to ensure data consistency and availability.

[0089] In the above process, the target information is not necessarily written separately to multiple blockchain platforms. The target information can be recorded on a single blockchain platform or recorded synchronously on multiple blockchain platforms. In the process of recording on a single blockchain platform, the target information is first written to a main blockchain platform and then synchronized to other blockchain platforms through a cross-chain mechanism. In the process of synchronously recording on multiple blockchain platforms, the target information is written to multiple blockchain platforms at the same time to ensure the consistency of data on multiple chains.

[0090] In the case of recording on a single blockchain platform, the user initiates an entry request through a browser plug-in, the smart contract writes the target information into the main blockchain platform, and the smart contract synchronizes the target information to other blockchain platforms through a cross-chain mechanism.

[0091] In the case of synchronous recording on multiple blockchain platforms, the user initiates an entry request through a browser plug-in, and the smart contract constructs a cross-chain message containing the target information. The smart contract broadcasts the cross-chain message to the cross-chain communication network. After the nodes in the cross-chain communication network receive the message, the cross-chain nodes write the target information into the blockchain platforms they manage.

[0092] It is understandable that whether recording through a single blockchain platform or multiple blockchain platforms simultaneously, it can ensure that the target information is correctly entered, and achieve data consistency and reliability through the cross-chain mechanism. It can improve the anti-attack capability and reliability, and can independently manage the target information on different blockchain platforms without relying on any third party.

[0093] It should be noted that when deploying smart contracts, it is necessary to ensure that the smart contracts support cross-chain communication protocols, for example, by implementing specific interfaces or calling specific functions. Smart contracts need to write appropriate logic to handle cross-chain requests and ensure the correctness and consistency of data. Browser plug-ins need to support the sending and receiving of cross-chain requests, as well as the corresponding error handling logic.

[0094] S300: In response to a user's request to obtain target information, a first smart contract is called through a browser plug-in to obtain the target information.

[0095] The target information is the domain name information and resolution record information stored in the target blockchain (Target Chain) obtained by the source blockchain through interaction with the target blockchain.

[0096] In the process of displaying the target information on the browser plug-in through the smart contract, if the target information is public and can be viewed by anyone, then there is no need to verify the private key. However, if the target information is sensitive or limited to specific users, the private key needs to be verified to ensure that only authorized users can access this information.

[0097] To obtain the target information, in some embodiments, in response to a user's request to obtain the target information, an instruction is sent to the browser plug-in to control the browser plug-in to obtain a private key and generate signed request data; then obtain the public key, and control the first smart contract to verify the signature in the signed request data through the public key; if the signature matches, the target information is obtained through the first smart contract.

[0098] If the target information needs to verify the private key before it can be displayed in the browser plug-in, the user requests to view the target information through the browser plug-in. The user can click "View domain name information" or a similar button through the browser plug-in to trigger the request. The browser plug-in uses the user's private key to sign the request to prove that the request comes from a legitimate user. The browser plug-in sends the signed request to the smart contract. After receiving the request, the smart contract uses the public key provided in the request to decrypt the signature to verify whether the decrypted signature matches the content of the request. If the signature verification is successful, the smart contract returns the target information to the browser plug-in.

[0099] In some embodiments, if the signature matches, the permission record can also be obtained, and the permission record is the permission information of the user defined by the permission model; if the permission record includes obtaining target information, the target information is obtained through the first smart contract. That is to say, when the signature verification is successful, the smart contract further checks whether the user has the authority to view the target information. If the user passes the signature verification and has the authority to view the target information, it can check the permission information stored in the smart contract.

[0100] According to the above, the browser plug-in can interact with multiple blockchain platforms. In some embodiments, a second smart contract is deployed, and the second smart contract is deployed on the public chain node of the target blockchain. In response to a first query request initiated by a user, the first smart contract sends a retrieval request to the target blockchain through a cross-chain bridge or a relay chain to retrieve the target information through the second smart contract. The first query request is a request initiated by the browser plug-in to interact with the first smart contract; the target information is sent to the first smart contract through the cross-chain bridge or the relay chain, and the target information is displayed through the browser plug-in.

[0101] There can be multiple target blockchains. The target blockchain and the source blockchain represent two different blockchain networks in cross-chain communication, which can be established through a certain cross-chain mechanism to achieve functions such as asset transfer, data synchronization or smart contract call. The target blockchain receives the assets or requested blockchain sent from the source blockchain. The target blockchain is responsible for executing operations initiated by the source blockchain, such as executing smart contract functions.

[0102] Exemplarily, a user initiates a request through a first smart contract, for example, to query information about a domain name, and the request is transmitted to a target blockchain through a cross-chain mechanism, such as a cross-chain bridge or a relay chain. A second smart contract processes the request and returns the result to the source blockchain. The first smart contract receives the result returned by the target blockchain and feeds the result back to the user.

[0103] To ensure the security of cross-chain communication, there needs to be a certain trust basis between the source blockchain and the target blockchain. This trust can be achieved through validator sets, multi-party computation (MPC), hash time lock contracts (HTLC), etc. Among them, the cross-chain bridge uses one or more mechanisms such as validator sets, MPC, HTLC, etc. to ensure the trusted transfer of assets or data between the two chains. The relay chain, as the central chain in the multi-chain ecosystem, is used to coordinate the communication between different parallel chains to ensure the consistency and security of the data.

[0104] If the user's requirement is to initiate a request on blockchain A to query the information of a domain name on blockchain B, blockchain A is the source blockchain and blockchain B is the target blockchain. Figure 4 As shown, illustratively, a user accesses a web server that provides a front-end interface that allows the user to interact with the system. The front-end interface can be composed of HTML, CSS, and JavaScript, and is responsible for presenting a graphical user interface (GUI). A browser plug-in is an extension that is installed in the user's browser to manage the user's private key and sign transactions. Users can enter their private keys through the browser plug-in, sign transactions with the private keys, send requests to blockchain A, and the smart contract of blockchain A sends requests to the target blockchain through a cross-chain bridge or relay chain. The smart contract of blockchain B performs data retrieval operations and returns the results to the source blockchain through the same cross-chain mechanism. The smart contract of blockchain A receives the results and displays the results to the user through the browser plug-in. Users can interact directly with the blockchain network without going through traditional centralized domain name registration agencies.

[0105] In the acquisition process, the user can obtain the target information through the smart contract, but in the migration process, the target information needs to be migrated from the source service provider to the target service provider, so it is different from the acquisition process. In some embodiments, the request for obtaining the target information includes the source service provider, the target service provider, and the target information; according to the request for the target information, the migration option is generated; then the first smart contract is called through the browser plug-in to obtain the target information; according to the migration option, the target information of the source service provider is migrated to the target service provider.

[0106] Among them, the source service provider is the blockchain platform from which the user wants to import or migrate data, and the target service provider is the blockchain platform to which the user wants to migrate data.

[0107] In the browser plug-in, in order to facilitate users to import and migrate with one click, a one-click import and migration focus can be set on the user interface. Users can complete the import and migration tasks by clicking the focus. Import and migration are to simplify the process of users moving data between different blockchain platforms.

[0108] For example, if user A wants to migrate her domain name abcde.com and its A record on Ethereum to Polkadot. User A initiates a migration request through a browser plug-in, selecting Ethereum as the source service provider and Polkadot as the target service provider. The browser plug-in signs the request with Alice's private key, and sends the signed request to the smart contract. The smart contract obtains user A's public key, decrypts the signature, and looks for the permission record corresponding to user A. If the verification is successful and there is permission, the smart contract constructs a cross-chain message and broadcasts it to the cross-chain communication network. After receiving the message, the nodes in the cross-chain communication network verify the validity of the message. After the verification is successful, the cross-chain node writes abcde.com and its A record to the Polkadot blockchain platform.

[0109] The method can utilize cross-chain communication mechanisms and smart contract interfaces to efficiently and flexibly register, manage, update, transfer and delete domain names on multiple blockchain platforms. Through browser plug-ins, the browser can interact directly with the blockchain network, and use smart contracts to store and manage target information in different blockchains, while ensuring data security, immutability and transparency, and supporting the invocation of cross-chain smart contracts to achieve seamless interoperability between different blockchain platforms. The method solves the problems of data security, ease of use and flexibility in existing domain name and DNS management, and realizes decentralized management of domain name and DNS records.

[0110] Based on the above blockchain-based decentralized domain name management method, Figure 5 As shown, some embodiments of the present application also provide a decentralized domain name management system based on blockchain, including:

[0111] A smart contract deployment unit, used to deploy a first smart contract, where the first smart contract is deployed on a public chain node of a source blockchain and is used to manage target information, where the target information includes domain name information and resolution record information;

[0112] A browser plug-in deployment unit, used to deploy a browser plug-in, where the browser plug-in is used to interact with the first smart contract;

[0113] An execution unit is used to respond to a user's request to obtain the target information, call the first smart contract through the browser plug-in to obtain the target information, wherein the target information is information stored in the target blockchain obtained by the source blockchain through interaction with the target blockchain.

[0114] The present application provides an electronic device, including:

[0115] Memory for storing computer programs;

[0116] A processor is used to execute the computer program, wherein the computer program is specifically used to implement the decentralized domain name management method based on blockchain.

[0117] The electronic device may be a server or terminal device that other electronic devices can log in and access. The electronic device may include at least one memory and at least one processor. The processor may execute multiple computer instructions stored in the memory to implement the steps of the information processing method proposed in the above-mentioned embodiment of the present application. The implementation process can refer to the description of the corresponding method embodiment above, and this embodiment will not be described in detail here.

[0118] In the embodiment of the present application, the memory may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one disk storage device or other volatile solid-state storage device. The processor may be a central processing unit (CPU), an application-specific integrated circuit (ASIC), a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic devices, etc. The present application does not limit the structure and model of the above-mentioned memory and processor, and can be flexibly adjusted according to actual needs.

[0119] As can be seen from the above technical solutions, the present application provides a decentralized domain name management method, system and electronic device based on blockchain, wherein the method deploys a first smart contract, wherein the first smart contract is deployed on the public chain node of the source blockchain, and is used to manage target information, the target information including domain name information and resolution record information, and then deploys a browser plug-in, the browser plug-in is used to interact with the first smart contract; in response to a user's request to obtain the target information, the first smart contract is called through the browser plug-in to obtain the target information, the target information is the information stored in the target blockchain obtained by the source blockchain through the interaction with the target blockchain. In the method, the user can initiate a request through the browser plug-in, and the smart contract automatically obtains the domain name information and resolution record to improve efficiency, and through a decentralized architecture, the user's domain name does not rely on a single service provider, reducing the risk caused by service provider problems to improve security.

[0120] Similar parts between the embodiments provided in this application can be referenced to each other. The specific implementation methods provided above are only a few examples under the general concept of this application and do not constitute a limitation on the protection scope of this application. For those skilled in the art, any other implementation methods expanded based on the scheme of this application without creative work belong to the protection scope of this application.

Claims

1. A decentralized domain name management method based on blockchain, characterized in that: include: Deploy a first smart contract, where the first smart contract is deployed on a public chain node of a source blockchain and is used to manage target information, where the target information includes domain name information and resolution record information; Deploy a browser plug-in, where the browser plug-in is used to interact with the first smart contract; In response to a user's request to obtain the target information, the first smart contract is called through the browser plug-in to obtain the target information, where the target information is information stored in the target blockchain and obtained by the source blockchain through interaction with the target blockchain.

2. The decentralized domain name management method based on blockchain according to claim 1 is characterized in that: Before deploying the first smart contract, the following steps are included: Define an interface, where the interface is used to implement a first smart contract; An abstraction layer is established, where the abstraction layer is used to interact with the browser plug-in and call the interface to interact with the first smart contract through the interface.

3. The decentralized domain name management method based on blockchain according to claim 1 is characterized in that: In response to the user's request for obtaining the target information, before calling the first smart contract through the browser plug-in to obtain the target information, the method includes: Creating an identity identifier that performs identity authentication using a public key and a private key; Registering the public key to the first smart contract through the browser plug-in; Calling the first smart contract, and verifying the signature through the first smart contract, where the signature is a signature made by the user using the private key through the browser plug-in; If the signatures match, in response to a request sent by the user to enter the domain name information and resolution record, the target information is received and stored in the target blockchain.

4. The decentralized domain name management method based on blockchain according to claim 3 is characterized in that: The obtaining of the target information comprises: In response to a user's request for obtaining the target information, sending an instruction to the browser plug-in to control the browser plug-in to obtain the private key and generate signed request data; Obtain the public key, and control the first smart contract to verify the signature in the signed request data through the public key; If the signatures match, the target information is obtained through the first smart contract.

5. The decentralized domain name management method based on blockchain according to claim 4 is characterized in that: If the signatures match, obtaining target information through the first smart contract includes: If the signature matches, obtain the permission record, where the permission record is the permission information of the user defined by the permission model; If the permission record includes obtaining the target information, the target information is obtained through the first smart contract.

6. The decentralized domain name management method based on blockchain according to claim 3 is characterized in that: The storing the target information to the target blockchain includes: Obtaining a backup blockchain connected to the target blockchain; Send an instruction to the target blockchain so that the target blockchain synchronizes the target information to the backup blockchain through a cross-chain bridge or a relay chain.

7. The decentralized domain name management method based on blockchain according to claim 1, characterized in that: In response to the user's request to obtain the target information, calling the first smart contract through the browser plug-in to obtain the target information further includes: Deploy a second smart contract, where the second smart contract is deployed on a public chain node of the target blockchain; In response to a first query request initiated by a user, the first smart contract sends a request to a target blockchain through a cross-chain bridge or a relay chain to retrieve the target information through the second smart contract, wherein the first query request is a request initiated by the browser plug-in interacting with the first smart contract; The target information is sent to the first smart contract through a cross-chain bridge or a relay chain, and the target information is displayed through the browser plug-in.

8. The decentralized domain name management method based on blockchain according to claim 1, characterized in that: The request for obtaining the target information includes a source service provider, a target service provider, and target information; The method further comprises: generating migration options based on the request for the target information; Calling the first smart contract through the browser plug-in to obtain the target information; According to the migration option, the target information of the source service provider is migrated to the target service provider.

9. A decentralized domain name management system based on blockchain, characterized in that: include: A smart contract deployment unit, used to deploy a first smart contract, where the first smart contract is deployed on a public chain node of a source blockchain and is used to manage target information, where the target information includes domain name information and resolution record information; A browser plug-in deployment unit, used to deploy a browser plug-in, where the browser plug-in is used to interact with the first smart contract; An execution unit is used to respond to a user's request to obtain the target information, call the first smart contract through the browser plug-in to obtain the target information, wherein the target information is information stored in the target blockchain obtained by the source blockchain through interaction with the target blockchain.

10. An electronic device, characterized in that: include: Memory for storing computer programs; A processor, configured to execute the computer program, wherein the computer program is specifically configured to implement the decentralized domain name management method based on blockchain as described in any one of claims 1 to 8.

Images