~snip~
The timestamps in the bet history are for when a bet is placed, not when the round begins. Per your concerns, we have added an "End Time" timestamp when the last player joins a duel. By comparing this timestamp with the EOS block, you will be able to confirm that the EOS block is selected before the hash is known. We understand that this solution isn't perfect, and we will look into potentially selecting an EOS block further in the future (~5 seconds) or switching to the Tron blockchain. Thank you again for raising these concerns, and please let us know if there's anything else we can do to help make our platform more provably fair!
Okay, this solves half the problem. Now player can ensure that EOS block is only picked after all the players having joined the duel. But other half of the issue is still there. Player can still not ensure that immediately next block is taken for the consideration.
Here is what I observed in some rounds played on DuelBits (timings as per Indian Standard Time):
Round 300590:
End Time -> 9:52:29 PM,
EOS Block -> 148648714;
EOS Block Creation Time -> 09:52:32 PM;
Difference -> 3 seconds
EOS Blocks created in the meantime -> 8
Round 300663:
End Time -> 11:00:22 PM,
EOS Block -> 148656853;
EOS Block Creation Time -> 11:00:22 PM;
Difference -> 0 second
EOS Blocks created in the meantime -> none
In round 300590, block created after 3 seconds was taken for the calculation. I understand this happens due to delay in API calls which is quite common. However, it opens possibility that casino maybe checking the calculation with every block and only choosing the block id which draws result in the favor of bot's position. For example, I as a player may suspect that DuelBits test-checked the result of round 300590 with the following blocks:
148648708 - maybe favoring player -
rejected Created at: 9:52:29 PM
148648709 - maybe favoring player -
rejected Created at: 9:52:29 PM
148648710 - maybe favoring player -
rejected Created at: 9:52:30 PM
148648711 - maybe favoring player -
rejected Created at: 9:52:30 PM
148648712 - maybe favoring player -
rejected Created at: 9:52:31 PM
148648713 - maybe favoring player -
rejected Created at: 9:52:31 PM
148648714 - Favoring bot -
taken Created at: 9:52:32 PM
Interesting thing is that Block 300590 was actually won by the Duebits Bot.
I am not accusing you of cheating but there is no way to make sure you are doing it or not. That's the problem of using EOS blocks because new blocks are created every half a second. This all reduces the effectiveness of Provably Fair System.
That's why I am proposing you to adopt TRON blockchain. Since new block is added on TRON network every 3 seconds, that will give you enough time to make API call and make sure that the very next or at max 3rd block validated after 'End Time' is used for the calculation. No scope left for the test-check making Provably Fair foolproof!
