First Reported11 Jun 2026
Last Updated2d ago
Stable

Duelbits HiLo UI Shows Wrong Probabilities

A veteran HiLo player with over $5 billion wagered across platforms published video evidence of Duelbits displaying inverted hit-probability percentages — the UI showed "Lower" at 92% when the correct probability was approximately 15% — and says the error cost him $20,000 with zero response from Duelbits leadership.

Fairness DoubtSupport FailureTechnical Issue
196%
Posts 24h
26Total Posts
51.2KImpressions
126Engagement
ImpactMedium Risk

Risk is de-escalating due to collapsing volume — no immediate action required for affiliates

DuelbitsJoe's unresolved silence remains a credibility concern; monitor for any belated response which would re-ignite the story

Players who frequently play HiLo on Duelbits should verify displayed probabilities independently until the casino addresses CasinoScarface's evidence

Signal VolumePosts / day
Sentiment% / day
ImpressionsReach / day
EngagementReactions / day
Top Posts6 POSTS
Jing
·4d ago

Yeah that's messed up, never heard of something like this before. Bump @DuelbitsJoe https://t.co/TieWqfpUtc

negative
231133.1K
degenlifestyl
·4d ago

@DrWgamba @CasinoScarface @DuelbitsJoe @housebets @p0rchy Dr. W, the “crypto terrorist” recording sessions only when his bag’s at risk. “I give visibility even when it doesn’t affect me” 😂 Bro, the reply nailed it — the ONLY thing you’ve ever supported is 100% about you. Ninja cat GIF and all. Selective outrage merchant. Clown.

negative
00128
Dr. W
·4d ago

@CasinoScarface @DuelbitsJoe Lately, I’ve also been recording all my sessions; that’s how I caught @housebets and @p0rchy in all the manipulations they’ve committed. I’m sharing it, brother. Unlike others, I do try to give visibility to these cases even when they don’t affect me directly; at least we’ll https://t.co/qhYDCdtqW1

negative
803556
Scarface
·4d ago

Hey @DuelbitsJoe, I've been away from the space for some time, but it seems you still haven't fixed what are clearly development errors on your platform. Earlier this year (or possibly late 2025), I returned to Duelbits and was quite active on the platform. One day, while playing HiLo, I noticed something unusual. At first, I thought I was imagining it because I was deep into a gambling session, but considering I've wagered well over $5 billion on HiLo alone across various sites, I decided to pay closer attention. What was the issue? I discovered what appeared to be a critical UI error. The "Lower" option was displayed as having a 92% hit chance when, based on the card shown, it should have been approximately 15% (or whatever the correct probability was). Instead, the platform displayed "Lower" as the higher-probability outcome and "Higher" as the lower-probability outcome. Any experienced HiLo player makes decisions based on the displayed percentages rather than waiting to calculate the probabilities manually. If the percentages shown are incorrect, that has the potential to mislead players and affect their decisions. You might not believe me, but I started recording my screen to see if it would happen again. It did. I captured it on video, sent the evidence to you, and what happened next? Nothing. So I'd like to ask the public for their opinion. Below, I'll attach screenshots and recordings of the gameplay. I asked you to investigate the issue, fix the error, and compensate me because I believe this mistake cost me approximately $20,000. What's even more concerning is that, to this day, another issue still exists: if you have an active HiLo session and refresh the page, the round can disappear entirely. How is that considered normal behavior? And while we're discussing this, let's also address the RTP claims. You promote your house games as having a 99% RTP, yet in the video, a HiLo sequence starting on a 5 (bet High, then Low on a J, then High on a 2, followed by a cashout) resulted in a net payout of 1.79x. Performing the same sequence and achieving the same outcome on Stake pays 1.83x. Can you explain that discrepancy?

negative
4071314.8K
Scarface
·4d ago

