Seer (BASED)

Demo

About

The problem it solves ### 1. Lowering the Barrier to Entry for Prediction Markets Traditional prediction markets often require users to understand gas mechanics, hold ETH for transaction fees, and interact with clunky interfaces. SEER removes these blockers by introducing: - **Gasless transactions** via Coinbase Paymaster, enabling users to place predictions *without holding ETH for gas*—this significantly simplifies the user experience. - **Swipe-based UX**, which makes adding a “Yes/No” prediction as intuitive as swiping on your phone—no confusing buttons, menus, or jargon. This combination makes prediction markets far more **accessible**, especially for users unfamiliar with Web3 workflows. ### 2. Seamless Creation and Participation in Markets Creating or joining prediction markets typically involves technical steps—configuring smart contracts, handling token decimals, and deploying to networks. SEER streamlines this with: - **OnchainKit integrations** for rapid, code-assisted deployment of markets, handling token precision (like USDC decimals) and smart contract interactions under the hood. - **MarketFactory + SimplePredictionMarket** smart contracts that abstract away complexities, letting users create and engage in markets effortlessly. This enables both creators and participants to seamlessly engage with market mechanics without needing deep blockchain knowledge. ### 3. Real-Time Feedback and Engagement Static prediction platforms mean you often wait for confirmation or results—but SEER delivers dynamic, real-time engagement through: - **Live leaderboards**, showing user rankings and market performance on the fly. - **Real-time position updates** powered by Supabase subscriptions, ensuring your predictions reflect current outcomes immediately after transaction confirmation. This real-time feedback loop boosts **user engagement** and creates a more lively, interactive prediction experience. --- ### Summary: What SEER Makes Possible | Problem / Barrier | SEER’s Solution | |-------------------------------------------|----------------------------------------------------------------------------------| | **Gas and web3 onboarding friction** | Eliminates gas requirement; offers intuitive swipe UX for predictions | | **Complex market setup** | One-click market creation using OnchainKit + smart contract abstractions | | **Delays in transaction confirmation and feedback** | Instant feedback with live leaderboards and real-time updates via Supabase | --- In essence, SEER transforms prediction markets from intimidating, slow, and technically-heavy systems into **fast**, **user-friendly**, and **engaging platforms**—empowering creators and participants alike with real-time, gasless, swipe-powered interactions. Smart Contract Address(es) contract creation: (marketfactory) 0xB788385cf679A69C43CfD9cB35045BBd4c2843f2 https://sepolia.basescan.org/address/0xB788385cf679A69C43CfD9cB35045BBd4c2843f2 swiping txns (batched + gasless txn) 0xC278b6b017B802d5A490C73c544266215507737f https://sepolia.basescan.org/address/0xC278b6b017B802d5A490C73c544266215507737f#internaltx Other Onchain Proof Search on Base (Beta) App as 'BASED'

How it's made

Challenges we ran into ### 1. Smart Contracts & ERC-4337 Account Abstraction While working on the smart contract integration within the **SEER** project on the Base network, one of the toughest hurdles was implementing **ERC-4337 account abstraction** in tandem with **gasless transactions**. Balancing security and user experience posed several challenges: - **Understanding the ERC-4337 flow** — Managing **EntryPoint**, **UserOperation**, bundler configuration, and paymaster intricacies demanded a steep learning curve. Incorporating these into a familiar smart contract development workflow was tricky. - **Manual simulation wasn't enough** — Testing flows only via foundry or scripts didn’t replicate real-world behavior. I needed to wire up the entire flow with the bundler, paymaster, and frontend to debug effectively. To overcome this, I: 1. Spent time stepping through the **ERC-4337 specification**, solidifying how UserOperations are verified and executed under the hood. 2. Used local debuggers and Foundry’s trace features to observe how operations were batched and sponsored via Coinbase’s paymaster. ### 2. Gasless Transactions (Coinbase Paymaster & Bundler) Enabling **gasless transactions** through Coinbase’s Paymaster (as configured in your README) introduced complications: - **Txn sponsorship edge cases** — The paymaster sometimes rejected valid requests due to nonce misalignment or calldata size—hard to trace without visibility. - **Frontend synchronization issues** — Ensuring the UI accurately reflected whether a transaction would be sponsored or fallback to a regular wallet flow required careful state management. My solution included: - Logging detailed payloads sent to the Paymaster and bundler, allowing me to isolate the exact root cause of rejection. - Introducing optimistic UI flows that first treat a transaction as gasless, then gracefully downgrade if sponsorship failed mid-flow. ### 3. Batched Transactions Batching multiple user operations or contract calls into a single **atomic transaction** was another headache: - **Batch execution failure modes** — When any single call in a batch failed, the entire batch reverted, often obfuscating which specific sub-call was at fault. - **Error debugging** — Finding the failing call within a batch wasn't straightforward in the native tooling. I tackled this by: - Adding granular logging inside each contract call, and additional events for entry and exit of batch steps. - Building a local batching test harness in Foundry, allowing me to trigger sub-calls in isolation and in batch to pinpoint issues quickly. --- ### Summary of How I Got Over These Challenges: | Issue | Solution Highlights | |----------------------------------------------|---------------------| | Understanding ERC-4337 account abstraction | Deep spec study + Foundry debug tooling | | Coinbase Paymaster misconfig or edge cases | Detailed logging + fallback flows | | Batched transaction failure localization | Event-driven debugging + batch testing harness | --- Going through these challenges taught me how valuable structured debugging, spec literacy, and resilient frontend design are when dealing with advanced blockchain UX patterns like gasless, abstracted accounts and batch processing. Thanks to these deep dives, the SEER project's user experience now feels seamless, even when there's a lot happening under the hood.