WalletChat - Wallet-to-Wallet Messaging for Web3

What is WalletChat

Most people associate crypto and web3 with finance and monetary assets. That’s only a small part of the story though, and the next frontier is web3 social. WalletChat is building the infrastructure for wallet-to-wallet messaging, enabling individuals and communities to connect in novel web3-native ways. We provide one-on-one direct messaging, community messaging, and more. Via our web app, browser extension, API, and widget - https://www.walletchat.fun/

We are a small team of five - experienced in building funded startups up to Series A and beyond, and developing novel tech products. We have got plenty of combined experience across web3 from organisations such as BanklessDAO, CoinMarketCap, Prysm, WildFireDAO, and others. We are spread between Singapore, US, and Bali.
The story of WalletChat and Our Traction

We have been working on WalletChat for the past five months. Starting with a browser extension that web3 users can utilise to message one another when doing things like viewing NFTs on OpenSea, and wishing to negotiate with each other. Later on we have launched our web app, which supports the same functionality, without requiring people to download anything.

In this web app, we have integrated token-gated group chats - upon login with your existing MetaMask or WalletConnect wallet, WalletChat automatically detects the NFTs inside your wallet and pre-populates your home screen with the right communities to interact with. This can supplement or replace discord, with a more minimal, accessible, and secure solution, tied directly to your wallet - which is quickly replacing any web2 tools, as a centre of your identity.

We have built a community of around 2.000 people around this product, and received around 50.000 API calls from people interacting with WalletChat. We have presented this at NFT NYC and partnered up with names like Lit Protocol, IPFS, POAP, and Buildspaces - who have either given us small grants (<= $5k) or supported us in other ways via marketing and shared resources. We have onboarded a couple of small NFT communities as beta testers of our group messaging. The feedback from anyone who has interacted with WalletChat has been overwhelmingly positive.

Next, we have realised the opportunity of partnering up with dapps directly, and offering them a full integration of WalletChat, in order to enable wallet-to-wallet messaging for their users, right from within their dapp. We have opened up our API for this purpose and we have also developed a website widget - which can easily be integrated as an NPM package into any website, within a matter of minutes. This has been our most recent release, which came out a couple of weeks ago.

What’s next

Although the v1 of our messaging widget is live, we have a bunch of additional things in our roadmap that we need to deliver, in order to satisfy many of the dapps on our waitlist, and make it feasible for them to integrate WalletChat. Because of this, we are looking to secure additional funding - to step on the gas, deliver a more fully rounded product, achieve many more integrations, and build the future of wallet-to-wallet messaging that we envision. We are asking for a $100k grant, which we will divide into three parts -

  1. Stage 1: $30k (2 months)
  • $20k to carry out extra development of features inside our roadmap (custom group chats, API v 2.0, UX improvements)
  • $5k for business development & marketing
  • $5k for operating & legal expenses
  1. Stage 2: $35k (2 months)
  • $20k to continue with extra development of features inside our roadmap (spam filtering, messaging permissions, multi-channel notifications)
  • $10k for business development & marketing
  • $5k for operating & legal expenses
  1. Stage 3: $35k (2 months)
  • $20k to continue with extra development of features inside our roadmap (one-way messaging, analytics dashboard, infrastructure scaling)
  • $10k for business development & marketing
  • $5k for legal & operating expenses

We have been almost entirely bootstrapped up until now, with <$10k received in grants, to fund our last 5 months of development. Securing additional funding will significantly help us to move forward. Some of these features might get reprioritised based on demand but the bottom line is that at the end of each stage, our improved product will enable us to integrate with more dapps, boosting our network, and strengthening the WalletChat ecosystem. We will provide status reports at each stage, detailing the progress we have made and new partnerships we have secured.

Please see the links below to inspect the live product, our community, and partnerships we have built so far. We don’t just talk the talk, we also walk the walk, we ship fast, and we build according to what the space requires.


Website - https://walletchat.fun/
Web app - https://app.walletchat.fun/
Widget - widgetdemo/README.md at main · Wallet-Chat/widgetdemo · GitHub
Discord - WalletChat
Twitter - https://twitter.com/wallet_chat
YouTube - https://www.youtube.com/channel/UCsG1R1juoE2tcxM3IQAq9cw/featured


Hi WalletChat team,

I think this is very cool. Quick question: if a dapp is using your widget, will a user have to manually connect their wallet to both the dapp and your widget separately, or will WalletChat automatically sign them in once they’ve connected to the dapp website?

Thank you, ser!

In short - it depends. But as long as the dapp has provided us with the necessary to inherit their sign in credentials, no second sign in is needed.

Cool. I think this is super important. I imagine most users will have some trepidation signing into a new chat feature with their wallet, but if they are already users of a specific dapp that adopts your widget, this would be frictionless and less of an adoption hurdle.

Yes. I think it’s more about removing friction than security though. Sign in with your wallet is a standard feature of all dapps now and doesn’t grant access to your tokens. The removing friction part is still important though.

Yes – referring mostly to the users perception of security, not the underlying actual security

1 Like

Thank you for your thoughtful comments, ser!

1 Like