The problem CoinSwipeOnBase solves

• Problem with existing DEXs: Clunky, data-heavy, and unfriendly for casual users.
• Opportunity: Gamify token discovery + lower entry barriers → create an addictive, fun, and engaging experience.
• Why Base:
  • Fast and cheap transactions (Layer 2 Ethereum).
  • Growing memecoin + retail culture.
  • Active ecosystem around new tokens (perfect for swipe-style discovery).
  • Ethereum compatibility with lower fees.
• Why CoinBase MPC Wallets:
  • No friction (auto wallet creation).
  • Smooth onboarding for non-crypto-native users.

Challenges I ran into

Uniswap DEX Integration: Ensuring smooth Base-supported token swaps with accurate fee deductions.
Hurdle: The primary difficulty here wasn't just integrating with a DEX , but ensuring that the contract could correctly handle swaps and accurately deduct fees on a live, forked network. Our initial tests revealed "invalid opcode" errors when attempting swaps. This was because the _dex parameter for unoswapTo in the uniswap router requires specific, dynamically generated swap data rather than a simple hardcoded identifier for successful execution on a live DEX.

Integration of MPC Wallets: Implementing Coinbase's MPC Wallet Kit for seamless user smart contract interaction was challenging due to limited documentation.
Hurdle: Integrating MPC (Multi-Party Computation) wallets like Coinbase's Wallet Kit often comes with a steep learning curve, especially when documentation is sparse. The core challenge was ensuring a seamless and secure connection to our dApp, particularly for smart contract interactions on the Base network. Initially, ChainNotConfiguredError was a recurring issue, preventing interaction with our forked Base mainnet. Soo we had to switch to the metamask embedded wallets for similar experience.

Real-Time Data Aggregation: Fetching live token data while ensuring responsiveness.
Hurdle: Providing real-time token data to the frontend, especially for trending tokens on the Base network, required a robust and responsive data aggregation strategy. DexScreener was used, since the goal was to fetch live data without impacting application performance.

Smart Contract Address(es)

Base Mainnet - 0x2447415B4D49219dfD3c03C880b2982dAeF06cFe