CN117319350A

CN117319350A - Block chain domain name registration proxy method and device, and data proxy method and device

Info

Publication number: CN117319350A
Application number: CN202311433291.9A
Authority: CN
Inventors: 朱煜松
Original assignee: Ant Blockchain Technology Shanghai Co Ltd
Current assignee: Ant Blockchain Technology Shanghai Co Ltd
Priority date: 2023-10-31
Filing date: 2023-10-31
Publication date: 2023-12-29

Abstract

The embodiment of the specification discloses a blockchain domain name registration proxy method and device, and a data proxy method and device. The proxy method comprises the following steps: receiving a proxy request for registering a blockchain domain name by a user; generating proxy acknowledgement information based on the proxy request; receiving and verifying a confirmation signature of the user to the agent confirmation information; when the confirmation signature passes the verification, constructing a blockchain transaction registered by the blockchain domain name based on the account domain name and the account public key; and signing the blockchain transaction registered by the blockchain domain name by using a private key of a preset proxy account, and submitting the signed transaction to the blockchain. The device comprises a request receiving module, a confirmation module, a construction module and a registration module.

Description

Block chain domain name registration proxy method and device, and data proxy method and device

Technical Field

One or more embodiments of the present disclosure relate to the field of information technology, and in particular, to a blockchain domain name registration proxy method and apparatus, and a data proxy method and apparatus.

Background

Blockchain is a novel application mode of computer technologies such as distributed data storage, point-to-point transmission, consensus mechanism, encryption algorithm and the like. Blockchains are essentially a de-centralized database, which is a string of data blocks that are generated in association using cryptographic methods. Each data block contains information of a batch of transactions, validity verification information for verifying the transaction information and verification information of adjacent blocks. The blockchain domain name is based on a blockchain domain name service and is used for mapping the blockchain address or the public key, so that memorization and use of the blockchain address or the public key are facilitated.

Disclosure of Invention

One or more embodiments of the present specification describe a blockchain domain name registration proxy method and apparatus, a data proxy method and apparatus, and a proxy scheme for proxy of blockchain domain name registration and manipulation of data on blockchains.

In a first aspect, embodiments of the present disclosure provide a blockchain domain name registration proxy method, performed by a proxy, including the steps of:

receiving a proxy request for registering a blockchain domain name by a user, wherein the proxy request comprises an account domain name and an account public key;

generating proxy acknowledgement information based on the proxy request;

receiving and verifying a confirmation signature of the user to the agent confirmation information;

when the confirmation signature passes verification, constructing a blockchain transaction registered by a blockchain domain name based on the account domain name and an account public key, wherein the blockchain transaction registered by the blockchain domain name comprises the account domain name and the account public key;

and signing the blockchain transaction registered by the blockchain domain name by using a private key of a preset proxy account, and submitting the signed transaction to the blockchain.

In a second aspect, the present embodiments provide a blockchain domain name registration proxy device,

comprising the following steps:

the system comprises a request receiving module, a request processing module and a processing module, wherein the request receiving module is used for receiving a proxy request of a user registration blockchain domain name, and the proxy request comprises an account domain name and an account public key;

The confirmation module is used for generating proxy confirmation information based on the proxy request, and receiving and verifying a confirmation signature of the user on the proxy confirmation information;

the construction module is used for constructing blockchain transactions registered by the blockchain domain name based on the account domain name and the account public key when the verification signature passes, wherein the blockchain transactions registered by the blockchain domain name comprise the account domain name and the account public key;

and the registration module is used for signing the blockchain transaction registered by the blockchain domain name by using a private key of a preset proxy account and submitting the signed transaction to the blockchain.

In a third aspect, the present embodiments provide a data proxy method, performed by a proxy,

the method comprises the following steps:

receiving a proxy request of a user, wherein the proxy request comprises proxy data;

generating proxy acknowledgement information based on the proxy request;

when the confirmation signature passes the verification, constructing a blockchain transaction based on the proxy data;

and signing the blockchain transaction by using a private key of a preset proxy account, and submitting the blockchain transaction to a blockchain.

In a fourth aspect, embodiments of the present description provide a data proxy apparatus,

Comprising the following steps:

a request receiving unit, configured to receive a proxy request of a user, where the proxy request includes proxy data;

the confirming unit is used for generating proxy confirming information based on the proxy request, and receiving and verifying a confirming signature of a user on the proxy confirming information;

a construction unit for constructing a blockchain transaction based on the proxy data when the validation signature verification passes;

and the registration unit is used for signing the private key of the block chain transaction using the preset proxy account and submitting the private key to the block chain.

In a fifth aspect, embodiments of the present description provide an electronic device comprising a processor and a memory;

the processor is connected with the memory;

the memory is used for storing executable program codes;

the processor runs a program corresponding to the executable program code by reading the executable program code stored in the memory for performing the method of any one of the above aspects.

In a sixth aspect, embodiments of the present description provide a computer-readable storage medium, on which is stored a computer program that, when executed by a processor, implements the method described in one or more embodiments of the present description.

The technical scheme provided by some embodiments of the present specification has the following beneficial effects:

in one or more embodiments of the present disclosure, the blockchain domain name registration proxy method and apparatus provided herein can implement blockchain domain name registration in a corresponding blockchain system only by a public key held and a blockchain domain name desired to be registered, without a user opening a wallet of the corresponding blockchain system. The intelligent contracts issued on the blockchain can automatically realize the proxy process of the blockchain domain name registration, so that the efficiency of the blockchain domain name registration proxy is improved, and the delay of the blockchain domain name registration proxy is reduced. By associating the unique number and the state identifier with the proxy request, the identification and the state tracking of the proxy request are realized, and the management of the proxy request is realized.

