Gauntlet–Challenge friends to Strava activities with real money (USDC)

Name: Gauntlet–Challenge friends to Strava activities with real money (USDC)
Availability: InStock
Author: lucidlogic

by lucidlogic·Feb 16, 2026·1 point·1 comment

Visit Project View on HN

AI Analysis

●●SolidBold BetSolve My Problem

Fitness app + real money on-chain—clever use case, but betting mechanics aren't novel.

Strengths

•On-chain USDC avoids building internal ledgers; ~$0.01 transaction costs on Base L2 are genuinely cheap
•Embedded wallet (Privy) lowers friction—no MetaMask required for non-technical athletes
•Strava integration + real money creates genuine skin-in-the-game motivation

Weaknesses

•Regulatory risk: betting platform classified as gaming/wagering in most jurisdictions—launch could face legal friction
•Limited differentiation: sports betting and fitness challenges both solved; crypto payment is the only novel angle

Post Description

Hey HN,

I built Gauntlet (gauntlet.bet) — a platform where you challenge friends to fitness activities on Strava with real money on the line. Stakes are held in USDC on Base L2, so payouts are instant and transparent. No internal ledger — everything is on-chain.

How it works: - Create a challenge (e.g. "Run 10K before March 1st — $25 stake") - Invite friends or make it open - Everyone stakes USDC via an embedded wallet (Privy) - Strava verifies completion automatically - Winners split the pot, losers lose their stake

Tech stack: Laravel 12, React 19, Inertia.js, Tailwind, MySQL. Blockchain side is a Node.js sidecar using viem for USDC transfers on Base. WebSockets via Laravel Reverb for real-time challenge updates.

Why on-chain? I didn't want to deal with holding user funds or building a ledger. USDC on Base means ~$0.01 transaction fees, near-instant finality, and users can verify everything. The embedded wallet (Privy) means nobody needs to know what a wallet is — they just sign in with email or Google.

What I learned: - Nonce management for sequential blockchain transactions is painful — ended up using cache locks to serialize payouts - fake() doesn't work in production (learned this the hard way today) - Strava's webhook API is solid but their rate limits are aggressive

Solo project, built over ~2 weeks. Would love feedback on the concept and any thoughts on the staking mechanics.