Minisend

Demo

About

The problem it solves **Minisend eliminates the last-mile friction preventing Base creators and builders from accessing their onchain earnings.** While users can easily earn USDC through Baseapp, creator platforms like farcaster and other dApps, converting those earnings to local fiat has been broken requiring expensive centralized exchanges, lengthy KYC processes, high fees (2-3%), and 3-7 day settlement times. For many users in Nigeria and Kenya, this process often fails entirely due to rejected verifications or frozen accounts, leaving earnings trapped onchain or forcing risky P2P trades. **Minisend transforms USDC withdrawals into a seamless, direct experience: USDC on Base → local fiat in minutes.** Nigerian users can send USDC directly to any bank account in NGN, while Kenyan users can instantly fund their M-Pesa mobile wallets in KES. This makes existing tasks dramatically easier and safer. Creators can confidently build knowing they can access earnings, developers can cash out bounties without exchange headaches, and merchants can pay local suppliers directly from onchain revenue. By enabling transparent, fast, and reliable offramps, Minisend directly supports Base's mission to "enable on and offramps in every country around the world" while keeping users within the Base ecosystem instead of bridging to other chains for better withdrawal options. Smart Contract Address(es) **Minisend utilizes external APIs from a payments infrastructure provider built on Base Network.** Rather than deploying custom smart contracts, we integrated with existing, audited smart contract infrastructure to handle USDC escrow, settlement verification, and fiat conversion logic. ## **Smart Contract Integration** ``` Architecture: Minisend (UI/UX Layer) → Payment APIs → Base Smart Contracts Network: Base Mainnet USDC Contract: 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 ``` **Every Minisend transaction:** 1. User initiates withdrawal through Minisend interface 2. Payment API coordinates smart contract interaction on Base 3. USDC is handled via partner's Base smart contracts 4. Settlement occurs through verified onchain transactions **Result:** 400 verifiable onchain transactions on Base, all traceable through our public API endpoints at https://minisend.xyz/api/onchain-proof Other Onchain Proof ## **Verifiable Transaction History & Public APIs** **Live Onchain Proof Endpoints:** - **Transaction API:** https://minisend.xyz/api/onchain-proof - **Public Dashboard:** https://minisend.xyz/proof These endpoints provide real-time, verifiable data of all Minisend activity on Base, including transaction hashes, settlement times, and wallet addresses. ## **Onchain Traction Metrics** **Transaction Volume Growth** - **425 total orders** initiated since launch - **330 successful onchain transactions** verified on Base - **$14,540 USDC** processed through the platform - Recent activity shows **daily usage** with transactions as recent as today (Sep 2nd ) **Verifiable Transaction Patterns** - **Transaction Hash Examples:** - `0x8285531566...d7eb2cf8` ($1 USDC → KES, settled ) - `0x5adbf2d9ed...bfe17beb` ($17 USDC → KES, settled ) - `0x1a8d9c1daf...ed814a47` ($2 USDC → KES, settled ) **Organic User Behavior** - **Repeat users demonstrating product-market fit:** Wallet `0x7D6109...2a9CEc` has **9+ transactions** - **Cross-border adoption:** Mix of KES (Kenya) and NGN (Nigeria) transactions - **Small-value, frequent transactions:** Pattern shows real utility for daily/weekly cashouts **Transparency & Verification** All transaction data is **publicly auditable** through our API endpoints, allowing anyone to verify our onchain activity, success rates, and user adoption metrics directly on Base blockchain.

How it's made

Challenges we ran into **The Problem:** Standard Web3 wallet connection patterns that work perfectly in standalone dApps completely broke down inside Farcaster's iframe context. **Specific Issues Encountered:** - `window.ethereum` was undefined within Farcaster's sandboxed iframe - Coinbase Wallet's standard connection flow triggered popup blockers - Cross-origin restrictions prevented direct wallet provider injection - Mobile wallet deep-linking failed due to iframe navigation constraints - User sessions weren't persisting between Farcaster frame interactions **The Solution: Minikit Integration** After struggling with custom wallet connection implementations, I discovered Coinbase's **Minikit SDK** specifically designed for this exact use case. The solution was elegantly simple: ```javascript // Wrapped the entire app with Minikit provider import { MiniKit } from '@coinbase/minikit-js' function App() { return ( <MiniKit.Provider> {/* Entire Minisend app */} </MiniKit.Provider> ) } ``` **Why This Worked:** - Minikit handles all the iframe/cross-origin complexity under the hood - Provides native Farcaster context awareness - Seamless Coinbase Wallet integration without popups - Persistent session management across frame interactions - Built-in mobile optimization for the Farcaster mobile app **Key Lesson:** Sometimes the right SDK saves weeks of custom implementation. Minikit turned a complex wallet integration problem into a simple wrapper implementation, letting me focus on the core offramp functionality instead of fighting browser security models.