Most launch platforms decide your visibility with upvotes. That sounds democratic until you notice what actually wins: posting at the right hour, having the right followers, and a network that shows up on cue.
So I built the opposite as an experiment. On LaunchBid, your rank is exactly the number of tokens bid on your product. No votes, no algorithm, no launch window. Totals never reset and anyone can outbid anyone.
The token economy
Three ways to get tokens:
- Share quest: post about it on X, paste your post link, get 50 tokens. Verified server-side against the post's real content.
- Explore quest: 2 tokens for each listing you visit, capped at 10 a day.
- Buy a pack: card checkout, credited automatically by webhook.
Listing costs 50 tokens and the share earns exactly 50, so a free listing costs one public post. That was deliberate: free-but-frictionless invites spam, free-but-costs-a-post invites distribution.
What I learned building it
Enforce money rules in the database, not the app. Every token movement is an append-only ledger row, balances can't go negative, and spending happens inside a single atomic Postgres function:
update profiles set token_balance = token_balance - 50
where id = v_user and token_balance >= 50
returning token_balance into v_balance;
if v_balance is null then
raise exception 'NOT_ENOUGH_TOKENS';
end if;
Because the guard lives in the where clause, two concurrent requests can never both succeed on the same last tokens. When I later raised the listing price, I changed one function and the entire app was correct.
Anonymous identity removes the biggest drop-off. There is no signup at all. Every visitor silently gets an anonymous session, so someone can land, earn tokens, and list a product without ever seeing a password field. Row-level security still isolates every balance.
Deterministic generation beats stored assets. Every product gets a pixel character generated from its slug, so a listing keeps its face forever with zero storage and zero uploads. That one bit me: I seeded the palette indices with a 32-bit hash and used >> to shift it.
const hair = HAIRS[(h >> 4) % HAIRS.length]; // negative index when the high bit is set
const hair = HAIRS[(h >>> 4) % HAIRS.length]; // fixed
Signed shifts turned half the hashes negative, which produced undefined colors and crashed rendering on the server. The board still looked fine in the browser because it silently fell back to client rendering, so the only visible symptom was my HTML quietly emptying out. Use >>> on hashes.
The honest part
Paying for rank sounds cynical. I would argue it is the most transparent thing on a launch site: everyone can see exactly what a position cost, and nobody pretends the ranking is organic.
It is Minecraft-themed, with skins, sound effects, and an explosion when you list something. Take a look: launchbid.lol
