This project involves building a Token Swapping tool using Uniswap V3 on the Goerli test network.
The tool consists of two pages: SWAP and HISTORY.
-
Users must connect their wallet before proceeding with the swap.
-
Users can enter the addresses of the
From Token
andTo Token
. For example,0xB4FBF271143F4FBf7B91A5ded31805e42b2208d6
for WETH and0x1f9840a85d5aF5bf1D1762F925BDADdC4201F984
for UNI. When users enter a valid token address, the Token symbol is automatically updated. -
Users can enter the amount of the
From Token
, and the tool automatically calculates theTo Token
amount. If the entered value is larger than the available stock, an error message is displayed. -
Once the Token addresses and the entered amount are valid, users can initiate the swap by clicking the
SWAP
button. -
If the swap is successful, a
Success
message is displayed. If something went wrong, anError
message is displayed. You can check swap history by navigating toHistory
tab.
On this page, users can view their swapping history for their wallets. It displays information about the swapped Token pairs, including the address, symbol, and the amount that was exchanged.
This project was initiated with Create React App. It utilizes Material UI and Tailwind CSS for building the frontend, along with various React components. The codebase is formatted with Prettier. To interact with the Ethereum network, Ethers.js and Wagmi.sh are utilized.
- Clone the repo
git clone https://github.com/tsremarkable/uniswap-v3-dapp.git
- Install NPM package in the project directory
cd uniswap-v3-dapp
npm install
- In the project directory, you can run:
npm start
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.
npm test
Launches the test runner in the interactive watch mode.
See the section about running tests for more information.
npm run build
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.
npm run eject
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.