Locking the amounts doesn't change the fact that the tx info and the score is known before sending it to blockchain. Now I could try the different tokens, use different accounts, use other signers, shuffle the hivengine json or wait until refblocknum/refblockprefix match to reach the target score...
Check @magicdice - they solved this problem a couple of years ago. IIRC, they had a "secret" that was unknown at the time of sending a bet, but published a couple of minutes later. This way users could verify that the system was fair - but only for past games, not predicting current outcomes.
edit: found the original magicdice post with the technical details: https://peakd.com/steemit/@magicdice/magic-dice-tech-talk-provably-fair-and-transparent
I am totally interested if you can calculate it now to change the outcome.
!PIZZA
did you use the waiting method? are you able to do it a few times in a row, and also, the major test is on the word games :P try to get RisingStar spelt on game 3. thats a little more complex than the default key... also any suggestions and feedback totally welcome!!
Spelling "RisingStar" probably takes some time, but "Rising" was easily possible
Waiting method alone takes too long, refblock info changes only once every 3 sec. I varied some of the other trx parameters mentioned above...
suggestions: as indicated above, don't use trx ID alone ;)