Wager Terms

0. Read this first

Wager races use real Bitcoin when production server gates allow them. The wager code path is unaudited and may contain bugs. Real Bitcoin is at risk: you may lose your entire stake due to software defects, key loss, browser crashes, settlement failures, provider limits, network congestion, or operator outages. Do not wager more than you can afford to lose. By using the wager feature, you accept full responsibility for any loss of funds.

If any of this is not acceptable to you, stop now. The rest of RyRacer (single races, race packs, leaderboard) is unaffected by this feature and stays available.

1. What this is

Wager races are skill-based two-player paid contests. Two players each stake bitcoin into an Ark escrow contract, race the same car, rules, and randomized track seed where applicable, and the higher validated score wins. RyRacer keeps 2.1% of a single-winner wager pot; winner receives 97.9% before network/provider fees. Ties/refunds have no platform fee. If both players post identical scores, the protocol treats the result as a tie and requires collaborative refund handling that may need both players and operator review.

Wager races are available only where RyRacer enables them through its launch controls. Do not participate if paid contests, Bitcoin wagering, wallet-based settlement, or similar activity is unlawful where you are located. RyRacer may restrict, pause, or terminate wager access at any time.

The public production per-player stake cap is 10,000 sats only when server-side gates, jurisdiction checks, compliance settings, velocity limits, and exposure caps allow it. Public client flags alone do not make wagers available.

2. How the money moves

• Each player sends their own stake sats to a shared 5-path Ark escrow address derived from both players, the Ark operator, and the platform arbiter.
• The 5 paths are aPayout, bPayout, sweep, collaborative, and unilateral. Winner payouts use the applicable player payout path and require the winner's browser wallet to cosign.
• RyRacer does not custody player funds or browser wallet private keys. Escrow movement is controlled by script conditions and signatures from the required player wallet, operator, and platform arbiter roles.
• On a clean single-winner settlement, the winner receives pot − fee. The fee is floor(pot × 210 / 10000) (2.1%, rounded down), so the winner receives 97.9% before network/provider fees.
• Ties and full-refund outcomes require the collaborative path. These outcomes have no platform fee and may require both players to sign a refund transaction and follow operator recovery instructions.
• On a forfeit (your opponent no-shows, disconnects, or fails plausibility), you win 97.9% of the pot before network/provider fees. The 2.1% platform fee still applies.
• On a mutual no-show (nobody funds), the match expires and nothing moves — nothing was escrowed in the first place.

3. You hold your own keys

The browser wallet stores a 32-byte private key in localStoragein plaintext (v1). You are responsible for backing it up via the widget's "Back up key" flow before funding.

If you lose your browser data without a backup, the funds in your wallet are gone. Ops cannot recover them. If you share your key, anyone with it can drain your wallet. Treat the backup like a bearer bond.

4. Refund and rescue status

The 5-path escrow includes collaborative and delayed unilateral exit paths, but the production user flow for tie refunds, full-refund outcomes, and failed settlement recovery may require manual operator handling.

Do not rely on an automated refund guarantee. If a match enters a failed or refund state, contact binmucker@proton.me with the match id, wallet public key, payment transaction ids, and any screenshots or error messages you have.

5. Score validation and cheating

All scores go through the same plausibility checks as paid races — minimum duration, maximum score rate, combo consistency. A score that fails plausibility is rejected, which counts as a forfeit for that player.

Attempts to tamper with the game client, replay scores, or sign for another player's slot are protocol violations and may result in account bans and forfeits.

6. Determinism caveat (v1)

The game loop uses wall-clock frame timing. Two players on different hardware see the same randomized event sequence, but the exact frame at which each event fires may differ by a few milliseconds. Mirror-match fairness in v1 is therefore perceptual, not bit-identical.

A future release will migrate to fixed-timestep physics for bit-identical cross-machine determinism. Practically, this effect is expected to be small, but it's a real property you should know about.

Disputed races based on wall-clock timing differences are not resolvable via replay in v1. They must go through the dispute and recovery process, and may not result in an automatic refund.

7. Jurisdiction, age, and eligibility

• You must be at least 18 years old and at least the age of majority in your jurisdiction.
• Wager races may be unlawful where you are located. The service may require jurisdiction checks or block access from restricted locations. Do not participate unless you are legally permitted to do so.
• You may not participate if you are sanctioned, blocked, using a prohibited payment method, acting for another person, or unable to pass any required identity, AML, or sanctions checks.
• If you want to self-exclude or cool off, contact binmucker@proton.me before participating.

8. Fees and settlement timing

• Platform fee: 2.1% of the pot, floored at the satoshi — floor(2 × stake × 210 / 10000). Winners receive 97.9% before network/provider fees. Applied to non-tie, non-refund outcomes only.
• Settlement target: under 2 minutes after both players submit. The server's timeout sweep runs every 2 minutes, but payout and refund timing is not guaranteed.
• The public production per-player stake cap is 10,000 sats only when the effective server-side stake, compliance, jurisdiction, velocity, and exposure gates allow it.
• If the operator is congested, settlement may take longer. The platform retries automatically up to 5 times. If all retries fail, the match is marked failed and ops is notified. Manual recovery may be required.
• Strike, Ark, Boltz, Lightning, mempool, wallet, and hosting providers may reject, delay, or limit transactions. Provider availability, rules, and transaction limits may change and can delay or prevent settlement.

9. Dispute policy

To dispute a wager outcome, contact binmucker@proton.me with the match id, wallet public key, transaction ids, screenshots, and a short description of what happened. Scores are validated by the same code for both players, but the game is not bit-identical across machines and replay verification is not complete.

RyRacer may review server logs, payment records, wallet signatures, score validation records, and payout or refund state. Some disputes cannot be technically reconstructed; available remedies may be limited to manual recovery, a refund process when possible, or no action if the records do not support the claim.

10. Contact

Support, privacy, dispute, refund, and security contact: binmucker@proton.me.