Context:
The Game Backend serves just one game instance and communicates with the game through the IGame interface. It will be implemented as a microservice that listens to the blockchain using the web3py library and reacts to events by sending transactions.
Requirements:
Initialization:
Event Listening:
Contract Interaction:
Implementation Details:
- Language: Python
- Libraries: web3py
- Integration: Interact with the
IGame contract as defined on the blockchain.
Notes:
- Make sure to align the logic with the specifications of the IGame interface.
- Proper error handling and validation should be considered even at this early stage.
- Since this is the first implementation stage, we will be focusing on essential functionalities; additional features and refinements may follow in subsequent tasks.
Please refer to the initial design documents and interface definitions for detailed specifications. Feel free to ask questions and discuss implementation details here.
Context:
The Game Backend serves just one game instance and communicates with the game through the
IGameinterface. It will be implemented as a microservice that listens to the blockchain using the web3py library and reacts to events by sending transactions.Requirements:
Initialization:
Event Listening:
moveId.Contract Interaction:
moveResultwith themoveIdextracted from the event.resultfrom the game logic based on the received event.Implementation Details:
IGamecontract as defined on the blockchain.Notes:
Please refer to the initial design documents and interface definitions for detailed specifications. Feel free to ask questions and discuss implementation details here.