Create a new game in the sgx-runtime

[haerdib]

In a next step, for every new imported and validated parentchain block we query the queued game state of the node GameQueues. If games are found, we create an ack_game extrinsic with all game hashes, including our tee_id (extrinsic signature should probably contain all information already), and send it to the node. The next validateer importing this ack_game extrinsic will check the following:

• if the contained tee_id is a known peer (this ensures, that only one validateer set will create the game).
• if the game is already registered in its game registry (to ensure the game is only created once within a validateer set)

If everything passed, the validateer will create the game, include it in the sidechain block, that will be broadcasted to its peers. The peers will import sidechain block and include the new game in their registry. Only then, they will import the parentchain block containing the ack_extrinsic, which will not be executed, as the game has been registered already.

Tasks:

• [x] For every new imported and validated parentchain block, we need to query the node state. To verify that the returned values are valid, we need to check the accompanied read proof: #6
• [x] Upon successful validation, we create an ack_game extrinsic including all game hashes, sign it, and send it to the node. #7
• [x] #8
• [ ] Upon detection, we need to check the following:
  • check if the extrinsic creator is a known peer (including ourself) #12
  • ensure that the game is not already registered (should probably a get state call into sgx-runtime) #11
• [ ] If both checks passed, we call into the into sgx-runtime connectfour pallet new_game . #9
• [ ] #10
• [ ] Run a manual system test with node and worker (Workflow see comment from @darkfriend77 below). Success? Congratulation! With this, this epic can be considered done 👍

[darkfriend77]

@darkfriend77 did I get that correct with the queue_game extrinsic of layer one that triggers a new game?

@haerdib after at least 2 players used gameRegistry.queue(), the gameregistry will start to create games and add them into the game queue. queue_game, is only internally executed by the on_initialize which is getting matches from the matchmaker and creates game.

Testing the game is pretty simple.

1. Launch ajuna-node (branch: https://github.com/ajuna-network/ajuna-node/tree/ajuna-network)

2. Queue Alice, gameRegistry.queue()

   

3. Queue Bob, gameRegistry.queue()

   

After that, a queue should exist with one game_id

At this point L1 is waiting on Ajuna TEE to acknowledge a game .... once TEE has created the game it should call.

4. AjunaTEE, gameRegistry.ackGame(...)

After acknowledging the queue should be empty again and the game in the registry should have changed it's state from waiting to accept.

once the Ajuna TEE reads that the game is accepted it can set the game engine on running

[haerdib]

Here's a proposed sequence diagram:

I hope this makes somewhat sense. If you detect an issue, please let me know immediately.

[haerdib]

With https://github.com/ajuna-network/worker/commit/00f336e6832c63586443bdb63b9f17b8b57b996f we have successfully demonstrated the creation of a new game. So I'm closing this issue for now.