Please beware of external links. Support will only be handled on this forum.
Manifold employees will have a Manifold Team badge next to their name.
In order for our team to investigate a bug/errors, please provide the following:
What is your wallet address? 0x3355C7C9340c47a8Cd005d8B30F579bAF4e873e6
A summary of the issue: i’m trying to mint x number of NFTs to multiple wallets, but i’m coming across an error in wallet/edition upload page preventing me from continuing. i’ve tried both manually inputting addresses as well as uploading a csv. i’ve also tried one vs. many editions and it’s the same error. i’ve tested this minting process a week or so ago with test contract 0xfdbce4a2992b5c03e4bb2bcc87df62041b03b31b and it wasn’t an issue.
a couple days ago, i tested with contract 0x229c02d3dc422e6ff9f5f2f25958d90b9e99ea60 and one edition of a test NFT and it worked fine. i believe manifold pushed up changes that is causing this issue.
What are you trying to do? move on to next step of minting x number of NFTs to multiple wallets
What is the actual outcome? Are you seeing any error messages?
i can’t move on to next step. an error message shows up at top of screen.
missing revert data in call exception; Transaction reverted without a reason string [ See: https://links.ethers.org/v5-errors-CALL_EXCEPTION ] (data="0x", transaction={"to":"0x65a9e36BA55AE6E2Ee80502ceBa62d6741857Ab7","data":"0x39ab3f4200000000000000000000000000000000000000000000000000000000000000200000000000000000000000000000000000000000000000000000000000000000","accessList":null}, error={"code":-32000,"message":"Request failed with status code 429"}, code=CALL_EXCEPTION, version=providers/5.7.2)
It doesn’t work on Arc still. I tried on Google Chrome and it worked. However, I got another error as I clicked Publish, which seems to be a “Gas Estimate Error on 8453” (base chain)? Can you please advise?
Big thank you for the help. I’m on call now and going to take this over along with @hoku.
Once I have that CSV I can find out which address is the offender as well as update our front end to return a muuuuch more helpful error and let you know which address is the bunk one.
any updates here? i’d like to get this out to our users asap. and if it’s not the method i took originally (batch erc1155 mint to multiple wallets via manifold), would appreciate any alternative suggestions.
i am unable to recreate the issue with your CSV + setup so far
is your wallet on base? sounds like it might not be swapping networks as expected. because this page should require you to be on the correct network before you can engage. but if you are not on that network those calls will fail like this.
i will update this to be more resilient as best i can in the meantime. for now your best bet is to swap to base ahead of time, and maybe try a different wallet browser extension that better supports network swapping and base network.
also let me know if i missed anything in the reproduction steps!
i’m not sure what network it was on by default. but if i needed it to be on base, i always got a prompt to change it to base.
also, instead of continuously trying to resolve this with the initial contract we made (which was ideal), we just ended up creating a new contract and resolved this issue. we don’t plan to try minting on the original contract we made again.
how bizarre. so sorry for all the troubles, what a huge inconvenience. i’m happy to hear the new contract works.
a new contract working but an old one not… i’m realizing now that maybe our UX was not properly picking up on the fact that the OG contract you were trying to interact with was actually deployed by a different wallet than the one in your browser extension. various wallets can be very buggy with which one is “connected” vs doing the txs.
can you provide the contract address for me and that you were originally trying to use? good for me to know these things as i can add extra guard rails in and return better error messages once i know the edge case exists! thank you so much!!!
Please beware of external links. Support will only be handled on this forum.
