Snowball
  • Welcome to the Snowball
  • Introduction
    • Problem Statement
    • Vision and Mission
    • Solution Overview
  • Modular Naming Service (MNS)
    • What is MNS?
    • MetaMask Snaps
      • Knowledge Base
      • FAQ
    • Identity Management System
      • Claiming Identity
      • Claiming Identity (ENS, SNS...)
      • Sub-identity
      • Primary Identity
      • Transferring Identity
      • Extending Identity Registration
      • Selling Identity
    • Identity Data Management
      • Record Type
        • Address Records
        • TXT Records
      • Records CRUD
    • Reputation Scoring System
      • For Users
      • For Projects
      • Data Sources & Inputs
    • Pricing
    • Use Cases
    • Roadmap
  • Programs & Gamification
    • Referral & Affiliate Systems
      • Affiliate Referral System
        • Terms and Conditions
        • How to Refer as an Affiliate
        • Affiliate Leaderboard Program
        • Eligibility & Requirements
        • Affiliate Tiers, Leaderboard Pools and Commissions
      • Referral System
        • How to Refer
        • Referral Leaderboard Program
        • Referral Tiers, Leaderboard Pools and Commissions
        • Terms & Conditions
      • Leaderboard & Monthly Rewards
      • Payoffs
    • Rewards & Gamification
      • What is Flakes?
      • Achievements
      • Daily Tasks
      • Repeatable tasks
      • Leaderboard
  • Decentralized Identity Layer
    • What is DiD Layer?
    • Cross-chain Interactions
    • Architecture
      • Reverse lookup
    • Tokenomics and Value Economics
      • Tokenomics
      • Value Economics
    • Why use dID on Rollup?
    • Deployments
    • Technical Documentation
      • Smart Contracts
        • RegistrarController
        • TransferController
        • PriceController
        • PublicResolver
        • SaleController
        • SnowRegistry
      • Events Documentation
      • Rest API
      • Typescript SDK
      • CAIP2
      • Reverse Lookup
  • About us
    • Team
Powered by GitBook
On this page
  • Reverse Lookup
  • Overview
  • Key Concepts
  • Current Functionality
  • Best Practices
  • Future Roadmap
  • Security Considerations
  • Use Cases
  1. Decentralized Identity Layer
  2. Architecture

Reverse lookup

Reverse Lookup

Overview

Reverse lookup enables addresses to be associated with human-readable names on the Aptos Network. While standard (forward) resolution allows names to point to addresses, reverse lookup does the opposite - it lets an address point back to a name. This feature is essential for improving user experience in dapps and wallets by displaying readable names instead of long hexadecimal addresses.

Key Concepts

Primary Names

  • Each address can have only one primary name

  • The primary name must be owned by the address setting it

  • Only active (non-expired) domains can be set as primary names

  • The domain must have its address record pointing to the owner's address

Ownership Requirements

To set a reverse lookup, two conditions must be met:

  1. You must own the domain you want to set as your primary name

  2. The domain must have its address record set to your address

This dual ownership requirement ensures security and proper name resolution in both directions.

Current Functionality

Network Scope

  • Currently operates only on the Aptos Network

  • Future expansion to other networks planned through wallet linking

Features

  • Set a domain as your primary name

  • Clear your primary name

  • Query primary names for any address

  • Automatic updates when domain ownership changes

  • Protections during grace periods

Automatic Management

The system automatically manages reverse records in several scenarios:

  • When a domain expires

  • When domain ownership changes

  • When address records are updated

Best Practices

  1. Choose Wisely: Select a primary name that best represents your identity

  2. Keep Updated: Maintain current address records for your primary name

  3. Monitor Expiration: Ensure your primary name doesn't expire

  4. Clear Outdated Records: Remove reverse records when no longer needed

Future Roadmap

Wallet Linking

  • Will enable cross-chain functionality

  • Will allow reverse lookup across multiple networks

  • Will maintain security through cryptographic proofs

Cross-chain Resolution

Once wallet linking is implemented:

  • Primary names will resolve across all supported networks

  • Single identity across multiple chains

  • Unified naming system for the entire web3 ecosystem

Security Considerations

  • Only proven ownership allows setting reverse records

  • Records are automatically cleared on domain expiration

  • Ownership changes trigger automatic updates

  • Grace period protections apply to reverse records

Use Cases

Current

  • Dapp user identification on Movement Network

  • Wallet address display enhancement

  • On-chain identity verification

Future (with Wallet Linking)

  • Cross-chain identity management

  • Unified web3 profiles

  • Multi-chain dapp integration

PreviousArchitectureNextTokenomics and Value Economics

Last updated 25 days ago