if using constructor, verifying smart contracts on etherscan with standard json input file on testnets is problematic.
In order to solve, should use an initialization function. This, however, is problematic with contracts used as libraries by other proxy contracts. In order to fix, should define variables values at contract creation, so they are included in the contract bytecode.
if using constructor, verifying smart contracts on etherscan with standard json input file on testnets is problematic. In order to solve, should use an initialization function. This, however, is problematic with contracts used as libraries by other proxy contracts. In order to fix, should define variables values at contract creation, so they are included in the contract bytecode.