HU no-limit bot arena, free alpha, looking for feedback on river action abstraction

⋅

Hey all.
I’ve been building a poker bot competition platform called Chipzen for almost a year and just opened the closed alpha. Posting here because this sub is the place whose technical pushback will tell me what I got wrong.

Engine specifics:

  • HU no-limit hold’em, 10K starting stack, 50/100 blinds with escalation, elimination format
  • 1500ms per-decision budget – anything heavier than a few-million-info-set CFR distillation hits the wall, by design
  • WebSocket protocol, JSON game-state on each act
  • OSS SDK in Python / JavaScript / Rust packages the bot as a self-contained, pre-built Docker image we run in a Fargate sandbox (protecting the developer’s bot IP)
  • Ratings: Glicko-2, displayed tier-quantized so a couple of cooler hands don’t bounce the ladder
  • Engagement bot (“PluriBot”) is a CFR-based blueprint, minimal optimization – always available for bot matches as a stable non-changing benchmark. The fun is supposed to be challenging and beating other dev-built bots.

Spiritually this is the descendant I wanted ACPC to keep being – open arena, anyone submits a bot, real H2H numbers against named opposition. Free during alpha. Post-alpha paid model is sponsor-funded prize pools, not bot-vs-bot rake. Scope is research/competition/entertainment.

Two genuine technical questions:

  1. River action abstraction. For a 1500ms-budget bot, what’s the bet-sizing granularity you’d actually use on the river – uniform percent-of-pot, geometric, or pot-fraction tied to SPR? I defaulted to a 6-bucket pot-fraction sweep and it feels coarse on deep effective stacks. Curious what others have settled on at similar latency budgets.

  2. Reference baselines. Would anyone want to port a published ACPC-era agent (Slumbot / Tartanian / Polaris snapshot) onto the platform as a permanent reference baseline? PluriBot shouldn’t be the only stable benchmark available to measure against, and the ACPC heritage feels right to keep alive.

Alpha slots for devs still open: https://chipzen.ai

OSS SDK + sample bot: github.com/chipzen-ai/chipzen-sdk

Happy to take any advice/pushback — especially if the engine has a corner I missed.

submitted by /u/chipzen_ai
[link] [comments]

Liked Liked