You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In light of the new game architecture thats based on an event sourced architecture implemented as a redux state machine, each committed player action will be signed by a user and later uploaded to IPFS, where another observer could easily replay and verify game-play. As we iterate on this architecture to move towards further decentralization, there remains some questions:
How to handle game logic versions for a game? that is, a game will naturally change over time, but we should be able to replay historical game moves on an older version of a game
How to handle trusted game logic source for a version? perhaps just hashing a source tree or docker image of a dist file is sufficient? and we have a verifier run as a docker container? assuming its byte-for-byte the same, and we can reply on a hash. But, can this be forged? is there any good reason for someone to forge it and it not being caught by one of the 3 parties in a game? (PvP via server)
Source of truth for game rules? (same as the game version)
Other...?
The text was updated successfully, but these errors were encountered:
In light of the new game architecture thats based on an event sourced architecture implemented as a redux state machine, each committed player action will be signed by a user and later uploaded to IPFS, where another observer could easily replay and verify game-play. As we iterate on this architecture to move towards further decentralization, there remains some questions:
How to handle game logic versions for a game? that is, a game will naturally change over time, but we should be able to replay historical game moves on an older version of a game
How to handle trusted game logic source for a version? perhaps just hashing a source tree or docker image of a dist file is sufficient? and we have a verifier run as a docker container? assuming its byte-for-byte the same, and we can reply on a hash. But, can this be forged? is there any good reason for someone to forge it and it not being caught by one of the 3 parties in a game? (PvP via server)
Source of truth for game rules? (same as the game version)
Other...?
The text was updated successfully, but these errors were encountered: