The problem XMTPHelper solves

Wherever XMTP is integrated, users can have their XMTPHelper with them, allowing them to subscrbe to new alerts and events on-chain such as when they've got a new follower or when they recieve transactions on their wallet. They can use it for getting notified of a low sale price for an NFT or any single event that happens on-chain.

We've extended the capabilities by allowing them to query data they're interested in in real-time using The Graph. Our implementation at the moment utilises the Substreams Uniswap v3 Subgraph to get the top 3 Uniswap pools with the highest total volume in USD, future extensibility could be another query on Uniswap such as querying the total pool count, transaction count, and total volume in USD and ETH - or using any other subgraph on The Graph's ecosystem.

We've got a third use-case built in as well that allows a user to register an image as an Intellectual Property Asset on Story Protocol, utilising image uploads in XMTP we then mint this asset and register it with Story Protocol - which will open up the doors for any creator with any media to easily register their content.

XMTPHelper protects itself through Harpie by blocking any malicious wallet address from interacting and using it's services. This prevents any unwanted use of our API connections and blocks a route into the XMTP network.

Future extensibility of the plugin will allow anyone to plug in features they want for users.

Challenges we ran into

Most our integrations worked well from the start, there was one main area which we had difficulty with which was decrypting an XMTP IPFS file to allow us to re-upload it with our own metadata for minting. We were able to decrype the image data using XMTP's own helpers, however we then tried to upload to IPFS using QuickNodes IPFS API. We kept getting bad gateway on upload after tried to send up the data in numerous formats (Form data, image), we believe the documentation and the provided example is incorrect. As we weren't able to reupload the image, we instead used the existing IPFS file that XMTP uses when someone sends an image and we minted that and registered it with Story Protocol. In the future we'd hopefully get round this so that users can specify what metadata they want to save alongside their media.