Universal Name Service
  • 🧰introduction
    • Executive Summary
    • Background
      • Competitive Landscape
    • Introduction
  • 🛞How It Works
    • Multi-Chain Registration
    • Seamless Transfers
    • Integrated Token Swap
    • Automatic Bridging
    • Contract Registration
  • ⚙️Technical Architecture
    • Smart Contract Architecture
      • A. ERC-721-Based Name Ownership
      • B. Custom Smart Contracts for Non-EVM Chains
      • C. Resolver Contracts
      • D. Integration with Decentralized Identity (DID) Standards
    • Name Resolution and Identity Management
      • A. Name Resolution Mechanism
      • B. Identity Management through Decentralized Ownership
      • C. Integration with Decentralized Identity Protocols
  • 💰Tokenomics
    • Tokenomics
      • Utility of $UNS
      • Token Allocation
  • 🚩Roadmap
    • Roadmap
Powered by GitBook
On this page
  1. How It Works

Multi-Chain Registration

  • Registering a UNS Name:

Users can register a unique, human-readable name (e.g., "user.uns") through the UNS platform. This name can then be mapped to the user’s wallet addresses across multiple supported blockchains, including Ethereum, Base, BNB Chain, Solana, and more.

The registration process involves connecting a user’s wallet to the UNS platform and selecting a name that becomes their universal identifier.

Once registered, users can manage their linked addresses through a user-friendly interface, making it easy to add or update addresses on supported chains.

  • Mapping Across Different Blockchains

1. EVM-Compatible Chains

ERC-721 NFTs for Name Registration:

For blockchains compatible with the Ethereum Virtual Machine (EVM), such as Ethereum, Base, and BNB Chain, UNS follows the ERC-721 standard for name registration, similar to how ENS operates. When a user registers a UNS name on these chains, they receive an ERC-721 NFT that represents ownership of the name.

This NFT is stored on the respective blockchain, and the associated smart contracts handle the mapping between the human-readable UNS name (e.g., "user.uns") and the blockchain addresses.

The resolver smart contract on these chains reads the NFT ownership and resolves the name to the appropriate address, making it possible to send assets directly using the UNS name.

2. Non-EVM-Compatible Chains

Alternative Name Service Implementations:

For non-EVM chains like Solana, which do not natively support the ERC-721 standard, UNS adopts chain-specific mechanisms for mapping names to addresses.

For example, on Solana, domain-like services can use custom token standards and data structures, such as SPL tokens or Metaplex NFTs. UNS would utilize these mechanisms to represent ownership and manage the mapping between a UNS name and a Solana wallet address.

In such cases, the UNS resolver for Solana translates "user.uns" into the correct Solana address using the respective metadata stored in a decentralized manner on the Solana blockchain. This approach ensures compatibility while leveraging Solana's native infrastructure for speed and cost-efficiency.

Adaptation to Other Standards:

For other chains like Polkadot or Cosmos, UNS may use the native methods these networks provide for identity and data storage. For instance, Polkadot allows for a more customizable approach through its parachains, enabling custom data structures and smart contract logic to store and resolve UNS names.

On these chains, the UNS system would use equivalent standards for name-to-address mappings, adapting the NFT model to their specific identity and metadata protocols, ensuring that users can still interact using a single name.

PreviousIntroductionNextSeamless Transfers

Last updated 4 months ago

🛞