Introduction

Please note that this document is a draft and the related inscriptions have not been officially deployed. Before the official tools are launched, DO NOT conduct transactions as defined in the protocol, as this may result in the loss of funds.

For traditional DIDs, the format typically follows <NAME>.<TLD>, where <TLD> identifies the top-level domain to which the name belongs, and within the same domain, names are generally not allowed to be duplicated.

To enhance flexibility and the liquidity of domain names, we propose a new DID protocol that defines the format as follows:

<DID>.(<TLD>*)

The BRC-137 protocol allows anyone to mint a unique inscription in a completely permissionless and decentralized manner. It is a semi-fungible inscription compatible with the BRC-20 protocol, with a total supply of 21,000,000.

Holders of BRC-137 inscriptions can inscribe a custom string as their name (unique, FCFS), and once the inscription is inscribed with a string, it becomes a non-fungible inscription <DID>. For infrastructure or dApps that integrate the BRC-137 protocol, it can be directly resolved to its holder's address.

At the same time, the inscription can establish binding relationships with multiple <TLD>. After the binding relationship is established, <DID>.<TLD> can also be resolved to its holder's address.

<TLD>are also distributed in a decentralized manner. Any organization or community can create their own to enhance their brand and establish an identity identification system.

In the Core Concept section, there will be a detailed explanation of <DID> and <TLD>and how is the protocol operated.

Last updated