About Peppermint (ERC721 Pre-Mint)
Gas-efficient contracts for Pre-Minting 1,000,000,000 NFTs!
Our goal is to Eliminate Minting Fees for all NFT projects by providing a new method of Pre-Minting an entire collection up-front for half the cost of minting a single, standard NFT. Everything afterwards is a standard Transfer.
We have created ERC721PreMint by utilizing and only slightly adapting the popular Open Zeppelin ERC721 contracts in order to maintain the highest level of open standards. However, the approach we have taken is so simple, that it can be easily adapted to any ERC721 framework.
By eliminating the heavy-lifting of Minting, we can help to alleviate some of the network congestion caused when there is huge demand for a new token release. Miners will be able to process more "transfers" than "mints" in a single block.
For more information on how our ERC721PreMint works under the hood, please visit our blog.
These contracts, while simple, have not been audited. Charged Particles, and its affiliates, are not liable for any outcome as a result of using ERC721PreMint.
Docs
https://docs.charged.fi/peppermint
Installation
npm install --save-dev peppermint
OR
yarn add -D peppermint
Usage
After installation, just import and inherit ERC721PreMint.sol
pragma solidity ^0.8.4;
import "@charged-particles/peppermint/ERC721PreMint.sol";
contract MyNFT is ERC721PreMint {
constructor(string memory name, string memory symbol, uint256 maxSupply)
ERC721PreMint(name, symbol, _msgSender(), maxSupply) {}
function preMint() external {
_preMint();
}
}
Deployment
npm run deploy hardhat
npm run deploy rinkeby
npm run deploy goerli
npm run deploy mainnet
OR
yarn deploy hardhat
yarn deploy rinkeby
yarn deploy goerli
yarn deploy mainnet
ConsecutiveTransfer Event
We use the ConsecutiveTransfer event of EIP-2309 during the Mint Phase.
Known marketplaces that support the EIP-2309 Standard:
- Opensea
- LooksRare
Roadmap
- [ ] Implement Pre-Mint for ERC1155
- [ ] Add support for Upgradeable Contracts
- [ ] Eliminate the Max-Supply and bring back the “allTokens” array.
See the open issues for a full list of proposed features (and known issues).
Contributing
Contributions are what make the open source community such an amazing place to learn, inspire, and create. Any contributions you make are greatly appreciated.
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!
- Fork the Project
- Create your Feature Branch (
git checkout -b feature/MyFeature) - Commit your Changes (
git commit -m 'Adding MyFeature') - Push to the Branch (
git push origin feature/MyFeature) - Open a Pull Request
Running tests locally
npm run test
OR
yarn test
License
Distributed under the MIT License. See LICENSE.txt for more information.
Contact
- Rob Secord (owner) - @RobSecord
Project Link: https://github.com/Charged-Particles/peppermint