Skip to content
This repository has been archived by the owner on Sep 15, 2022. It is now read-only.

Error: Couldn't get permission to approve these tokens for trading. Their contract might not be implemented correctly. Please contact the developer! #193

Open
FantasyGameFoundation opened this issue Feb 21, 2022 · 6 comments

Comments

@FantasyGameFoundation
Copy link

I deployed CreatureFactory and corresponding contracts with hardhat, because it is deployed on rinkeby, the proxyRegistryAddress = 0xF57B2c51dED3A29e6891aba85459d600256Cf317, but when I create a sell order, the error message is as follows

code: -32000, message: 'execution reverted'}
Error: Couldn't get permission to approve these tokens for trading. Their contract might not be implemented correctly. Please contact the developer!

I have executed creature.transferOwnership(creatureFactory.address), set gasPrice: 20000000000, is there anything else I am missing

@drummel
Copy link

drummel commented Feb 22, 2022

Same issue :(

@phungnmd
Copy link

Same issue too +1

@swayam18
Copy link

Did anyone manage to find the answer? Perhaps there is a new proxy registry that we should be using?

@swayam18
Copy link

Okay, I believe the new rinkeyby proxy registry is at:
0x1e525eeaf261ca41b809884cbde9dd9e1619573a

https://rinkeby.etherscan.io/address/0x1e525eeaf261ca41b809884cbde9dd9e1619573a

I verified this by creating a new account on OpenSea and checking the address that is used to register the proxy when we put up an NFT for sale for the first time

This contract was deployed about 26 days ago.

It should be sufficient to just change to this new address

@thomasoss
Copy link

I used the ProxyRegistryAddress that was coded in 2_deploy_contracts.js in the opensea-creatures example (https://github.com/ProjectOpenSea/opensea-creatures). This was in January 2022
The address was
0xf57b2c51ded3a29e6891aba85459d600256cf317 f
or Rinkeby

Now I tried to use a factory contract deployed in March 2022. I got the error

Couldn't get permission to approve these tokens for trading. Their contract might not be implemented correctly. Please contact the developer!

I again checked the ProxyRegistryAddress for Rinkeby in the 2_deploy_contract.js in the repository mentioned above. It has changed to
0x1E525EEAF261cA41b809884CBDE9DD9E1619573A

I could not find any documentation in OpenSea where the current ProxyRegistryAddress for a given environment like Rinkeby is documented.

After this experience I think it is a good idea to code a setter for the ProxyRegistryAddress to be able to change the address after the deployment of a contract.

@vrogojin
Copy link

0x1E525EEAF261cA41b809884CBDE9DD9E1619573A not working for me either. Dah!

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

No branches or pull requests

6 participants