Hey @DuelbitsJoe, I've been away from the space for some time, but it seems you still haven't fixed what are clearly development errors on your platform. Earlier this year (or possibly late 2025), I returned to Duelbits and was quite active on the platform. One day, while playing HiLo, I noticed something unusual. At first, I thought I was imagining it because I was deep into a gambling session, but considering I've wagered well over $5 billion on HiLo alone across various sites, I decided to pay closer attention. What was the issue? I discovered what appeared to be a critical UI error. The "Lower" option was displayed as having a 92% hit chance when, based on the card shown, it should have been approximately 15% (or whatever the correct probability was). Instead, the platform displayed "Lower" as the higher-probability outcome and "Higher" as the lower-probability outcome. Any experienced HiLo player makes decisions based on the displayed percentages rather than waiting to calculate the probabilities manually. If the percentages shown are incorrect, that has the potential to mislead players and affect their decisions. You might not believe me, but I started recording my screen to see if it would happen again. It did. I captured it on video, sent the evidence to you, and what happened next? Nothing. So I'd like to ask the public for their opinion. Below, I'll attach screenshots and recordings of the gameplay. I asked you to investigate the issue, fix the error, and compensate me because I believe this mistake cost me approximately $20,000. What's even more concerning is that, to this day, another issue still exists: if you have an active HiLo session and refresh the page, the round can disappear entirely. How is that considered normal behavior? And while we're discussing this, let's also address the RTP claims. You promote your house games as having a 99% RTP, yet in the video, a HiLo sequence starting on a 5 (bet High, then Low on a J, then High on a 2, followed by a cashout) resulted in a net payout of 1.79x. Performing the same sequence and achieving the same outcome on Stake pays 1.83x. Can you explain that discrepancy?

negative
11159
wisPy
·4d ago

Well.... pretty pathetic from @Duelbits @DuelbitsJoe @DuelbitsAce told on here that i should log into my account and redeem my free spins find nothing go to support told I am limited from "certain promotions" no reason given end of story https://t.co/NgWNmyjLgx https://t.co/4uAC4Smclz

negative
80431.0K
Developing Story
11 JUN · 07:50 UTC

CasinoScarface, a player who claims over $5 billion in lifetime HiLo wagers, published a detailed complaint with video evidence showing Duelbits' HiLo game displaying critically wrong probability percentages. The UI showed "Lower" with a 92% hit chance when the actual probability based on the card shown should have been approximately 15% — effectively swapping the high and low probability labels.

The error is an active UI bug, not a one-time glitch. CasinoScarface says he recorded his screen and captured it happening repeatedly, sent the evidence to DuelbitsJoe, and received no response whatsoever.

The player estimates the error cost him roughly $20,000, arguing that experienced HiLo players make rapid decisions based on the displayed percentages rather than manually calculating probabilities on every card. The complaint also flags a second unresolved issue: refreshing the page during an active HiLo session causes the round to disappear entirely.

11 JUN · 07:50 UTC

CasinoScarface added a secondary allegation regarding RTP claims. He demonstrated that a specific HiLo sequence (High on 5, Low on J, High on 2, then cashout) pays 1.79x on Duelbits versus 1.83x on Stake for the same sequence — challenging Duelbits' advertised 99% RTP on house games.

JingaLingJoya amplified the complaint to the public timeline, calling it 'messed up' and directly tagging DuelbitsJoe for a response. DrWgamba also engaged, connecting the Duelbits situation to his own experience with Housebets and noting he now records all his sessions as a precaution.

The complaint comes at a particularly awkward moment for Duelbits: the brand was just named the first ProvablyFair.org certified casino on June 10 with 10 games independently verified. A public UI error on one of its most-played originals directly undercuts the trust the certification is meant to build.

11 JUN · 14:00 UTC

Post volume surged to 20 in a single day with 95% negative sentiment and 13,842 impressions — the story has become the most active negative narrative in the ecosystem. The ProvablyFair.org juxtaposition is amplifying the story's reach: players are framing the HiLo UI error not just as a technical bug but as a direct contradiction to the freshly-minted certification.

DuelbitsJoe has not yet responded publicly. The silence is becoming its own narrative — every hour without a statement increases community suspicion that the complaint is being ignored rather than investigated. A separate complaint also surfaced from elloWisp, who reported being told by Duelbits support that they are 'limited from certain promotions' with no reason given, adding a secondary trust issue to Duelbits' current community standing.