Other features and advantages of one or more embodiments of the present disclosure are further disclosed in the following detailed description, the accompanying drawings.

Drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present description, the drawings that are required in the embodiments will be briefly described below, and it is apparent that the drawings in the following description are only some embodiments of the present description, and other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.

Fig. 1 is a schematic diagram of an application scenario of a blockchain domain name registration proxy method according to an embodiment of the present disclosure.

Fig. 2 is a flowchart of a blockchain domain name registration agent method according to an embodiment of the present disclosure.

FIG. 3 is a timing diagram of a blockchain domain name registration proxy method in accordance with embodiments of the present disclosure.

Fig. 4 is a schematic diagram of a smart contract scenario according to an embodiment of the present disclosure.

Fig. 5 is a flowchart of a method for generating proxy acknowledgement information according to an embodiment of the present disclosure.

Fig. 6 is a schematic diagram of a blockchain domain name registration agent device according to an embodiment of the present disclosure.

FIG. 7 is a schematic diagram of a blockchain domain name registration agent device with intelligent contracts in accordance with embodiments of the present disclosure.

Fig. 8 is a flowchart of a data proxy method according to an embodiment of the present disclosure.

Fig. 9 is a flowchart of a method for generating proxy acknowledgement information based on a proxy request according to an embodiment of the present disclosure.

Fig. 10 is a schematic diagram of a data proxy device according to an embodiment of the present disclosure.

FIG. 11 is a schematic diagram of a data proxy device with smart contracts in an embodiment of the present disclosure.

Fig. 12 is a schematic diagram of an electronic device according to an embodiment of the present disclosure.

Detailed Description

The technical solutions of the embodiments of the present specification are explained and illustrated below with reference to the drawings of the embodiments of the present specification, but the following embodiments are only preferred embodiments of the present specification, and not all the embodiments. Based on the examples in the implementation manner, those skilled in the art may obtain other examples without making any creative effort, which fall within the protection scope of the present specification.

The terms first, second, third and the like in the description and in the claims and in the above drawings are used for distinguishing between different objects and not necessarily for describing a particular sequential or chronological order. Furthermore, the terms "comprise" and "have," as well as any variations thereof, are intended to cover a non-exclusive inclusion. For example, a process, method, system, article, or apparatus that comprises a list of steps or elements is not limited to only those listed steps or elements but may include other steps or elements not listed or inherent to such process, method, article, or apparatus.

In the following description, directional or positional relationships such as the terms "inner", "outer", "upper", "lower", "left", "right", etc., are presented merely to facilitate describing the embodiments and simplify the description, and do not indicate or imply that the devices or elements referred to must have a particular orientation, be constructed and operate in a particular orientation, and therefore should not be construed as limiting the description.

Before introducing the technical scheme of the embodiments of the present specification, application scenarios of one or more embodiments of the present specification are described.

Noun interpretation:

agent party

The agent 200 referred to in this specification relates to a provider that establishes an information interaction channel between the user 300 and the blockchain 100, implementing data manipulation functions on the blockchain 100 without the user 300 having a corresponding blockchain account. The agent 200 has a corresponding blockchain account, also known as an electronic wallet, blockchain wallet. The agent 200 performs its function through a server or through an intelligent contract 201 published on the blockchain 100.

Proxy request

The proxy request referred to in this specification relates to the transmission of information necessary to complete the proxy to the proxy 200. What response to the proxy request is required or what action is performed, there are two ways to determine. The first way is that the proxy 200 accepts only one proxy response or operation, and executes the proxy response or operation for the received proxy request; alternatively, the agent 200 automatically matches the supported response or operation according to the information contained in the received agent request and the necessary information required for each response or operation, and feeds back error reporting information when the matched response or operation cannot be obtained.

Account domain name

The account domain name referred to in this specification relates to a string provided by the user 300 for referring to the public key of an account. The account domain name is validated upon completion of registration with the domain name registration service on blockchain 100. In some cases the domain name registration service of blockchain 100 requires that the account domain name have a specified suffix, the suffix of the account domain name of domain name registration service ENS (Ethereum Name Service) on the exemplary ethernet is.

Validating signatures

The validation signature referred to in this specification relates to the signature of the received agent validation information by the user 300 using a private key. The agent acknowledgement information is provided by agent 200 to user 300. In some cases the proxy validation information includes the entire content of the proxy request, in other cases the proxy validation information includes one or more of a timestamp, a unique number, or a status identification in addition to the entire content of the proxy request.

Proxy account

The proxy account referred to in this specification relates to a blockchain account that proxy 200 owns on the blockchain. The blockchain account is used to perform operations associated with the proxy request to commit transactions at the blockchain.

Transfer into account

The transfer-in account referred to in this specification relates to a blockchain account set by the agent 200 for the transfer-in party as a transaction generated by the agent account. In some blockchains 100, the transfer account and the proxy account may be the same account, i.e., a portion of the blockchain allows for self-transactions.

Application scenario introduction:

