Quote from: The Bitcoin Co-op on January 21, 2017, 09:57:36 PM

Quote from: domob on January 21, 2017, 08:33:04 PM

Quote from: The Bitcoin Co-op on January 21, 2017, 08:04:36 PM

There are other ways to fix it, too. For example, if some players issue transactions in one block, and some confirm in the next block but not all of them, the gamestate could choose not to update until all of the transactions are confirmed, giving each player an equal chance.

This is unfortunately not very straight-forward to do. There's no network consensus about unconfirmed transactions (that's precisely why they are still unconfirmed), so one cannot take them into account for consensus-stuff like game-state transitions. (There might be more complex hacks around this in some way, but I doubt one can find a good solution that fully retains Huntercoin's trustlessness and decentralisation.)

What if you made blocks really fast, and then made the gamestate wait for at least 2 confirmations instead of 1? Could it then take the 1-confirmed transactions into account and hold off including others that were issued in the same block but already got to 2 confirmations?

Yes, that might be a possible approach. But I'm not sure what that would buy you - then you still have to get a miner to include your tx, and tx sent at the "same time" might still not confirm in the same block. Also making blocks very fast is problematic due to orphan blocks.