Transferring assets in blockchain is not as easy as it should be. Wallet addresses are huge and ugly, there is a lot of copy-pasting, and many people use the strategy to make a small transaction - just to be sure everything is ok - before transferring all the assets. In practice, this doubles the transaction fee that the sender has to pay.
To solve this problem, we proposed adatar.me, a funded proposal from Catalyst Fund 6 (back then called ‘Gravatar for ADA Wallets’). We have launched in mainnet in February 2022, and you can check a live demo during our presentation in Gimbalab’s playground here:
https://www.youtube.com/embed/_DiLlr_AxGkThe project is still ongoing, as we are improving the UX, developing the project’s visual identity and working on our API. If you’d like to support us, feel free to send a tip at <https://adatar.me/tip/adatar.me> (:
The current proposal’s objective is to increase the adoption of Adatar. So far, the team has been focused on the project’s development from the technical perspective.
While we have developed human readable addresses and adatars for payment addresses that users can use at <https://adatar.me> we want to open it up for any dApps that want to enable human readability for addresses. We intend to achieve this by exposing our services via open API for dApps to consume. This will allow dApps to reap the full functionality of adatar by plugging into our API interfaces.
DApps will benefit with the hassle free integration we offer and transform all of their use cases with payment addresses to display human readable ones. Our open API enables dApps to get customized, adatar supported addresses out to the box.
The Adatar widget that we are proposing to develop in this proposal is going to be incorporated into other project’s websites. We are building a tool that can benefit many other developments, and therefore, the whole ecosystem.
We are aligned with this possible direction mentioned in the challenge brief: “Developing common tools, frameworks, core infrastructures, or proof of concepts”.
Also, we are aligned with the following challenge KPIs:
- increase the number and the quality of Cardano Open Source projects
- increase of open source tools and frameworks from the community for the community
We see this as a low risk development. The API is something that we are sure we can develop, and we have the people to do it. The only risk we foresee is lack of adoption, which we might mitigate with a specific budget for it included in this proposal.