Wallet –to –wallet messaging solves transparency issues and help one another easily. The one who has same NFT can message another NFT holder and can clarify his doubts and can form a group too. Even though both the members don’t know each other, their NFT forms a bridge of trust to be kind and help each other. Even though this idea seems to be very simple. It has very good output in the future. It is one of the unique way of creating a chatting Dapp. This proposal effectively addresses the challenge.

On the Cardano ecosystem, there are many wallets under construction and development, such as: Daedelus, Yoroi, Nami, Eternl, Gero, Flint… These wallets help users make many transactions every day. However, messaging between two wallet users is quite difficult. I am using Yoroi and Nami wallet. In Yoroi, we can transact but cannot include a message in each transaction. Nami wallet is a bit better, when making a transaction, there will be an "Optional message" section for you to send a message. But to send a message to the receiver in the Nami wallet, you have to make a transaction, and it costs a fee of at least 0.17 Ada. This proposal would build an open-source wallet messaging app that can be integrated into Cardano wallets and users can send messages between two wallets. This idea has many benefits for both Cardano wallets and the entire Cardano ecosystem. It will also facilitate the move towards fair trading between wallets without going through third-party platforms with audited smart contracts.

This project aims to introduce an interesting feature: The ability to communicate with our new web3 identities. As an NFT collector, I sometimes want to get in touch with someone who has that certain NFT that I want. It was easy to find the wallet address containing the NFT, but not so easy to get in touch with the owner of that wallet. “Not so easy” is really an understatement. It was near impossible. Except if the entire collection was only a few NFTs and almost all of the people that owned those NFTs were in that collections Discord server. Having a “A wallet-to-wallet messaging app where individuals can privately message each other” will allow for lots of engagement between community members. People will get messages for offers on NFTs they have probably forgotten about already….or that they themselves think have little value.

This proposal adds value to the Cardano ecosystem in the following ways. Providing an integration between wallet messaging that the community can use. Also it will allow for more transactions being performed due to users being able to directly message a wallet holder.

The impact of this suggestion will be enormous because most users may need to identify themselves on the chain in the future and may also need to communicate with one another using their wallets. As the article correctly notes, ecosystem maturity and Cardano adoption are likely to arise within and outside of the chain. These measures are very closely linked with the KPIs to measure the challenge, which gives the proposal a favorable outlook. They have plans to encrypt messages as their future plan, which demonstrates that the author wants to ensure their product is to the best of its abilities. The proposer also takes it upon himself to thoroughly identify any dangers that the project may have to overcome in order to offer effective outcomes. The community members would be truly independent if the implementation were effective because they wouldn't need to use their web2 IDs for any form of communication. Since wallet-to-wallet messaging is open-source, it will always be free and available for any company or person to integrate with their services, encouraging greater acceptance and simple usage.

The projects aims to enable wallet to wallet messaging which could be a very important step to building stronger communities. An example would be 2 people holding NFTs that represent an interest in protecting the environment. There is no easy way yet to talk to another wallet which might have the same interests as you and thus makes it hard to find like-minded people to collaborate with. This could also add more depth to GameFi and metaverse dApps and make it easier for them to integrate chat features and build a community. Though more details would strengthen the proposal such as how is it being run and where the chat data is stored, do users have to pay fees every time they send a text? And what if a user does not yet use the messaging platform, is it still possible to reach them?

The proposal is trying solve an ongoing problem for many of us in the NFT space. A communication tool with the wallet holding the desired NFT. As stated in the proposal, we can find our desired NFT at the marketplace (JPGStore) along with the owner of the NFT. However there is no way to communicate with the owner. With this proposal, Cardano community members in the NFT are able to communicate and thus providing benefits to the community. With that in mind, I strongly agree this proposal effectively addresses the challenge.

The proposer has presented all the details of this proposal and it is sufficient to audit the progress and the success of the proposal. The team will know if the project is successful by checking the community feedback ,ratings ,emotion mapping and no of users are using this chat app. It is very clear of how this project going to be. They provided a discord channel to help the community of how secure the chatting system .

The team will have monthly reports on the following issues: UX research documents, UI designs, Feedback, ratings… They also list 2 KPIs to measure project effectiveness, such as number of organizational and individual adopters and number of logins into the wallet-to-wallet messaging platform. The monthly reports and KPIs listed by the team are very suitable for auditing the "Open Source Wallet Messaging App" project.

One could not match the budget timelines with the tasks on the roadmap. For example the budget allocates ten days to UX research while the ten days are not indicated in the roadmap for the same topic. Also on comparing another budget item with the roadmap I found a mismatch in completion time. On their budget the backend and frontend development is said to take 50 days while on their roadmap the indicated time is 34 days. An assessor and a voter will now have to guess which one is it. The proposer should include numbers of days/weeks or dates in the roadmap and not leave this open for interpretation.

The proposer lays out the problem clearly and shows steps on how to go about developing the app.

The proposer will submit bi-weekly progress to Catalyst and their Discord. Their development reports will also be available on the github link provided. Their Discord has a dedicated weekly-project-updates announcement channel showing that they keep their community up to date with developments.

The proposal's objectives are clearly stated, quantifiable, and based on the clear road map in front of us. More trust is given to the plan via the Monthly Reports, ongoing debates, and feedback loops on disagreement. The measures are in line with the requirements of the challenge and will certainly be crucial in encouraging people to start utilizing their wallets as their identities going ahead. Because the project is open-source, assessing it in terms of technological progress is simpler. The pre-launch and post-launch metrics are quite clear and useful, despite the milestones' lack of technical specifics and timelines linked with each of them. Whether or whether the proposal was successful will be determined by the number of organizational and individual adopters as well as the number of dApp logins. The ultimate success story to look forward to would-be developers using their code to integrate into their projects, as stated by the drafter himself as the long-term goal. I agree that the auditing of this idea should be very simple given the abundance of KPIs and ambitions, and if financed, this may offer Cardano a completely new outlook and the holders a new identity.

The team will share monthly progress reports to Catalyst and on their discord. They will also track KPIs relevant to open source projects such as number of pull requests made and the number of unique logins to their messaging platform. The code is also open source so anyone can check up on the progress at their own time. 

Clear roadmap and deliverables are listed in this proposal. There is a clear communication channel using Discord which is a plus. The proposal has 2 target set Short Term and Long Term success. On the first Short Term Success, the key metric and indicator are well listed, with the given information, I believe its sufficient to measure the short term success of the proposal. Now for the Long Term success, again key metric and indicator are listed. But they are not as detail as the first. Though this is just a small set back, I am grateful for the information is given. Thus, the information provided is sufficient to audit the progress and the success of the proposal.