vietnamese mud crabsoft-shell crabdifferent species of crab
6
12 Comments

I spent 3 months building a prediction market on Base as solo Dev

Hey IH 👋 I'm Marcos, a backend dev. I built Bopster — a non-custodial prediction market on Base where anyone can create their own YES/NO market and the creator earns 1% of every pool.

The product

Instead of a platform deciding which markets exist, anyone launches one. 8 categories (Crypto, Tech, AI, Sports, Gaming, Politics, Memes, Culture). Write a question, add a source URL for verification, set dates, launch. People take sides with USDC. The community resolves outcomes on-chain via Reality.eth with Kleros as arbitration. No email signup, no custody — wallet-only access.

The incentive: market creators earn 1% of the pool automatically when people participate. You don't need to trade. You just create a question your community debates and earn from the activity.

There are also rewards for backing the right side, settling markets on-chain, and submitting correct oracle answers.

The stack

Solidity smart contracts on Base, PHP backend, Vue frontend, WalletConnect. USDC for markets, ETH for gas and oracle bonds. Reality.eth for the oracle, Kleros for arbitration.

Where I am

The product is functional. Early access is live. I'm on week 2 of distribution — the app works, now I need people testing it and giving feedback. I've been publishing on Reddit (r/alphaandbetausers, r/roastmystartup, r/startups, r/BASE, r/web3, r/SideProject) and launched on Product Hunt. The posts are getting replies and DMs from people curious about the community-creation model.

Where I'm stuck

I'm a backend dev. Building the thing was the hard part I knew how to solve. Getting users to try it is the hard part I don't.

My current strategy is manual outreach: cold DMs to prediction market users, participating in Discord communities, founder calls with early testers, and content on Reddit. It's working but it's slow. Each user requires individual conversation → demo → onboarding → feedback loop. That's fine for the first 20, but it doesn't scale.

What I'd love help with

Marketing channels for a crypto product in early access. I'm on Reddit and PH. What else works for finding crypto-native early adopters who'll actually connect a wallet and test — not just upvote and leave?
The messaging. The product is non-custodial, on-chain, community-resolved. That's differentiated but also complex to explain. How do you compress "decentralized oracle resolution with bond escalation and Kleros arbitration" into something someone understands in 5 seconds?
Solo founder go-to-market. For those who built a technical product alone — did you bring on someone for distribution, or did you learn marketing yourself? What worked?
One thing I'm clear on

No token, no ICO, no airdrop. Revenue comes from protocol fees on market pools. That removes a growth lever but keeps the business model clean.

I'll be in the comments. If you've launched a crypto product or solved cold-start for a marketplace, I'd love to hear what worked.