blockchain 100 is an open shared, commonly maintained, decentralized ledger. The information recorded on the blockchain is transaction-based, i.e., each block on the blockchain 100 records transactions that occur on the blockchain 100 during a corresponding period of time. Storing information on the blockchain 100 is accomplished by way of information accompanying the blockchain transaction. One of the reasons for the data recording methods using transactions as carriers is that it is not free and cost-free to record data on the blockchain 100. Corresponding commissions can be conveniently paid for the carrier by the transaction, and opportunities to be preferentially recorded by the blockchain 100 are contended by how much commission is set. Types of blockchains 100 include public chains, federated chains, and private chains, depending on the degree of openness. The openness of the blockchain 100 affects the rules of the transaction and consensus mechanisms running on the joining blockchain and blocks. Wherein the open degree of the public chain is the highest, and the threshold is the lowest. Because rules are most open, many creative applications based on blockchains are often proposed and generalized on the public chain, with the public chain users 300 being the most. The federation and private chains are less open and joining the federation and private chains typically requires an audit process under the wire.

When joining the public chain, only the account public key needs to be provided, and other blockchain users are informed of the account public key. This account public key is also commonly used directly as a wallet address, or account address, sometimes referred to as a wallet or account for short. The hash value of the account public key is used as an account address on part of the blockchain. Assets on the blockchain are in a certified form. Typically, each blockchain has one pass, e.g., the pass of the bitcoin chain is bitcoin and the pass of the ethernet is ethernet.

The public key, the account, that has just been provided is not authenticated under the name. Therefore, before other blockchain users transfer the general certificate to the account, the transaction cannot be actively completed because the handling fee cannot be paid. I.e., transaction or record functions of the blockchain cannot be actively used. With the rapid development of blockchain technology and blockchain applications, blockchains are very diverse, and the population of blockchain users is also increasingly large. For one blockchain user, when it is desired to use the functions or applications of other blockchains 100, it is desired to provide account addresses to the corresponding blockchains, while it is also desired to obtain some evidence of the corresponding blockchains into the account addresses provided by the user. Providing a public key, while easy to do, obtaining a certificate into the provided account address is a cumbersome process. When there are many blockchains, a complex and time-consuming task is created.

Illustratively, when the user 300 wishes to record some information through the blockchain. If the user 300 has an account with the blockchain, the user 300 issues a transaction, the transfer account and the transfer account of the transaction are both self, and information which is expected to be recorded by the blockchain is loaded in the carrying information of the transaction. After the transaction is submitted to the nodes of the blockchain after the commission is set, after waiting for a period of time, the corresponding transaction can be found by polling the blocks of the blockchain 100, and the corresponding transaction and the carried information are checked and recorded in the blockchain 100. In some blockchain consensus schemes, there is an error rollback scheme that requires waiting for enough time to ensure that transactions and carried information are recorded into the blockchain. In some blockchains, some users 300 handle rollback by waiting 6 block heights.

But when the user 300 does not have an account on the blockchain, or has an account on the blockchain but the generic certificate under the account name is 0, or is insufficient to pay the commission of one transaction, or can pay only a small commission resulting in a low priority with unacceptable delay. At this point, the user 300 will not be able to implement the use of blockchains as desired. To enable a user 300 to transact on different blockchains or to use functions that other blockchains have, one or more embodiments of the present specification provide methods and apparatus for data brokering on blockchain 100. Referring to fig. 1, the problem that the user 300 lacks a pass and cannot use the blockchain function is solved by proxy. The user 300 sends the information to be carried to the agent 200, and the agent 200 initiates a transaction using its account on the blockchain, with the information to be carried sent by the user 300 attached to the transaction. Thus storing information that user 300 needs to submit in the blockchain.

Illustratively, the public key, which is an account address on the blockchain, is typically of a longer length, and an exemplary account address on, for example, a bitcoin chain is: 1PTFYUG6 nCzRByoRfGT 5kefUNuZjNF84o is a string of characters comprising numbers, capital letters and lowercase letters. Not only is hard to memorize, but also a better way to use is by copying the form of the paste. If manual input is required, the method is not only tedious but also prone to error. In order to solve the problem that the blockchain account address is difficult to memorize and inconvenient to use, the technology of the blockchain domain name is proposed in the field. Registering a blockchain domain name also requires that an account with a pass be used under the name on the corresponding blockchain to be implemented. One or more embodiments of the present specification provide a scheme for performing blockchain domain name registration on a blockchain by proxy registration. Referring to fig. 2, the blockchain domain name technology is a technology for establishing a mapping relationship between a custom string and an account address, and provides a service for resolving a blockchain domain name into a corresponding account address. The custom character string is the blockchain domain name. Illustratively, account addresses: 1PTFYUG6nCzRrByoRfGT5kefUNuZjNF84o, registered domain name love. On the corresponding blockchain, the love.bit can refer to 1 PTFYIG 6 nCzRByoRfGT 5kefUNuZjNF84o, and when the account address needs to be filled, the love.bit is filled. The account address referred to in this specification is the user public key.

The process of registering and proxy for blockchain domain names is mainly completed by the proxy 200. The present specification provides a blockchain domain name registration agent 200 method, which is executed by the agent 200, please refer to fig. x3, and includes the steps of:

step 102) receiving a proxy request for registering a blockchain domain name by a user, wherein the proxy request comprises an account domain name and an account public key;

step 104) generating proxy confirmation information based on the proxy request;

step 106) receiving and verifying a confirmation signature of the user on the proxy confirmation information;

step 108) constructing a blockchain transaction registered by a blockchain domain name based on the account domain name and an account public key when the verification signature passes, wherein the blockchain transaction registered by the blockchain domain name comprises the account domain name and the account public key;

step 110), signing the blockchain transaction registered by the blockchain domain name by using a private key of a preset proxy account, and submitting the signed transaction to the blockchain.

Specifically, the user 300 sends a proxy request for registering a blockchain domain name to the proxy 200, where the proxy request needs to include at least the blockchain domain name ac_name to be registered and the account public key of the user 300. After receiving the proxy request, the proxy 200 generates a unique number for the proxy request, and generates proxy confirmation information based on the unique number and the proxy request. Since the user knows the content of the proxy request, the proxy 200 may also send only the unique number to the user. The user generates a confirmation signature, and the confirmation content is signed by using the private key of the user in a mode of generating the confirmation signature. The validation may include only the unique number, or the unique number and the blockchain domain name ac_name to be registered, or the unique number and the account public key of the user, or the unique number, the blockchain domain name ac_name to be registered, and the account public key of the user. The validation signature shown in fig. 2 relates to sign (order_id, ac_name), with sign () representing a signature function. The user sends a confirmation signature to the agent 200. The agent 200 verifies the validation signature by: decrypting the validation signature using the user-provided account public key will decrypt the validation content. And checking whether the decrypted confirmation content accords with the corresponding proxy request or not, and passing the verification. After confirming that the signature verification is passed, the agent 200 initiates a transaction by using its account on the blockchain 100, and completes the registration of the blockchain domain name through the transaction, that is, registers the received blockchain domain name ac_name and the account public key pubkey of the user on the corresponding blockchain.

The service in which the blockchain provides blockchain nameplates is referred to as the blockchain nameplate service. That is, the registration of the domain name on the blockchain is accomplished by invoking the blockchain domain name service. On the other hand, even if no special blockchain domain name service exists on the blockchain, the blockchain domain name service can be realized by upgrading the consensus mechanism and prescribing the relevant terms about the blockchain domain name in the consensus mechanism. For example, in the information carried by the transaction, the blockchain domain name and the account public key data pair are provided according to a preset format, namely, the declaration of a blockchain domain name is indicated, and other blockchain link points accept the declaration, so that the registration of the blockchain domain name can be completed. The same blockchain domain name is obtained by the claiming the previous user. Each blockchain node needs to poll the blockchain, and separately store the blockchain domain name and account public key data pair attached to the transaction in the block, and establish an index. So that each blockchain node is able to provide blockchain domain name service. Other implementations of blockchain functions and blockchain services disclosed in the art can be used in the blockchain domain name registration proxy method 200 described in this specification.

One way the blockchain provides blockchain domain name service is through intelligent contracts 201 that are published and run on the blockchain. The intelligent contract 201 receives the blockchain domain name ac_name and the account public key pubkey of the user, and after receiving a corresponding number of certificates as fees, the intelligent contract 201 associates the blockchain domain name ac_name with the account public key pubkey of the user and stores the associated blockchain domain name ac_name and the account public key pubkey in a registration domain name table of the intelligent contract 201, namely, the completion of registration of the blockchain domain name is indicated. When the blockchain domain name cannot be registered due to the duplicate name of the blockchain domain name registered with other blockchain users, the corresponding blockchain domain name service gives feedback, and the registration result of the blockchain domain name of the user is informed of registration failure based on the feedback. After prompting the user to replace the blockchain domain name, registering again. The blockchain domain name registration service of part of the blockchains is realized by a community organization, the community organization can provide the blockchain domain name registration service for the blockchain users by issuing the intelligent contracts 201, and the blockchain domain name registration service for the blockchain users can also be realized by establishing a server of the community organization and interacting the server with the blockchains. To provide confidence, the server's operational data should be periodically verified through the blockchain.

On the other hand, in further embodiments, the method is performed by the intelligent contract 201 issued by the agent 200 on the blockchain. Referring to FIG. 4, the smart contract 201 published on the blockchain is a piece of code written on the blockchain. The smart contract 201 can interact with the blockchain as well as access networks or hosts outside of the blockchain. In the smart contract 201, code is automatically executed once some event triggers a term in the contract. A technique called a predictor is used to take care of the triggering of events. The predictive machine can actively read or receive external information. That is, the predetermined condition is satisfied, and the corresponding code is executed without artificial control. Each blockchain node has the complete code of the intelligent contract 201, and each blockchain node is independently executed, and the executed results are unified according to a preset consensus mechanism. The execution environment of the smart contract 201 is not just a blockchain, but execution of the smart contract 201 on a blockchain has reliability and reliability provided by the blockchain and is thus widely used. The blockchain domain name registration agent 200 method writes the intelligent contract 201 in the form of a code, and issues the intelligent contract 201 onto the blockchain. The user interacts with the intelligent contract 201, i.e., the blockchain domain name registration agent method 200 can be implemented by the intelligent contract 201 to complete the process of registering the blockchain domain name on the blockchain for the user. Specifically, the smart contract 201 sets a preset reception table and proxy request reception address for receiving and storing a proxy request transmitted by the user. The receive table stores account domain names and account public keys. And after the designated address receives the proxy request sent by the user, analyzing whether the proxy request contains the account domain name and the account public key, and if so, writing the corresponding account domain name and the account public key into a receiving table for storage. Agent acknowledgement information is then generated, either shown on the blockchain, or written to the specified address. When presented on the blockchain, users poll the blockchain. When writing the specified address, the user can obtain the proxy confirmation information by reading the content of the specified address. After signing the proxy confirmation information, the user writes the confirmation signature into the designated receiving address of the intelligent contract 201, and the intelligent contract 201 periodically pulls information from the designated receiving address and can obtain the corresponding confirmation signature after checking. After verifying the confirmation signature, the intelligent contract 201 automatically generates a transaction for registering the blockchain domain name, signs the transaction by using the private key of the transaction, and sends the transaction to the blockchain, namely, the user submits the registration of the blockchain domain name. When the block of the blockchain records the related transaction, the registration of the blockchain domain name is realized. When a blockchain domain name cannot be registered due to the duplicate of a blockchain domain name registered with other blockchain users, the corresponding blockchain domain name service will give feedback, based on which the intelligent contract 201 informs the user that the registration result of the blockchain domain name is a registration failure. After prompting the user to replace the blockchain domain name, registering again. Because the blockchain domain name is public on the blockchain, the related check is easier to carry out before the user submits the proxy request for the registration of the blockchain domain name. When blockchain domain name renaming occurs, other means known in the art may be employed and are not limited to the means disclosed in this specification.

