Based

Demo

About

The problem it solves ### The Problem: The "Reputation Paradox" for Builders As of late 2026, the Web3 developer ecosystem is booming. Hackathons settle millions in prizes, and DAOs manage billions in treasury. The talent is there. **But the signal is lost in the noise.** Currently, a builder trying to prove they are "The One" has to navigate a broken landscape: 1. **PDF Certificates:** Web1 technology. Easily photoshopped, impossible to verify programmatically. 2. **LinkedIn Flexes:** Web2 theatre. Self-reported, often exaggerated ("Trust me, bro"), and disconnected from actual onchain activity. 3. **GitHub Graphs:** Good for code, bad for context. A green square doesn't say if you were the *Lead Architect* or just fixed a typo. There is no "Etherscan" for Human Impact. There is no single source of truth for *what you built* and *what role you played*. That is the gap **BASED** fills. ### The Solution: Definitive Onchain Proof **BASED** is not just another NFT minter; it is the **reputation layer** for the Base ecosystem. We turn vague "contributions" into verifiable, immutable **Soulbound Tokens (SBTs)**. #### Phase 1: The "Trustless" Resume (Live Now) We built the infrastructure to standardize reputation data. 1. **Context-Aware Metadata** Most POAPs or NFTs just say "You were there." **BASED** says "You *did* this." Our protocol captures: 'Project Name', 'Specific Role' (e.g., "Winner", "Mentor"), 'Issuer Authenticity', and 'Timestamp'. It’s not just attendance; it’s **Outcome**. 2. **Zero-Friction Batching (The "Organizer" UX)** In an efficient hackathon, organizers shouldn't spend 3 hours minting 100 certs manually. **The Fix:** We built an **Optimistic Client-Side Sequencer**. Organizers paste a simple CSV. Our engine generates unique, generative SVG art for *each* recipient instantly and queues the transactions. 100 winners? 1 click flow. 3. **Social Native (Farcaster Integration)** A certificate that lives in a wallet is dead. A certificate that lives in the feed is alive. **The Feature:** Every BASED proof is inherently a **Farcaster Frame**. Paste the link on Warpcast, and it renders an interactive credential. Builders don't just "share a link"; they embed their verifiable status directly into the conversation. #### Phase 2: The "Graph" of Talent (Roadmap) Phase 2 shifts BASED from a "Tool" to a "Network." 1. **The "Vouch" Protocol** Reputation isn't just top-down (Organizer to Builder). It's peer-to-peer. We are building a mechanism where Verified Winners can "Vouch" for teammates. This creates a *Web of Trust*. If a 5x Hackathon Winner vouches for you, that signal outweighs 100 LinkedIn endorsements. 2. **Onchain Headhunting** Recruiters currently spam generic DMs. In Phase 2, they can query the **BASED Graph**: *"Find me a wallet that has won a DeFi Hackathon AND has contributed to open-source governance."* The hiring process becomes queryable.

How it's made

Challenges we ran into #### 1. The "Static" Batching Problem We wanted organizers to mint unique certificates for multiple winners instantly. However, standard contract batching approaches (like ERC-1155) usually enforce *identical* metadata for the whole batch number, or require expensive off-chain indexing to map IDs to diverse metadata. **The Pivot:** We realized we couldn't rely on simple IPFS folder uploads because the "Award Date" and "Specific Role" might vary per user in the same batch. **The Fix:** We architected a **Frontend Generative Pipeline**. The client generates a unique SVG + JSON payload for *every single row* in the CSV on-the-fly, hashes it, and feeds it to the sequencer. We effectively decentralized the "Minting Service" to the user's browser, removing the need for a centralized backend API that could fail or be rate-limited. #### 2. The React 19 vs OnchainKit Conflict We committed to building on the bleeding edge (Next.js 15 + React 19). However, this triggered severe dependency conflicts with '@coinbase/onchainkit', which wasn't ready for the new React hook semantics. **The Engineering Call:** Instead of downgrading which is tech debt, we **reverse-engineered** the identity layer. We manually promoted 'wagmi' experimental hooks to stable implementations within our app to handle ENS/Base name resolution. This allowed us to keep the high-performance React 19 architecture (Server Components) while preserving the native "Base" look and feel. #### 3. The "Ghost" Network Friction During beta testing with hackathon participants, we found a 30% drop-off rate where users thought they minted, but they were actually on Ethereum Sepolia (L1). The UI showed "Success" (for the L1 tx), but the item never appeared in their L2 app. **The Solution:** We built a strict **Network Guard**. It’s not just a warning banner; it’s a UI gatekeeper. It programmatically intercepts the 'writeContract' intent, checks the chain ID against the rigorous Base Sepolia constant, and triggers a wallet-level 'switchChain' request *before* the transaction payload is even constructed. We force the user to be on the right rail, or the train doesn't leave the station.