-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Transfer ERC721 token #5145
Comments
By the way if you try to enter in the amount field 1 the the transaction will be confirmed but will fail later. |
I can second to this. It would be valuable of Metamask knew how to transfer ERC-721 non fungible tokens. |
I concur, it would be invaluable |
Thanks all, we're eager to get started on this but are waiting until we've migrated some of our backend controllers to a simpler shared module. See #5806 for more details, we'll update here when work starts! |
Hey there. Any progress on this front? I've been trying to use metamask to view/move NFT's (erc721) with only partial success. I can see that it's not possible to send NFT's yet, but I can sort of view them By this I mean that I can add my NFT as a custom token and see that I have 1 of them. If I then transfer it to another metamask account, both the sending and recieving accounts now show my balance as being 1. |
still working on it @nfurfaro, hang tight. given our design bandwidth and some backend changes, rough ETA ~3 weeks |
Hey there! Any updates here? Would really be an invaluable feature.... |
Seconded - any updates? Trying to get ENS addresses into metamask in token form... |
Hi! Also working on a project considering using ERC-721. Is there an estimate when you tackle this? |
I would also like to see this feature. It would really be a boost to the NFT community! |
I'll note that there is also a new NFT standard that would be good to support also: #5887 |
We would love to see this happen as well as we've seen several people trying to transfer their Unlock membershp tokens using MetaMask. See for example this transaction https://etherscan.io/tx/0x901df122a0b64c9b82ed3d90bf3baacfadbdddb8223f05ae518112dce0ab2bae |
Opps, I just transferred some ERC721 tokens to my metamask brave extension. I was planning on transferring one of them to another wallet/. Am I screwed now? |
no you are fine. you have transferred them to an Ethereum address they are safe |
Still not able to transfer NFTs. Any updates on this? |
+1 request |
this work has taken longer than originally expected because of some dependencies. sorry about that. you can certainly still transfer/view them either from MetaMask Mobile or by going to a dapp like Rarible or OpenSea. @folktale42 |
Is there any development work we can do ahead of time to prepare for this change? web specifically |
This is very important issue and seems to becoming urgent for many NFT owners and projects. Is there any estimated time for update? Thanks. |
Any update on this? |
I'm also curious if there are any updates on this issue. |
This will be released on extension very soon. |
What problem are you trying to solve?
We have ERC721 token than we are using in crowdsurance project. Before token activation it can be transfer to another user / account. The new version of Metamask supports ERC20 token transfer but did not recognise the difference between two types of token. We can add ERC721 token to the address and we can try to send it to other address but the transaction will fail because ERC721 transfer expect as the second argument not a token amount but unique NFT ID.
Describe the solution you'd like
It will be great for Metamask to recognise ERC721 token and support a transfer of this type of tokens.
Additional context
Here it is an example how it looks now when we transfer one ERC721 token to another account using our Dapp. You can see that Matamask consider this transaction with token amount equal to NFT ID.
and it is not possible to enter this type transaction in Metamask directly because the number of LCST token is 1 and Metamask is now allowing to enter in the amount field value that is more then 1
The text was updated successfully, but these errors were encountered: