Warning: Jackbit Technical Flaw (CSP/API 404s) - Support Ignoring Verified Fixes

[thedemiurge]

I'm posting this to warn the gambling community about a recent experience with Jackbit. I identified a critical front-end relay error (CSP violations and malformed API paths) that was breaking the transaction dashboard.

Despite providing the technical diagnosis and helping resolve the issue, support (specifically Agent Marceline) has attempted to dismiss the case as a 'game rule' dispute.

I have posted the full console logs, GIF evidence of the failure, and email receipts over in the Service Discussion board here: https://bitcointalk.org/index.php?topic=5581765.new#new

If you are a VIP player, be aware that their support team may lack the technical literacy to handle actual site bugs, even when a user provides the fix for them.

[Agbe]

It would have been better you posted it in their announcement thread here https://bitcointalk.org/index.php?topic=5434569.500 and those who are still using the casino would have seen it and if there is any representative. Though when I visit the ANN thread, their last active in the forum or post on the thread was January this year. Thank for informing the community. We put it into consideration.

[CryptSafe]

I'm posting this to warn the gambling community about a recent experience with Jackbit. I identified a critical front-end relay error (CSP violations and malformed API paths) that was breaking the transaction dashboard.

Despite providing the technical diagnosis and helping resolve the issue, support (specifically Agent Marceline) has attempted to dismiss the case as a 'game rule' dispute.

I have posted the full console logs, GIF evidence of the failure, and email receipts over in the Service Discussion board here: https://bitcointalk.org/index.php?topic=5581765.new#new

If you are a VIP player, be aware that their support team may lack the technical literacy to handle actual site bugs, even when a user provides the fix for them.

If their online customer support does not give you a tangible response,  I believe they have a mail which you can write directly to the team so they can take up your matter and make sure they resolve it, because this might likely cause big damage to the casino if they do not take proactive measures to make necessary amendments, as JackBit is a big casino in the online crypto space.
Although they are not active here, I know this information would be very helpful to members who still use the platform.

[YeppaYoke]

This isn't a thing that casinos generally pay for. A user saying "the transaction page doesn't load" would've probably yielded the exact same result.
Casinos usually pay for issues regarding actual business/game logic (infinite money glitch), not 'waaah button is not loading'.

In your write-up you use a lot of fancy words that make it seem like you did something impressive.
"professional-grade technical labor"
"Jackbit’s user dashboard suffered a failure in its transaction history relay logic"

Like, those are things you could see immediately just by opening chrome devtools.
It also seems like you AI-generated a big portion of it, you don't really sound like a technical user.

Overall, don't expect bounties for UI bugs.

EDIT: this could've also very well been (and probably was) a cache error. Take a look at the 2 images below

Config loader
https://i.ibb.co/YTdsB9C4/brave-gf7s4-Hpyxd.png
As you can see, this request is cached to your disk.

Config loader response
https://i.ibb.co/QvSjK7ZN/brave-5-Jsrc2nw-Rq.png
As you can see, again, this request contains the API base for each API call.

How notification check is called
https://i.ibb.co/7JTdsJdq/brave-4-Bhma-Ik-Ir2.png
You can see that the 'fusionUrl' from the previous response is used to call the API.

If the fusionUrl is old or missing, the API call might fail, which is what looks as to have happened to you.

In your writeup:

Code:

GET https://jackbit.co/api//Notifications/v2/user-notifications 404 (Not Found)

This doesn't seem to be what an actual JackBit API URL looks like. My guess is that the config failed to load and you called the API with the actual host domain that you were on as the base url.

So yeah, maybe stop and think before you waste hours talking to AI about a fictional bug.

[Hispo]

I'm posting this to warn the gambling community about a recent experience with Jackbit. I identified a critical front-end relay error (CSP violations and malformed API paths) that was breaking the transaction dashboard.

Despite providing the technical diagnosis and helping resolve the issue, support (specifically Agent Marceline) has attempted to dismiss the case as a 'game rule' dispute.

I have posted the full console logs, GIF evidence of the failure, and email receipts over in the Service Discussion board here: https://bitcointalk.org/index.php?topic=5581765.new#new

If you are a VIP player, be aware that their support team may lack the technical literacy to handle actual site bugs, even when a user provides the fix for them.

Does your discovery have anything to do with exploiting the casino or withdrawing from their wallets more money than one actually has available on one's account?
Because even if that agent did not have much literacy when comes to those bugs you mentioned, usually they only care about game breaking bugs and exploits,.which could effectively cost them millions of dollars or at least some thousands of dollars, is someone decided to take advantage of those exploits.
As someone already mentioned here on this thread, your discovery needs to be considered a thread against the economy of the casino in order for it to be taken seriously.

Still, it would be cool if they gave you some tips for reporting and expkning how to deal with minor stuff which also affects the gambling experience of thousands of people out there.

[khaled0111]

Sorry but I'm not really sure what you are complaining about here. Are you frustrated because they didn’t pay you a bounty for your finding or because they didn’t acknowledge the bug publicly and pushed a silent patch instead?
Also, can you tell us why you considered this bug "critical"? Because as far as I can see (and I can be mistaken), it doesn’t look that "critical", tbh.