Technical note · Fair play
Fair play across a shared network
Detection on the Bodog network is not a Bodog feature — it is a PaiWangLuo feature. Because Bodog, Bovada, and Ignition share one platform, the same anti-bot machinery watches all of them and can act across all of them. This note describes the signals that machinery uses and why cross-skin reach is the part most people underestimate.
The network removes the data a bot needs (anonymous tables) and watches the data a bot leaks (timing, sizing, sessions, device, funding). Crucially, that watching happens at the platform layer, so a flag raised on one skin can lead to action on accounts across every skin. There is no "clean" sister brand to retreat to.
The first line is structural, not detective
Before any model runs, the table design already blunts automated play. Hidden screen names and shuffled seating mean a bot cannot accumulate reads on specific opponents — the core edge most profitable bots rely on. This is passive defence built into the platform, and it applies identically to Bodog, Bovada, and Ignition.
What the active detection layer watches
On top of the structural defence sits behavioural analysis. The categories below are standard across serious operators; the difference here is that they are computed once, centrally, over the combined traffic of every skin.
| Signal class | What it captures | Why a bot struggles to hide it |
|---|---|---|
| Timing | Action delays and their variance | Software cadence is more regular than human hesitation |
| Bet sizing | Distribution of raise/bet amounts | Solver-clean sizing forms tell-tale clusters |
| Session shape | Length, table count, breaks | Bots play longer, flatter sessions than people |
| Device | Fingerprint, automation traces | Headless or emulated environments leak markers |
| Funding | Deposit / withdrawal graph | Shared wallets and payout patterns link accounts |
Why cross-skin reach is the real story
On a standalone poker room, evading detection is a single-room problem. On a shared platform it is not. A device fingerprint, a funding pattern, or a behavioural cluster seen on Bovada is visible to the same layer that runs Bodog and Ignition. Opening an account on a different skin does not reset the slate — it presents the same identity to the same watcher.
What this means in practice
- No fresh start by switching brands. Bodog → Bovada → Ignition is one identity space, not three.
- Detection improves with scale. More skins feeding one model means more examples of normal and abnormal play.
- Enforcement is network-wide. Action taken on a flagged account is not contained to the skin where the flag arose.
The honest researcher's takeaway
For studying how multi-skin operators police automated play, the Bodog network is a clean example: structural defence (anonymous tables) plus centralised behavioural detection plus cross-skin enforcement. For anyone weighing whether to run automated software here, the same three facts read as a warning. Both readings come from the same architecture, which is why understanding the network comes before any conclusion about bots on it.
If you are researching detection design, cross-skin correlation, or how automated play behaves against a shared platform, we are happy to compare notes — including with people building the bot software on the other side of this problem.
Reach out