:1234: Code to reproduce I'm using 2 upgradeable contracts: one ERC20 token and another which injects an IERC20Upgradeable value in its initialiser: function initialize(IERC20Upgradeable _token) public initializer { __Pausable_init(); __AccessControl_init(); __UUPSUpgradeable_init(); …

Is this the correct way or should I change it? You can pass in the first proxy's address as the parameter. For reference, see Example on how to use ERC20 token in another contract Also, if I wish to split the deployment, what's the equivalent for <Contract>.attach for upgradeable contracts? <…

Is it okay to use msg.sender and msg.data in these contracts or should I use _msgSender() and _msgData() from Context*?

[image] Vivraan: Is it okay to use msg.sender and msg.data in these contracts or should I use _msgSender() and _msgData() from Context* ? It's okay unless you are planning to use meta transactions. See this thread for more info on Context: Help understanding contract Context

Injecting an upgradeable contract in another + deploying in parts

Support Upgrades

ericglau January 22, 2022, 4:15pm 5

It's okay unless you are planning to use meta transactions. See this thread for more info on Context: Help understanding contract Context

Topic		Replies	Views
Deploying Upgradeable proxy contract without redeploying implementation Upgrades erc721 , proxies	0	531	November 11, 2021
How to deploy a Proxy Upgradeable Contract from a contract? Upgrades	14	4982	July 30, 2021
Upgradable Contracts Review Wanted proxies , etherscan-verify	19	2337	March 20, 2022
Deploy ERC20Upgradeable without Proxy for governable upgrades Smart Contracts	3	397	December 28, 2022
How to deploy upgradeable token Upgrades erc20	5	2394	April 6, 2021

Injecting an upgradeable contract in another + deploying in parts

Related topics