This project is deployed by github-pages. Link
- Install Metamask browser download
- Create Metamask test account Tutorial
- Add test blockchain network Tutorial
- Testnet
- Network Name — Sepolia Testnet
- New RPC URL — https://eth-sepolia.g.alchemy.com/v2/[TEST_NET_KEY]
- Chain ID — 11155111
- Currency Symbol — SepoliaETH
- Block explorer URL — https://sepolia.etherscan.io/
- Get test ETH coins Google Faucet
- Project website
- Test account
- Email [email protected]
- Password 123456
This project was bootstrapped with Create React App.
- nvm use 20.0.0
In the project directory, you can run:
Runs the app in the development mode.
Open http://localhost:3000 to view it in the browser.
The page will reload if you make edits.
You will also see any lint errors in the console.
Launches the test runner in the interactive watch mode.
See the section about running tests for more information.
Builds the app for production to the build
folder.
It correctly bundles React in production mode and optimizes the build for the best performance.
The build is minified and the filenames include the hashes.
Your app is ready to be deployed!
See the section about deployment for more information.
Note: this is a one-way operation. Once you eject
, you can’t go back!
If you aren’t satisfied with the build tool and configuration choices, you can eject
at any time. This command will remove the single build dependency from your project.
Instead, it will copy all the configuration files and the transitive dependencies (webpack, Babel, ESLint, etc) right into your project so you have full control over them. All of the commands except eject
will still work, but they will point to the copied scripts so you can tweak them. At this point you’re on your own.
You don’t have to ever use eject
. The curated feature set is suitable for small and middle deployments, and you shouldn’t feel obligated to use this feature. However we understand that this tool wouldn’t be useful if you couldn’t customize it when you are ready for it.
Ultimately you need to check the Link header in the response to actually know, but for now you can be pretty sure that
- If it’s a “directory” then it will be /.acl
- If it’s an actual file then it will be /that-file.acl
To make sure everything is working so far, let’s compile our contract:
npx hardhat compile
start a local node:
npx hardhat node
Deploy (Example):
npx hardhat run --network localhost scriptsNFT/deploy-market.js
- NFT marketplace Contract deployed to address: 0xaD16EC538856733c0b3C4fbba720df89cCaeb313
- contracts/ is where we’ll keep our NFT smart contract code
- scripts/ is where we’ll keep scripts to deploy and interact with our smart contract
Alchemy -> nft-manage
npx hardhat run scripts/deploy-market.js --network localhost