12 JUN · 00:00 UTC

Post volume surged to 26 in a single day with 85% negative sentiment and 49,941 impressions — the story has become the most active negative narrative in the ecosystem and is now impossible for Duelbits to ignore.

The ProvablyFair.org juxtaposition continues to amplify the story's reach: players are framing the HiLo UI error not just as a technical bug but as a direct contradiction to the freshly-minted certification. DuelbitsJoe has now been silent for over 24 hours since CasinoScarface's detailed public callout.

The silence is hardening into its own narrative — every hour without a statement increases community suspicion that the complaint is being ignored rather than investigated.

Two new dynamics emerged: DegenDynasty1 is now actively attacking DrWgamba in the thread, calling him a 'crypto terrorist' and 'selective outrage merchant,' creating in-thread drama that is extending the post's visibility. Meanwhile, a separate complaint from elloWisp — who was told by Duelbits support that they are 'limited from certain promotions' with no reason given — adds a second, unrelated trust dimension to Duelbits' current community standing.

12 JUN · 05:45 UTC

After the 27-post surge that made this the most active negative narrative in the ecosystem, volume collapsed 96% to a single post on June 12. The story burned hot and fast — but DuelbitsJoe's silence has now stretched past 48 hours, transforming the absence of a response into its own verdict.

Every additional hour without a statement from Duelbits increases community suspicion that CasinoScarface's complaint — backed by screen recordings and a detailed public callout — is being ignored rather than investigated. The ProvablyFair.org juxtaposition continues to raise the stakes: a freshly certified casino now faces credible allegations of wrong probability displays with zero public acknowledgment.

Two dynamics are extending the story's tail even as raw post volume recedes: DegenDynasty1's ongoing attacks on DrWgamba in the thread are creating in-feed drama that keeps the post circulating, and elloWisp's separate complaint about being 'limited from certain promotions' with no reason given adds a second, unrelated trust dimension to Duelbits' current community standing. The combined weight of both complaints — one technical, one service-related — paints a picture of a casino that is unresponsive when challenged.

12 JUN · 12:30 UTCLATEST

Volume collapsed 96% to a single residual post on June 12, with impressions dropping from 51,236 to 13. The story burned through its entire community attention in 48 hours, but the underlying credibility wound is now permanent — DuelbitsJoe's silence has stretched past 72 hours across two separate public complaints (the HiLo UI error and elloWisp's promo restriction).

The absence of any response from Duelbits is now the story. In an ecosystem where ProvablyFair.org certification was meant to signal trustworthiness, a casino carrying that badge has chosen to ignore rather than address a documented technical complaint from a high-volume player ($5 billion+ wagered on HiLo alone).

The DegenDynasty1 vs DrWgamba side-drama that kept the thread circulating has also gone quiet. With no new evidence, no response from Duelbits, and no escalation, the theme has exhausted its community momentum — but the unresolved complaint remains a permanent reference point for anyone researching Duelbits' credibility.

11 JUN · 07:50 UTC

CasinoScarface, a player who claims over $5 billion in lifetime HiLo wagers, published a detailed complaint with video evidence showing Duelbits' HiLo game displaying critically wrong probability percentages. The UI showed "Lower" with a 92% hit chance when the actual probability based on the card shown should have been approximately 15% — effectively swapping the high and low probability labels.

The error is an active UI bug, not a one-time glitch. CasinoScarface says he recorded his screen and captured it happening repeatedly, sent the evidence to DuelbitsJoe, and received no response whatsoever.

The player estimates the error cost him roughly $20,000, arguing that experienced HiLo players make rapid decisions based on the displayed percentages rather than manually calculating probabilities on every card. The complaint also flags a second unresolved issue: refreshing the page during an active HiLo session causes the round to disappear entirely.

11 JUN · 07:50 UTC

CasinoScarface added a secondary allegation regarding RTP claims. He demonstrated that a specific HiLo sequence (High on 5, Low on J, High on 2, then cashout) pays 1.79x on Duelbits versus 1.83x on Stake for the same sequence — challenging Duelbits' advertised 99% RTP on house games.

