Inspiration
Passionate about name service. We were frustrated not to find a working application on the Hedera blockchain. We decided to develop this application.
What it does
When transacting on Hedera, users normally interact with wallet addresses—long strings of numeric characters that are unreadable and almost impossible to remember. Similar to the way web users replace numerical IP addresses by registering domain names through the Domain Name Service (DNS), blockchain users can transform long and unreadable Hedera addresses to a unique on-chain profile with .lovesh.bar domain.
How we built it
We have researched the functioning of name services and have been inspired by the following approaches and applications:
bonfida : solana name service • tezos demains : tezos name service • ens : ethereum name service
Challenges we ran into
We had problems with the rooting of subdomains with Fleek, which is why we used AWS for the moment. We also took some time to figure out the best approach.
Accomplishments that we're proud of
We are proud to have a proof of concept that works and to have achieved a simple and easy experience.
What we learned
We learned about solidity and the functioning of Hedera, which has its own particularities. We also learned a lot about name service.
What's next for *.lovesh.bar
We would like :
- to set up commissions from each type of operation such as name service purchase, swap, and more, create a governance token that allows you to receive vault shares and vote on the evolution of the project.
- provide a premium offer on the name service with specific character like emojies and for example allow to request merch
- provide an SDK that allows a company to replace loveshbar domain with its own domain name and create its own subdomain and of course supporting them in the setup of this SDK.
Roadmap :
- During june we would like to integrate royalties into the name service NFTs and Moonpay to allow users to credit their address directly. We want to replace Aws by Fleek to become more decentralized and start to build a community.
- Between July and August, we would like to test our different use cases and publish our roadmap for governance, and put forward our strategies and partnership.
- Finally, in September, communicate and talk about our product
We explain it all in this video: pitch


Log in or sign up for Devpost to join the conversation.