Closed sk33z3r closed 2 years ago
Closing this ticket since #185 has been closed. We are minting on the new contract, and only very special cases have used the APIs to mint against the old NFTFactory
address.
So far all the issues that have been encountered are generally a misunderstanding of how to upload and pin files.
Closing.
We've uncovered something that appears to be causing a lot of strange, intermittent issues with the minting process. This began happening today, and some great minds on Discord got together and it looks like we may have pinpointed a root cause for the disparate issues.
I've attached 2 files. Here are the main differences we think are relevant to the issue:
new_contract.txt old_contract.txt
old_contract.txt
- Old contract, submitted for verification on 2021-12-07. This contract was functioning well for users on 2/27, 2/28 and 3/1. Take note of lines 1444 to 1450. You can see that the contract appears to expect thatmetadata.json
is a sub-file at the IPFS CID.new_contract.txt
- New contract, submitted for verification on 2022-02-28. This contract has only appeared today. We noticed it when some minters that deployed their contract yesterday had to deploy again today. It seems that almost no one can mint at the moment with this contract. Take note of line 1488. As you can see, it appears the contract is resolving the IPFS CID and not a sub-file at that hash.Additional Context for the Mint UI:
metadata.json
as a sub-file of whatever CID is entered into the form.Please provide some clear details on what's happening, and how we should expect to be able to mint items right now.