Word to the wise: At 17:14 I am still having issues with Openseas. It has something to do with Openseas not able to read the id as a hexadecimal format (with 64 character padding zeroes.); If someone has a solution to that for ERC1155, I am all ears. I believe tweaking the solidity contract for "casting" the id to the required format may be a solution (not sure). Though, the test minting process seems to work on rarible! Contract ID for video (if interested): 0x994b3363b78e3b2b5e29846b092be9c63efefb4d
Hi, First of all. Nice video. Very clear and worked all well on Sepolia Test NW. I'm having issues with gas fees trying to deploy on Mainnet. Any suggestions. It always tells me >> Returned error: gas required exceeds allowance (235901) >> whatever gas limit I set.
Thanks for your favor but did you use Python since 2:35? You did not mention that. I got confused because you start explaining without explaining the program that we need to use to follow your lead in this video. 😅
Amazing explanation really. Thank you! I would love to ask if it is possible to "Lazy Mint" an item using this mechanism? However, do I have to create my own contract? Cannot I just use the one that Rarible provides?
You most certainly can. It's really all in the smart contract that you would have to write. Contract writing is in itself probably where the heart of the material is at at. I'd look on github for audited contracts and obtain the components your are looking for. This is a pretty good guide on how to start with lazy minting: nftschool.dev/tutorial/lazy-minting/#creating-a-signed-voucher
I have a 10k collection, need to upload it for sale today. has the ipfs and meta data done. having issue with smart contract, should i use ther ERC1155 or the ERC721 also is this still the best method for bulk uploading
After OpenSea started using a recaptcha, will this still work? Also, idk if rarible does the same too (also, I'm not good at coding whatsoever, and i might have missed it, but does it set a price /minimum bid when it is uploaded automatically, and do you have to do something to "make it for sale"? sry, I'm new to nfts and coding and i know practically nothing about topics of this sort.)
It should still work. The recaptcha, I believe, is more so for the folks who are using "memorized" clicks to upload thousands of images. They do upload their NFT's in sequential order and neceessarily via a smart contract. The probably did this to reduce their own overhead cost. I might be wrong though... In order to sell your NFT, you'd just have to specify some additional parameters in your smart contract. (selling point)
So how come we can mint directly onto opensea for free (gas fees arent an issues until selling them), but minting with a smart contract makes us pay the gas fees upfront on each NFT we mint? I have a large collection, and paying $10-50, per NFT, for gas upfront would be insane.
Ahh yes. Openseas does something called ‘lazy minting’ (which might be at default) So you won’t pay the gas fee upfront. Only when a customer purchases the NFT will the gas fee be added to the purchase price.
@@SpencerPaoHere I tried and uploaded an NFT to Open Sea and as soon as you want to sell it, you need to pay so it doesn't have lazy minting but Rarible does actually have lazy minting, you upload your file, and then put it for sell without any payment.
@@sairon63 this is incorrect. Both minting and listing on opensea is 100% free. The first time you list an ETHERUM based NFT there is a fee to pay, but its free forever after that. If you use polygon, there are no fees at any point.
@@BruceBates No, I'm not wrong, you probably did not try it recently. Listing is free but setting a price tag or schedule can't be done for free (Just like Rarible _at least before somebody buys an NFT). I tried again 1 min ago and as soon as I clicked on the sell button to set an ETH price for my listed NFT, it connects to your wallet and wants some ETH, however, on the other hand, Rarible is entirely free.
@@sairon63 again you are wrong. I use it ever single day of the week. I do not even have enough funds in my wallet for a single transaction (0.06 USD), yet I can still mint and list for free on opensea and do so almost every day.
I'd need more details on gas fees etc. But, the idea here is bulk minting. So, one transaction at whichever the fees currently are can mint you X nft's. Definitley try it on a testnet to get an accurate gauge on how much it'd cost to mint X nft's.
@@SpencerPaoHere Soooooo... imagine that my nfts are numbers from 1 to 100. I need to turn the numbers to hexadecimal in the same order. my problem is that the code runs the files alphabeticaly instead of logically, so it goes like: 1, 10, 100, 11, 12, 13... ...19, 2, 20... Then 1=1, 10=2, 100=3, etc... And so in the end, i get somewhat random hex values for my numbers.
@@vitopos8153 Ahh yeah. That makes sense. What step in the process is the numbering off? (if you want order) The 'rename_files_sequentially.py' or the 'rename-images-to-numbered-sequence.js'. Regardless, it's a matter of sorting the input values to get the order you desire or tweaking the logic a little to get the ordered sequence.
@@SpencerPaoHere Since the NFTs are based on numbers from 1 to 100, I didn't need to run 'rename_files_sequentially.py', so the problem is on 'rename-images-to-numbered-sequence.js'. I tried to set VSC's files order to the same order that the code is renaming the files, but that didn't work. I had the same results. Do you know what part of the code I should change for it to run in numerical order? Thanks for the answers, btw.
@@vitopos8153 Ahh yes. Unfortunately, Javascript is not my strongest language -- came with the forked repository. However, it probably has something to do with line 30 on rename-images-to-numbered-sequences. The filenames are being read in in alphabetical order (as you mentioned) and this can mess up the ordering. So, to counter this you can play around with 3 images and edit their naming convention. You can follow the hexademical format i.e (000..0001.png) (64 digits in total but with leading zeroes) OR you can tweak the python script such that there will be a conversion to hexadecimal format (but in number/letter format). There should be some additional logic to deal with (1.png vs 10.png) perhaps by slciking the numbers from the extension and treating the numbers as such.
