No, each wallet address can only have one reverse record configured.
No, you can only have one primary domain linked to an address.
Yes, you can change and switch the domain you link to a wallet address at any time.
Yes and no. There’s nothing stopping users from pointing multiple addresses to a domain in the contracts. However, our website UI does not support this at the moment. If there is demand, we may change this in the future.
Our resolution libraries and APIs support Reverse Resolution. See our Integration Pathways guides for more detailed instructions.
Yes, Reverse Resolution is a new feature for our domains with a new set of smart contracts. Applications will need to upgrade their resolution libraries to access the new Reverse Resolution functions we’ll include.
Yes, there is a separate Reverse Resolution contract on Ethereum for L1 domains.
No, you cannot set Reverse Resolution for Zilliqa domains. Reverse resolution only supports Ethereum and Polygon domains.
Yes, you can configure Reverse Resolution for subdomains, as there is no difference from a regular domain.
No, Reverse Resolution only supports Ethereum addresses because the Ethereum blockchain only supports the algorithms to verify the signature of Ethereum transactions. We would have to implement signature verification of other blockchains into our smart contracts to support them, significantly increasing gas costs for configuring Reverse Resolution.
What happens when a single wallet has a reverse record to both Unstoppable Domains and a third party?
Integrating applications will need to check and decide how to display both records. Of course, we’d love to have Unstoppable Domains records take precedence, but it’s ultimately up to each application to decide.
Whenever a domain owner changes, reverse records are wiped automatically at the contract level, not only our website UI.
We create a new reverse record on the blockchain where the domain is being transferred to.
By default, L1 reverse records take precedence over L2 reverse records. If we detect a domain with both L1 and L2 records in our website UI, we’ll ask the user to clear the record from the chain where the domain is not stored.