Skip to content

Launch First integrated Backend, Game Contract, and Top Grid #36

Description

@utgarda

Objective

Launch the initial version of the system with the following components:

  • Backend running on a server, listening to move events, sending answerPlayerMove transactions 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 answerPlayerMove Transactions: Implement logic to send answerPlayerMove transactions 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 BattleShip Contract: Modify the contract to send answerPlayerMove to the grid.
  • Create Forge Deploy Script for Game Contracts: Script to handle the deployment of game contracts.
  • Deploy and Register BattleShip: Deploy this version of BattleShip and register it with the system.

Acceptance Criteria

  • Backend server is running and functioning correctly.
  • answerPlayerMove transactions are sent correctly.
  • Game contract is deployed and operational, forwarding transactions.
  • Top grid contract is deployed and accepting answerPlayerMove.
  • BattleShip is updated, deployed, and registered.

Metadata

Metadata

Labels

backendGame Backend MicroservicecontractsSolidity contractsenhancementNew feature or request

Type

No type
No fields configured for issues without a type.

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions