How the Clearing Floor was built

GameBling existed once before, as a Counter-Strike betting site on infrastructure that eventually died the way old stacks do — quietly, expensively, and all at once. When we decided to rebuild it on hashtag.org, we made one decision before writing any code, and it turned out to decide everything else: a game joins this floor only when its results can be proven by an authority that is not a player. Our own servers, or the publisher’s official records. Nobody self-reports; nobody ever takes an opponent’s word for a scoreline with money on it.

That single rule is why the catalog looks the way it does. CS2 is the flagship because we can run the servers ourselves and the server is the referee. Dota 2 works because Valve hosts every lobby and publishes every match record. PUBG and osu! work as performance duels because Krafton and osu! publish official APIs. Battlefield 6 is contests-only — EA publishes no per-match records, so head-to-head cannot be settled honestly, and we would rather ship a smaller honest product than a bigger dishonest one. Some big titles are missing entirely because their publishers prohibit or prevent proof. The rule decides; we just enforce it.

The money engine

Under the floor sits a settlement engine with two properties we treat as sacred. Every money movement is idempotent — retried, raced, or replayed, a settlement can only ever happen once, because every movement carries a caller-supplied key the ledger enforces. And no stake can strand: every failure path in the system ends in a refund. A match that never starts refunds. A queue you leave refunds. A server that dies mid-negotiation refunds. The wallet is GIGI credits on the hashtag.org network, so deposits, escrow, and payouts all live on one ledger with one audit trail.

On top of that engine sits the part you see: the Clearing Floor. A match is a two-sided ticket that walks a rail — STAKE, MATCH, PLAY, SETTLE — with live scores pushed in real time, a career heat panel fed kill-by-kill from the servers, and settlement the instant the authoritative record lands. The design language is a settlement terminal, because that is what this actually is.

The referee that never blinks

Real money attracts cheating, so fair play got three layers before launch got one feature. VAC screens every player at the door, and an account with a ban on record cannot stake at all. An anomaly engine scores every settled match’s stats — impossible accuracy, inhuman timing — and anything suspicious holds the money in escrow for human review instead of paying out. And because our CS2 servers record a demo of every match, that review happens against evidence, not testimony. An AI advisor reads flagged matches and writes its verdict for the human who decides.

The same data feeds friendlier machines. An AI coach reads your real match history — the server-reported one, not your memory of it — and prescribes drills. Scouting briefs size up your counterparty when a match locks. None of these systems move money; all of them make the floor smarter.

Built in public, shipped in weeks

The rebuild went from empty repository to live floor in about a week, and then kept shipping: five games with five settlement paths, squad wagers with per-member stake consent, weekly contest pools, a compliance rail with age attestation and regional gating, and the legal pages nobody reads until they matter. This changelog is the honest record of that pace — including this week’s wave: per-kill wagering, the in-game money HUD, automatic clips, proximity voice, and the move to our own cloud.

The thesis has not changed since the first commit: skill wagering works when nobody has to trust anybody — not their opponent, not a screenshot, not even us, because the record is public and the money math is checkable. Everything on this floor is a consequence of that sentence. The rest is shipping.