Practical overview
When it fits
Use the repository when examining an Avalanche-connected card-game project or following its documented contract setup and Fuji deployment stages.
Who it is for
- Developers exploring browser-based NFT card games connected to Avalanche.
- Learners following a documented Hardhat contract compile-and-deploy workflow for the Fuji test network.
Documented uses
- Explore a multiplayer NFT card-battle game concept.
- Prepare, compile and deploy the game's smart contract to Avalanche Fuji.
- Connect the deployed contract artifact and address to the frontend.
Requirements & limits
- The project separates contract work under web3 from frontend contract configuration.
- The documented setup depends on external gists for the Hardhat configuration, deployment script and Solidity contract.
- Wallet pairing is described, while the provided instructions concentrate on contract setup rather than gameplay steps.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Prepare and deploy the contract to Avalanche Fuji
Compile the game contract, deploy it to Fuji, and connect the deployment details to the frontend.
Before you start
- The project repository and its web3 directory.
- Node.js package tooling and the documented Hardhat packages.
- Core wallet extension configured for testnet and funded through the Avalanche faucet.
- A PRIVATE_KEY environment variable and the referenced Hardhat configuration, deployment script and Solidity contract code.
Steps
In the web3 directory, initialize a Hardhat TypeScript project and install the listed OpenZeppelin, dotenv, Hardhat ethers and Hardhat toolbox packages.
Configure Core for testnet, fund the wallet, and set PRIVATE_KEY in a .env file.
Add the referenced hardhat.config.ts, deploy.ts and AvaxGods.sol files, then run npx hardhat compile.
Run npx hardhat run scripts/deploy.ts --network fuji.
Move the generated AVAXGods.json artifact into the frontend's contract folder and enter the deployed address in contract/index.js.
Expected outcome
The instructions describe a compiled contract deployed to Fuji, with its artifact and address supplied to the frontend.
Guide limitations
- The README refers to gists for key configuration, deployment and contract files; those are needed to complete the documented stages.
- The guide covers contract setup and frontend configuration, not launching or playing a multiplayer match.
- The private key is sensitive wallet data.
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 18 October 2026
- Original website title
- adrianhajdin/project_web3_battle_game · Official homepage title · retained in its source language