Contact person: Live Stream Poker Betting Integration

Phone:Show

Email:Show

Location: port harcourt, Nigeria

Budget: Recommended by industry experts

Time to start: As soon as possible

Project description:
"I need somone with poker experience to build this into a live stream with the following features do not bid if you cant do the project.

The Goal
They want a rule‑driven system that:
• Controls how bets are placed and matched.
• Handles all‑in situations and creates side pots automatically.
• Locks pots at the right time so no one can sneak in late bets.
• Makes payouts in the correct order and deducts the host’s commission.
• Shows all of this visually on screen for players and viewers.
1. Pot Locking
• When the host clicks “Deal,” the current pot is locked — no more bets can go into it.
• Any new bets after that go into a new pot (for the next round).
: . First Bet Sets the Minimum
• The first player to bet decides the minimum bet amount for that round.
• Everyone else must either:
• Match that amount, or
• Go all-in if they have less money than the minimum.
3. Raise Handling
• If someone raises the bet (e.g., from $50 to $70), the current bet amount becomes $70.
• Other players must add only the difference between what they’ve already bet and the new total.
4. All-In & Side Pots
• If a player can’t match the full bet but still wants to play, they can go all-in with what they have.
• Their money goes into the main pot.
• Any extra bets from other players beyond that amount go into a side pot.
• Only players who matched the full bet can win from that side pot.
• Multiple side pots can exist if this happens more than once.
5. Pot Structure
• Main Pot: Everyone’s money up to the smallest all-in.
• Side Pots: Extra pots for players who bet more than the all-in player.

6. Payouts
• The host picks the winner(s) manually.
• Payout order:
1. Main pot first
2. Then side pots in the order they were created
• A player can only win from pots they were eligible for.
Host Commission
• Host can set a percentage cut (e.g., 10%).
• This is automatically deducted before payouts.

8. UI & Animations
• Always show:
• Pot name
• Total value
• Who’s in the pot
• Animate:
• Chips moving from player to pot when betting
• Chips moving from pot to winner when paying out
Validations (Error Checks)
• Players must have enough balance or be all-in to bet.
• No betting after a pot is locked.
• Winners must be eligible for the pot they’re being awarded.

Example in Action
1. Player A bets $50 → minimum set.
2. Player B matches $50.
3. Player C has $30 → goes all-in.
4. Player D raises to $70.
5. A & B add $20 more to match.
6. C is only in the main pot.
7. Side pot created for A, B, D.
8. If D raises again, another side pot is made.
Architecture overview

make sure you write 25 at the end of your bid to ensure you read my requirement
• Backend services
• Game Service: Orchestrates tables, rounds, pot states, bet validation, payouts.
• Pot Manager: Pure domain logic for bets, raises, all‑ins, and side pots.
• Wallet Service: Player balances, debits/credits, escrow during hands.
• Payout Service: Host commission + multi‑pot settlement with eligibility checks.
• Transport
• HTTP API: Room/table setup, host controls, winner selection.
• WebSockets ([login to view URL]): Real‑time bet updates, pot changes, animations.
• Storage
• PostgreSQL: Persistent state per game/round/pot/player contribution.
• Redis: Pub/sub for rooms, ephemeral locks, idempotency keys.
• Clients
• Host Console: Deal/lock, pick winner(s), override/undo.
• Viewer/Player Overlay: Pot cards, animated bet chips, payout animations." (client-provided description)