openzeppelin-contracts VS hardhat-deploy

Lets look the events of Open Zeppelin’s ERC20 token contract:

ERC-777 is difficult to implement properly, due to its susceptibility to different forms of attack(opens in a new tab). It is recommended to use ERC-20 instead. This page remains as a historical archive.

This depends if you're writing a contract from scratch or using existing code. If you're making something new, then yes (recommend not to use THE most recent available, always better to go with tried and tested). For existing projects, never try to override the solidity version. This may be a pain with "@" imports - ideally everyone should specify the library version (e.g. https://github.com/OpenZeppelin/openzeppelin-contracts/blob/v2.5.1/contracts/token/ERC20/ERC20.sol).

Attempting to implement this repository: https://github.com/wighawag/hardhat-deploy

or we can use the hardhat-deploy community plugin to deploy our contracts more professionally.

I imagine you have figured out how to do it by now. Consider using this plugin - https://github.com/wighawag/hardhat-deploy It will make your life easier and adds hre.getNamedAccounts() and hre.getUnnamedAccounts() Also it is exposed in the environment when running tests

Deploying consisted of using hardhat and its fantastic hardhat-deploy plugin to automagically manage deployments for us.

Next, lets install a package called hardhat-deploy which makes working with hardhat 2x easier & fun 👻

Hardhat-deploy now supports zkSync (Github)

Uses hardhat-deploy to keep track of deployments (upgradable or normal)

Once the hardhat project is initialized, Next we install hardhat-deploy which will make our life easier with deployments and tests😁

Install hardhat-deploy plugin as npm install hardhat-deploy and import it inside 'hardhat.config.js' file as:

Just found https://github.com/wighawag/hardhat-deploy, which is pretty much what I was looking for