Recent advances may lead to greater adoption of Web3 usernames


Ever since the Ethereum Name Service (ENS) was launched in 2017, Web3 users have been able to replace long strings of characters that represent a cryptographic string with a more easily remembered blockchain username or Web3 domain name. Create an address. For example, Ethereum (ETH) users can now send crypto to the network’s founder, Vitalik Buterin, at his Vitalik.eth username without knowing that his address is 0xd8da6bf26964af9d7eed9e03e53415d37aa96045.

But despite this advancement that has made it very easy to identify users, hardly anyone has taken advantage of it. There are over 200 million unique addresses on Ethereum, yet only 2.2 million .eth names had been registered as of January. This means that at least 97% of Ethereum addresses are not associated with ENS usernames.

This lack of usernames creates user experience problems in the Web3 ecosystem. Just imagine if the initial email addresses consisted of a long string of characters that looked like 0x7a16ff8270133f063aab6c9977183d9e72835428 or 0x3A7937851d67Ee2f51C959663749093Dc87D9C9a. If that were the case, email would not have survived as a practice.

But despite this early lack of adoption, there is some evidence that the tide may be turning in favor of Web3 usernames. Some recent advances in wallet and messaging apps may be onboarding more users than ever before.

One of these advancements is better wallet integration with free usernames.

Wallet integration and free username

The wallet has the ability to understand long Web3 names. According to Metamask’s changelog, it introduced the ability to send .eth names in October, 2017, right after ENS was launched. Other wallets including Coinbase Wallet, TrustWallet and others have followed suit with this feature. Some of these wallets also integrate with ENS rivals Invincible Domains, Space ID, Bonfida and others.

However, these wallets still show users a crypto address by default, as new users usually do not automatically receive a name.

In order for a user to receive crypto through their Web3 name, they must first register a username with a specialized name provider. This means figuring out which provider to use, navigating the providers’ interface, and going through the registration process.

To make matters worse, names can be expensive. ENS names typically cost $5 and expire after one year, while unstoppable domain names that don’t need to be renewed typically cost $20-$40. Compare this to how easy it is to sign up for an email address for free using Gmail, Outlook, Yahoo. etc., and it’s easy to see why most crypto users don’t have a Web3 username.

Some wallet apps are trying to solve this problem by offering free domain names to their users. For example, Coinbase Wallet allows new users to register a single .cb.id username for free once per year, and Kresus Wallet also offers its users a free .kresus username of up to 8 characters.

This practice of giving free usernames has started recently. And some popular wallets like Trustwallet and MetaMask still don’t offer the feature. But as more users onboard the Web3 ecosystem, it could lead to greater adoption of Web3 usernames over time.

Another recent advancement is instant messaging integration.

Chat messaging with web3 usernames

Some messaging apps have started implementing Web3 names as usernames, increasing the usefulness of these names beyond the payment use-case. One example is Blockscan Chat. It allows users to send instant messages to any Ethereum address or ENS username.

Caption: Blockscan chat interface. Source: Blockscan

When messages are sent using Blockscan Chat, they generate alerts on the Etherscan Block Explorer. If the recipient sees the alert and logs in to the app, they are able to read the message. The developer of the app claims that all its messages are end-to-end encrypted. So although anyone can see if a particular user has received a message, only the sender and recipient can read it.

A Web3 username is not an absolute requirement to use Blockscan Chat, as it allows users to send messages to crypto addresses as well. But the name makes it very easy for users to find each other in the app.

Grill.chat interface showing .eth name. Source: grill.chat

Another example is grill.chat, a messaging app running on a subsocial (SUB) network. When a user signs up for it for the first time, he/she is given a random username. But they can optionally attach an Ethereum wallet to their account. If they do, the app automatically changes their random username to their .eth username.

Being able to chat with other users via their web3 username is arguably a more useful feature than being able to send crypto with them.

After all, the crypto community is still small. If a crypto user needs money from friends or family, they can use traditional Web2 apps like Venmo or Apple Pay for now, as their friends and family may not know how to use Web3 wallets. Is. But if someone wants to chat specifically about crypto and web3 apps, being able to look them up by their username could be a huge advantage. This added use-case may attract more users to adopt Web3 names in the future.

Another recent advancement in Web3 names is cross-chain names.

cross-chain web3 name

When Web3 names were first invented, ENS was the only protocol that could be used to create them, and it could only be used on Ethereum.

But since then the Web3 ecosystem has grown to include many different chains. And as the number of chains grew, so did the number of naming protocols. Users can now register usernames for both Polygon (MATIC) from Unstoppable Domains, Solana (SOL) from Bonfida and Arbitrum One (ARB) from SpaceID and BNB Chain (BNB).

This fragmentation across chains can make integration difficult for wallets and block explorers and create confusion for users. For example, let’s say a person has the Polygon username newton.crypto. But when they go to register that same name on the bnb chain, they find that newton.bnb is already taken, so they register einstein.bnb instead. When a user looks up this person’s address on a Block Explorer, either name may appear, depending on which Block Explorer’s developer has chosen to display. And regardless of which one is displayed, it can cause confusion for users.

For example in this case, if a user wanted to send crypto to Newton.crypto via the BNB chain, they could simply send it to Newton.bnb, which would be the wrong recipient.

Some Web3 companies are trying to fix this problem by creating a single name for each identity in multiple chains. For example, the redefined app allows users to register a username on Arbitrum One, but use it to receive funds on 8 other chains: Polygon, Optimism (OP), BNB Chain, Solana, Bitcoin (BTC), Fantom (FTM), Moonbeam (GLMR) and nigh.

To make this feature possible, Redefine lets users write an address or username for each network in the Arbitrum smart contract via the “Manage” tab within the app. Once the addresses are listed in the contract, anyone can initiate a transaction to the correct address using the “Send” function within the app. To send money, the sender only needs to know the redefined username of the recipient, not the name or address of the recipient on a particular chain.

Redefined usernames start with @ and do not have extensions. For example, @newton and @einstein are possible redefined usernames.

did.id, also known as “.bit”, is one such project that runs on the Nervos network. It allows users to register for a .bit username that works on 39 different networks including Bitcoin, Ethereum, Polygon, Solana, Bitcoin Cash (BCH), Internet Computer (ICP), and many more. Registration can be done directly with a Nervos network wallet or indirectly using Polygon.

did.id does not feature a user interface with a “send” function. However, it integrates with nine different wallet apps, including imToken, Tokenpocket, MathWallet, Huobi Wallet, Bitkeep, HyperPay, AlphaWallet, ViaWallet, and MIBAO. Hence it is available to the remitter who use these wallets.

Cross-chain usernames are yet another new development that may drive greater adoption of web3 usernames over time.

When will usernames be captured?

Despite these advances, it is still unclear how long it will take for the mass adoption of Web3 usernames. Right now, more than 90% of Web3 addresses are not associated with any username. So there’s a big hill to climb in terms of adoption. And in the meantime, users are still required to cut and paste a complex string of characters to find a person’s Web3 identity.

There is still a lot of friction left for users of most wallet apps, including the continued high cost of enrolling users.

Nevertheless, these advances may pave the way for the mass adoption of Web3 usernames at some point in the future.