DEV Community

Matteo Leonesi
Matteo Leonesi

Posted on


Hawaii Liquidity Pool, training project

Hawaii Liquidity Pools

Studing Defi and Erc standards


About the Project

This project is born to give me (and anyone who wants to contribute to the project) the possibility to learn Solidity (Defi, Ercs standards ...) and Hardhat, anyone can contribute adding by Defi, NFT functionality or improve one that already exists. You can create new tokens, or use existing ones to create new contracts and functions(tested with hardhat is better).

Guide To Contribute :

  • if you want to create token (and you don't want to use the existing ones), call it with a name of a Hawaiian city
  • if you want to create functionalities that already exists (and you don't want to improve it) call your new functionalities in this way: "functionalityname_yourname".
  • add comment if needed.
  • follow the "contributing“ section in the

Convered Concepts until now :

  • erc20
  • primitive swap
  • buy erc20 tokens with eth
  • erc20 liquidity pool

Built With

Getting Started with Hardhat

npx hardhat accounts
npx hardhat compile
npx hardhat clean
npx hardhat node
npx hardhat test
npx hardhat help
Enter fullscreen mode Exit fullscreen mode


Contributions are what make the open source community such an amazing place to learn, inspire, and create. Any contributions you make are greatly appreciated.

  1. If you have a suggestion that would make this better, please fork the repo and create a pull request. You can also simply open an issue with the tag "enhancement".
    Don't forget to give the project a star! Thanks again! ❤️

  2. Fork the Project

  3. Create your Feature Branch (git checkout -b feature/AmazingFeature)

  4. Commit your Changes (git commit -m 'Add some AmazingFeature')

  5. Push to the Branch (git push origin feature/AmazingFeature)

  6. Open a Pull Request

Conventional Commits name

  • build: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
  • ci: Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs)
  • docs: Documentation only changes
  • feat: A new feature
  • fix: A bug fix
  • perf: A code change that improves performance
  • refactor: A code change that neither fixes a bug nor adds a feature
  • style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
  • test: Adding missing tests or correcting existing tests

Solidity Style Guide

Top comments (0)