Parsed records are the core of .bit, and the flexibility of parsed records is also the source of .bit's great scalability. A parsed record is a key-value pair, and .bit supports an infinite number of parsed records. As shown above, different applications will read different parse records to do different jobs. Therefore, it is important to manage the namespace of the key of the parsed record. The namespace usage specification is essentially a protocol that can be followed to enable good collaboration between applications.
The key of a parsed record is a hierarchical structure using
. separated by a hierarchy, such as
custom_key.bitcc_config, etc. Among them,
custom_key are called primary namespaces;
bitcc_config are called secondary namespaces.
.bit has strict constraints on the use of namespaces at the contract level, and currently provides four first-level namespaces.
This namespace is generally used to store the user's digital assets receipt address, such as
address.eth, etc. Also, there is a whitelist inside the contract that has built-in mainstream digital assets symbols as legal key.
This namespace is generally used to store users' personal information, such as
profile.facebook, etc. Also, there is a whitelist inside the contract with built-in mainstream social network names as legitimate key.
This namespace is generally used to store decentralized network-related content, such as
dweb.resilio, etc. Also, there is a dweb.resilio inside the contract. Also, there is a whitelist inside the contract with the mainstream decentralized storage protocol built-in name as a legal key.
This namespace is not constrained, and developers can create any name and number of sub-namespaces under this space and define their meaning. For example,
The .bit contract does not verify the legitimacy of the value of the parsed record, the .bit just provides a convention. For example, a user would normally set the value of
address.btc to a BTC address. However, the application should check if this value is really a legitimate BTC address when using this value.
Addition of first-level namespaces
Currently, .bit only provides four level 1 namespaces
custom_key, but this is not the final result. The .bit team will gradually add more level 1 namespaces. If you think some namespaces should be added to allow better collaboration between applications. You can report in Github Issues.