what do you mean with " MP apps should help the players by verifying each bet directly after it was made."? is the Bet ID not enough where user can check the outcome?
could you give us a sample MP app who implemented it so we could check and tell our coders to add it?
AFAIK ideal way for MP apps for
each bet:
1) Get serverseedhash for next bet, show it to user, save it in browser (localstorage.) Note: if the browser is refreshed, STILL, use that same serverseedhash.
2) Generate a cryptographically-secure random clientseed, example of Ryan:
https://gist.github.com/RHavar/a6511dea4d4c41aeb1eb Note: if the browser is refreshed, STILL, use that same clientseed.
3) Allow the player to change the clientseed, if he desires to do so.
4) Player clicks *bet*, you send those seeds to make the bet and get the result/serverseed back.
5) Check if the previously saved serverseedhash matches the hash of the bet result serverseed (in the user's browser)
6) Check if you calculate the same bet result with that serverseed (in the user's browser)
And repeat for next bet. This seems like a big process but is fairly easy to make and the player shouldn't even really notice.
You can see DustDice does this:
https://github.com/dustdice/dustdice/blob/master/public/scripts/game-logic/engine.js#L205 This is just after making a bet. It verifies the game and it generates a new client seed.
* You will notice that in the process, the clientseed for each bet is different. That is the best way, but some players like to pick a "lucky clientseed". You could actually combine a random but still saved clientseed, described by Ryan here: https://bitcointalksearch.org/topic/m.12018096is there a provably fair option for the user to verify all his bets after his session and not to check after each loss? this is interrupting each players game and not preferable in our opinion
That is the "nonce method" (using the same seeds for 10, 100 or even 1 million bets, but an incremental nonce to make the result different.) This way, you can verify all the bets, since the verifier just uses the incremental nonce too. But MP doesn't use this method.
MP uses the "per roll method" so the verifying has to be after each bet. This makes sense if you want to automatically verify bets since you don't need to request a new serverseed every time. But it only works if MP apps actually implement the verification process