.bit Integration Guide
After the rebranding, we upgraded the
DASbranding to.bit. While to maintain forward compatibility, the open source library remains theDASbrand for now.
Prepare for Integration
It's recommended to read through docs.did.id document to save developers' time for integration.
The key content:
Integration Guide
Application Example
If you do not know what to build, here is an example.
Frontend Integration
If you need to integrate .bit in Web frontend, you need to read this document.
Backend Integration
If you need to integrate .bit in backend, you need to read this document.
Wallet Integration
If you are developing a wallet, you can not only resolve .bit account to improve user experience, but also list .bit Registration Service to earn shared revenue.
.bit Alias
.bit Alias is one of the most powerful features of .bit, which provides an extra guarantee of security for users in the blockchain world.
List Your Dapp on .bit Official Website
We are constantly collecting projects that have completed integration with .bit. If we missed your project's information, please email [email protected] with the following information:
- Project name;
- Logo and URL;
- Project description.
Useful Resources
- .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.
- .bit Open-Source Libraries Here's the list of useful .bit open source libraries to help you develop your application.
Contact Us
If you encounter any problem related to development, please feel free to contact us through the following ways: