i’m wondering if it is possible to mint additional existing (1155) tokens after a burn & redeem was initiated (and ended)?
for example, tokenID 4 of a contract was created using the burn & redeem function a while back, and in the case where i’d like to mint additional tokens, how would i go about doing so?
i don’t see a native functionality exposed via the Studio UI and have also tried checking on etherscan of the contract and thought perhaps [mintExtensionExisting] would be the function to call - maybe i’m just not getting the syntax correctly?
however, i’m still a bit unsure why with the inputs as shown in the screenshot below, the tx seems like it will still fail if i go ahead writing it.
how do i find instanceID for tokenID 4 of the token in the said contract (0xCD955030a01d9284A236485b1689821A632511c9)?
Under airdrop, enter:
recipients (don’t forget the square brackets, if it doesn’t work, try putting the 0x address in quotes):
amounts (don’t forget the square brackets).:
correct, it’s from more than a year ago, and i’m just using it as a sort of a test for a potential new burn & redeem / mint; and unfortunately that’s why i thought i got all the info already (the burn extension contract address and other inputs) but couldn’t seem to get it to work.
then question now is:
if i am to initiate a new burn & redeem (on this same creator contract), would i be registering for the newest burn & redeem extension upon publishing on the studio UI, and hence will be able to write to the airdrop method after the redeeming phase concludes? (such as the one i found and linked above: https://etherscan.io/address/0xde659726cfd166aca4867994d396efef386ead68#writeContract), or would i be stuck with using the old extension since it has already been registered on my creator contract?
and yes, there’s no airdrop functionality on this previous burn & redeem token setup page - where would it have been as i don’t see it now either when test setting up a new one up until the “publish” step? with the new burn & redeem, would it simply appear somewhere in the webpage after it’s initiated?
anyhow, i’d like to confirm because the potential drop mechanism will be dependent on it, i’ll have to know in advance about the possibilities (as i would otherwise not be able to fulfill a potential promise if i were to say something like “so and so that fit a certain criteria will be airdropped tokens after the burn & redeem windows ends”.)
hopefully this all makes sense, and thanks a lot again for all the help so far !
ah amazing, thanks for confirming - i think that pretty much answers the initial question and everything then ! i’ll try it out in the next few days as i’m not releasing the new piece just yet, but will circle back if there’s any additional issue