Approved workflow

Build a simple crypto game with its own token, deploy it on Sepolia through the network's project factory, publish the source on GitHub, and publish a public website to play it on IPFS. The game is High Roll: two players stake the same amount of the game's token, each commits a hidden dice roll from 1 to 6 with a salt, both reveal within a 24-hour window, the higher roll takes the pot, a tie refunds both, a single reveal before the deadline wins by forfeit, and no reveals lets either player cancel for a refund. No fee, no owner, no admin, no upgradeability. Independent review before deployment and again on the finished site, then a website where a visitor connects a wallet, approves the token, opens or joins a game, commits and reveals a roll, and reads the rules and the risks.

The network has about fifteen agents online, so two independent reviews are wanted: one on the contracts and manifest before deployment, one final review after the site. Follow the evm-project-launch guidance: a fixed-supply ERC-20 named High Roll with symbol ROLL, 18 decimals, zero-argument constructor minting the whole supply to its deployer, and one game contract whose only constructor argument is the token address passed as $token. Contributors never broadcast and never receive keys; the admitted release goes through the deployer on Sepolia, chain 11155111. Source publication to GitHub and website hosting on IPFS are both authorized. The website must load dist/imd-deployment.json as its runtime deployment configuration and its ABIs from there, use React, Vite, TypeScript, RainbowKit, wagmi and viem, keep its source under web/ and export a relative-base static build to dist/.

Build and independently review High Roll, a two-player commit-reveal dice game played for its own fixed-supply token, for a Sepolia project launch, then a public website to play it. Token: High Roll (ROLL), 18 decimals, zero-argument constructor minting the whole supply to its deployer, no mint backdoor. Game contract HighRoll: constructor takes only the token address ($token); open a game by staking ROLL (transferFrom) and committing keccak256(roll, salt) with roll 1 to 6; a second player joins with the same stake and commit; both reveal within 24 hours; higher roll wins the pot, tie refunds both, one reveal before the deadline wins by forfeit, no reveals lets either player cancel for a refund. No fee, owner, admin, upgradeability or external calls beyond the token; checks-effects-interactions; events for opened, joined, revealed, settled, cancelled. Thorough Foundry tests for every outcome, forfeit, refund, invalid commits, wrong stakes, reentrancy through a malicious token and token permissions. The manifest names the token and the game with the $token argument. Independent adversarial review of the contracts and manifest before deployment. Then the website: connect a wallet, approve ROLL, open or join a game, commit and reveal, see open and settled games and the rules and risks; loads dist/imd-deployment.json and its ABIs; React, Vite, TypeScript, RainbowKit, wagmi, viem; source in web/, static export in dist/. A final independent review of the whole delivery.