I have an ERC20 token already deployed on the Ropsten testnet with two versions. V1 is a simple unproxied ERC20 token and looks like this: // SPDX-License-Identifier: MIT pragma solidity ^0.8.2; import "@openzeppelin/contracts/token/ERC20/ERC20.sol"; import "@openzeppelin/contracts/access/Ownable…

[image] lalalei: I used the V2 ABI and contract address You need to use V2 ABI but proxy address, not implementation address, which is what you seem to be using based on the effect of getting owner zero.

Bumping this thread. Some more info: Contracts V1 and V2 are generated from wizard.openzeppelin.com . Nothing was modified. V2 passes the get owner, symbol, and name truffle tests.

Please use our Upgrades Plugin for Truffle in order to deploy a UUPS contract. [image] Upgrades Plugins - OpenZeppelin Docs

Hi, thanks for your response. I've already deployed the contract using truffle upgrades plugins. My problem is interacting with the deployed contract with web3.

Sorry, I wasn't able to check this post earlier. Your solution worked! I know understand. Thank you very much.

How to interact with UUPS upgradeable contract using web3?

Support Upgrades

Topic		Replies	Views
Call UUPS proxied contract with a web3 node.js app Developer Wanted erc20 , proxies , web3js	3	1073	November 10, 2021
Error interacting with upgradeable contract via web3 "Contract with hash not found." SDK erc20 , proxies	2	3368	August 17, 2020
Unable to interact with Upgradeable OpenZeppelin Contract Upgrades erc20 , proxies	2	1912	June 23, 2021
Upgrade of UUPS Contract failing cause of delegatecall Upgrades	3	530	October 10, 2023
How to call methods of the upgraded contract using proxy address? Upgrades	7	4497	October 22, 2020

How to interact with UUPS upgradeable contract using web3?

Related topics