The problem Cherry solves

Call it Peer-toPeer Fiverr, or Tinder for Devs, Cherry makes it fun and seamless to connect with fellow builders, chat, collaborate and even pay each other.
While our UI resembles Tinder, our use case fits a niche closer to Fiverr, but filling a market segment that the established freelance service doesn't: Conversations arise organically. Having a chat with someone, makes it easy to gauge their skills and whether you'd get along and effectively work together.
Worldcoin: Thanks to WorldID, users can rest assured they are chatting with a unique human.
Request Network: Once in a chat, payments can be requested and sent just as easily sending another message.
Celo: Payments can be requested and sent on Celo Mainnet, the main mobile-focused Ethereum L2.
Mantle: Similarly, users can also request and send payments on Mantle's (Mainnet) hyper-performant rollup.

Challenges we ran into

Implementing our own Ora prompt contract was quite straightforward, but we found it hard to get back the model's output. It came in the form of an event, which we couldn't listen for. Each call was quite expensive, so we decided not to deploy it on Mantle mainnet as we had initially hoped.
We then tried to deploy a similar functionality through Golem's Modelserve.ai since the underlying AI model was the same, Llama2. In this instance, the main rodeblock came from its conflicts with Next.js. We thought about the alternative option to route through a separate server but decided not to build this in the end.