Hi,
yesterday I had problems on minting a new token because of the Arveawe network issue.
Then I finally minted the token but the full collection disappeared on Opensea.
I need to fix this asap. Please let me know.
This is the collection’s contract: 0xa7a40b2d711ddc7d53585986e21fa5905fe61bbb
This used to be functioning link on OS: https://opensea.io/collection/strangers-2026
This i my OS profile: skygolpe - Profile | OpenSea
Hi,
I checked and the contract looks fine on-chain. Have you tried reaching out to Opensea directly regarding this issue?
Hi,
Thank you for checking the contract. Yes, I also realized that everything appears to be fine on-chain, and apparently, the token itself was minted correctly.
However, I want to clarify that this issue seems to have started specifically during the Manifold minting process, when I first received the Arweave network error. Before that, the STRANGERS 2026 collection was already visible and properly indexed on OpenSea. After the failed attempt / Arweave error and the later successful mint, the existing OpenSea collection page started returning “Page not found.”
The issue is now creating a real problem for me, because this is a veryimportant collection for me with many collectors already involved, and at the moment, the collection is no longer visible on OpenSea.
I can try to contact OpenSea as well, but before doing that, could you please help me verify a few things from the Manifold side?
-
Can you confirm that the Arweave upload for the latest token fully completed and did not leave any pending or failed metadata job?
-
Can you confirm that the tokenURI for the latest token resolves correctly and consistently?
-
Can you confirm that the contractURI / collection-level metadata is still correctly resolving?
-
Is there any possibility that OpenSea indexed the collection while the metadata was temporarily unavailable because of the Arweave issue?
-
Can Manifold trigger, request, or help coordinate a re-index / metadata refresh with OpenSea?
The token is visible on other aggregators, so I understand this is not an on-chain issue. But the timing strongly suggests that the OpenSea problem was triggered by the metadata / Arweave issue during the Manifold minting flow.
I would really appreciate your help here. Since this happened while using the Manifold minting service, and since Manifold likely has a more direct technical relationship with OpenSea than I do as an individual creator, I would appreciate if you could help escalate or support the resolution from your side as well.
At the moment I have an important collection that has effectively disappeared from OpenSea, so I need to understand how we can get this resolved as quickly as possible.
Thank you.
I sorted with OS. The collection is now visible.
This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.