Hi, I use OpenZeppelin SDK & and all the good things in @openzeppelin/contracts-ethereum-package/contracts/... I have a simple function initialize() public initializer { ... } at the very beginning of my contract to setup everything. But I inherit others in initializers from the OpenZeppelin cont…

Ah, I see. It seems like the issue is Truffle not handling function overloads by default. Truffle 5 added a way to do this , using the .methods proprty. In your case, I believe the code should be something like: await myContract.methods['initialize()']({ from: accounts[0] }); Alternatively, renami…

Problem as sometimes initialize() can't be called

Archive SDK

abcoathup Split this topic February 21, 2020, 8:48am 7

A post was split to a new topic: OpenZeppelin CLI regular deploy doesn’t offer initialization

Topic		Replies	Views
Suggestion: add note for overloaded "initialize" function General	3	513	October 7, 2019
Initialise a contract via the CLI and programmatically with OpenZeppelin SDK Guides and Tutorials	0	1148	August 30, 2019
Picking No when prompted to call method after deployment results in error SDK	6	1511	February 20, 2020
Calling initialize() after deployment from a factory reverts SDK erc20	4	1087	July 15, 2020
Contract `MyContract` has a constructor When Including "constructor() initializer {}" Smart Contracts erc721	1	2217	October 25, 2021

Problem as sometimes initialize() can't be called

Related topics