Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Game: research how to do verifiable game architecture #5

Open
pkieltyka opened this issue Aug 20, 2018 · 0 comments
Open

Game: research how to do verifiable game architecture #5

pkieltyka opened this issue Aug 20, 2018 · 0 comments
Assignees

Comments

@pkieltyka
Copy link
Member

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:

  1. 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

  2. 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)

  3. Source of truth for game rules? (same as the game version)

  4. Other...?

@pkieltyka pkieltyka reopened this Jan 14, 2019
@attente attente transferred this issue from another repository Apr 16, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants