One of the biggest initial challenges was making the XMTP application accessible to messaging by Base users. This seemingly perplexing blocker was easily resolved by changing the XMTP environment variable setting from "dev" to "production".

Another challenge that we faced is working with the tool use—in order for the user to have a seamless experience, we wanted to the agent to operate in the background with minimal user input required. However, we initially had some problems in getting the bet formation tool call precisely correct (it needed to be in a particular data format) in order for the bet verification tool call to work properly. This required additional system prompting and response guardrails.
Moreover, we wanted the agent to combine tool calls (i.e web search before doing a bet verification tool call), which took some more work to get right. With additional time, we would add further explicit safe guards.

Moreover, we were able to run our code using a server on a mac—however, when we deploy to the linux, we face an issue where it failed to find the native linux node bindings for GNU (node package: @xmtp/node-bindings-linux-x64-gnu, ubuntu Docker container), and MUSL (node package: @xmtp/node-bindings-linux-x64-musl, alpine Docker container).