Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implementation Contract Address mismatch? #36

Open
sawyerru opened this issue Sep 9, 2021 · 0 comments
Open

Implementation Contract Address mismatch? #36

sawyerru opened this issue Sep 9, 2021 · 0 comments

Comments

@sawyerru
Copy link

sawyerru commented Sep 9, 2021

Hello, I'm looking at a seeming mismatch on this repo vs Etherscan.
On Etherscan there is a proxy address pointed to the new USDP Contract (V3): 0xb54d4E8BB827f99af764b37249990Fa9D6840E20

But when I look at your IMPLEMENTATION_SLOT=0x7050c9e0f4ca769c69bd3a8ef740bc37934f8e2c036e5a723fd8ee048ed3f8c3
And make the following POST request:

{
    "id": 1,
    "jsonrpc": "2.0",
    "method": "eth_getStorageAt",
    "params": [
        "0x8e870d67f660d95d5be530380d0ec0bd388289e1", 
        "0x7050c9e0f4ca769c69bd3a8ef740bc37934f8e2c036e5a723fd8ee048ed3f8c3", 
        "latest"
    ]
}

I still get the 86eee0422322710866af89e9cae3f7383d55310a address (getImplementationAddress.js)

Should the IMPLEMENTATION_SLOT be changed to the new contract, or is Etherscan reading this wrong since you've moved into a new Ticker and name?

Thanks!

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants
@sawyerru and others