Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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

Level 22 Dex - Sentry 429 (Too Many Requests) in MetaMask #365

Closed
remedcu opened this issue Jun 22, 2022 · 1 comment
Closed

Level 22 Dex - Sentry 429 (Too Many Requests) in MetaMask #365

remedcu opened this issue Jun 22, 2022 · 1 comment

Comments

@remedcu
Copy link

remedcu commented Jun 22, 2022

I have created an issue in MetaMask, which you can see here: MetaMask/metamask-extension#15000

This happens in approve transactions, and I use the command: await contract.approve(instance, 10000)

I even imported the contract to remix, deployed it to the instance address, and tried the GUI for approval, but still the same result.

Out of curiosity, I tried another level (23 and so on), which works well.

Is it a problem with Metamask, OpenZeppelin, or some weird bug just for me?

@mattjaf
Copy link
Contributor

mattjaf commented Jun 24, 2022

There's other ways to interact with a contract. I noticed this as well and was still able to solve it.

I created a pull request on this issue adding a hint, I didn't want to be so obvious about it, I could of hinted at what does "at address do???" I might do that

SPOILER ALERT
Head over to Remix.
Create a new contract called AnyToken.sol with the contents of:
import "https://github.com/OpenZeppelin/openzeppelin-contracts/blob/master/contracts/token/ERC20/ERC20.sol";
compile it
Then, right under the deploy button there's a button that says At Address
paste the address of await contract.token1() and click
After that, paste the address of await contract.token2() and click

I'm sure you can figure out the rest.

I was stoked to find out that was possible

@OpenZeppelin OpenZeppelin locked and limited conversation to collaborators Jan 16, 2023
@xaler5 xaler5 converted this issue into discussion #565 Jan 16, 2023

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
None yet
Projects
Archived in project
Development

No branches or pull requests

2 participants