Common FAQ

Why are names registered as hashes?

Hashes provide a fixed length identifier that can easily be passed around between contracts with fixed overhead and no issues passing around variable-length strings.

Which wallets support EVMNS so far?

Currently you can add EOS EVM Mainnet by MetaMask Wallet. Read the article and know how to add the EOS EVM networks (mainnet and testnet) to your MetaMask. Then you can visit our official website to operate more.

How will EVMNS team manage and spend the funds? Will there be a foundation or transparent oversight?

Funds are sent to the EVMNS root contract, for the keyholders to determine how funds get allocated. We're considering multiple options for the long-term use of the funds, such as funding the core EVMNS team, as well as other teams building on EVMNS. There are also tax considerations to address.

Where can I manage all my .evm names?

Go to evmns.space and click on "My Domains".

Can I trade EVMNS domains on NFT exchanges?

Currently there is no NFT exchanges for trading .evm names, it will list on exchanges soon.

How can I transfer my registered domains to someone else?

You can transfer .evm names on "My Domains" interface to others.

What is the "registrant" and "controller" of a name?

The registrant is the account that owns the .evm name. They can transfer ownership to another account, and they can replace the controller address. The registrant is the owner of the NFT token that represents the name.

The controller is the account that controls day-to-day operations with the name: creating subdomains, setting the resolver and records, and so forth.

Can I change the address my name points to after I’ve bought it?

Yes, you can update the addresses and other resources pointed to by your name at any time.

Can I transfer my assets to a .evm name?

Currently not, it needs the support of reverse resolution from a name. We are reaching for this feature.

Who owns the EVMNS rootnode? What powers does that grant them?

The root node is presently owned by a contract, with keys held by EVMNS team and future will be changed into a multisig contract. With the root ownership only used to effect administrative changes, such as the introduction of a new TLD, or to recover from an emergency such as a critical vulnerability in a TLD registrar.

Since the owner of a node can change ownership of a subnode (unless they have otherwise locked it from their control), the owner of the root can change any node in the EVMNS tree. This means that the keyholders can replace the contracts that govern issuing and managing domains, giving them ultimate control over the structure of the EVMNS system and the names registered in it. However, the root key holders have locked control of the .evm registrar contract, which means that even keyholders cannot affect the ownership of .evm domains.

The keyholders are still capable of doing the followings:

• Control allocation and replacement of TLDs other than .evm - this is required to implement DNSSEC integration.

• Enable and disable controllers for the .evm registrar, which affect registration and renewal policies for .evm names.

• Update the pricing for .evm names.

• Receive and manage registration revenue.

What about foreign characters? What about upper case letters? Is any unicode character valid?

Two types of characters are invalid for registration: Chinese characters and zero-width characters. Since the EVMNS contracts only deal with hashes, they have no direct way to enforce limits on what can be registered; character length restrictions are implemented by allowing users to challenge a short name by providing its preimage to prove it’s too short.

Since the EVMNS contracts only deal with hashes, they have no direct way to enforce limits on what can be registered; character length restrictions are implemented by allowing users to challenge a short name by providing its preimage to prove it’s too short. both ‘harry.evm’ and ‘HARRY.evm’, or even <picture of my dog>.evm. However, resolvers such as browsers and wallets should apply the nameprep algorithm to any names users enter before resolving; as a result, names that are not valid outputs of nameprep will not be resolvable by standard resolvers, making them effectively useless. Dapps that assist users with registering names should prevent users from registering unresolvable names by using nameprep to preprocess names being requested for registration.

Nameprep isn’t enforced in the EVMNS system. Is this a security/spoofing/phishing concern?

It’s not enforced by the EVMNS contracts, but, as described above, resolvers are expected to use it before resolving names. This means that non-nameprep names will not be resolvable.

What are the differences between EVMNS and other naming services such as Namecoin and Handshake?

EVMNS complements and extends the usefulness of DNS with decentralized, trustworthy name resolution for Web3 resources such as blockchain addresses and distributed content, while Namecoin and Handshake are efforts to replace all or part of DNS with a blockchain-based alternative.

What kinds of behaviors are likely to result in losing ownership of a name?

The .evm registrar is structured such that names, once issued, cannot be revoked so long as an active registration is maintained.

What is the referral reward?

Referral reward is an incentive set for users to invite friends to join EVMNS and register new domain names. The inviter can get certain percentage reward from invitees registration fee, it has two levels of referral reward which relatively gains 20% and 5% from first and second level invitation.