.bit Integration Guide
After the branding upgrade, we upgraded the
.bit, but to maintain forward compatibility, the open source library will remain the
DASbrand for now.
Prepare for Integration
It's recommended reading through docs.did.id document, so that the developer's time can be saved.
The key content：
If you do not know what to build, here is an example.
If you need to integrate .bit in Web frontend, you need to read this document.
If you need to integrate .bit in backend, you need to read this document.
If you are developing a wallet, then you can not only resolve .bit account to improve user experience, but also list .bit Registration Service to earn commission.
.bit Alias is one of the most powerful feature of .bit, which provide an extra layer of security for users in blockchain world.
List Your Dapp on .bit Official Website
We are constantly collecting projects that have completed integration with .bit. If we have missed your project information, please email [email protected] with the following information:
- Project name;
- Logo and URL;
- Project description.
- .bit Record Key Namespaces The key of the record for every .bit account must be in the namespace, including types such as address/profile/ dWeb. Here is the list of them.
- .bit Open-Source Libraries Here's a list of useful .bit open source libraries to help you develop your application.
If you encounter any problems in the development, please feel free to contact us through the following ways: