-
Notifications
You must be signed in to change notification settings - Fork 0
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
OPENSEA: setApprovalForAll via OpenSea website will trigger Metamask error #4
Comments
I am working on that @zhangzhongnan928 |
Hi, @zhangzhongnan928 , its known Metamask bug, which will be fixed in the next Metamask release |
This issue is severe because it renders MetaMask unusable on Chrome—once triggered, MetaMask won't work, requiring reinstallation. Interestingly, Firefox is affected but doesn't cause MetaMask to fail in the same way. To replicate, make sure you own some STTT tokens. Visit https://testnets.opensea.io/account, log in, click "List for sale," and follow the listing process. This bug can happen on both Firefox and Chrome, specifically with Metamask versions 11.11.4 (Chrome) and 11.10.1 (Firefox). The one I tried when reproducing, was one of the tokens of this collection in Sepolia https://testnets.opensea.io/collection/st404-testing-token-v3-4/ The core problem arises from MetaMask mistaking certain NFTs for ERC20 tokens due to their ERC20-like features. Consequently, when attempting to use |
hi, i still have this issue with forge token. ca: 0x73576a927cd93a578a9dfd61c75671d97c779da7 |
@Fast288 , are you sure it's correct repo for 0x73576a927cd93a578a9dfd61c75671d97c779da7 ? |
yes, its the token contract adress: 0x73576A927Cd93a578a9dFD61c75671D97c779da7 its ERC404. I cant list it to on opensea, my metamask gives me the error. |
@Fast288 , we didn't deploy this contract to mainnet, so you are wrong. Contract name is ST404, not ERC404 |
ok, any idea how i can fix the issue? |
Hi, |
You are using $FORGE token, which is not of this github repo:
I followed up your post when you posted to MetaMask, please discuss this issue there following my reply there MetaMask/metamask-extension#18507 (comment) |
Tried JoyID with STTT in Opensea, works fine.
Tried MM with Uniswpa V# NFT in Opensea, works fine.
The text was updated successfully, but these errors were encountered: