Changes to on-chain (for discussion)

[voidcenter]

• refactored solidity file to isolate business logic (maybe we need a different game. I feel like we probably need a list of tutorials, gradually ramping up functionality. like 1. template with something like the game here. 2. add random seed 3. add other chains.)
• moved scripts from Makefile to package.json, this seems more common in ts projects.

this is not to be merged immediately, there are something we need to discuss

• why do they need to reset before deploying their own contract?
• what is ignition?
• can't find /test folder
• is ignition/deployments needed?

Lastly can we add our own chain beside sepolia? @labiv3 maybe we need think of a name for our testnet

[tohacking]

• ignition is the hardhat deployment module's name: https://hardhat.org/ignition/docs/getting-started#overview
• there's no test right now
• ignition/deployments is only needed if we want to share our deployment information and avoid duplicated deployments

[tohacking]

About Ignition and deployment, I don't think we need to settle on one tech stack. It could be just a temporary decision that the only thing we offers is hardhat with its ignition module.

We can always offer multiple choices, e.g using Hardhat(deploy using ignition) vs Foundry(deploy using forge), or something else.