Reverse Resolution is a feature which takes a piece of data (such as an 0x wallet address) and maps it to a given domain name. This feature enables essential integrations such as displaying a users .avax address when they connect to a dapp or making it easier to find your own wallet address from a list of such addresses.
Security Audits. Our security partners at Paladin have completed security audits on four contracts relating to forward & reverse resolution. As always, we are grateful for their help!
UI/UX Improvements for Records. We have improved the UI/UX for managing & viewing records on a domain. Users will have an easier time adding, editing and deleting records on their domain. When viewing standard records, we have added useful links to other sites. For example, when a user clicks a Validator Node ID, they will be presented with options to view that Validator on third party sites. Similarly, clicking a C-Chain address gives options for block explorers.
Support for Core Wallet. We have added support for the new Core Wallet extension, enabling users of that wallet to connect to and use the Avvy Domains webapp.
IPFS Deployment. Our deployment pipeline includes deployment to IPFS. Users can find the CID of the current deployment on Github or visit the deployment using DNSLink at ipns://avvy.domains/. Users can also access the IPFS deployment at avvy.avax using one of the .avax website resolution methods (avax.sh linking service or a browser extension).
EnumDAO & Signal.web3. Users can now message .avax domains from EnumDAO’s Signal fork. For more information see the announcement
Ark Protocol. Users can now use their .avax domain as a username on Arweave & wherever Ark Protocol is supported. Read more about the integration
NFTrade. NFTrade has verified the Avvy Domains collection on their NFT marketplace. View the collection.
Common Features. We have a new standard record type for representing E.164 phone numbers, specifically for the Signal.web3 integration though potentially useful in a broad range of applications. We have also started adding schemas for existing standard record types. Such schemas are potentially useful for applications saving data to the chain as well as for verifying the format of data being retrieved from the chain.
Website Resolution. We have added support for website resolution to the Chrome extension. Users can enter domainname.avax/ directly in the address bar of their Chrome-based browser to access web3 websites hosted on IPFS or web2 websites referenced using DNS.
IPFS Integration. We have added IPFS configuration options. Users can configure their IPFS gateway or set the extension to load ipfs:// and ipns:// protocols directly in the browser (in Brave, for instance).
These changes are pending approval by Chrome.
The Avvy Domains system consists of a series of interacting contracts with different responsibilities. The hashing & encoding algorithms required for interacting with names are non-trivial, leading to potential difficulties for integrators. We wanted to simplify integration as much as possible so we created a project we call the Indexer.
The Indexer helps users get a complete view of the .avax namespace. The project handles state reconstruction. The default setup uses event logs from the configured RPC and saves the reconstructed state in an SQL database.
Customizable for project-specific needs. Integrators have the option to customize the data source used to fetch event logs, the data storage method used (to extend beyond SQL) and the structure of the final data.
The first release of the Indexer is available on Github. We will be working to improve this tool, as well as provide examples on how to use it.
Our primary focus until the next update will be on integrations & usage. We are continuing to work with projects in the Avalanche ecosystem to ensure .avax domains are widely integrated.
Integration Examples. We are building a library of integration examples to share with projects hoping to integrate Avvy Domains. This should ease the process of integration for technical workers.
Usage Tutorials. We want users to understand the benefits of Avvy Domains and to understand how to set up their .avax domains. We will be working to improve communications on these topics.
Encrypted Records. Forward resolution records are currently stored plaintext on-chain. This can be problematic for users who wish to keep information private or to keep links between pieces of information private. We plan to offer a method of encrypting such records for storage on-chain.
Additional Clients. Looking slightly longer-term, we expect to need client implementations for iOS and Android. We intend to explore implementing a base client in Rust or Golang, both of which have implementations of the Poseidon hashing algorithm which Avvy Domains uses. The releases from the base client will then be used in the iOS and Android clients.
Join us on social media to keep up with news & development.