Wreck League Versus
Build, Battle, Earn $TOWER
About
The problem it solves Games often face significant challenges with distribution and capturing user attention. Wreck League Versus positions itself as a pioneering project by embedding game mechanics directly into a social layer, creating a unique and engaging experience for players. a) Empowering players as Key Opinion Leaders (KOLs): Every player becomes a KOL for the game. By enabling tipping of in-game items through social feeds and allowing players to build and own their Mechs, we incentivize active promotion of the game. Players benefit directly from their engagement, creating a self-sustaining ecosystem.  b) Innovative sponsorship model: In the future, we plan to introduce a sponsorship mechanism where non-players can back players' Mechs in battles. This fosters collaboration and creates a feedback loop between different player personas, further reinforcing the idea that everyone is their own KOL. By reimagining how games engage with their communities, Wreck League Versus is not just a game. It’s a social experiment in game distribution and player-driven growth where your battle power is your social power. Smart Contract Address(es) 0xaD53EB2841Dc02fbbA0A69b8867243d55760Ba13 0x27C92C6F3140a68f3eCD52cB65CE1EE8678b9Ac0 Other Onchain Proof towerecosystem.base.eth: 0x7Dd4bE401f5b275eB78C7De1f91e0B438C2bba85 $TOWER: 0xf7c1cefcf7e1dd8161e00099facd3e1db9e528ee
How it's made
Challenges we ran into As early adopters building on the Base chain and its ecosystem, we encountered several challenges due to gaps in documentation and functionalities between Farcaster and the Base App, especially as the Base App is still in beta. However, we proactively worked with the Base team to debug and resolve these issues, contributing to the improvement of the platform. a) Trending & Ranking on Base App: Initially, we believed that modifying the manifest would impact the list of Trending Apps. After engaging with the Base team, we gained a deeper understanding of the underlying mechanics, and the team addressed the issue promptly. b) Sharing functionality via encodeURIComponent: We discovered that the encodeURIComponent function was not working, preventing users from sharing content from our mini-app. This was escalated as a priority issue through close collaboration with the Base team. c) Metrics, funnel, and distribution insights on Base App: In the early stages, there was a lack of detailed analytics to track where users were coming from (e.g., social feeds, mini-app leaderboards, etc.). We provided feedback to the Base team, and later the team rolled out base.dev, a toolkit designed to help builders analyze Base App-specific metrics. By addressing these challenges head-on and collaborating with the Base team, we not only improved our own project but also contributed to the ecosystem’s growth and usability for other developers.