Vanity name registering system resistant against frontrunning
Table of Contents
Vanity name registering system resistant against frontrunning
This project is built with:
-
This project consists of 3 smart contracts:
-
VanityNameRegistrar - base contract which inherits ERC721 contract. When I read project task, I recognized that every name should be unique and that should be ideal to be represented as NFT. So, in this project, every vanity name is one NFT.
-
VanityNamePrices - contract for calculate prices for vanity names.
-
VanityNameController - controller contract, which should be main connection between some future front-end and this vanity name system.
-
-
Clone the repo
git clone https://github.com/StefanVitor/vanity-name-system
-
npm install
-
If you want to deploy contracts to Rinkeby / Ropsten, it should be add secrets.json file in main directory with format
{
"mnemonic": "abc def ghi..."
}
- Deploy contracts on local truffle or Rinkeby / Ropsten network
truffle --network networkName migrate --reset
- Test contracts on local truffle or Rinkeby / Ropsten network
truffle --network networkName test
- Fork the Project
- Create your Feature Branch (
git checkout -b feature/AmazingFeature
) - Commit your Changes (
git commit -m 'Add some AmazingFeature'
) - Push to the Branch (
git push origin feature/AmazingFeature
) - Open a Pull Request
Distributed under the MIT. See LICENSE
for more information.
Stefan Vitorovic - @StefanVitorovic - [email protected]
Project Link: https://github.com/StefanVitor/vanity-name-system