Please describe your proposed solution.

The web3 space is built around transactions and currently, most transactions happen via third-party platforms with audited smart contracts. In the future, audited smart contracts will be used between individuals to perform private transactions without the need for a third party.

To reach this stage of maturity, the ecosystem needs tools to aid peer-to-peer communications tailored to the web3 space.

Wallet-to-wallet messaging will play a key role in aiding individual transactions and bridging the communication gaps in the web3 space.

Making this open source ensures that players in this ecosystem do not have to start from scratch.

Such a messaging service will also play a key role in the NFT space. Let's take a case study to discuss why wallet-to-wallet messaging is important in this space.

Boss Cat Rocket Club:

Problem Statement:

BCRC holders are looking to connect with other BCRC holders to collect individual NFTs to complete a set. A completed set holds a higher monetary value. The issue is that there is no easy way of connecting with other BCRC holding wallets.

Problem Action Points:

a. Ability to find individual wallets containing specific NFTs (can be done through JPEG.store etc.)

b. Ability to communicate with these wallets

We are solving the issue listed in point 'b', which is the ability to communicate between wallets.

Please describe how your proposed solution will address the Challenge that you have submitted it in.

Ecosystem Maturity:

Open-source infrastructure in general helps the ecosystem by creating a foundation on which other individuals and organizations can build. It saves immense amounts of time and effort that goes into creating the same infrastructure over and over again.

We believe wallet-to-wallet communication is a key component in the ecosystem's maturity, hence we are building the infrastructure required. And keeping it open source!

Cardano Adoption:

Availability of the rights open source tools on Cardano attracts organizations and individuals to the ecosystem. This in turn brings rapid adoption by creating a utility that doesn't exist on other chains.

Our open-source wallet-to-wallet messaging will forever be free and open for any organization/individuals to integrate with their services.

What are the main risks that could prevent you from delivering the project successfully and please explain how you will mitigate each risk?

The risk of creating wallet-to-wallet messaging is the possibility of scams and private data leaking.

To mitigate these issues we are implementing the following security measures:

1. Ability to block messages and wallets
2. Permission for sharing links
3. Message encryption (future development)

Adoption and advertising:

We are planning on creating organic adoption through open sourcing, social media, and collaborations.

Please provide a detailed plan, including timeline and key milestones for delivering your proposal.

UX Research:

1. Research existing chat-based platforms and messaging services to understand the needs of the users.
2. Documenting the user experience in in each of these platforms through pain & gain testing, emotion mapping, and user stories.
3. Understanding the needs of users in a wallet-based chat and security measures
4. User flows

UI Design:

1. Low fidelity wireframes
2. Hi-fidelity wireframes
3. Usability testing w/ discord community

Discord link: <https://discord.gg/R9QSJ5gHZC>

Backend & Frontend Development:

1. Message requests: 5 days, 2 full stack developer
2. Create chat & integrate UI design: 15 Days, 2 full-stack devs
3. Block feature: 7 days, 2 full-stack developers
4. Security measures (Permission for sharing links): 7 days, 2 full-stack developers

Please provide a detailed budget breakdown.

Answer

UX Research:

10 days x 6hrs x $25 = $1,500

UI Design w/ Interactive Prototypes:

15 days x 6hrs x $25 = $2,250

Backend Research & Development:

30 days x 5hrs x $40 = $6,000

Frontend Development:

20 days x 5hrs x $35 = $3,500

Total = $13,250

Please provide details of the people who will work on the project.

Sam Jeffrey is a full-stack developer with 2 years of experience. He is the founder of Fetachain and has worked with Gimbalabs and rarely.io marketplace. He is also a graduate of the Plutus pioneer program.

Linkedin:

<https://www.linkedin.com/in/sam-jeffrey-m-2091731a7/>

Satwik Gade is a branding expert and graphic designer with 10+ years of experience. He currently works with India's most popular newspaper company, The Hindu.

Linkedin:

<https://www.linkedin.com/in/satwik-gade-b8b49311/>

Harsha Gullapalli is UI/UX and product designer with 3**+ years** of experience in the field.

Linkedin:

<https://www.linkedin.com/in/harsha-gullapalli-4b23451a/>

Srinivas Vijayakumar is a web developer with 3+ years of experience creating apps and websites.

Linkedin:

<https://www.linkedin.com/in/srinivas-vijayakumar-924152137/>

If you are funded, will you return to Catalyst in a later round for further funding? Please explain why / why not.

No.

This is a proposal that needs one-time funding and once all the research, development & documentation is completed, there would be no need for further funding.

Please describe what you will measure to track your project's progress, and how will you measure these?

Pre-launch/Development:

Monthly Report

• UX research documents will be posted bi-weekly on discord and also submitted in the Catalyst progress report
• UI designs will be shared on discord with the community and feedback loops will be used.
• Feedback will be both qualitative (comments) & quantitative (ratings & emotion mapping)
• These ratings will also be shared in the monthly progress report
• Development progress will be openly viewable on our Github repository
• Once development is completed (front & backend), there will be feedback loops from the community along with the monthly progress report.

Discord link: <https://discord.gg/R9QSJ5gHZC>

Post Development KPIs:

• Number of organizational and individual adopters. This will be measured by the number of pull requests on our Github Repository.
• Number of logins into the wallet-to-wallet messaging platform. This will be measured by the number of unique wallet log-ins on the platform.

What does success for this project look like?

Short-term success:

In the short term, we'd consider success as being able to deliver the code, UX research documentation, and UI implementation in the span of 2 months.

In terms of adoption, success would be 2 to 3 pull requests in the organizational level and 50-100 logins.

Long-term success:

In the long term, we believe success is multiple developers using our code to integrate in their projects and at least a couple of thousand individual logins.

Please provide information on whether this proposal is a continuation of a previously funded project in Catalyst or an entirely new one.

No.