Summary
Install the required Web3 libraries to prepare the frontend for wallet connectivity and smart contract interaction. These dependencies provide the foundation for replacing static deployment data with live on-chain data and enabling future blockchain transactions.
Motivation
The current frontend is prepared to display deployment information, but it still requires the Web3 tooling needed to communicate with deployed smart contracts. Adding these dependencies establishes the infrastructure for connecting wallets, reading contract state, and submitting transactions.
Proposed Changes
- Add wagmi for React hooks and wallet management.
- Add viem as the blockchain client for contract reads and writes.
- Add @tanstack/react-query for efficient caching and asynchronous blockchain data fetching.
Expected Outcome
- Support wallet connections (e.g., MetaMask).
- Enable reading live data from deployed smart contracts.
- Prepare the frontend for mint, redeem, and other on-chain interactions.
- Provide the foundation for replacing static deployment data with blockchain-backed data in future changes.
Notes
Running npm install will also update package-lock.json automatically to lock the dependency tree for reproducible installations. No application logic or UI behavior is changed in this issue.
Summary
Install the required Web3 libraries to prepare the frontend for wallet connectivity and smart contract interaction. These dependencies provide the foundation for replacing static deployment data with live on-chain data and enabling future blockchain transactions.
Motivation
The current frontend is prepared to display deployment information, but it still requires the Web3 tooling needed to communicate with deployed smart contracts. Adding these dependencies establishes the infrastructure for connecting wallets, reading contract state, and submitting transactions.
Proposed Changes
Expected Outcome
Notes
Running npm install will also update package-lock.json automatically to lock the dependency tree for reproducible installations. No application logic or UI behavior is changed in this issue.