This article tells what NEO domain name binding is, why it matters to identity verification and how to bind a NEO domain name

by Zhang Zhe

Whenever I scan the QR code and transfer money, even if I transfer money to another wallet of my own, I still have to go back and check the address again every time. . If it is a QR code sent by someone else, you have to confirm the address with the person after scanning the code, for fear of transferring to the wrong person.

Anyone who has used other payment apps knows that when you transfer the money, scan the QR code given by the other party or enter the other party’s payment account; you will see the other party’s personal information for verification to prevent sending to the wrong person. However, when using the blockchain wallet, scanning code can only get a string of address. As for this address, whether it’s what we need or whether the QR code is wrong. There is no other information to verify.

(On a payment app, you can see the other party’s information when you enter the other party’s account)

(However on a blockchain wallet, with a scanned code, one can’t verify the other party’s information after obtaining the address)

Fortunately, we already have NNS as the foundation. NNS previously provided a service to map the domain name to the address, allowing the user to obtain the correct address by entering the domain name to confirm the identity of the other party at the time of transfer, and then transfer the money. But the downside of this transfer method is that the transfer via scanning a QR code or direct copying and pasting an address is faster than it, although they may make you feel they are unreliable.

So can we combine NNS and transfer via scanning the QR code to make the whole process safe and convenient?

It is already there. NNS provides the domain name binding service — a decentralized service that binds the home address of a domain name to that domain name. As long as the wallet supports this service, as long as someone scans the code to see the address, you can see the domain name it is bound to.

For most small transactions, security is a minor issue. We only need to have a thing to check the identity of the other party. It is safe and convenient to bind the domain name with the QR code. However, when we deal with some important transactions, to avoid transfer errors, we need to verify that these addresses and domain names are correct. At this time, entering the domain name for transfer can be verified to avoid errors such as mistakes and omissions.

Where can I bind my domain name now?

Regarding the setting of a binding domain name, we have now completed the setting function on the PC, and the user can operate it on the NEL web wallet. The function of setting on the mobile phone is currently under development and will be released in the O3 wallet after development.

NEL’s web wallet already supports the service of displaying domain names when transferring money. The Teemo wallet’s support is under development. We are contacting the O3 Wallet, and they will support this new NNS service in the future.

How do I set up and use this service?

1. First, you need to have your own NNS domain name. If you still have a domain name, you can go to NEL’s web wallet (https://wallet.nel.group) or bid/purchase a domain name in the O3 wallet’s NNS app.

2. Log in to the NEL web wallet (temporarily only supports the NEL web wallet) and check [Domain Management]. You can see that no domain name has been bound at this time.

3. Swipe down to see [My Neo Name]. Select the domain name you want to bind to the current address and click on “Bind domain” in the lower right corner. (I am using the .test domain on TestNet here)

4. After clicking, the confirmation message of the bound domain name will pop up. After confirming, click the button of [Bind Domain Name] and confirm the transaction. Wait for the blockchain to confirm and complete the binding.

5. After the binding is successful, you can see the domain name that has been bound.

6. In the future, as long as you enter the address when you transfer, you can see that the domain name has been bound to the address.

7. It should be noted that an address can only be bound to one domain name in the same period, and the domain name to be bound must be an unexpired domain name already owned by this address. If the domain name expires or transferred to others, or the user has it bound to another domain name during the binding period, the original binding relationship will be invalid. Also, to avoid unnecessary confusion, the bound domain name should not be mapped to other addresses than the bound address. Otherwise, the transferrer may misunderstand it.

In addition to the use of personal transfers, domain name binding can be more widely used in exchanges and gaming. These applications often require users to first recharge funds to an address and then operate on a centralized server. The current recharge page usually gives a QR code and an address. If these addresses are bound to the user’s subdomain given by these applications, the user can know what function they are using and to whom they transfer money during the whole process.

Imagine that we can add our domain name on the QR code that will be given to others later. When they scan the QR code to get the address, the address will also display its domain name. They will be relieved at once. Or when you pay for a game, scan a code and you get something like alice.buysth.xgame.neo, what else can you worry about? Isn’t it very cool!