receive.me - UNS & ENS UX integration

Inspiration

Cryptocurrency payment methods are often complex and not optimally used for casual payments. identity and payments are usually provided on a 'just in time' basis, as users generally have multiple accounts for both wallets and socials. Poor UX/UI serves as a barrier to entry for many individuals interested in transacting on-chain, showcasing an underlying need for accessibility driven solutions. Therefore, we have created receive.me, an accessibility driven application, which aims to reduce the complexities associated with transacting on-chain & name services. We accomplish this through enabling users to curate a unique Web3 profile, compatible with existing name service infrastructure, such as ENS and UNS, multiple wallet addresses, and various social profiles.

What it does

Receive.me centralizes client information under a single Web3 profile. Receive.me supports existing name service infrastructure, such as ENS and UNS, in addition to providing users with the freedom to showcase wallet addresses for their favorite cryptocurrencies under a single profile. Additionally, users can add their respective social media accounts such as their X account, GitHub, and more. The receive.me profile enables users to personalize their on-chain identity, thereby reducing user information fragmentation.

How we built it

Receive.me was built using next.js, nest.js, typescript, particle auth, and UNS API.

Challenges we ran into

The Amazon Kendra integration was quite challenging, and we are still researching how to integrate these services into our platform.

Accomplishments that we're proud of

We are incredibly proud of the hard work the receive.me team has put into the development of our product suite. Additionally, we are equally as proud of the accolades awarded to receive.me over the past few months, such as hackathon grants from TronDao, Avalanche, and Algorand. Furthermore, we are also proud of the support we have received from off-chain entities such as Edmonton Unlimited, MITACS, eHub, Fasken, and Edmonton Tech Start-up community.

What we learned

Learned about the UNS API , both the Partner and Resolution APIs
Learned about how we can potentially integrate AWS services into our products
Made many other improvements to our user experience along the way (new profile layout, badges features & more)

What's next for receive.me - UNS & ENS UX integration

During the hackathon, receive.me participated in Namescon in Austin Texas, to research our focus on name service within our product suite. Following the conclusion of the Web3 and AI Unstoppable Hackathon, we will continue to expand receive.me’s product suite. This includes additional support for UNS and ENS as well as integrations with relevant AWS products, such as Amazon Kendra. We also plan to craft an advisory board to guide the core team on general business strategy, marketing approaches, and revenue model curation. Finally, we plan to expand the core team to include additional positions to ensure that we can properly scale.

Some future specific dev improvements/objectives can be listed below:

Integrate POAPs to our badges
Integrate L2 networks as options to connected addresses (Arbitrum, Optimism, zkSync, etc)
Integrate more wallets/socials
Add more personalization features
Dynamic Open Graph implementation
New profile layouts
Launching our own TLD (long-term projection)