JingaLingJoya amplified the complaint to the public timeline, calling it 'messed up' and directly tagging DuelbitsJoe for a response. DrWgamba also engaged, connecting the Duelbits situation to his own experience with Housebets and noting he now records all his sessions as a precaution.

The complaint comes at a particularly awkward moment for Duelbits: the brand was just named the first ProvablyFair.org certified casino on June 10 with 10 games independently verified. A public UI error on one of its most-played originals directly undercuts the trust the certification is meant to build.

11 JUN · 14:00 UTC

Post volume surged to 20 in a single day with 95% negative sentiment and 13,842 impressions — the story has become the most active negative narrative in the ecosystem. The ProvablyFair.org juxtaposition is amplifying the story's reach: players are framing the HiLo UI error not just as a technical bug but as a direct contradiction to the freshly-minted certification.

DuelbitsJoe has not yet responded publicly. The silence is becoming its own narrative — every hour without a statement increases community suspicion that the complaint is being ignored rather than investigated. A separate complaint also surfaced from elloWisp, who reported being told by Duelbits support that they are 'limited from certain promotions' with no reason given, adding a secondary trust issue to Duelbits' current community standing.

12 JUN · 00:00 UTC

Post volume surged to 26 in a single day with 85% negative sentiment and 49,941 impressions — the story has become the most active negative narrative in the ecosystem and is now impossible for Duelbits to ignore.

The ProvablyFair.org juxtaposition continues to amplify the story's reach: players are framing the HiLo UI error not just as a technical bug but as a direct contradiction to the freshly-minted certification. DuelbitsJoe has now been silent for over 24 hours since CasinoScarface's detailed public callout.

The silence is hardening into its own narrative — every hour without a statement increases community suspicion that the complaint is being ignored rather than investigated.

Two new dynamics emerged: DegenDynasty1 is now actively attacking DrWgamba in the thread, calling him a 'crypto terrorist' and 'selective outrage merchant,' creating in-thread drama that is extending the post's visibility. Meanwhile, a separate complaint from elloWisp — who was told by Duelbits support that they are 'limited from certain promotions' with no reason given — adds a second, unrelated trust dimension to Duelbits' current community standing.

12 JUN · 05:45 UTC

After the 27-post surge that made this the most active negative narrative in the ecosystem, volume collapsed 96% to a single post on June 12. The story burned hot and fast — but DuelbitsJoe's silence has now stretched past 48 hours, transforming the absence of a response into its own verdict.

Every additional hour without a statement from Duelbits increases community suspicion that CasinoScarface's complaint — backed by screen recordings and a detailed public callout — is being ignored rather than investigated. The ProvablyFair.org juxtaposition continues to raise the stakes: a freshly certified casino now faces credible allegations of wrong probability displays with zero public acknowledgment.

Two dynamics are extending the story's tail even as raw post volume recedes: DegenDynasty1's ongoing attacks on DrWgamba in the thread are creating in-feed drama that keeps the post circulating, and elloWisp's separate complaint about being 'limited from certain promotions' with no reason given adds a second, unrelated trust dimension to Duelbits' current community standing. The combined weight of both complaints — one technical, one service-related — paints a picture of a casino that is unresponsive when challenged.

12 JUN · 12:30 UTCLATEST

Volume collapsed 96% to a single residual post on June 12, with impressions dropping from 51,236 to 13. The story burned through its entire community attention in 48 hours, but the underlying credibility wound is now permanent — DuelbitsJoe's silence has stretched past 72 hours across two separate public complaints (the HiLo UI error and elloWisp's promo restriction).

The absence of any response from Duelbits is now the story. In an ecosystem where ProvablyFair.org certification was meant to signal trustworthiness, a casino carrying that badge has chosen to ignore rather than address a documented technical complaint from a high-volume player ($5 billion+ wagered on HiLo alone).

The DegenDynasty1 vs DrWgamba side-drama that kept the thread circulating has also gone quiet. With no new evidence, no response from Duelbits, and no escalation, the theme has exhausted its community momentum — but the unresolved complaint remains a permanent reference point for anyone researching Duelbits' credibility.