-
Notifications
You must be signed in to change notification settings - Fork 0
Open
Labels
backendGame Backend MicroserviceGame Backend MicroservicecontractsSolidity contractsSolidity contractsenhancementNew feature or requestNew feature or request
Description
Objective
Launch the initial version of the system with the following components:
- Backend running on a server, listening to move events, sending
answerPlayerMovetransactions to the game contract. - Game contract deployed, accepting transactions, and forwarding them to the top grid contract.
- Top grid contract deployed and accepting
answerPlayerMove.
Tasks
Backend
- Setup Backend Server: Configure and launch a backend server to listen to move events.
- Send
answerPlayerMoveTransactions: Implement logic to sendanswerPlayerMovetransactions to the game contract.
Game Contract
- Deploy Game Contract: Deploy the game contract on the appropriate network.
- Forward Transactions to Top Grid Contract: Ensure the game contract forwards transactions to the top grid contract.
Top Grid Contract
- Deploy Top Grid Contract: Deploy the top grid contract to accept
answerPlayerMove.
Development Details
- Update
BattleShipContract: Modify the contract to sendanswerPlayerMoveto the grid. - Create Forge Deploy Script for Game Contracts: Script to handle the deployment of game contracts.
- Deploy and Register
BattleShip: Deploy this version ofBattleShipand register it with the system.
Acceptance Criteria
- Backend server is running and functioning correctly.
-
answerPlayerMovetransactions are sent correctly. - Game contract is deployed and operational, forwarding transactions.
- Top grid contract is deployed and accepting
answerPlayerMove. -
BattleShipis updated, deployed, and registered.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
backendGame Backend MicroserviceGame Backend MicroservicecontractsSolidity contractsSolidity contractsenhancementNew feature or requestNew feature or request
Type
Projects
Status
In Progress