In another aspect, referring to fig. 5, in another embodiment, a method for generating proxy acknowledgement information based on the proxy request includes the steps of:

step 202) requesting association of a unique number and a status identifier for the agent;

step 204), generating agent confirmation information based on the unique number, the account domain name and the account public key, sending the agent confirmation information to a user, and configuring the state identifier as to-be-confirmed;

step 206) when the confirmation signature is received within a preset time period and verification is passed, configuring the state identifier as to-be-registered;

step 208) when the confirmation signature is received within a preset time period and verification fails, configuring the state identifier to be corrected, and generating agent confirmation information again to be sent to the user;

step 210) if the confirmation signature is not received within the preset time period or the verification of the received confirmation signature is not passed after the preset time period is finished, configuring the state identifier as timeout.

And generating confirmation information and sending the confirmation information to a user for signing, and generating the confirmation signature, so that the agent requests which are not prepared can be screened out, and the pressure of the blockchain is relieved. The agent request can be tracked by means of the state identifier, so that the agent request can be managed. There are different processing methods for proxy requests in different states, and the processing method is not limited to the processing method disclosed in this embodiment. It is also possible to provide a direct setting of the status flag as error and termination of the proxy request, prompting the user to initiate a proxy request again, when the received validation signature is not validated.

In another aspect, in further embodiments, a method of constructing a blockchain transaction for blockchain domain name registration based on the proxy request includes the steps of:

generating a transaction, wherein a transfer account of the transaction is the proxy account, a transfer account of the transaction is a preset account, carrying information of the transaction comprises an account domain name and an account public key, configuring the state identifier as a to-be-signed block chain transaction registered by the block chain domain name is obtained based on the transaction.

The proxy account is a blockchain account that proxy 200 is able to manage. The agent 200 may provide multiple agent accounts to increase the efficiency of processing agent requests as a whole. The aforementioned blockchain domain name registration agent 200 method is implemented in the agent 200 using a distributed device, with multiple agent accounts being an alternative embodiment. The distributed devices can share a proxy account, and only each device in the distributed devices needs to store a private key. The use of multiple proxy accounts has a relatively good effect because of some risk associated with the transmission of the private key.

In another aspect, in further embodiments, the blockchain is polled after submitting the blockchain transaction signature registered by the blockchain domain name to the blockchain;

And if the blockchain transaction registered by the blockchain domain name is queried by the blockrecords of the blockchain, continuously polling the blockchain until the blockchain meets the preset transaction confirmation condition.

To cope with the rolling back of the blockchain, when the blockchain transaction registered by the blockchain domain name is queried to be recorded by the blockchain of the blockchain, the query is further needed to be continued until the height of the blockchain is increased by a preset amount, and the probability of the rolling back of the blockchain can be considered to be low when the height of the blockchain is increased by 6 in an exemplary manner. That is, after the transaction validation condition is the blockchain transaction that records the blockchain domain name registration, the blockchain generates 6 new blocks. When the blockchain transaction in which the blockchain domain name registration is recorded cannot be queried within a set time, the blockchain transaction in which the blockchain domain name registration is required to be re-submitted. Otherwise, the proxy registration request of the user is caused to be delayed and not completed. As a recommendation, when the blockchain transaction registered by the blockchain domain name is re-submitted, the set commission fee is required to be increased. If the blockchain transaction is recorded by the blockchain after resubmitting, a loss of one time of handling is caused, and the loss is acceptable for balancing the agent request of the user to be completed in a proper time. By polling the average transaction charges for the current period of the blockchain, the appropriate charge setting value can be obtained. In some embodiments, a wait of 10 minutes may be set as a preset transaction confirmation condition. Due to the higher handling costs, there is a greater opportunity to be recorded by blocks of the faster blockchain. Therefore, when receiving the user agent request, the user agent can also receive the amount of the commission which the user is willing to provide at the same time, and set the commission of the blockchain transaction registered by the blockchain domain name according to the amount of the commission provided by the user.

generating a transaction, wherein a transfer account of the transaction is the proxy account, a transfer account of the transaction is a preset account, carrying information of the transaction comprises an account domain name and an account public key, and obtaining a blockchain transaction registered by a blockchain domain name based on the transaction. And submitting the blockchain transaction to the blockchain domain name service based on the blockchain transaction of which the blockchain domain name is registered according to the manner of providing the blockchain domain name service on the blockchain.

In another aspect, the present disclosure provides a blockchain domain name registration agent device, referring to fig. 6, including:

a request receiving module 21, configured to receive a proxy request for registering a blockchain domain name for a user, where the proxy request includes an account domain name and an account public key;

a validation module 22, configured to generate proxy validation information based on the proxy request, and receive and verify a validation signature of the proxy validation information by a user;

a constructing module 23, configured to construct a blockchain transaction with a blockchain domain name registration based on the account domain name and the account public key when the verification signature passes, where the blockchain transaction with the blockchain domain name registration includes the account domain name and the account public key;

The registration module 24 is configured to sign the blockchain transaction registered by the blockchain domain name using a private key of a preset proxy account and submit the signed transaction to the blockchain.

The request receiving module 21, the confirmation module 22, the construction module 23 and the registration module 24 may be located in the same device, server cluster or platform, or may be operated in a distributed manner in different devices, servers, server clusters or platforms, and perform data interaction with each other through a network. Where registration module 24 stores the private key of the proxy account, it should be secure enough. When the number of faced proxy requests is large, the request receiving module 21, the confirming module 22 and the constructing module 23 can be located in a server with low security, and firewall measures with low security can be set. The registration module 24 is located on a server with higher security, and only allows access to the server where the construction module 23 is located, and at the same time sets firewall measures with higher security. The server carrying registration module 24 only allows the steps performed by registration module 24 to be a more preferred embodiment.

On the other hand, in another embodiment, referring to fig. 7, the system further includes an intelligent contract issuing module 25, where the intelligent contract issuing module 25 is configured to issue an intelligent contract 201 on a blockchain, and the request receiving module 21, the validating module 22, the constructing module 23, and the registering module 24 all run on the intelligent contract 201. The smart contract issuing module 25 issues the smart contract 201 by constructing the smart contract and then onto the blockchain. After a period of time, the blockchain receives and runs the smart contract 201, i.e., the deployment of the request receiving module 21, the validating module 22, the constructing module 23, and the registering module 24 is completed. And when running on the blockchain, the request receiving module 21, the confirmation module 22, the construction module 23 and the registration module 24 have higher security due to the security provided by the blockchain. Processing efficiency is limited by the efficiency of blockchain operation and execution of the smart contract 201 on the blockchain incurs a corresponding cost, which would result when the smart contract 201 is operated on the blockchain.

On the other hand, in further embodiments, the confirmation module 22 includes:

the confirmation information generation sub-module is used for requesting the agent to associate the unique number with the state identifier, generating agent confirmation information based on the unique number, the account domain name and the account public key, sending the agent confirmation information to the user, and configuring the state identifier to be confirmed;

and the confirmation signature receiving sub-module is used for configuring the state identifier to be registered when the confirmation signature is received within a preset time period and verification is passed, configuring the state identifier to be corrected when the confirmation signature is received within the preset time period and verification is not passed, generating agent confirmation information again and sending the agent confirmation information to a user, and configuring the state identifier to be overtime when the confirmation signature is not received within the preset time period or the received confirmation signature is not verified after the preset time period is finished.

In another aspect, the present disclosure provides a method of a data proxy 200, performed by the proxy 200, please refer to fig. 8, comprising the steps of:

step 302) receiving a proxy request of a user, the proxy request comprising proxy data;

step 304) generating proxy acknowledgement information based on the proxy request;

Step 306) receiving and verifying a confirmation signature of the user to the agent confirmation information;

step 308) when the validation signature verification passes, constructing a blockchain transaction based on the proxy data;

step 310) submitting the blockchain transaction to the blockchain after signing the blockchain transaction by using a private key of a preset proxy account.

For example, if the user needs to submit the information to the blockchain for certification, the information to be certified is proxy data. The information requiring the certification is transmitted to the agent 200, and the agent 200 generates agent confirmation information including the information requiring the certification or a hash value of the information requiring the certification and an agent identification. After the user checks, a confirmation signature is generated using the private key signature, and the confirmation signature is provided to the agent 200. The agent 200 verifies that the signature passes, and issues a blockchain transaction on the blockchain, and the transaction carries information provided by the user and needing to be stored. When the blockchain transaction is recorded by the block, the process of submitting the information needing to be stored to the blockchain for storing is completed.

Still another example, a user may need to transfer credentials to a target user account with the blockchain, but the user does not have an account with the blockchain. The user sends the account address and the number of passes of the target user account as a proxy request to the proxy party 200. The agent 200 generates agent confirmation information to be transmitted to the user, the agent 200 is provided with the agent after the user signs the agent using the private key, and the agent 200 constructs a blockchain transaction based on the agent data after verifying the confirmation signature. Namely generating blockchain transactions and transferring corresponding quantity of the general certificates to the target user addresses. The user needs to pay the fee to the agent 200, and the specific payment process is completed through other settlement means.

On the other hand, in further embodiments, the data broker 200 method is performed by a smart contract 201 published by the broker 200 on a blockchain. The intelligent contract 201 can automatically complete the proxy request of the user, and has higher execution efficiency and reliability. The smart contract 201 is capable of receiving and executing execution code provided by a user at his own time, thereby enabling the user to customize the blockchain style that needs to be used. The specific execution code may be obtained by means disclosed in the art.

In another aspect, referring to fig. 9, in another embodiment, a method for generating proxy acknowledgement information based on the proxy request includes the steps of:

step 402) requesting association of a unique number and a status identifier for the agent;

step 404) generating agent confirmation information based on the unique number and the agent data, and sending the agent confirmation information to a user, and configuring the state identifier as to-be-confirmed;

step 406) when the confirmation signature is received within a preset time period and verification is passed, configuring the state identifier as to-be-registered;

step 408), when the confirmation signature is received within a preset time period and verification fails, configuring the state identifier to be corrected, and generating agent confirmation information again to be sent to the user;

Step 410) if the confirmation signature is not received within the preset time period or the verification of the received confirmation signature is not passed after the preset time period is finished, configuring the state identifier as timeout. And managing the proxy request by means of the state identifier, and performing different operations on the proxy request in different states. The manner in which the proxy request is operated is not limited to the exemplary processing manner provided in this embodiment. For example, for proxy requests to be corrected, the proxy request may be processed in a directly terminated manner and the user prompted to submit the proxy request again.

In another aspect, in further embodiments, a method of constructing a blockchain transaction based on the proxy data includes the steps of:

generating a transaction, wherein a transfer account of the transaction is the proxy account, a transfer account of the transaction is a preset account, carrying information of the transaction comprises proxy data, the state identifier is configured to be signed, and blockchain transaction is obtained based on the transaction.

generating a transaction, wherein a transfer account of the transaction is the proxy account, a transfer account of the transaction is a preset account, carrying information of the transaction comprises proxy data, and blockchain transaction is obtained based on the transaction.

In another aspect, the present disclosure provides a data proxy device, referring to fig. 10, comprising:

a request receiving unit 41 for receiving a proxy request of a user, the proxy request including proxy data;

a validation unit 42 for generating proxy validation information based on the proxy request, receiving and verifying a validation signature of the proxy validation information by a user;

a construction unit 43 for constructing a blockchain transaction based on the proxy data when the validation signature passes;

the registration unit 44 is configured to sign the blockchain transaction using a private key of a preset proxy account and submit the signed transaction to the blockchain. The request receiving unit 41, the confirmation unit 42, the construction unit 43 and the registration unit 44 may be located in the same device, server cluster or platform, or may be operated in a distributed manner in different devices, servers, server clusters or platforms, and perform data interaction with each other through a network. Where registration unit 44 stores the private key of the proxy account, it should be secure enough.

On the other hand, in further embodiments, the smart contract 201 issuing unit 45 is also included. Referring to fig. 11, the smart contract 201 issuing unit 45 is configured to issue a smart contract 201 on a blockchain, and the request receiving unit 41, the validating unit 42, the constructing unit 43, and the registering unit 44 all run on the smart contract 201.

On the other hand, in another embodiment, the confirmation unit 42 includes:

the confirmation information generation subunit is used for associating the unique number with the state identifier for the proxy request, generating proxy confirmation information based on the unique number and proxy data and sending the proxy confirmation information to a user, and configuring the state identifier to be confirmed;

and the confirmation signature receiving subunit is used for configuring the state identifier as to-be-registered when the confirmation signature is received within a preset time period and verification is passed, configuring the state identifier as to-be-corrected when the confirmation signature is received within the preset time period and verification is not passed, generating agent confirmation information again and sending the agent confirmation information to a user, and configuring the state identifier as overtime when the confirmation signature is not received within the preset time period or the received confirmation signature verification is not passed at the end of the preset time period.

Please refer to fig. 12, which is a schematic diagram illustrating a structure of an electronic device according to an embodiment of the present disclosure.

As shown in fig. 12, the electronic device 500 may include at least one processor 501, at least one network interface 504, a user interface 503, a memory 505, and at least one communication bus 502. Wherein the communication bus 502 may be used to enable connectivity communication of the various components described above. The user interface 503 may include keys, and the optional user interface may also include a standard wired interface, a wireless interface, among others. The network interface 504 may include, but is not limited to, a bluetooth module, an NFC module, a Wi-Fi module, and the like. Wherein the processor 501 may include one or more processing cores. The processor 501 utilizes various interfaces and lines to connect various portions of the overall electronic device 500, perform various functions of the routing device 500 and process data by executing or executing instructions, programs, code sets, or instruction sets stored in the memory 505, and invoking data stored in the memory 505. Alternatively, the processor 501 may be implemented in at least one hardware form of DSP, FPGA, PLA. The processor 501 may integrate one or a combination of several of a CPU, GPU, modem, etc. The CPU mainly processes an operating system, a user interface, an application program and the like; the GPU is used for rendering and drawing the content required to be displayed by the display screen; the modem is used to handle wireless communications.

It will be appreciated that the modem may not be integrated into the processor 501 and may be implemented by a single chip.

The memory 505 may include RAM or ROM. Optionally, the memory 505 comprises a non-transitory computer readable medium. Memory 505 may be used to store instructions, programs, code sets, or instruction sets. The memory 505 may include a stored program area and a stored data area, wherein the stored program area may store instructions for implementing an operating system, instructions for at least one function (such as a touch function, a sound playing function, an image playing function, etc.), instructions for implementing the above-described various method embodiments, etc.; the storage data area may store data or the like referred to in the above respective method embodiments. The memory 505 may also optionally be at least one storage device located remotely from the processor 501. The memory 505, which is a type of computer storage medium, may include an operating system, a network communication module, a user interface module, and application programs. The processor 501 may be configured to invoke the applications stored in the memory 505 and to perform the methods of one or more of the embodiments described above.

The present description also provides a computer-readable storage medium having instructions stored therein, which when executed on a computer or processor, cause the computer or processor to perform one or more steps of the above embodiments. The above-described constituent modules of the electronic apparatus may be stored in the computer-readable storage medium if implemented in the form of software functional units and sold or used as independent products.

