Next scheduled rescrape ... never
Version 1
Last scraped
Scraped on 22/04/2025, 22:34:45 UTC
@foxymethoxy

I have to admit you are a funny clown, but facts say more than thousand hallucinations!  Wink

Why not speak about facts instead of hallucinated Stake's in-house Black Jack simulations?

You can of course simulate how Black Jack should be, but what has this to do with Stake's in-house Black Jack?

Only the scam artists Bijan and Edward know what code is running on their backend server!

The Curacao Gaming Control Board doesn't care that Stake's in-house Black Jack is provably rigged!

Hi,

I explained that yes, that is exactly Stake's implementation- it is 1:1.

Show proof that Stake uses your simulation software?


If you use the same seed pair, and nonce, you will get the same result- you can double check that by checking on stake's site, or stakestats.

If I use what same seed pair and nonce, I will get what same result?


Therefore, my simulator is simulating what would be genuine, real games, if those seeds were used. You can try to diminish that by saying it's just a simulation, but that's exactly how the game is coded- the visuals and frontend are just there to animate the mechanics, which are core and are indeed open source and reproducible.

Your simulator?

But there is a difference between your simulator and Stake's backend server software?

There is a difference between a simulator and reality.

Did your simulator came to a 4,6% expeeiencedexperienced house edge after 180,900 bets?

If Stake uses your simulator, your simulator should lead to the same 4,6% experienced house edge, right?


If my code can replicate the results of every hand you ever play, given the same inputs (hmac(secret=unhashedserverseed, message=clientseed:nonce:round)) independent of their site, then it is the same game.

 Cheesy

 
Your analysis was flawed because you were miscounting natural blackjacks, improperly using doubles and splits, and this skews your RTP down.

Here you show what a stupid little sickhead you are!

1) I didn't count my Stake bets statistics, Stake did!  Roll Eyes

2) My analysis of the maximal possible deviation from the expected outcome is not flawed.

If you believe it is flawed, show where and why it is flawed?


Stake Stats uses similar code to reproduce your bets- they are not connected to the house, or anything like that.

The bets I made on stake.com are not connected to the house?

So Stake outsourced my bets to who?


They have no idea whether you won or lost, and yet, they can still reproduce specific nonces.

Stake isn't aware about its bets statistics?

Is Stake isn't aware about the crypto currencies threythey took from me, or did somelse not related to Stake take it?

I have read a lot of hallucinations here on Bitcointalk, but you are doubtless one of the top hallucinators here!  Cheesy


Have you ever considered why, or tried to do it yourself? I guess not.

I am not able to understand what you want mesuggest to try?

But my Stake bets statistics (confirmed by Stake) is 100% proof that their in-house Black Jack is rigged and there is no need to try something else.
Original archived Re: 🚨Exposing Stake Originals: "PROVABLY FAIR" Statistical Evidence of Manipulation
Scraped on 22/04/2025, 22:29:30 UTC
@foxymethoxy

I have to admit you are a funny clown, but facts say more than thousand hallucinations!  Wink

Why not speak about facts instead of hallucinated Stake's in-house Black Jack simulations?

You can of course simulate how Black Jack should be, but what has this to do with Stake's in-house Black Jack?

Only the scam artists Bijan and Edward know what code is running on their backend server!

The Curacao Gaming Control Board doesn't care that Stake's in-house Black Jack is provably rigged!

Hi,

I explained that yes, that is exactly Stake's implementation- it is 1:1.

Show proof that Stake uses your software?


If you use the same seed pair, and nonce, you will get the same result- you can double check that by checking on stake's site, or stakestats.

If I use what same seed pair and nonce, I will get what same result?


Therefore, my simulator is simulating what would be genuine, real games, if those seeds were used. You can try to diminish that by saying it's just a simulation, but that's exactly how the game is coded- the visuals and frontend are just there to animate the mechanics, which are core and are indeed open source and reproducible.

Your simulator?

But there is a difference between your simulator and Stake's backend server software?

There is a difference between a simulator and reality.

Did your simulator came to a 4,6% expeeienced house edge after 180,900 bets?

If Stake uses your simulator, your simulator should lead to the same 4,6% experienced house edge, right?


If my code can replicate the results of every hand you ever play, given the same inputs (hmac(secret=unhashedserverseed, message=clientseed:nonce:round)) independent of their site, then it is the same game.

 Cheesy

 
Your analysis was flawed because you were miscounting natural blackjacks, improperly using doubles and splits, and this skews your RTP down.

Here you show what a stupid little sickhead you are!

1) I didn't count my Stake bets statistics, Stake didRoll Eyes

2) My analysis of the maximal possible deviation from the expected outcome is not flawed

If it is flawed, show where and why it is flawed?


Stake Stats uses similar code to reproduce your bets- they are not connected to the house, or anything like that.

The bets I made on stake.com are not connected to the house?

So Stake outsourced my bets to who?


They have no idea whether you won or lost, and yet, they can still reproduce specific nonces.

Stake isn't aware about its bets statistics?

Is Stake aware about the crypto currencies threy took from me, or did somelse not related to Stake take it?


Have you ever considered why, or tried to do it yourself? I guess not.

I am not able to understand what you want me to try?

But my Stake bets statistics (confirmed by Stake) is 100% proof that their in-house Black Jack is rigged and there is no need to try something else.