Search content
Sort by
Showing 9 of 9 results by dvdx1995
dvdx
again Benford law can be applied and is much effective with binary data.
you have pulled the program i appreciate it.
but your claims about archive data is absolutely wrong.
archive data you must know how to read.
again Benford law can be applied and is much effective with binary data.
you have pulled the program i appreciate it.
but your claims about archive data is absolutely wrong.
archive data you must know how to read.
The byteGenerator function generates a sequence of numbers based on the given inputs: serverSeed, clientSeed, nonce, and cursor. This function is based on the HMAC-SHA256 algorithm, which is widely used to generate cryptographically secure hashes. There is no obvious connection to Benford's law here, since this law deals with the distribution of the first digits of numeric data, while this function generates a sequence of bytes based on inputs.
Quote
there is manipualation in the back end of stake.com
hence the automated data which is archive in the back end won’t have such different iteration.
hence the automated data which is archive in the back end won’t have such different iteration.
Stake give you the results of each of the round played as the game is ended (win or lose)
Told you that you can either verify the results by the graphic image of the bet, or inspecting your network tab in the browser to see the outcomes...
there is no any time for manipulation in the back end, also if they would manipulate the result you would clearly see it while verifying the bets with the function i provided to you.
Quote
if you are saying that archive filing does not prove fairness of the bet. so why within 2days they archive the bet . and when we search bet it’s shows betid not found. i revolve seeds after a months of play. they archive only few bets which is manipulated or giving you loss on the first tile.
this is also a illegal practice by stake.com
your php program is good . i didn’t find any issue with the bet which is showing the system.
the problem is with the archive bet.
they are archiving the bets which they have manipulated and i am 100000percent sure…
this is also a illegal practice by stake.com
your php program is good . i didn’t find any issue with the bet which is showing the system.
the problem is with the archive bet.
they are archiving the bets which they have manipulated and i am 100000percent sure…
I assume as the amount of bets which they handle every day it may be some delays to generate the file for each of the user and it's unique bets ...
Im not behind the stake so i don't know how this process work in their backend to generate this file, but I i'm 101% sure that the file which they genereting to "provide" your bets does not prove the bet fairness....
It is just only to show you the bets which you can't see in your bet history as they limit the history to maximum of 40 last bets...
You can create this archive of your bets by your self registering each of your bet places and the outcome by yourself... then rotate your seed to verify the outcome and if you will find any game that have differend results with your own archive then we may assume something is mainpulated.. but since that point you have not proved that they manipulated anything.
Your acusation to them is that the iteration is different and some bets are missing in the bet archive file which you can download, but i will repeat this for x time, IT DOES NOT MATTER , as the FAIRNESS OF EACH BET is not based of that what you have in their "archive" but by the factors that i already mentioned to you at least 3 times.
looks like you sign up on bitcointalk.org only this post. just kidding.
see the fairness can be manioulated by stake it’s happening .
hence the archive results are different.
if they can manioulate the archive results which means they are purposely deleting the bets .
anyways your php script was helpful , but stake.com is manipulating the bets that’s for sure
and casino.guru is covering them by spreading all lies about the website.
Alright, so even though the facts and arguments presented to you, as well as the solutions on how you can verify each game fairness, don't seem to convince you, you still remain stubborn and believe you know best. Despite zero evidence of any manipulation, you insist that black is white..
I provided you with all the possibilities and data you need to verify each bet, also those which you have in your archive of bets and compare it with what the function calculating the occurrence of mines (sorted from 1 to 24 mines) returns... and you haven't provided any specific bet where manipulation is evident... Nevertheless, I wish you a good day and good luck. As I mentioned before, and as other users have confirmed in your previous topics, there doesn't appear to be any manipulation of bets here.
From my side, that's all.
looks like your profile was created only to comment on this bet,post 28th sept.
go ahead and compare iteration in point 3 of the post. how can i open 13 bombs on mines games of 2 bombs.
Yes and what is the point i opened exatyly my account because i wanted to explain you how this system works , how you can verify each of the bet, i even provided for you OPEN SOURCE CODE which everyone can see and verify if it returns correct results .. just wanted to be helpfull . But you like a parrot repeat the same over and over again..
Quote
and moreover you are saying the archive bets data is not usually provably fair.
what bullshit you are saying man.
Please read once again my comments on this topic and i hope you will understand WHY ARCHIVE BETS DOES NOT PROVE FAIRNESS ..what bullshit you are saying man.
HOW ARCHIVE CAN PROVE FAIRNESS IF YOU DONT KNOW SERVER SEED ??
THEY ARCHIVE BETS DAILY AND I DO NOT FIND ANY INFORMATION ABOUT UNHASHED SERVER SEED SO IF THAT ARICHVE IN YOUR OPINION PROVIDE A FAIRNESS HOW YOU CAN CALCULATE IT WITHOUT SERVER SEED ??
Last comment on that. Wish you to have a good day.
dvdx
again Benford law can be applied and is much effective with binary data.
you have pulled the program i appreciate it.
but your claims about archive data is absolutely wrong.
archive data you must know how to read.
again Benford law can be applied and is much effective with binary data.
you have pulled the program i appreciate it.
but your claims about archive data is absolutely wrong.
archive data you must know how to read.
The byteGenerator function generates a sequence of numbers based on the given inputs: serverSeed, clientSeed, nonce, and cursor. This function is based on the HMAC-SHA256 algorithm, which is widely used to generate cryptographically secure hashes. There is no obvious connection to Benford's law here, since this law deals with the distribution of the first digits of numeric data, while this function generates a sequence of bytes based on inputs.
Quote
there is manipualation in the back end of stake.com
hence the automated data which is archive in the back end won’t have such different iteration.
hence the automated data which is archive in the back end won’t have such different iteration.
Stake give you the results of each of the round played as the game is ended (win or lose)
Told you that you can either verify the results by the graphic image of the bet, or inspecting your network tab in the browser to see the outcomes...
there is no any time for manipulation in the back end, also if they would manipulate the result you would clearly see it while verifying the bets with the function i provided to you.
Quote
if you are saying that archive filing does not prove fairness of the bet. so why within 2days they archive the bet . and when we search bet it’s shows betid not found. i revolve seeds after a months of play. they archive only few bets which is manipulated or giving you loss on the first tile.
this is also a illegal practice by stake.com
your php program is good . i didn’t find any issue with the bet which is showing the system.
the problem is with the archive bet.
they are archiving the bets which they have manipulated and i am 100000percent sure…
this is also a illegal practice by stake.com
your php program is good . i didn’t find any issue with the bet which is showing the system.
the problem is with the archive bet.
they are archiving the bets which they have manipulated and i am 100000percent sure…
I assume as the amount of bets which they handle every day it may be some delays to generate the file for each of the user and it's unique bets ...
Im not behind the stake so i don't know how this process work in their backend to generate this file, but I i'm 101% sure that the file which they genereting to "provide" your bets does not prove the bet fairness....
It is just only to show you the bets which you can't see in your bet history as they limit the history to maximum of 40 last bets...
You can create this archive of your bets by your self registering each of your bet places and the outcome by yourself... then rotate your seed to verify the outcome and if you will find any game that have differend results with your own archive then we may assume something is mainpulated.. but since that point you have not proved that they manipulated anything.
Your acusation to them is that the iteration is different and some bets are missing in the bet archive file which you can download, but i will repeat this for x time, IT DOES NOT MATTER , as the FAIRNESS OF EACH BET is not based of that what you have in their "archive" but by the factors that i already mentioned to you at least 3 times.
looks like you sign up on bitcointalk.org only this post. just kidding.
see the fairness can be manioulated by stake it’s happening .
hence the archive results are different.
if they can manioulate the archive results which means they are purposely deleting the bets .
anyways your php script was helpful , but stake.com is manipulating the bets that’s for sure
and casino.guru is covering them by spreading all lies about the website.
Alright, so even though the facts and arguments presented to you, as well as the solutions on how you can verify each game fairness, don't seem to convince you, you still remain stubborn and believe you know best. Despite zero evidence of any manipulation, you insist that black is white..
I provided you with all the possibilities and data you need to verify each bet, also those which you have in your archive of bets and compare it with what the function calculating the occurrence of minutes (sorted from 1 to 24 minutes) returns... and you haven't provided any specific bet where manipulation is evident... Nevertheless, I wish you a good day and good luck. As I mentioned before, and as other users have confirmed in your previous topics, there doesn't appear to be any manipulation of bets here.
From my side, that's all.
dvdx
again Benford law can be applied and is much effective with binary data.
you have pulled the program i appreciate it.
but your claims about archive data is absolutely wrong.
archive data you must know how to read.
again Benford law can be applied and is much effective with binary data.
you have pulled the program i appreciate it.
but your claims about archive data is absolutely wrong.
archive data you must know how to read.
The byteGenerator function generates a sequence of numbers based on the given inputs: serverSeed, clientSeed, nonce, and cursor. This function is based on the HMAC-SHA256 algorithm, which is widely used to generate cryptographically secure hashes. There is no obvious connection to Benford's law here, since this law deals with the distribution of the first digits of numeric data, while this function generates a sequence of bytes based on inputs.
Quote
there is manipualation in the back end of stake.com
hence the automated data which is archive in the back end won’t have such different iteration.
hence the automated data which is archive in the back end won’t have such different iteration.
Stake give you the results of each of the round played as the game is ended (win or lose)
Told you that you can either verify the results by the graphic image of the bet, or inspecting your network tab in the browser to see the outcomes...
there is no any time for manipulation in the back end, also if they would manipulate the result you would clearly see it while verifying the bets with the function i provided to you.
Quote
if you are saying that archive filing does not prove fairness of the bet. so why within 2days they archive the bet . and when we search bet it’s shows betid not found. i revolve seeds after a months of play. they archive only few bets which is manipulated or giving you loss on the first tile.
this is also a illegal practice by stake.com
your php program is good . i didn’t find any issue with the bet which is showing the system.
the problem is with the archive bet.
they are archiving the bets which they have manipulated and i am 100000percent sure…
this is also a illegal practice by stake.com
your php program is good . i didn’t find any issue with the bet which is showing the system.
the problem is with the archive bet.
they are archiving the bets which they have manipulated and i am 100000percent sure…
I assume as the amount of bets which they handle every day it may be some delays to generate the file for each of the user and it's unique bets ...
Im not behind the stake so i don't know how this process work in their backend to generate this file, but I i'm 101% sure that the file which they genereting to "provide" your bets does not prove the bet fairness....
It is just only to show you the bets which you can't see in your bet history as they limit the history to maximum of 40 last bets...
You can create this archive of your bets by your self registering each of your bet places and the outcome by yourself... then rotate your seed to verify the outcome and if you will find any game that have differend results with your own archive then we may assume something is mainpulated.. but since that point you have not proved that they manipulated anything.
Your acusation to them is that the iteration is different and some bets are missing in the bet archive file which you can download, but i will repeat this for x time, IT DOES NOT MATTER , as the FAIRNESS OF EACH BET is not based of that what you have in their "archive" but by the factors that i already mentioned to you at least 3 times.
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
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
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
}
]
}
"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.
the one which stake has not archived the bet , its showing the correct mines.
you still did not understand the question. the problem is the iteration. the point 3 .
iteration 1 :
iteration 1:
{"id":"4199e11e-8861-4b8f-9b43-97ad560cd766","iid":"house:167247337064","type":"casino","scope":"house","userId":"c3299987-21b5-49ef-bb2b-92a8512912b1","betCasino":{"id":"4199e11e-8861-4b8f-9b43-97ad560cd766","active":false,"userId":"c3299987-21b5-49ef-bb2b-92a8512912b1","gameId":"f65ec3b7-705d-42e1-9050 d9ea6fd032b3","currency":"trx","value":0.0000165150794972,"expectedAmount":0.0000020809,"amount":0.00020809,"payoutMultiplier":0,"payout":0,"mobile":false,"serverSeedId":"c7ae0581-091f-4b85-ac5a-9e8e15c5f7b1","clientSeedId":"fc7c4338-e91f-4c13-9cdf-e4475593d7c9","nonce":544,"stateMines":{"_mines":[11,0],"rounds":[{"field":24,"payoutMultiplier":1.076086956521739},{"field":3,"payoutMultiplier":1.1739130434782608},{"field":10,"payoutMultiplier":1.2857142857142859},{"field":9,"payoutMultiplier":1.4142857142857147},{"field":11,"payoutMultiplier":0}],"minesCount":2},"updatedAt":1688820636227,"createdAt":1688820636227}}
for this betid the mines and reveal tile is correct. as soon as i clicked the bomb at 11 , the game is over and it’s archived in the system.[/u]
whereas for iteration 2 , which was registered in the system ..
id":"827819c9-5d9b-4579-a88c-befc0fa54e99","ip":"XXX.YYY.ZZZ.AAA","iid":"house:167250384449","type":"casino","nonce":602,"value":0.0000132,"active":false,"amount":0.0000132,"gameId":"f65ec3b7-705d-42e1-9050-d9ea6fd032b3","mobile":false,"payout":0,"userId":"c3299987-21b5-49ef-bb2b-92a8512912b1","currency":"usdc","gameName":"mines","createdAt":1688821605532,"updatedAt":1688821605532,"clientSeed":"O1zKuEp8081boobs","stateMines":{"_mines":[3,7],"rounds":[{"field":23,"payoutMultiplier":1.076086956521739},{"field":18,"payoutMultiplier":1.1739130434782608},{"field":13,"payoutMultiplier":1.2857142857142858},{"field":5,"payoutMultiplier":1.4142857142857146},{"field":6,"payoutMultiplier":1.5631578947368425},{"field":0,"payoutMultiplier":1.7368421052631584},{"field":1,"payoutMultiplier":1.941176470588236},{"field":2,"payoutMultiplier":2.1838235294117654},{"field":3,"payoutMultiplier":0},{"field":4,"payoutMultiplier":0},{"field":9,"payoutMultiplier":0},{"field":7,"payoutMultiplier":0},{"field":11,"payoutMultiplier":0},{"field":12,"payoutMultiplier":0},{"field":14,"payoutMultiplier":0},{"field":24,"payoutMultiplier":0},{"field":17,"payoutMultiplier":0},{"field":16,"payoutMultiplier":0},{"field":15,"payoutMultiplier":0},{"field":21,"payoutMultiplier":0},{"field":22,"payoutMultiplier":0},{"field":20,"payoutMultiplier":0}],"minesCount":2},"clientSeedId":"fc7c4338-e91f-4c13-9cdf-e4475593d7c9","serverSeedId":"c7ae0581-091f-4b85-ac5a-9e8e15c5f7b1","expectedAmount":1.3200000000000002e-7,"serverSeedHash":"aff867a8be94f30f5bd66c7bbf0fa7a85e1c10b187c22fddb93b5efe807cc4e7","payoutMultiplier":0},
mines for this bet id was 3, and 7 . as soon as i clicked on 3. the game should be over . but its not the game shows that i clicked on tiles 4,9,7,1,12,14,24,17,16,15,21,22,20 and 2 . how is this possible . and its not a. autobet which has been placed.
this iteration shows that apart from mines on tiles 3,7 the bombs were on rest of the tiles as well. [\b][\u]
stake controls the iteration , later on the bets are deleted citing as archive and the mines field array is filled. [\b][\u]
hence the bet is manipulated. [\b][\u]
when you play mines on 2 mines you will find bomb on the first click this is one of the reasons[\b][\u]
in this game i have got 7 first bomb for mines of 2. what are the chances for that. [\b][\u]
I think you missunderstood the concept of stake bet archive ...
That they provide for the customers some service like bet archiver where you can download and check out your bets it's actually nothing which can prove the bet was fair or not.
To verify if bet was fair you must have
1. record of the tiles (ordered, per click id) which you opened till busted on mine ( after that game is over) or you won/payed out the game at current nonce.
2. fields where mines were placed on your bet (before unhashed server seed is unrevealed) - you can see it in graphic view of the bet, as well if you more advanced you can check that in your browser network tab as stake actually provide this infrmation on the response request when you bust/cashout/win the round.
3. amount of mines played in specific game (per nonce)
4. unhashed server seed , hashed server seed , client seed , and nonce.
And now you can verify the fairness of the specific BET NONCE.
As i already wrote, i don't know why that iteration was shown/stored in their Archive bet system, but once again as you have the all data which i listed above you don't even need to have such like bet archive provided by Stake to proof the fairness of the bet or bets.
this is the issue with stake archiving the data within 3 -5 days and we revealing the seeds after big nonces . the archive doesn’t show the real esscense of gameplay.
the iteration on the back end is clearly something else.
also stake.com registered a mines games in two different iteration for same odds. which clearly specify that in the back end there is something wrong.
are you aware about hash value hash highway. merkle root verifcation using Benfords laws using merkle trees.
Will repear myself for x time..
To verify if bet was fair or not you don't need to have stake archivng... telling you that archiving file which you can download DOES NOT PROOF FAIRNESS OF THE BET... also the iteration which they store there does not prove anything...
That what prove the fairness of the bet is that what i mentioned in my previous comment, and you can verify any nonce you played on specific seed from nonce 0 to nonce X after you rotate the seed to get from stake unhashed server seed.
merkle root verifcation using Benfords laws using merkle trees. in this case does not have any sense as for stake the base of the calculation is binary outcome of keyed hash value using the HMAC method
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
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
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
}
]
}
"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.
the one which stake has not archived the bet , its showing the correct mines.
you still did not understand the question. the problem is the iteration. the point 3 .
iteration 1 :
iteration 1:
{"id":"4199e11e-8861-4b8f-9b43-97ad560cd766","iid":"house:167247337064","type":"casino","scope":"house","userId":"c3299987-21b5-49ef-bb2b-92a8512912b1","betCasino":{"id":"4199e11e-8861-4b8f-9b43-97ad560cd766","active":false,"userId":"c3299987-21b5-49ef-bb2b-92a8512912b1","gameId":"f65ec3b7-705d-42e1-9050 d9ea6fd032b3","currency":"trx","value":0.0000165150794972,"expectedAmount":0.0000020809,"amount":0.00020809,"payoutMultiplier":0,"payout":0,"mobile":false,"serverSeedId":"c7ae0581-091f-4b85-ac5a-9e8e15c5f7b1","clientSeedId":"fc7c4338-e91f-4c13-9cdf-e4475593d7c9","nonce":544,"stateMines":{"_mines":[11,0],"rounds":[{"field":24,"payoutMultiplier":1.076086956521739},{"field":3,"payoutMultiplier":1.1739130434782608},{"field":10,"payoutMultiplier":1.2857142857142859},{"field":9,"payoutMultiplier":1.4142857142857147},{"field":11,"payoutMultiplier":0}],"minesCount":2},"updatedAt":1688820636227,"createdAt":1688820636227}}
for this betid the mines and reveal tile is correct. as soon as i clicked the bomb at 11 , the game is over and it’s archived in the system.[/u]
whereas for iteration 2 , which was registered in the system ..
id":"827819c9-5d9b-4579-a88c-befc0fa54e99","ip":"XXX.YYY.ZZZ.AAA","iid":"house:167250384449","type":"casino","nonce":602,"value":0.0000132,"active":false,"amount":0.0000132,"gameId":"f65ec3b7-705d-42e1-9050-d9ea6fd032b3","mobile":false,"payout":0,"userId":"c3299987-21b5-49ef-bb2b-92a8512912b1","currency":"usdc","gameName":"mines","createdAt":1688821605532,"updatedAt":1688821605532,"clientSeed":"O1zKuEp8081boobs","stateMines":{"_mines":[3,7],"rounds":[{"field":23,"payoutMultiplier":1.076086956521739},{"field":18,"payoutMultiplier":1.1739130434782608},{"field":13,"payoutMultiplier":1.2857142857142858},{"field":5,"payoutMultiplier":1.4142857142857146},{"field":6,"payoutMultiplier":1.5631578947368425},{"field":0,"payoutMultiplier":1.7368421052631584},{"field":1,"payoutMultiplier":1.941176470588236},{"field":2,"payoutMultiplier":2.1838235294117654},{"field":3,"payoutMultiplier":0},{"field":4,"payoutMultiplier":0},{"field":9,"payoutMultiplier":0},{"field":7,"payoutMultiplier":0},{"field":11,"payoutMultiplier":0},{"field":12,"payoutMultiplier":0},{"field":14,"payoutMultiplier":0},{"field":24,"payoutMultiplier":0},{"field":17,"payoutMultiplier":0},{"field":16,"payoutMultiplier":0},{"field":15,"payoutMultiplier":0},{"field":21,"payoutMultiplier":0},{"field":22,"payoutMultiplier":0},{"field":20,"payoutMultiplier":0}],"minesCount":2},"clientSeedId":"fc7c4338-e91f-4c13-9cdf-e4475593d7c9","serverSeedId":"c7ae0581-091f-4b85-ac5a-9e8e15c5f7b1","expectedAmount":1.3200000000000002e-7,"serverSeedHash":"aff867a8be94f30f5bd66c7bbf0fa7a85e1c10b187c22fddb93b5efe807cc4e7","payoutMultiplier":0},
mines for this bet id was 3, and 7 . as soon as i clicked on 3. the game should be over . but its not the game shows that i clicked on tiles 4,9,7,1,12,14,24,17,16,15,21,22,20 and 2 . how is this possible . and its not a. autobet which has been placed.
this iteration shows that apart from mines on tiles 3,7 the bombs were on rest of the tiles as well. [\b][\u]
stake controls the iteration , later on the bets are deleted citing as archive and the mines field array is filled. [\b][\u]
hence the bet is manipulated. [\b][\u]
when you play mines on 2 mines you will find bomb on the first click this is one of the reasons[\b][\u]
in this game i have got 7 first bomb for mines of 2. what are the chances for that. [\b][\u]
I think you missunderstood the concept of stake bet archive ...
That they provide for the customers some service like bet archiver where you can download and check out your bets it's actually nothing which can prove the bet was fair or not.
To verify if bet was fair you must have
1. record of the tiles (ordered, per click id) which you opened till busted on mine ( after that game is over) or you won/payed out the game at current nonce.
2. places where mines were placed on your bet (before unhashed server seed is unrevealed) - you can see it in graphic view of the bet, as well if you more advanced you can check that in your browser network tab as stake actually provide this infrmation on the response request when you bust/cashout/win the round.
3. amount of mines played in specific game (per nonce)
4. unhashed server seed , hashed server seed , client seed , and nonce.
And now you can verify the fairness of the specific BET NONCE without even needed of having such thing like bet archive provided by stake.
As i already wrote, i don't know why that iteration was shown/stored in their Archive bet system, but once again as you have the all data which i listed above you don't even need to have such a service to proof the fairness of the bet or bets.
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
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
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
}
]
}
"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.
⭐ Merited by decodx (1)
Hello there.
I was watching your topic about the accusation of stake.. but im not sure where do you find the evidence they cheater.
Iterations for mine bets which you provided differes as it depends if mines are opened one by one or automatically (multiple field at once)
I have prepared some php code which you can use to verify outcome of the mine games with tool that stake provide.
You can use some online php compilers example https://www.w3schools.com/php/phptryit.asp?filename=tryphp_compiler
For the exaple my outcome is the same as in stake web page.
I was watching your topic about the accusation of stake.. but im not sure where do you find the evidence they cheater.
Iterations for mine bets which you provided differes as it depends if mines are opened one by one or automatically (multiple field at once)
I have prepared some php code which you can use to verify outcome of the mine games with tool that stake provide.
You can use some online php compilers example https://www.w3schools.com/php/phptryit.asp?filename=tryphp_compiler
Code:
<?php
// Example usage:
$cursor = 0; // please do not update this value
//we need 24 results for mines to generate as we have 24 possible mines
$count = 24;
$hashedServerSeed = 'def3a5cbd25b59adf1d26cfca8efa8e349240c6f5a7a9754a7bc3614a68a5283';
$clientSeed = 'Vl-f-FEmK7';
$serverSeed = 'd67cb6c65af339a914a82fbdc652fe13bd022da2c753bf445751a73a3eb4c6d9';
$nonce = 1;
function verifyIfServerSeedIsTrue(string $hashedServerSeed, string $serverSeed): bool
{
//lets verify if my unhashedServerSeed is actually sha256 hashedServerSeed
return hash('sha256', $serverSeed) === $hashedServerSeed;
}
echo "lets verify if my unhashedServerSeed is actually sha256 hashedServerSeed , Result: => ";
var_dump(verifyIfServerSeedIsTrue($hashedServerSeed, $serverSeed));
$hmac_sha256 = [];
function byteGenerator(string $serverSeed, string $clientSeed, int $nonce, int $cursor): \Generator
{
// Setup cursor variables
$currentRound = floor($cursor / 32);
$currentRoundCursor = $cursor - ($currentRound * 32);
// Generate outputs until cursor requirement is fulfilled
while (true) {
// Calculate the HMAC
// Initialize the HMAC context
$msg = $clientSeed . ":" . $nonce . ":" . $currentRound;
$hmac = hash_hmac('sha256', $msg, $serverSeed, true);
$hmacBytes = str_split($hmac);
// Update cursor for the next iteration of the loop
while ($currentRoundCursor < 32) {
yield ord($hmacBytes[$currentRoundCursor]); // Yield the number
$currentRoundCursor += 1;
}
$currentRoundCursor = 0;
$currentRound += 1;
}
}
// Convert the hash output from the rng byteGenerator to floats
function generateFloats (string $serverSeed, string $clientSeed, int $nonce, int $cursor, int $count): array
{
// Random number generator function
$rng = byteGenerator($serverSeed, $clientSeed, $nonce, $cursor);
// Declare bytes as empty array
$bytes = [];
// Populate bytes array with sets of 4 from RNG output
while (count($bytes) < $count * 4) {
$bytes[] = $rng->current();
$rng->next();
}
// Chunk the array into sets of 4
$byteChunks = array_chunk($bytes, 4);
// Map and reduce each chunk to calculate floats
$result = array_map(function ($byteChunk) {
$partialResult = 0.0;
foreach ($byteChunk as $i => $value) {
$partialResult += $value / pow(256, $i + 1);
}
return $partialResult;
}, $byteChunks);
return $result;
};
function fisherYatesShuffle(array $array): array
{
$result = [];
$cells = [0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24];
for ($i=0; $i< count($array); $i++) {
$result[$i] = $cells[$array[$i]];
array_splice($cells, $array[$i], 1);
}
return $result;
}
$results = generateFloats($serverSeed, $clientSeed, $nonce, $cursor, $count);
$int_array = [];
foreach ($results as $result) {
$r = ($result * ($count+1));
$int_array[] = (int) $r;
$count -= 1;
}
$mines_positions = fisherYatesShuffle($int_array);
echo "<br><b>Mines postions</b></br>";
echo "Game Nonce:" . $nonce;
foreach ($mines_positions as $key => $value) {
echo "</br>" . $key . " = " . $value;
};
?>
// Example usage:
$cursor = 0; // please do not update this value
//we need 24 results for mines to generate as we have 24 possible mines
$count = 24;
$hashedServerSeed = 'def3a5cbd25b59adf1d26cfca8efa8e349240c6f5a7a9754a7bc3614a68a5283';
$clientSeed = 'Vl-f-FEmK7';
$serverSeed = 'd67cb6c65af339a914a82fbdc652fe13bd022da2c753bf445751a73a3eb4c6d9';
$nonce = 1;
function verifyIfServerSeedIsTrue(string $hashedServerSeed, string $serverSeed): bool
{
//lets verify if my unhashedServerSeed is actually sha256 hashedServerSeed
return hash('sha256', $serverSeed) === $hashedServerSeed;
}
echo "lets verify if my unhashedServerSeed is actually sha256 hashedServerSeed , Result: => ";
var_dump(verifyIfServerSeedIsTrue($hashedServerSeed, $serverSeed));
$hmac_sha256 = [];
function byteGenerator(string $serverSeed, string $clientSeed, int $nonce, int $cursor): \Generator
{
// Setup cursor variables
$currentRound = floor($cursor / 32);
$currentRoundCursor = $cursor - ($currentRound * 32);
// Generate outputs until cursor requirement is fulfilled
while (true) {
// Calculate the HMAC
// Initialize the HMAC context
$msg = $clientSeed . ":" . $nonce . ":" . $currentRound;
$hmac = hash_hmac('sha256', $msg, $serverSeed, true);
$hmacBytes = str_split($hmac);
// Update cursor for the next iteration of the loop
while ($currentRoundCursor < 32) {
yield ord($hmacBytes[$currentRoundCursor]); // Yield the number
$currentRoundCursor += 1;
}
$currentRoundCursor = 0;
$currentRound += 1;
}
}
// Convert the hash output from the rng byteGenerator to floats
function generateFloats (string $serverSeed, string $clientSeed, int $nonce, int $cursor, int $count): array
{
// Random number generator function
$rng = byteGenerator($serverSeed, $clientSeed, $nonce, $cursor);
// Declare bytes as empty array
$bytes = [];
// Populate bytes array with sets of 4 from RNG output
while (count($bytes) < $count * 4) {
$bytes[] = $rng->current();
$rng->next();
}
// Chunk the array into sets of 4
$byteChunks = array_chunk($bytes, 4);
// Map and reduce each chunk to calculate floats
$result = array_map(function ($byteChunk) {
$partialResult = 0.0;
foreach ($byteChunk as $i => $value) {
$partialResult += $value / pow(256, $i + 1);
}
return $partialResult;
}, $byteChunks);
return $result;
};
function fisherYatesShuffle(array $array): array
{
$result = [];
$cells = [0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24];
for ($i=0; $i< count($array); $i++) {
$result[$i] = $cells[$array[$i]];
array_splice($cells, $array[$i], 1);
}
return $result;
}
$results = generateFloats($serverSeed, $clientSeed, $nonce, $cursor, $count);
$int_array = [];
foreach ($results as $result) {
$r = ($result * ($count+1));
$int_array[] = (int) $r;
$count -= 1;
}
$mines_positions = fisherYatesShuffle($int_array);
echo "<br><b>Mines postions</b></br>";
echo "Game Nonce:" . $nonce;
foreach ($mines_positions as $key => $value) {
echo "</br>" . $key . " = " . $value;
};
?>
For the exaple my outcome is the same as in stake web page.
Quote
lets verify if my unhashedServerSeed is actually sha256 hashedServerSeed , Result: => bool(true)
Mines postions
Game Nonce:1
0 = 5
1 = 7
2 = 14
3 = 15
4 = 13
5 = 11
6 = 18
7 = 8
8 = 12
9 = 2
10 = 16
11 = 23
12 = 6
13 = 1
14 = 0
15 = 21
16 = 20
17 = 19
18 = 17
19 = 22
20 = 9
21 = 10
22 = 3
23 = 24
Mines postions
Game Nonce:1
0 = 5
1 = 7
2 = 14
3 = 15
4 = 13
5 = 11
6 = 18
7 = 8
8 = 12
9 = 2
10 = 16
11 = 23
12 = 6
13 = 1
14 = 0
15 = 21
16 = 20
17 = 19
18 = 17
19 = 22
20 = 9
21 = 10
22 = 3
23 = 24
its not about the calculation for mines there is no paranthesis of code is giving to find the solution.
How it is not about the calculation...
Result where mines are placed is generated at the beggining once you change seed on stake (for infinite nonce)
no matter if game nonce is 10 or 100 000 000 , places for mines are known. as stake knowns your seed and server seed (unhashed) so they can know that before.
IT does not matter HOW MANY MINES YOU PLAY as the PLACES WHERE MINES ARE PLACED ARE KNOWN BEFORE GAME EVEN START.
WHAT IS IMPORTANT IS that once server seed is unhashed and you can know it .. you can verify the results for each of the round you played via the tool they provide or if you don't trust their tools you can write your own ... example is my php code .. which gave you exactly the results of mines fo each game for the provided serverseed , clientseed .
Only think which you basically care is IF MINES ARE ON THE SAME POSITION AS THEY SHOULD BE
Lets say you played 1 000 games on mines from nonce 1 to 1001
You have recorded every of the game and can see in which places mines were placed .. now lets rotate your seed at nonce 1002 and verify each bet with their tool/my code.
You can compare if the mine places which you had playing while hash was still not revealed are the same after you know unhashed serverseed.
under point 3 , if you compare the iteration of the mines you will come to know how different are these as registered in the back end.
if you had ever played mines you know the game ends when you pick a bomb, so for a game of 2 mines how can i pick up more than 11 bombs in the second iteration.
is there ny logic
?Regarding to the different itarations registered in archive files.
As i already told you it depends if you open fields ONE BY ONE or VIA AUTOMATIC BET (WHEN YOU CHOOSE WHICH FIELDS TO OPEN)
BUT EVEN IF YOU OPEN IT ONE BY ONE , it does not matter of the
If its shown one way or another as the MOST IMPORTANT IS THE MINE PLACES NOT THE FIELDS WHICH YOU HAVE IN THE LOG.
Example
Compare this as a log from mines opened ONE BY ONE (MANUALLY CLICKING).
Quote
"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
}
]
}
"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
}
]
}
WITH THE LOG OF MINES OPENED BY PRE SELECTED FIELDS
Quote
"state": {
"mines": [
0,
24,
9
],
"minesCount": 3,
"rounds": [
{
"field": 0,
"payoutMultiplier": 0
},
{
"field": 6,
"payoutMultiplier": 0
},
{
"field": 12,
"payoutMultiplier": 0
},
{
"field": 18,
"payoutMultiplier": 0
},
{
"field": 24,
"payoutMultiplier": 0
},
{
"field": 21,
"payoutMultiplier": 0
},
{
"field": 17,
"payoutMultiplier": 0
},
{
"field": 10,
"payoutMultiplier": 0
},
{
"field": 16,
"payoutMultiplier": 0
},
{
"field": 8,
"payoutMultiplier": 0
},
{
"field": 2,
"payoutMultiplier": 0
},
{
"field": 14,
"payoutMultiplier": 0
},
{
"field": 4,
"payoutMultiplier": 0
},
{
"field": 20,
"payoutMultiplier": 0
}
]
}
"mines": [
0,
24,
9
],
"minesCount": 3,
"rounds": [
{
"field": 0,
"payoutMultiplier": 0
},
{
"field": 6,
"payoutMultiplier": 0
},
{
"field": 12,
"payoutMultiplier": 0
},
{
"field": 18,
"payoutMultiplier": 0
},
{
"field": 24,
"payoutMultiplier": 0
},
{
"field": 21,
"payoutMultiplier": 0
},
{
"field": 17,
"payoutMultiplier": 0
},
{
"field": 10,
"payoutMultiplier": 0
},
{
"field": 16,
"payoutMultiplier": 0
},
{
"field": 8,
"payoutMultiplier": 0
},
{
"field": 2,
"payoutMultiplier": 0
},
{
"field": 14,
"payoutMultiplier": 0
},
{
"field": 4,
"payoutMultiplier": 0
},
{
"field": 20,
"payoutMultiplier": 0
}
]
}
As you can see the logs show me that i "clicked" fields 0,6,12 etc.. BUT YOU CAN SEE THAT I ALREADY FAILED ON THE with the 1st one as mines positions are 0,24,9
This means if i play with 1 mine at that particular game, the mine would be at field 0
if i will play with 2 mines it would be 1st mine at field 0 , 2nd mine at field 24,
if i will play with 3 mines it would be 1st mine at field 0, 2nd mine at field 24 , 3rd mine at field 9
and so on (positions and the order of mines you can verify via the tool that STAKE or I have provided to you, i"ve shared the URL where you can just copy and past the code already. (https://www.w3schools.com/php/phptryit.asp?filename=tryphp_compiler)).
SO TO VERIFY IF THE GAMES WAS CORRECT WE ONLY NEED TO KNOW MINES POSITIONS AND THE POSITIONS WHICH WE OPENED/CLICKED AND IT SHOULD BE ORDERED BY THE FIELD ID WHICH WAS CLICKED OR SELECTED 1st,2nd,3rd etc..
I'm a bit concerns based on your replays/analysis that you are not even sure how the game of mines works and how it generates the outcome for each game.
You have found some different iteration for 2 games, which AS I ALREADY EXPLAINED, DOES NOT MATTER. IF ORDER OF MINES AND ORDER OF FIELDS OPENED ARE EQUAL TO YOUR ACTUALL RECORDED GAMEPLAY IT MEANS THERE IS NOTHING RIGGED/MANIPULATED as you suggesting.
⭐ Merited by Kirito89 (1)
Hello there.
I was watching your topic about the accusation of stake.. but im not sure where do you find the evidence they cheater.
Iterations for mine bets which you provided differes as it depends if mines are opened one by one or automatically (multiple field at once)
I have prepared some php code which you can use to verify outcome of the mine games with tool that stake provide.
You can use some online php compilers example https://www.w3schools.com/php/phptryit.asp?filename=tryphp_compiler
For the exaple my outcome is the same as in stake web page.
I was watching your topic about the accusation of stake.. but im not sure where do you find the evidence they cheater.
Iterations for mine bets which you provided differes as it depends if mines are opened one by one or automatically (multiple field at once)
I have prepared some php code which you can use to verify outcome of the mine games with tool that stake provide.
You can use some online php compilers example https://www.w3schools.com/php/phptryit.asp?filename=tryphp_compiler
Code:
<?php
// Example usage:
$cursor = 0; // please do not update this value
//we need 24 results for mines to generate as we have 24 possible mines
$count = 24;
$hashedServerSeed = 'def3a5cbd25b59adf1d26cfca8efa8e349240c6f5a7a9754a7bc3614a68a5283';
$clientSeed = 'Vl-f-FEmK7';
$serverSeed = 'd67cb6c65af339a914a82fbdc652fe13bd022da2c753bf445751a73a3eb4c6d9';
$nonce = 1;
function verifyIfServerSeedIsTrue(string $hashedServerSeed, string $serverSeed): bool
{
//lets verify if my unhashedServerSeed is actually sha256 hashedServerSeed
return hash('sha256', $serverSeed) === $hashedServerSeed;
}
echo "lets verify if my unhashedServerSeed is actually sha256 hashedServerSeed , Result: => ";
var_dump(verifyIfServerSeedIsTrue($hashedServerSeed, $serverSeed));
$hmac_sha256 = [];
function byteGenerator(string $serverSeed, string $clientSeed, int $nonce, int $cursor): \Generator
{
// Setup cursor variables
$currentRound = floor($cursor / 32);
$currentRoundCursor = $cursor - ($currentRound * 32);
// Generate outputs until cursor requirement is fulfilled
while (true) {
// Calculate the HMAC
// Initialize the HMAC context
$msg = $clientSeed . ":" . $nonce . ":" . $currentRound;
$hmac = hash_hmac('sha256', $msg, $serverSeed, true);
$hmacBytes = str_split($hmac);
// Update cursor for the next iteration of the loop
while ($currentRoundCursor < 32) {
yield ord($hmacBytes[$currentRoundCursor]); // Yield the number
$currentRoundCursor += 1;
}
$currentRoundCursor = 0;
$currentRound += 1;
}
}
// Convert the hash output from the rng byteGenerator to floats
function generateFloats (string $serverSeed, string $clientSeed, int $nonce, int $cursor, int $count): array
{
// Random number generator function
$rng = byteGenerator($serverSeed, $clientSeed, $nonce, $cursor);
// Declare bytes as empty array
$bytes = [];
// Populate bytes array with sets of 4 from RNG output
while (count($bytes) < $count * 4) {
$bytes[] = $rng->current();
$rng->next();
}
// Chunk the array into sets of 4
$byteChunks = array_chunk($bytes, 4);
// Map and reduce each chunk to calculate floats
$result = array_map(function ($byteChunk) {
$partialResult = 0.0;
foreach ($byteChunk as $i => $value) {
$partialResult += $value / pow(256, $i + 1);
}
return $partialResult;
}, $byteChunks);
return $result;
};
function fisherYatesShuffle(array $array): array
{
$result = [];
$cells = [0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24];
for ($i=0; $i< count($array); $i++) {
$result[$i] = $cells[$array[$i]];
array_splice($cells, $array[$i], 1);
}
return $result;
}
$results = generateFloats($serverSeed, $clientSeed, $nonce, $cursor, $count);
$int_array = [];
foreach ($results as $result) {
$r = ($result * ($count+1));
$int_array[] = (int) $r;
$count -= 1;
}
$mines_positions = fisherYatesShuffle($int_array);
echo "<br><b>Mines postions</b></br>";
echo "Game Nonce:" . $nonce;
foreach ($mines_positions as $key => $value) {
echo "</br>" . $key . " = " . $value;
};
?>
// Example usage:
$cursor = 0; // please do not update this value
//we need 24 results for mines to generate as we have 24 possible mines
$count = 24;
$hashedServerSeed = 'def3a5cbd25b59adf1d26cfca8efa8e349240c6f5a7a9754a7bc3614a68a5283';
$clientSeed = 'Vl-f-FEmK7';
$serverSeed = 'd67cb6c65af339a914a82fbdc652fe13bd022da2c753bf445751a73a3eb4c6d9';
$nonce = 1;
function verifyIfServerSeedIsTrue(string $hashedServerSeed, string $serverSeed): bool
{
//lets verify if my unhashedServerSeed is actually sha256 hashedServerSeed
return hash('sha256', $serverSeed) === $hashedServerSeed;
}
echo "lets verify if my unhashedServerSeed is actually sha256 hashedServerSeed , Result: => ";
var_dump(verifyIfServerSeedIsTrue($hashedServerSeed, $serverSeed));
$hmac_sha256 = [];
function byteGenerator(string $serverSeed, string $clientSeed, int $nonce, int $cursor): \Generator
{
// Setup cursor variables
$currentRound = floor($cursor / 32);
$currentRoundCursor = $cursor - ($currentRound * 32);
// Generate outputs until cursor requirement is fulfilled
while (true) {
// Calculate the HMAC
// Initialize the HMAC context
$msg = $clientSeed . ":" . $nonce . ":" . $currentRound;
$hmac = hash_hmac('sha256', $msg, $serverSeed, true);
$hmacBytes = str_split($hmac);
// Update cursor for the next iteration of the loop
while ($currentRoundCursor < 32) {
yield ord($hmacBytes[$currentRoundCursor]); // Yield the number
$currentRoundCursor += 1;
}
$currentRoundCursor = 0;
$currentRound += 1;
}
}
// Convert the hash output from the rng byteGenerator to floats
function generateFloats (string $serverSeed, string $clientSeed, int $nonce, int $cursor, int $count): array
{
// Random number generator function
$rng = byteGenerator($serverSeed, $clientSeed, $nonce, $cursor);
// Declare bytes as empty array
$bytes = [];
// Populate bytes array with sets of 4 from RNG output
while (count($bytes) < $count * 4) {
$bytes[] = $rng->current();
$rng->next();
}
// Chunk the array into sets of 4
$byteChunks = array_chunk($bytes, 4);
// Map and reduce each chunk to calculate floats
$result = array_map(function ($byteChunk) {
$partialResult = 0.0;
foreach ($byteChunk as $i => $value) {
$partialResult += $value / pow(256, $i + 1);
}
return $partialResult;
}, $byteChunks);
return $result;
};
function fisherYatesShuffle(array $array): array
{
$result = [];
$cells = [0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24];
for ($i=0; $i< count($array); $i++) {
$result[$i] = $cells[$array[$i]];
array_splice($cells, $array[$i], 1);
}
return $result;
}
$results = generateFloats($serverSeed, $clientSeed, $nonce, $cursor, $count);
$int_array = [];
foreach ($results as $result) {
$r = ($result * ($count+1));
$int_array[] = (int) $r;
$count -= 1;
}
$mines_positions = fisherYatesShuffle($int_array);
echo "<br><b>Mines postions</b></br>";
echo "Game Nonce:" . $nonce;
foreach ($mines_positions as $key => $value) {
echo "</br>" . $key . " = " . $value;
};
?>
For the exaple my outcome is the same as in stake web page.
Quote
lets verify if my unhashedServerSeed is actually sha256 hashedServerSeed , Result: => bool(true)
Mines postions
Game Nonce:1
0 = 5
1 = 7
2 = 14
3 = 15
4 = 13
5 = 11
6 = 18
7 = 8
8 = 12
9 = 2
10 = 16
11 = 23
12 = 6
13 = 1
14 = 0
15 = 21
16 = 20
17 = 19
18 = 17
19 = 22
20 = 9
21 = 10
22 = 3
23 = 24
Mines postions
Game Nonce:1
0 = 5
1 = 7
2 = 14
3 = 15
4 = 13
5 = 11
6 = 18
7 = 8
8 = 12
9 = 2
10 = 16
11 = 23
12 = 6
13 = 1
14 = 0
15 = 21
16 = 20
17 = 19
18 = 17
19 = 22
20 = 9
21 = 10
22 = 3
23 = 24
its not about the calculation for mines there is no paranthesis of code is giving to find the solution.
How it is not about the calculation...
Result where mines are placed is generated at the beggining once you change seed on stake ( for infinite nonce)
no matter if game nonce is 10 or 100 000 000 , places for mines are known. as stake knowns your seed and server seed (unhashed) so they can know that before.
IT does not matter HOW MANY MINES YOU PLAY as the PLACES WHERE MINES ARE PLACED ARE KNOWN BEFORE GAME EVEN START.
WHAT IS IMPORTANT IS that once server seed is unhashed and you can know it .. you can verify the results for each of the round you played via the tool they provide or if you don't trust their tools you can write your own ... example is my php code .. which gave you exactly the results of mines fo each game for the provided serverseed , clientseed .
Only think which you basically care is IF MINES ARE ON THE SAME POSITION AS THEY SHOULD BE
Lets say you played 1 000 games on mines from nonca 1 to 1001
You have recorded every of the game and can see in which places mines were placed .. now lets rotate your seed at nonca 1002 and verify each bet with their tool/my code.
You can compare if the mine places which you had playing while hash was still not revealed are the same after you know unhashed serverseed.
⭐ Merited by decodx (2)
Hello there.
I was watching your topic about the accusation of stake.. but im not sure where do you find the evidence they cheater.
Iterations for mine bets which you provided differes as it depends if mines are opened one by one or automatically (multiple field at once)
I have prepared some php code which you can use to verify outcome of the mine games with tool that stake provide.
I was watching your topic about the accusation of stake.. but im not sure where do you find the evidence they cheater.
Iterations for mine bets which you provided differes as it depends if mines are opened one by one or automatically (multiple field at once)
I have prepared some php code which you can use to verify outcome of the mine games with tool that stake provide.
Code:
<?php
// Example usage:
$nonce = 1;
$cursor = 0;
//we need 24 results for mines to generate as we have 24 possible mines
$count = 24;
$hashedServerSeed = 'def3a5cbd25b59adf1d26cfca8efa8e349240c6f5a7a9754a7bc3614a68a5283';
$clientSeed = 'Vl-f-FEmK7';
$serverSeed = 'd67cb6c65af339a914a82fbdc652fe13bd022da2c753bf445751a73a3eb4c6d9';
function verifyIfServerSeedIsTrue(string $hashedServerSeed, string $serverSeed): bool
{
//lets verify if my unhashedServerSeed is actually sha256 hashedServerSeed
return hash('sha256', $serverSeed) === $hashedServerSeed;
}
echo "lets verify if my unhashedServerSeed is actually sha256 hashedServerSeed , Result: => ";
var_dump(verifyIfServerSeedIsTrue($hashedServerSeed, $serverSeed));
$hmac_sha256 = [];
function byteGenerator(string $serverSeed, string $clientSeed, int $nonce, int$cursor): \Generator
{
// Setup cursor variables
$currentRound = floor($cursor / 32);
$currentRoundCursor = $cursor - ($currentRound * 32);
// Generate outputs until cursor requirement is fulfilled
while (true) {
// Calculate the HMAC
// Initialize the HMAC context
$msg = $clientSeed . ":" . $nonce . ":" . $currentRound;
$hmac = hash_hmac('sha256', $msg, $serverSeed, true);
$hmacBytes = str_split($hmac);
// Update cursor for the next iteration of the loop
while ($currentRoundCursor < 32) {
yield ord($hmacBytes[$currentRoundCursor]); // Yield the number
$currentRoundCursor += 1;
}
$currentRoundCursor = 0;
$currentRound += 1;
}
}
// Convert the hash output from the rng byteGenerator to floats
function generateFloats (string $serverSeed, string $clientSeed, int $nonce, int $cursor, int $count): array
{
// Random number generator function
$rng = byteGenerator($serverSeed, $clientSeed, $nonce, $cursor);
// Declare bytes as empty array
$bytes = [];
// Populate bytes array with sets of 4 from RNG output
while (count($bytes) < $count * 4) {
$bytes[] = $rng->current();
$rng->next();
}
// Chunk the array into sets of 4
$byteChunks = array_chunk($bytes, 4);
// Map and reduce each chunk to calculate floats
$result = array_map(function ($byteChunk) {
$partialResult = 0.0;
foreach ($byteChunk as $i => $value) {
$partialResult += $value / pow(256, $i + 1);
}
return $partialResult;
}, $byteChunks);
return $result;
};
function fisherYatesShuffle(array $array): array
{
$result = [];
$cells = [0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24];
for ($i=0; $i< count($array) ; $i++) {
$result[$i] = $cells[$array[$i]];
array_splice($cells, $array[$i], 1);
}
return $result;
}
$results = generateFloats($serverSeed, $clientSeed, $nonce, $cursor, $count);
$int_array = [];
foreach( $results as $result) {
$r = ($result * ($count+1));
$int_array[] = (int) $r;
$count = $count -1;
}
$mines_positions = fisherYatesShuffle($int_array);
echo "<br><b>Mines postions</b></br>";
echo "Game Nonce:" . $nonce;
foreach ($mines_positions as $key => $value) {
echo "</br>" . $key . " = " . $value;
};
?>
// Example usage:
$nonce = 1;
$cursor = 0;
//we need 24 results for mines to generate as we have 24 possible mines
$count = 24;
$hashedServerSeed = 'def3a5cbd25b59adf1d26cfca8efa8e349240c6f5a7a9754a7bc3614a68a5283';
$clientSeed = 'Vl-f-FEmK7';
$serverSeed = 'd67cb6c65af339a914a82fbdc652fe13bd022da2c753bf445751a73a3eb4c6d9';
function verifyIfServerSeedIsTrue(string $hashedServerSeed, string $serverSeed): bool
{
//lets verify if my unhashedServerSeed is actually sha256 hashedServerSeed
return hash('sha256', $serverSeed) === $hashedServerSeed;
}
echo "lets verify if my unhashedServerSeed is actually sha256 hashedServerSeed , Result: => ";
var_dump(verifyIfServerSeedIsTrue($hashedServerSeed, $serverSeed));
$hmac_sha256 = [];
function byteGenerator(string $serverSeed, string $clientSeed, int $nonce, int$cursor): \Generator
{
// Setup cursor variables
$currentRound = floor($cursor / 32);
$currentRoundCursor = $cursor - ($currentRound * 32);
// Generate outputs until cursor requirement is fulfilled
while (true) {
// Calculate the HMAC
// Initialize the HMAC context
$msg = $clientSeed . ":" . $nonce . ":" . $currentRound;
$hmac = hash_hmac('sha256', $msg, $serverSeed, true);
$hmacBytes = str_split($hmac);
// Update cursor for the next iteration of the loop
while ($currentRoundCursor < 32) {
yield ord($hmacBytes[$currentRoundCursor]); // Yield the number
$currentRoundCursor += 1;
}
$currentRoundCursor = 0;
$currentRound += 1;
}
}
// Convert the hash output from the rng byteGenerator to floats
function generateFloats (string $serverSeed, string $clientSeed, int $nonce, int $cursor, int $count): array
{
// Random number generator function
$rng = byteGenerator($serverSeed, $clientSeed, $nonce, $cursor);
// Declare bytes as empty array
$bytes = [];
// Populate bytes array with sets of 4 from RNG output
while (count($bytes) < $count * 4) {
$bytes[] = $rng->current();
$rng->next();
}
// Chunk the array into sets of 4
$byteChunks = array_chunk($bytes, 4);
// Map and reduce each chunk to calculate floats
$result = array_map(function ($byteChunk) {
$partialResult = 0.0;
foreach ($byteChunk as $i => $value) {
$partialResult += $value / pow(256, $i + 1);
}
return $partialResult;
}, $byteChunks);
return $result;
};
function fisherYatesShuffle(array $array): array
{
$result = [];
$cells = [0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24];
for ($i=0; $i< count($array) ; $i++) {
$result[$i] = $cells[$array[$i]];
array_splice($cells, $array[$i], 1);
}
return $result;
}
$results = generateFloats($serverSeed, $clientSeed, $nonce, $cursor, $count);
$int_array = [];
foreach( $results as $result) {
$r = ($result * ($count+1));
$int_array[] = (int) $r;
$count = $count -1;
}
$mines_positions = fisherYatesShuffle($int_array);
echo "<br><b>Mines postions</b></br>";
echo "Game Nonce:" . $nonce;
foreach ($mines_positions as $key => $value) {
echo "</br>" . $key . " = " . $value;
};
?>