Bitcoin Forum
May 22, 2024, 06:46:33 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: « 1 2 3 [4]  All
  Print  
Author Topic: stake.com and Casino.guru coverup.  (Read 586 times)
cryptogeniusdice (OP)
Newbie
*
Offline Offline

Activity: 130
Merit: 0


View Profile
October 15, 2023, 10:50:33 AM
 #61

compare both the iterations dydx is from CG

Let me guess, he's from casinoguru because he pointed out your wrongs and mistakes? Because, apparently, anyone that's against you in this case, are working for casinoguru. But sure, why not? I'll take the bait. So what if he's from CG? It doesn't change the fact that your arguments are wrong and Stake didn't cheat you.


if your mother sleeps with whole village you can’t deny the fact she is whore. this is how much you are in denial about stake.com .
cryptogeniusdice (OP)
Newbie
*
Offline Offline

Activity: 130
Merit: 0


View Profile
October 30, 2023, 11:03:08 AM
 #62

dvdx how come your code is not now working.


please send the code here again
cryptogeniusdice (OP)
Newbie
*
Offline Offline

Activity: 130
Merit: 0


View Profile
November 11, 2023, 10:46:09 AM
 #63

dvdx



i am at certainity that hiw the games of mines work. but can you proof read the difference between the first and the ssecond iteration also explain me why is it two iterations are so much having difference.
and also how come second iteration has 2 mines , in it . so how come so many tiles opened for bombs it clearly specifies over there.
also https://onlinephp.io/ can you migrate the program here ans give us a link , so that i can verify if its working or not


Will try to explain this to you one more time like to 5 year old.


Let's assume i go to mines and wanted to play mine game with 3 mines

At the beggining i known HASHED SERVER SEED , MY SECRET AND NONCE

Lets say it's

HASHED SERVER SEED = 'e7f3006651ac9fa2252cb6db7de2cfa50e8fb9ff479fd16afd45e9f5fa52c24b';
MY SECRET = 'J8ziLyE0L5';
NONCE = 1;

I Started to open mines at position
1st Click "field" : 0,
2nd Click "field" : 6,
3rd Click "field": 12,
4th Click "field": 18,
5th Click "field": 24,
6th Click "field": 21,
7th Click "field": 17,

On the 7th Click i busted as mine was uncovered/clicked.

Now i want to verify if actually MINE WAS AT THAT POSITION at that game with NONCE 1.

So i have rotated the seed to get the output for SERVER SEED , stake output for that string in
SERVER SEED UNHASHED = '8935bff6600c9ebb504505757ca881131e5f4a2766e8b0debd687100be6e17c4';

Okay move on now to verify the outcome of the mines for that particular game

For that instance I've used the code which i wrote yesterday to verify the mine bet

Output of my code (link for you to verify https://onlinephp.io/c/b9616 )

Code:
lets verify if my unhashedServerSeed is actually sha256 hashedServerSeed , Result: => bool(true)
Mines postions
Game Nonce:1
0 = 13
1 = 17
2 = 5
3 = 8
4 = 10
5 = 24
6 = 15
7 = 7
8 = 6
9 = 22
10 = 19
11 = 0
12 = 21
13 = 1
14 = 3
15 = 20
16 = 4
17 = 16
18 = 2
19 = 23
20 = 11
21 = 12
22 = 18
23 = 14


Okay so i know that i have played with 3 mines that particular game

It means in my game mines positions are

0 = 13 (1st mine position field)
1 = 17 (2nd mine position field)
2 = 5 (3rd mine position field)

Okay it clearly shows a mine at position field 17 which i uncovered and busted (as explained above)

NOW ASSUME BY SOME REASON STAKE PUT THAT BET TO THE ARCHIVE WITH THE REST OF THE FIELD WHICH I DID NOT OPENED/CLICKED

SO IN MY LOGS I SEE

Code:
"state": {
                "mines": [
                    13,
                    17,
                    5
                ],
                "minesCount": 3,
                "rounds": [
                    {
                        "field": 0,
                        "payoutMultiplier": 1.125
                    },
                    {
                        "field": 6,
                        "payoutMultiplier": 1.2857142857142856
                    },
                    {
                        "field": 12,
                        "payoutMultiplier": 1.4785714285714282
                    },
                    {
                        "field": 18,
                        "payoutMultiplier": 1.7120300751879696
                    },
                    {
                        "field": 24,
                        "payoutMultiplier": 1.9973684210526312
                    },
                    {
                        "field": 21,
                        "payoutMultiplier": 2.3498452012383897
                    },
                    {
                        "field": 17,
                        "payoutMultiplier": 0
                    },
                    {
                        "field": 1,
                        "payoutMultiplier": 0
                    },
                    {
                        "field": 2,
                        "payoutMultiplier": 0
                    },
                    {
                        "field": 3,
                        "payoutMultiplier": 0
                    },
                    {
                        "field": 4,
                        "payoutMultiplier": 0
                    },
                    {
                        "field": 5,
                        "payoutMultiplier": 0
                    },
                    {
                        "field": 7,
                        "payoutMultiplier": 0
                    },
                    {
                        "field": 8,
                        "payoutMultiplier": 0
                    },
                    {
                        "field": 9,
                        "payoutMultiplier": 0
                    },                    
                    {
                        "field": 10,
                        "payoutMultiplier": 0
                    },
                    {
                        "field": 11,
                        "payoutMultiplier": 0
                    },
                    {
                        "field": 13,
                        "payoutMultiplier": 0
                    },                    
                    {
                        "field": 14,
                        "payoutMultiplier": 0
                    },
                    {
                        "field": 15,
                        "payoutMultiplier": 0
                    },                    
                    {
                        "field": 16,
                        "payoutMultiplier": 0
                    }
                    {
                        "field": 19,
                        "payoutMultiplier": 0
                    }
                ]
            }

Does that log format affect anyhow the result of the game ?

NO IT DID NOT

1st .
1. Mines position -> IN THE LOG MINES ARE IN THE SAME ORDER AS IN MY CODE OUTPUT (AFTER VERIFICATION OF BET)

2. ORDER OF FIELDS OPENED IS EXACTLY THE SAME AS MY MANUALL CLICKS TILL I BUSTED ON FIELD 17

the EXTRA DATA FOR OPENED FIELDS DOEST NOT AFFECT ANYTHING AS AT THAT POINT I ALREADY LOST THAT GAME ( WHEN CLICKED MINE AT FIELD 17)

So it means even if for some reason the output for fields opened have some EXTRA additional fields which were not clicked, BUT the ORDER OF that which we clicked is OK, it means there is no any manipulation.

I don't know how STAKE store the logs for best, but if the ORDER OF THE FIELDS OPENED TILL BUST IS EQUAL TO ACTUALLY CLICKED FIELDS IN GAME AND MINES POSITIONS IS IN THE SAME ORDER
IT MEAN THE RESULT IS FAIR.





nice coverup dvdx you gave us the calculation on mines , then you deleted it . its shows that provabkyfair.me is entity of stake.com . either you are employee of stake.com or casino.guru. stake.com scams are not stopping on originals
Pages: « 1 2 3 [4]  All
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!