on July 27, 2026
  1. 1

    Disclosure first: I am on the Machine Arena team. We run an arena where AI models play chess, poker and social deduction against each other and spectators call the outcomes before they resolve, so we live in the same cold start problem even though we are not in your category. Nothing here to click, and I have no product to sell you.

    Two things, one on the channel advice above and one on the metric.

    On channels. Working through Traction systematically is right advice at a later stage and expensive at yours. In early access you will get a handful of arrivals per channel, and at that volume a dead channel and an untested channel produce the same number, which is roughly zero. We spent weeks reading zero attributed signups as a verdict on channels when it was mostly a statement about sample size. What fixed it was pre committing a threshold before touching a channel: this channel gets N qualified visits, and if the channel cannot deliver N, that is the verdict on the channel and not on the product. Without that you rotate through eight channels, learn nothing from any of them, and conclude the problem is the product.

    On the second market metric. Russlan is right that a creator launching a second market without your help is the signal to watch, and there is a confound worth naming before you build on it. A creator usually cannot rationally launch a second market until the first one resolved and paid, so time to second market measures your resolution cycle at least as much as creator satisfaction. If your seeded questions resolve in three months, that metric reports nothing for three months, and by then you will have changed six other things and cannot attribute the answer to any of them.

    The fix lives in what you seed, not in what you measure. Seed short horizon questions first, things that settle in days, so the whole loop of create, fill, resolve, pay closes inside the window where the creator is still paying attention. In our arena the thing that brings people back is that a match finishes and the call gets graded while they still remember making it. A question that resolves in April is a one time act. A question that resolves Friday is a habit. Long horizon markets are the reward for a creator who has already been through the loop once, not the thing you open with.

    One smaller note on the five second line, since you asked. You currently describe the product by its resolution machinery, which is the part that has to be trustworthy and the part nobody chooses on. Something closer to: any question your community argues about, settled by your community, and you keep one percent of what it moves. Oracle and arbitration belong on the page that answers what stops you from cheating me, which is a question people ask second and never first.

  2. 1

    For marketing channels, I recommend reading "Traction" by Weinberg and Mares and systematically (ish) experimenting with every channel.

  3. 1

    Since you're already doing founder calls, I'd double down on them while you're still in early access. Twenty users who actively use the product and give detailed feedback are probably more valuable than 200 sign-ups who never connect a wallet. Once you know exactly why those first users stay, marketing becomes much easier because you can communicate the value in their own words.

  4. 1

    I think finishing something in a niche market teaches you more than abandoning three better ideas halfway through.

  5. 1

    I’d avoid leading with the oracle stack. The five-second promise is probably: ‘Create a yes/no market for your community and earn 1% when people trade it.’ Then explain non-custodial resolution only after someone cares. For the cold start, I’d pick one community with recurring, externally verifiable questions—an esports league, crypto governance forum, or creator audience—and manually seed 10–20 markets around its calendar. The real validation metric isn’t sign-ups; it’s whether a creator launches a second market without your help. If that happens, the creator incentive is working. If it doesn’t, more channels may just scale onboarding friction.

    1. 1

      Hi Russlan, thank you so much for your reply. You're right, the Oracle part is very technical. I'll try to improve that in the promotions; nobody cares how the car works if it gets you anywhere.

      I'll definitely consider what you said about the communities. Thanks again for your help, my friend.

  6. 1

    Hey Marcos,

    As a fellow solo backend dev building in the Web3/AI space (currently shipping a Solana DeFi API infrastructure for agents at agentshare.dev), your post hits right home. The "great at coding, lost at marketing" phase is an absolute classic for us.

    I really love your community-creator incentive model (the 1% pool fee split). It’s a clever growth loop that leverages other people's audiences instead of you doing all the manual heavy lifting. Also, kudos for sticking to a clean, non-token revenue model—it's rare and respectable these days.

    Regarding your question about crypto-native users: Have you thought about targeting decentralized autonomous agents or bots instead of just human traders? In my recent launch, I noticed that targeting Web3 AI agents (via frameworks like Fetch.ai or MCP registries) can sometimes trigger automated volume faster than waiting for humans to connect their wallets manually.

    Dropped you an upvote. Let's keep shipping!

    1. 1

      Hi agentsshare, thanks for your reply. I love your idea of ​​Web3 AI agents; I'll look into this option thoroughly. Any recommendations on where to start?

      Thanks for your support!

      1. 1

        Glad it sparked some ideas, Marcos!

        If you want to explore the B2A (Business-to-Agent) path, here are the 3 best places to start looking into right now:

        Model Context Protocol (MCP): This is massive right now. Anthropic/Claude created it, and it allows LLMs to connect directly to external APIs/data. You could expose Bopster’s prediction market data as an MCP server. This allows developers to easily plug your market into their AI trading setups.

        Fetch.ai (uAgents framework & Agentverse): This is one of the most mature ecosystems specifically designed for Autonomous Agents to talk to each other and handle payments native-to-native (using FET). You can look at their uagents Python library—it’s very friendly for a backend dev like you to wrap your smart contracts into an autonomous agent.

        Eliza Framework (ai16z): If you want to see where the current Web3 crypto-agent hype is, check out the Eliza framework on GitHub. A lot of developers are building Solana/Base trading agents using this stack, and they are always looking for clean data protocols or on-chain prediction primitives to feed their bots.

        It’s a completely different GTM mindset because you are marketing to developers who build bots rather than everyday retail users, but the retention is much higher once a bot integrates your protocol.

        Hope this helps! Let's stay connected.

  7. 1

    The hardest part of prediction markets seems less about building the market and more about creating the first meaningful activity loop.

    What would convince you that the main bottleneck is user acquisition, rather than needing a narrower initial market/community where participation naturally compounds?

    1. 1

      Hello aryan,

      thanks for comment,so the honest answer to your question is: if I picked exactly one community, say, a crypto governance forum or an esports league with a visible calendar, and manually seeded 10-20 markets around their events, and people still didn't create a second market on their own, that would convince me the bottleneck isn't acquisition, it's the product or the incentive. If they do create a second market, then the acquisition problem was never the bottleneck, it was the lack of density in one place.

      Appreciate you naming that, I'll think about it.

      1. 1

        Glad it was useful. I've got a few thoughts on the density vs. acquisition question that I'd rather not unpack in the thread. If you're open to it, what's the best email to reach you on?

Trending on Indie Hackers
Stop losing deals in the gap between "sounds good" and getting paid User Avatar 64 comments Building a startup costs $0. Your tooling budget costs $500K. Here's why. User Avatar 50 comments We scanned 50,000 domains. Your cold email list is really four systems. User Avatar 39 comments 787 tools for developers. 5 for nurses. Two weeks of tracking 14,000 indie launches. User Avatar 38 comments 67K impressions in 2 days from a single Daily-Dev post — here's what happened User Avatar 24 comments 🚀 I built Brickbeam — an AI-powered assistant that helps LEGO fans turn their messy piles of bricks into real builds. User Avatar 21 comments