Quote from: dvdx1995 on Today at 08:11:10 PM

Quote from: cryptogeniusdice on Today at 07:42:53 PM

Quote from: dvdx1995 on Today at 05:58:18 PM

Quote from: cryptogeniusdice on Today at 05:34:27 PM

Quote from: dvdx1995 on Today at 03:17:39 PM

Quote from: cryptogeniusdice on Today at 02:38:40 PM

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.

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.

Quote

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

If you check on stake at provably-fair/implementation they provided the function which they use to generate that binary value and the numbers out of that binary value

Code:

// Random number generation based on following inputs: serverSeed, clientSeed, nonce and cursor
function byteGenerator({ serverSeed, clientSeed, nonce, cursor }) {
  // Setup curser variables
  let currentRound = Math.floor(cursor / 32);
  let currentRoundCursor = cursor;
  currentRoundCursor -= currentRound * 32;

  // Generate outputs until cursor requirement fullfilled
  while (true) {
   // HMAC function used to output provided inputs into bytes
   const hmac = createHmac('sha256', serverSeed);
   hmac.update(`${clientSeed}:${nonce}:${currentRound}`);
   const buffer = hmac.digest();

   // Update curser for next iteration of loop
   while (currentRoundCursor < 32) {
   yield Number(buffer[currentRoundCursor]);
   currentRoundCursor += 1;
   }
   currentRoundCursor = 0;
   currentRound += 1;
  }
}

And i used exactly the same functionality in my code to output that binary value out of the HMAC method..

Code:

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…