The problem Trope Cast solves

Trope addresses several key challenges faced by football fans and the broader football community:

1. Fragmented Fan Engagement:

Fans currently engage with football content across various disconnected platforms (social media, forums, news sites) without a unified experience.
Existing platforms lack tailored incentives for user-generated content and active participation.

2. Limited Monetization for Content Creators:

Football content creators struggle to monetize their work, relying on inconsistent ad revenue or sponsorships.
Fans have limited means to support their favorite creators directly.

3. Lack of Direct Interaction During Live Events:

Fans have few opportunities for real-time interaction and engagement during live football matches.
Existing platforms do not provide integrated rewards for live participation.

4. Complexity and Skepticism Around Crypto Adoption:

Football fans who are new to blockchain and crypto find the technology intimidating and difficult to navigate.
There is a lack of practical, rewarding use cases that demonstrate the value of crypto to everyday users.

How Trope Solves These Problems

1. Unified Fan Engagement Platform:

Trope creates a comprehensive social media platform specifically for football fans, integrating content creation, live interaction, and community engagement in one place.
Users can share and discover football-related content, participate in discussions, and join live streams, all within the Trope ecosystem.

2.Monetization for Content Creators:

Trope introduces a token-based reward system where content creators earn TRO tokens based on the engagement their content receives.
Fans can directly tip and support their favorite creators using TRO tokens, providing a reliable and direct monetization method.

3.Enhanced Live Event Interaction:

Trope integrates live streaming with real-time interaction features, allowing fans to participate in polls, quizzes, and discussions during matches.

Challenges we ran into

We began this project just 48 hours ago due to not having a Warpcast account. Since we are using the Pinata Farcaster FDK, we needed our Warpcast DEVELOPER_MNEMONIC and DEVELOPER_FID. You can read more about this here: https://x.com/DruxAMB/status/1806311599256358974.

Our dev lead, Muhammad, spent nearly 5 hours resolving a bug related to fetching data from the @pinatacloud (@farcaster_xyz) API. Thanks to the support from @pinatacloud developer @stevedylandev, who helped us debug the issue together. More details can be found here: https://x.com/DruxAMB/status/1807331279722979522.

Currently, we are addressing a bug that occurs when creating a signer after successfully signing in with a user's Warpcast account. Our development team is actively discussing the solution with Pinata's support team on Discord.