New answers tagged

0

Seems, this is the solution - verification https://medium.com/etherscan-blog/and-finally-proxy-contract-support-on-etherscan-693e3da0714b


1

Register the interfaces found in the OpenZeppelin file, or do I need to explicitly include the _registerInterface lines of the file in my own Smart Contract Calling the parent does this for you. You do not need to do it yourself. Both parent and child code live in the same address. Only if you use Solidity libraries your life gets complicated.


0

What about using deployProxy? // migrations/NN_deploy_upgradeable_box.js const { deployProxy } = require('@openzeppelin/truffle-upgrades'); const Box = artifacts.require('Box'); module.exports = async function (deployer) { const instance = await deployProxy(Box, [42], { deployer }); console.log('Deployed', instance.address); };


1

the functions I wish to use. Depends what you want to use them for. If you want to interact with a token, the token interface defines the functions you are work with. If you want to create a token then the implementation must cover each function mentioned in the interface. Open Zeppelin is well-crafted and modular so you don't have to reinvent everything. ...


Top 50 recent answers are included