Docs of Communities ID
WebsiteTwitterDiscord
  • What is Communities ID
  • DID as a Service
    • Omni DID
    • Bridge DID
    • Soulbound DID
  • Why "DID as a Service"?
  • How to start?
    • For project owners
    • For regular users
  • Terminology
  • Pricing & Business Model
    • Business Model
    • Pricing Policy
  • Frequently Asked Questions
  • -BRAND GUIDE-
    • Community Settings
    • Mint Settings
      • Mint Mode
      • Pricing
      • Base URL (PFP)
    • Renewal & Expiration
  • -USER GUIDE-
    • Mint
    • Burn
    • Renewal & Expiration
    • Set as Primary
    • Soulbound
  • -Developers-
    • SDK
      • Overview
        • Install & Initialize
        • Search Brand/User
        • Resolving Name
        • Modify User DID
      • API reference
        • Collector
        • Resolver
        • Operator
  • - Legal -
    • Privacy Policy
    • Terms of Service
Powered by GitBook
On this page
  1. -Developers-
  2. SDK
  3. Overview

Resolving Name

PreviousSearch Brand/UserNextModify User DID

Last updated 1 year ago

The Resolver function facilitates the forward and reverse resolution of User DIDs and wallet addresses. It acts as a bridge between the user-friendly naming systems and the native crypto wallet addresses.

Here are some examples:

const { resolver } = new CommunitiesID(options);
await resolver.resolveName('a.did')
await resolver.lookupAddress('0x123')

For DIDs not associated with CID, the Resolver can map to domains of ENS or Space ID. This ensures compatibility with multiple DID systems without the need to integrate multiple DID service provider SDKs.

This functionality is only supported on mainnet. Besides, to resolve name from CID, you should pass Biance and Arbitrum RPC

For more details, please refer to .

API doc