When I arrived at the hackathon in Paris, I had no idea I would stumble upon a new and exciting trend in the world of web3 messaging services. It was all about wallet-to-wallet, end-to-end encrypted communication channels. If you had a crypto wallet, you could establish a decentralized communication channel with another recipient and send them messages securely.

Two major players were dominating this space: XMTP and the Push protocol. Both projects had their merits, but Push seemed to be doing much more than just focusing on messaging. However, XMTP had the advantage of simplicity and ease of use.

Using XMTP was a breeze. All I had to do was authenticate my wallet through the client, pass my wallet parameters to a few functions, and messages were already flowing through the decentralized channel. During the conference, I witnessed its application in a local cafe, where you could order a cup of coffee and croissants and pay for it directly within the channel using USDC on the Polygon network. It was a remarkable demonstration of the technology's potential.

As I delved into the hackathon and started working on XMTP, one of the challenges we set for ourselves was sending an image. It may sound simple, but it turned out to be one of the more complex tasks. XMTP used end-to-end encryption, which meant that we had to upload the image to web3 storage units to ensure its security and integrity. It was a reminder of the decentralized and trustless nature of web3 technologies.

I couldn't help but be excited about the future of web3 messaging services. It had been a while since I had seen a chat client that exceeded everyone's wildest web3 dreams. The potential for secure, private, and decentralized communication through crypto wallets was just the beginning. I was eager to see where this technology would take us and what new innovations and applications would emerge in the world of web3 messaging.