The current Nameable contract uses constructor to initialize state
|
constructor(string memory newName, string memory newVersion) { |
The latest implementation of TokenNFTConnector uses Proxy. https://github.com/The-Poolz/TokenNFTConnector/blob/386cd2bd61efccb3626fd1640e779ac31c552a65/contracts/ConnectorManageable.sol#L8
Should we also add NameableUpgradeable contract for the proxy?
Upgradeable contracts do not use the constructor to initialize the contract state. Constructors are made to be executed once on the deployment of contracts and are not included in the deployed contract bytecode. Implementation contracts do not contain the state variables that need to be initialized; state variables reside on the proxy
The current
Nameablecontract uses constructor to initialize statePoolz-Helper/contracts/Nameable.sol
Line 13 in 863eaf7
The latest implementation of
TokenNFTConnectorusesProxy. https://github.com/The-Poolz/TokenNFTConnector/blob/386cd2bd61efccb3626fd1640e779ac31c552a65/contracts/ConnectorManageable.sol#L8Should we also add
NameableUpgradeablecontract for the proxy?Upgradeable contractsdo not use the constructor to initialize the contract state. Constructors are made to be executed once on the deployment of contracts and are not included in the deployed contract bytecode. Implementation contracts do not contain the state variables that need to be initialized; state variables reside on the proxy