B137
Mint DIDProfile
  • General
    • Infographic
    • B137 Protocol
    • Why Composable DID?
    • Use Cases
    • Tokenomics
  • User Guide
    • Minting Soul Dust (DID)
    • Deploying Inscription Book (TLD)
    • Joining Community (Bind)
  • Advanced
    • Introduction
    • Core Concept
    • Operations
    • Batch
  • Integration
    • Introduction
    • API
      • Resolution
        • Get wallet address (forward resolution)
        • Get DID name (reverse resolution)
        • Get DID Details
        • Get TLD Details
      • Social Graph
        • Get Primary DID name
        • Get associated TLD of a DID
        • Get "Link to" List of a DID
        • Get "Linked by" list of a DID
        • Get Twitter handle of an address
      • Marketplace (unavailable)
      • Social Assets Management (unavailable)
    • Indexer
  • Links
    • Website
    • Discord
    • Medium
    • Twitter
Powered by GitBook
On this page
  1. General

Why Composable DID?

DIDs are typically presented in the form of DID.TLD, where TLD stands for top-level domain, usually provided by a DID service provider for users to mint domain names under that TLD. For example, on Ethereum, we have seen vigorous competition for certain rare DIDs under the fixed .eth, such as 000.eth.

The Sats Name Service (SNS), based on the Ordinal Protocol, allows anyone to create Namespaces and Mint any Names in accordance with the protocol standards. DIDs inherently carry a strong symbol of personal identity and have low liquidity. In a situation where rare names can be minted arbitrarily under different namespaces, it becomes very difficult for DID holders to benefit. Furthermore, the relationship between Spacename and Names is too weak, reducing it to merely a name identifier and losing many possibilities based on this affiliation.

Therefore, the B137 protocol proposes a DID system with composability. It achieves the functionality of different TLDs in SNS while preventing an overabundance of names by limiting the supply of B137-TLD and B137-DID.

PreviousB137 ProtocolNextUse Cases

Last updated 10 months ago