Ok I’ll take a look, but now the claim isn’t even loading the images from my .csv smh I guess the servers are busy. I’ll mint the last 315 tokens and update the .csv. Thanks again.
Not sure what you’re trying to do here exactly. But if you’re trying to sell them via a claim page you shouldn’t be minting them. Minting them to your wallet means you own them.
If you’re trying to sell them via a claim page you just need to set up a claim page and not mint anything.
To clarify, the tokens you pointed to on opensea have been minted to you. Which is fine if you’re trying to sell them on opensea or another platform.
But if you are trying to sell nfts on a claim page, those minted tokens won’t sell and only anything that hasn’t been minted yet will sell (claim pages are “lazy mint”, meaning tokens are minted when a sale occurs)
Looks like, based on your opensea link, you minted 1000 tokens. I’m not sure what your intention is with them, but you wouldn’t be able to sell those tokens on a claim page or manifold. It would be fine if you’re trying to sell these minted tokens on another platform.
Ok I see. So if I wanted to sell them strictly on the manifold claim page, I would have to burn the tokens and not mint them? If I want to strictly sell them on OpenSea, then it is fine that I minted all 1,315 to my wallet.
I guess the main concern is since I minted them, and no metadata is attached to the ones I minted on OpenSea, I guess I’d have to burn all the tokens? Because it seems that the claim page for updating metadata only applies to lazy minting that mints as it’s purchased. So I won’t even be able to update the metadata on the ones minted in my wallet for OpenSea?
This is the first time I’ve done a collection. So I don’t know any other way to mint with the metadata that I created besides making a drop on OpenSea, which will effectively make their default “take 10% of sales from creator “ on their platform.
Also on my claim page, it says that 0/1,315 haven’t been minted. I haven’t started the sale yet. So I don’t know if the metadata that I upload on claims page will occur until the sale begins. I extended the sale start date on 12/13/2023 at 10AM EST. I wanted to make sure I figured it out. The claims page link also has a link to the OpenSea collection. This is all so confusing. I don’t know if I should burn the tokens and figure out how to link all the metadata to all the NFTs before minting them.
You could burn them. Or you could simply blank out the metadata and kill the tokens that way, and deploy a new contract.
If you’re intending to sell these on manifold, the recommended way would be to sell them all and do a post sale reveal so it’s not predictable which token someone would get.
So, to avoid confusion, if you intend to sell 1315 tokens of a collection on manifold, you should:
- Create a new claim page (ERC721)
- Set a limit of 1315
- Set the assets and description to indicate that all tokens are unique and the tokens people get won’t be revealed until sale ends. (Important to make the mint random)
Once it’s done, you do a post mint reveal. See:
For the existing tokens, you should remove the assets and disable the claim page (set the token metadata to blank or some placeholder). You could burn them all but there doesn’t seem to be a point to doing so.
It sounds like this way it does random reveal on Manifold claims, but on OpenSea it shows all of the NFTs and if I list for sale there, people can see all 1,315 and choose which one they like. Which is fine, but I’m concerned about it not showing properties on OpenSea. The only other alternative would be:
-
Burn all tokens and it’ll stop showing all of the minted ones in my wallet( and OpenSea).
-
Use OpenSea new studio and “Drop” it’ll mint the NFTs in ordered number, not random according to OS staff. They also take %10 of earnings.
-
Use the method on Manifold, the claims will “lazy mint” and it’ll reveal them after minting, but random.
-
Don’t do anything. Sell on OS and buyers can see all NFTs and purchase what they want, but it might not show any attributes from my metadata. I don’t know any other way to show the metadata.
Also the user in the video has his on limited edition. All of them were minted, and it’s still on pre-reveal.
If you want to keep as is you’ll want to update the metadata of the 1000 tokens by uploading the csv again, which will upload to arweave and trigger a transaction to do the update. The changes should reflect immediately.
If you want to go the random reveal route you can blank out the tokens rather than burning (which is more work) by setting them all to an identical placeholder image and clearing the info. Again, these changes should reflect immediately/within a few hours.
The changes on Arweave with the .csv file will also make the change on the platform(OpenSea) after it updates? I’ve not seen it update on there, I don’t know if it’s because it’s on Optimism or because I haven’t listed any for sale on OpenSea yet(they’re on there but I haven’t put any for sale), and if that would trigger the update on the metadata. I’m looking to hear back from the OS representative before I sign for any sale, because it has some addresses I wasn’t so sure about.
I truly appreciate your time in explaining everything, I can see I’m close to the finish line lol just a few small details that need to be figured out.
You have to make the update with the csv, it uploads to arweave then it will trigger a transaction (you must save it) to have things update. If you don’t issue a transaction nothing will update.
If you are clearing the metadata you should be able to set the metadata to identical and set it that way.
I’ll try. Sometimes it gets stuck when loading the token images and doesn’t make it to page one of the preview(tokens with images and traits). It finished updating to Arweave, I think I figured out what the problem is. Since I minted all of the tokens to my wallet, is there a way to bulk update the metadata on your batch tokens(from my contract)? I did several sets of 200 tokens, when you click into each individual token, I see there is a way you can manually add properties, even though when you say refresh, it deletes everything. How do you get it to save? Will there be an update to use a .csv file to batch update all the tokens?
Ok, so you currently have 1315 tokens in the claim DISSARAE. What exactly do you want to do right now? Do you want to:
- Update the metadata so all tokens have something unique?
- Clear them out and create a new claim using post-reveal?
If 1:
- Go into Edit Claim → Tokens → Custom → Delete All
- Then - Upload CSV
- Then Begin Arweave Upload
- Then Publish Changes to Blockchain (after the previous steps are done)
If 2:
- Go Into Edit Claim → Tokens → Editions
- Upload a new blank image or placeholder so all tokens end up the same
- Then hit Save (which will trigger a blockchain transaction)
I think 2 because they’re all minted to my wallet. I’m putting them for sale on OpenSea. I’ve been updating the metadata manually in my contract>batch> tokens> and copying pasting the claims metadata since it has the attributes filled in. I have two windows side by side because I don’t see any other way to create the metadata for each token in the contract( or bulk upload metadata with a .csv like you can in claims). So I’ll have to spend the next few days copying pasting 200(batch) metadata manually. Unless there’s a way to batch metadata upload, don’t know if that’s a feature yet. Then I’ll upload a blank .csv for the claims so I can effectively delete it.
You don’t need to, follow the steps for 2 and it should update all tokens to the same image.
It’s regarding the contract batch mint. I found out the only way the metadata uploads on OpenSea with the various attributes is to go to the batch in the contract( like batch 200, minted) then go into the edit, modify the assets, then go on to the next. It’ll finish the group of 200, I mint the changes to Optimism, I then go to OpenSea and refresh metadata, and it worked. I tested with a couple, so I’m doing the first batch of 200 I minted. I’m almost finished.
It looks like you’re referring to the claim page, which doesn’t seem to affect any of the tokens I minted to my wallet(in batches of 200), and not changing on OpenSea market.
In my collection none of the tokens are the same, each one is unique with unique attributes, that’s why I’m confused when you say each image will be the same.
I’m talking about the claim page, which is what I saw, I didn’t realize you minted batches of 200 tokens. Those ones, then yes, you’d have to update them the way you are.
To be honest, I’m kind of confused as to what you’re trying to achieve. You’ve minted batches of 200 tokens, which are created now. You can updated these individually and can sell them on another platform.
You also have created a claim page, which would result in minting new tokens, using the assets that you’ve set. I haven’t dug into it, but the assets all seem to be similar between the claim page and minted tokens. It’s unclear what the intent is here.
Claim Page = set up new tokens for sale. Tokens that will mint to the purchaser directly when they buy. Updating these tokens can be done as per my post above.
Batch Mint = mint tokens to yourself or directly to others. The sale of these tokens would be using another platform or by selling these individually. Batch mint individual token updates post mint would need to be done individually.
Yes I realized when I batch minted it was two ways of getting the tokens on mainnet for sale. I saw the video of claim page and thought that was for simply editing the tokens that were already minted(mistake on my part).
So it looks like after I finish editing the metadata for my minted batches, I should completely delete the claim page tokens? And make sure to set the settings so that it doesn’t start a sale on my manifold website, perhaps removing the custom url and uploading the claim page with a blank .csv or could I simply delete the claim altogether?
I think a good suggestion for newer users is instead of calling it “claim page”( not sure if that’s the technical term)maybe call it “collection minting” or something similar. Then have a message when hovering over the options that explains this will mint new tokens for a collection, with the user specifying the total amount. Also let the user know that if they have already batch minted on a contract, it is not necessary to make a claim page.
yes, you can cancel the claim page/set it in the past if you are updating the tokens in the batch the way you are and selling via opensea.
(the best way to ‘end’ the claim is to set the start to the past or reduce the total supply to 0.
Got it, that makes sense. So by setting the claim page to zero, purchasers would not be able to mint anything from a claim because they wouldn’t exist or be on Arweave anymore after setting the supply to 0 and saving the changes?
correct, and set the start/end time to the past.