Open knerushkin-rumblefish opened 2 years ago
You can initialize different identifiers for different instances of the same contract to resolve the overriding issue. Somewhat like:
const tokens = ["token1", "token2", token3"]; // identifiers of different ERC20PresetMinterPauser instances
let _tokens = [];
for (let i = 0; i < 3; i++) {
log(`Deploying ${tokens[i].toUpperCase()} contract ...`);
_tokens[i] = await deploy(tokens[i], {
from: deployer,
contract: "ERC20PresetMinterPauser", // This is where you initialize the contract to be deployed
args: [`${tokens[i]} token`, tokens[i].toUpperCase(), 1000000],
log: true
});
Describe the bug When I'm deploying multiple ERC20, after it I have deployment data only for the latest one being deployed
To Reproduce Steps to reproduce the behavior:
Expected behavior Get post-deployment data containing address informations about all deployed ERC20 Is there any way to do that?
versions