The technical features in the present examples and embodiments may be arbitrarily combined without conflict.

In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When loaded and executed on a computer, produces a flow or function in accordance with embodiments of the present description, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable apparatus. The computer instructions may be stored in or transmitted across a computer-readable storage medium. The computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center by a wired (e.g., coaxial cable, fiber optic, digital subscriber line (Digital Subscriber Line, DSL)), or wireless (e.g., infrared, wireless, microwave, etc.). The computer readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that contains an integration of one or more available media. The usable medium may be a magnetic medium (e.g., a floppy Disk, a hard Disk, a magnetic tape), an optical medium (e.g., a digital versatile Disk (Digital Versatile Disc, DVD)), or a semiconductor medium (e.g., a Solid State Disk (SSD)), or the like.

When the method is realized by hardware and firmware, the method flow is programmed into a hardware circuit to obtain a corresponding hardware circuit structure, so as to realize corresponding functions. For example, a programmable logic device (Programmable Logic Device, PLD), such as a Field Programmable Gate Array (FPGA), is an integrated circuit whose logic function is determined by the user programming the device. A designer programs to "integrate" a digital system onto a PLD without requiring the chip manufacturer to design and fabricate application-specific integrated circuit chips. Moreover, nowadays, instead of manually manufacturing integrated circuit chips, such programming is mostly implemented with "logic compiler" software, which is similar to the software compiler used in program development and writing, and the original code before being compiled is also written in a specific programming language, which is called hardware description language (Hardware Description Language, HDL), but also HDL is not just one, but a plurality of. It will also be apparent to those skilled in the art that a hardware circuit implementing the logic method flow can be readily obtained by merely slightly programming the method flow into an integrated circuit using several of the hardware description languages described above.

The above-described embodiments are merely preferred embodiments of the present disclosure, and do not limit the scope of the disclosure, and various modifications and improvements made by those skilled in the art to the technical solutions of the disclosure should fall within the protection scope defined by the claims of the disclosure without departing from the design spirit of the disclosure.

Claims

1. The block chain domain name registration proxy method is executed by a proxy party and comprises the following steps:

generating proxy acknowledgement information based on the proxy request;

2. The blockchain domain name registration proxy method of claim 1,

The method is performed by an intelligent contract issued by an agent on a blockchain.

3. The blockchain domain name registration proxy method of claim 1 or 2,

the method for generating proxy confirmation information based on the proxy request comprises the following steps:

requesting an association of a unique number and a status identifier for the agent;

generating agent confirmation information based on the unique number, the account domain name and the account public key, sending the agent confirmation information to a user, and configuring the state identifier as to-be-confirmed;

when the confirmation signature is received within a preset time period and verification is passed, the state identifier is configured to be registered;

when the confirmation signature is received within a preset time period and verification fails, configuring the state identifier to be corrected, and generating agent confirmation information again to be sent to the user;

and if the confirmation signature is not received within the preset time period or the verification of the received confirmation signature is not passed after the preset time period is finished, configuring the state identifier as overtime.

4. The blockchain domain name registration proxy method of claim 3,

the method for constructing blockchain transactions for blockchain domain name registration based on the proxy request includes the steps of:

5. The blockchain domain name registration proxy method of claim 4,

submitting the blockchain transaction signature registered by the blockchain domain name to a blockchain, and then polling the blockchain;

6. The blockchain domain name registration proxy method of claim 1 or 2,

generating a transaction, wherein a transfer account of the transaction is the proxy account, a transfer account of the transaction is a preset account, carrying information of the transaction comprises an account domain name and an account public key, and obtaining a blockchain transaction registered by a blockchain domain name based on the transaction.

7. A blockchain domain name registration proxy device,

comprising the following steps:

8. The blockchain domain name registration proxy device of claim 7,

the system further comprises an intelligent contract issuing module, wherein the intelligent contract issuing module is used for issuing intelligent contracts on a blockchain, and the request receiving module, the confirmation module, the construction module and the registration module are all operated on the intelligent contracts.

9. The blockchain domain name registration proxy device of claim 7 or 8,

the confirmation module includes:

10. The data proxy method is executed by a proxy side,

the method comprises the following steps:

generating proxy acknowledgement information based on the proxy request;

11. The data proxy method of claim 10,

the data proxy method is performed by intelligent contracts issued by the proxy on the blockchain.

12. The data proxy method of claim 10 or 11,

generating agent confirmation information based on the unique number and the agent data, sending the agent confirmation information to a user, and configuring the state identifier as to-be-confirmed;

13. The data proxy method of claim 12,

the method for constructing blockchain transactions based on the proxy data includes the steps of:

14. The data proxy method of claim 10 or 11,

15. The data proxy device is provided with a data proxy device,

comprising the following steps:

16. The data proxy device of claim 15,

the system further comprises an intelligent contract issuing unit, wherein the intelligent contract issuing unit is used for issuing intelligent contracts on a blockchain, and the request receiving unit, the confirmation unit, the construction unit and the registration unit all run on the intelligent contracts.

17. The data proxy device of claim 15 or 16,

the confirmation unit includes:

18. An electronic device including a processor and a memory;

the processor is connected with the memory;

the memory is used for storing executable program codes;

the processor runs a program corresponding to executable program code stored in the memory by reading the executable program code for performing the method according to any of claims 1-6, 10-14.

19. A computer readable storage medium having stored thereon a computer program which, when executed by a processor, implements the method of any of claims 1-6, 10-14.