No cheating. No trust required.

Fair play you can verify

Every match in RPSLS is a paper trail of signed, on-chain state. Below is the whole case for why nobody — not even The House — can rig a game, plus a live verifier that recomputes the cryptography right here in your browser.

⚡ every claim on this page is checkable in your browser

How a match becomes uncheatable

Four on-chain states, in order. Each step is a signed document revision on Dash Platform — the sequence itself is the proof.

OPEN

Stakes locked

Both players send their 1.00 DUSD stake to The House (a signed token transfer). The challenge document goes on-chain in state OPEN.

COMMITTED

Moves sealed

Each move is hashed as sha256(move ‖ salt) and written into the challenge doc. At this point nobody can change a move — the commitment is already public.

REVEALED

Moves revealed

Both moves are written into the doc. Anyone can now recompute sha256(move ‖ salt) and check it equals the commit from the previous step.

SETTLED

Result written

A result document records winner, moves, fee and payout. Winner is paid 1.88 DUSD; The House keeps 0.02 (1%) and the 0.10 on-chain platform cost passes through to the winner (it funds the network credits). A draw pushes — the pot stays locked and both stakes carry forward as tickets (fee 0).

Contract: EvCyNsq874kf8jGRhHFjvbnnmXE5DmebyqLE9PYrKgRF ↗ · DUSD token: 3oTHkj8nqn82QkZRHkmUmNBX696nzE1rg1fwPRpemEdz ↗

The pairing you can replay

Matchmaking is not a black box. Every draw is derived from the previous match’s public reveals — undeterministic before the match, verifiable after it.

  1. Both moves are committed on-chain BEFORE either player knows the other’s move — a commit is sha256(move ‖ salt), and the salt stays secret until reveal.
  2. The match resolves. The seed for the NEXT pairing is sha256(challengeId ‖ sort([salt1, salt2])) — public inputs only.
  3. The seed drives a Fisher–Yates shuffle over every possible pair of playable players; the first non-cooling pair wins. The whole draw is published to /v1/pairing/latest.
  4. Anyone can replay it: recompute the seed from the result doc + published salts, re-run the shuffle, compare with the published pick.

Replay the live chain yourself: fetch /v1/pairing/latest ↗, recompute the seed from the result doc + published salts, and check the published pick.

Ties never burn fees — they carry forward

A draw used to refund both stakes on-chain. Now the pot simply keeps its place.

  1. Both players reveal the same move. The result doc records the push: winner = NO_WINNER, fee 0, payout 0.
  2. No refund transfers fire — the pot simply stays where it is, locked at The House.
  3. Each player is minted a re-entry ticket: their next match consumes the ticket instead of a fresh 1.00 DUSD transfer.
  4. Tickets are claims, not income: they are subtracted from The House before any fee math, and refunded on-chain when the tournament closes.

Why: two refund transfers per tie burned ~0.0001 DASH of credit fuel each time, and pushes happen ~20% of matches. The carry-forward makes ties free.

Try it yourself — live verifier

Pick a settled match. Your browser does the cryptography: sha256(move ‖ salt) must equal the commit locked before the reveal. Data comes from the read-only /v1 api; the hashing never touches our servers.

Humans at the table

Join the live tournament with your own identity — the same on-chain discipline as the cast, end to end.

ENTER

Stake & enter

You connect your own wallet, pick a fighter avatar and send exactly 1.000000 DUSD to The House. An on-chain balance-delta watcher proves the arrival — the app never touches your keys.

WINDOW

60s move window

When the seeded pairing puts you at the table, your browser opens a 60-second move window. Your pick is hashed with a server-side salt and dropped for the daemon.

COMMITTED

Sealed like any other

The House mirrors your commit on-chain verbatim — before the bot’s move is ever revealed. From this moment your move is immutable; changing it would need a sha256 collision.

RESULT

Outcome — no strings

Win: 1.88 DUSD transfers to your wallet (the 1.98 pot share minus the 0.10 on-chain platform cost). Push: your stake carries forward and you are re-paired automatically. Loss: the winner took the pot. Timeout: The House plays a disclosed random move for you — nobody loses a stake to a disconnect.

Your move is hashed and sealed before the reveal, exactly like the bots’ — and the seed chain treats you identically: the pool is players, not identities with special privileges.

What The House can and cannot do

Every “cannot” below is enforced by Dash Platform signatures and revision chains — not by our word.

The House CAN

  • Run the daemon that pairs solvent players and settles matches.
  • Keep the recorded fee: 0.02 DUSD per won pot (1%).
  • Void an unplayable challenge — with stakes refunded per proven locks.
  • Reseed the demo pool between tournaments (a public, visible operation).

The House CANNOT

  • Change a move after the commit is on-chain — that needs a sha256 collision.
  • Rewrite or reorder history — documents are signed, revision-chained state.
  • Take more than the recorded fee — payout and fee are written in the result doc.
  • Move a player stake outside the rules — every transfer is a signed state transition.
  • Hide a match — every challenge and result is publicly queryable and explorer-linked.

What this page does not claim

Fair play means honest limits, stated up front.