You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
I tried to connect to mainnet -but could not - so I'm keeping this example on Base. Deploy & Run is connected to Base and I inputted the basescan API key in the setting tab. Then I selected a verified contract. Then I copied a txn with this contract and pasted it into the debugger. I get the error below.
Expected behavior
The contract should load and I should be able to walk through the txn.
Screenshots
After some delay of minutes, I got connected to mainnet. With the wrong APi key in settings (input for Basescan) it doesn't work. When I use the correct api key, it does work.
So could this be just a problem on basescan?
The error in the toaster needs to be more clear when connecting using the wrong API key
What is NOTOK?
Desktop (please complete the following information):
OS: [e.g. Windows, Linux or MacOS]
Browser: [e.g. chrome, firefox]
Version: [e.g. 22]
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
Describe the bug
I tried to connect to mainnet -but could not - so I'm keeping this example on Base. Deploy & Run is connected to Base and I inputted the basescan API key in the setting tab. Then I selected a verified contract. Then I copied a txn with this contract and pasted it into the debugger. I get the error below.
Expected behavior
The contract should load and I should be able to walk through the txn.
Screenshots
After some delay of minutes, I got connected to mainnet. With the wrong APi key in settings (input for Basescan) it doesn't work. When I use the correct api key, it does work.
So could this be just a problem on basescan?
The error in the toaster needs to be more clear when connecting using the wrong API key
What is NOTOK?
Desktop (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: