aptos-labs / aptos-names-contracts

Aptos Name Service

Branches

• main branch → current dev
• mainnet branch → current mainnet deployment
• testnet branch → current testnet deployment

Testing

Unit test

Run ./sh_scripts/move_tests.sh.

Deploy to testnet

1. Run aptos init to create a new profile.
2. Update the address you want to deploy to and profile in move_publish.sh.
3. Run ./sh_scripts/move_publish.sh to deploy.

aptos-names-contracts's Issues

[Bug] Missing subdomain grace period enables sniping

@banool

Presently, renewal of an Aptos domain entails "reregistration" during a grace period: a domain has to first expire, then the holder has to "reregister" the domain

Subdomains, however, have no reregistration grace period, which means that subdomain holders are force to reregister at the moment of expiry. This process can easily be sniped by a bot or a block producer.

Hence it is suggested that subdomains implement a grace period

See core/sources/domains.move::name_is_registerable()

Feature: attach metadata to domain name resource

Any plans to add the ability to attach custom metadata such as web URLs, images, description, etc... to the domain name?

This would allow users to discover who is behind a certain domain name (e.g. by viewing their social links) or obtain more information about an address in general, which could lead to more trustworthiness when interacting with Aptos accounts.

I'm also aware a lot of other web3 domain name standards use this approach, e.g.:

• https://ens.domains (Ethereum)
• https://unstoppabledomains.com (Ethereum)
• https://find.xyz (Flow)
• https://www.sns.id (Solana)
• ...

not able to pass option into an entry fun

Currently, there is no way to pass an Option into an entry function in TS (see this SO thread). However, this force_clear_registration method expects an Option.

aptos-names-contracts/core/sources/domains.move

Line 283 in 143bdb5

public entry fun force_clear_registration(sign: &signer, subdomain_name: Option<String>, domain_name: String) acquires NameRegistryV1 {

A workaround would be turning the Option into a vector instead.