Run It Twice Main Pot Side Pot Resolution Mechanics

The USA Run It Twice Main Pot Side Pot Resolution protocol is not a courtesy feature — it is a hard-coded settlement layer that most operators implement with catastrophic gaps in pot isolation logic. When a table triggers two-board mode, the main pot and every side pot must resolve against two independent board states, and the software must track fractional eligibility per board. Miss that, and you get collusion-grade errors where a short stack scoops equity it never qualified for. 😤

The core failure point sits in the split-engine handoff. Side pots are built from capped contribution layers, and each layer carries its own eligibility matrix. Under run-it-twice, that matrix doubles. A player all-in for 4,000 in a 12,000 main pot has zero claim on the second board's side pot remainder unless the layer math re-tabulates per board. I have audited skins where the engine reused the first board's eligibility vector for the second board — a silent bankroll leak that pays the wrong stack 30% of the time on multi-way all-ins.

Objecting Player Rights in USA Cardrooms

Here is where the Objecting Player in USA clause becomes a legal tripwire, not a UX nicety. House rules across Nevada, New Jersey, and Pennsylvania cardrooms grant any dealt-in player the right to object before the first flop card drops. The objection must be logged with a timestamp, and the objecting player's equity path must be flagged in the hand history. Operators who bury the objection toggle three menus deep are begging for dispute escalation.

The technical requirement is brutal: objection state must bind to the hand ID, not the session. If the objecting player is later eliminated from the main pot but still live in a side pot, the objection status governs whether the second board even materializes for that layer. I have seen engines that honored the objection globally but ignored it at the side-pot layer — resulting in a split resolution on a pot that should have run once. That is a rules violation with real cash exposure.

Fractional Equity and Board-State Locking

Run-it-twice math demands that each board resolve independently, then equity is averaged across both boards at the settlement layer — never mid-hand. The Main Pot Side Pot Resolution logic must lock board-state per layer before the river of board one completes. Any engine that recalculates eligibility after board two's turn card is fundamentally broken. 🎯

Watch the fractional carry: a player with 60% main-pot equity on board one and 0% on board two nets 30% of the main pot, but side-pot layers can invert that ratio entirely. The objection flag, when active, collapses the average to a single-board result — and the settlement ledger must reflect that collapse at the exact millisecond the objection was registered, not at showdown. Operators running unsigned objection logs are sitting on a dispute bomb.

Audit Vectors for Settlement Integrity

Pull the hand history and verify three things: board-state lock timestamps precede board-two dealing, eligibility vectors differ per board in the raw log, and objection flags carry hand-ID binding with a flop-timing gate. Any deviation means the resolution engine is leaking value or exposing the house to regulatory complaints. The objecting player's legal standing in USA jurisdictions depends entirely on that timestamp chain holding — and if the side-pot layer resolves before the objection gate closes, the entire run-it-twice settlement is void retroactively.