> For the complete documentation index, see [llms.txt](https://docs.overtime.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.overtime.io/overtime-casino/games/table-games/ultimate-texas-holdem.md).

# Ultimate Texas Hold'em

Heads-up Texas Hold'em against the dealer, with the twist that defines the game: the earlier you commit to your hand, the bigger you're allowed to raise. Staged VRF reveals keep every unseen card out of storage until you've acted.

{% content-ref url="/spaces/qSlj8vWOOVBuhXhcN6iy/pages/NZrywrDfHMp3ldl3BIfA" %}
[OVERTIME CASINO](/overtime-casino/introduction-to-overtime-casino.md)
{% endcontent-ref %}

***

### How it works

You post two equal bets up front, an **Ante** and a **Blind,** and then play out a hand of Hold'em against the dealer across three decision points. At each one, you can raise once (and only once per hand); the size you're allowed depends on how early you act:

1. **Pre-flop** (you've seen only your two hole cards): raise **3× your ante**, or check.
2. **Post-flop** (you've seen the flop) only if you checked pre-flop: raise **2× your ante**, or check.
3. **Post-river** (all five community cards are out) only if you've checked all the way: raise **1× your ante**, or fold.

Once you raise, you're done raising. The earlier you're confident enough to commit, the more you can put behind your hand, which rewards reading a strong hole-card start.

Each decision triggers a **separate Chainlink VRF request** for the cards it reveals. The flop doesn't exist until you act pre-flop; the turn and river don't exist until you act post-flop; the dealer's hole cards aren't drawn until showdown. Future cards are never sitting in contract storage while you decide, which blocks any attempt to read them via `eth_getStorageAt` and act on them.

***

### How the bets resolve

After the river, your best five-card hand is compared to the dealer's. The three bets settle independently:

**Ante** - the dealer must qualify (have at least a pair) for the Ante to be in play:

* Dealer doesn't qualify → Ante pushes (returned)
* You win → Ante pays 1:1
* Dealer wins → Ante lost

**Play** (your raise) — resolves on hand comparison regardless of dealer qualification:

* You win → Play pays 1:1
* Tie → Play pushes
* Dealer wins → Play lost

**Blind** — pays only when you win, on a bonus scale based on your hand strength. On a tie it pushes; on a loss it's lost. Below a Straight, a winning Blind simply returns your stake.

| Winning hand       | Blind payout      |
| ------------------ | ----------------- |
| Royal Flush        | 500:1             |
| Straight Flush     | 50:1              |
| Four of a Kind     | 10:1              |
| Full House         | 3:1               |
| Flush              | 1:1               |
| Straight           | 1:1               |
| Less than Straight | Push (stake back) |

These are the standard Vegas / Shuffle Master Ultimate Texas Hold'em rules, with the Flush Blind payout set to 1:1 for margin.

***

### Limits

| Parameter        | Value                                          |
| ---------------- | ---------------------------------------------- |
| Minimum bet      | 3 USD (configurable per game via core)         |
| Ante / Blind     | Equal, posted at start                         |
| Max raise        | 3× ante (pre-flop), 2× (post-flop), 1× (river) |
| Blind top payout | 500:1 (Royal Flush)                            |
| Dealer qualifier | Pair or better (affects Ante only)             |
| Cancellation     | Admin/resolver only                            |

Supported collaterals: **USDC**, **WETH**, **$OVER**. Free bets supported via the `isFreeBet` flag — Ante/Blind and all raises route through the free-bet system.

***

### User guide

#### 1. Open Ultimate Texas Hold'em

Select it from the casino lobby. Set your Ante (the Blind matches it automatically) and your collateral.

#### 2. See your hole cards, decide pre-flop

The first VRF request deals your two hole cards. Raise 3× now if you like your start, or check to see the flop.

#### 3. Post-flop decision (if you checked)

The flop is dealt by the next VRF request. Raise 2×, or check to see the turn and river.

#### 4. River decision (if you checked through)

The turn and river complete the board. Make your final call: raise 1×, or fold.

#### 5. Showdown

The dealer's hole cards are revealed by the final VRF request, hands are compared, and the Ante, Play, and Blind all settle in one transaction.

***

### Why this matters

Ultimate Texas Hold'em lives or dies on information ordering. The strategy is built entirely around acting before you've seen the next card — that's why an early raise is allowed to be bigger. If the unseen cards were readable from contract storage during your decision, the entire strategic structure collapses. Overtime's staged VRF means each card is generated only when the game needs to show it to you, from an independent verifiable random word. The dealer's hole cards come last, at showdown, and never exist before that. You play the same game a Vegas table offers — except you can verify the deck was never stacked.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.overtime.io/overtime-casino/games/table-games/ultimate-texas-holdem.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
