Error During NFT Minting - “Bad Result from Backend” on Final Step

[fuax_fuax]

Subject: Error During NFT Minting - “Bad Result from Backend” on Final Step

Hello,

I’m attempting to mint my NFT collection of 50 static images using the 1-of-1 token batch ERC721 contract on the Base network. The process runs smoothly through the first two steps (Upload Files and Deploy), but fails at the Mint stage with the error: “Bad result from backend.”

I’ve attached screenshots from the third occurrence of this issue. Interestingly, I can see a successful transaction on Base (transaction hash and contract address included below), which I believe indicates successful deployment—though I’m not entirely certain, as I’m quite new to this.

I’ve been working on launching this collection for nearly a year now, and your platform seemed like the breakthrough I needed. After discovering it yesterday, I was genuinely excited and relieved—this is by far the closest I’ve gotten to completing the project. I’m hoping to avoid a repeat of my previous experience with ThirdWeb, where funds are still locked in their server wallet.

I’m happy to provide any additional information you need to help diagnose the issue. I truly appreciate your time and assistance, and I’m impressed by how well-designed your system is.

Thank you in advance for your help.

Best regards,
Nine (The Stationary Timewalker)
contract address: 0x49EA914264794544E95509b219f401dB00532d61
transaction hash:
0x9440f53a2c4e03aff0139b652bdab2438e6302e08ded2d711fda5ac9a9f882f3
my wallet address:
0x7d0cce5987b7784587f2fd6ea72a05439ca1517c
(this is my unstoppable domains wallet i use to sign in aka fuartworx.unstoppable)
I am using google chrome web browser.
wallet is unstoppable domains and it is also linked to my metamask.

— Current page —

Manifold Studio

— Browser Details —

{
  "userAgent": "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/143.0.0.0 Safari/537.36",
  "screenResolution": "2560x1600",
  "windowSize": "2560x1474",
  "isMetamask": true,
  "isRainbow": false,
  "isCoinbaseWallet": false,
  "isLedgerConnect": false,
  "isBitski": false,
  "isDawn": false
}

[fuax_fuax]

here is some information from my console.

Explanation

Understanding the problem

This error is coming from the ethers.js library (version 5.8.0). It indicates that the RPC provider (the backend) returned an invalid response when the library tried to execute getCode.

Specifically, the library expected a hex string (the bytecode of the contract at 0xDd5e0E456CFddBB21B5f54bB4ff670203B6b5c3F), but the backend returned an empty object (result={}). This triggered an INVALID_ARGUMENT error because an empty object cannot be “hexlified” (converted into a byte array). This usually happens when:

• The RPC node is malfunctioning or returning a non-standard JSON-RPC response.
• There is a network interceptor (like a proxy or browser extension) modifying the response.
• The node is out of sync and doesn’t recognize the request format.

How to verify

• Check the Network Tab: Open Chrome DevTools, go to the Network tab, and look for the POST request to your RPC endpoint (e.g., Infura, Alchemy, or a local node).
• Inspect Response: Look at the “Response” body for that specific call. A valid response for eth_getCode should look like {"jsonrpc":"2.0","id":1,"result":"0x..."}. If it looks like {"result":{}}, the backend is the issue.
• Switch Networks: Try switching the provider URL to a different RPC node to see if the error persists.

Suggested fix

Since this is a SERVER_ERROR caused by a malformed response from the backend, you should wrap the provider call in a try-catch block and handle the specific SERVER_ERROR code to provide a better user experience or trigger a fallback provider.

[dongqtm]

GM!

Sorry you’re running into this issue — we’re actively investigating it now.

To help us narrow things down, does this only happen with this specific wallet? Have you minted on Manifold before using a different wallet?

[fuax_fuax]

I have only tried this now. I’ve never minted before, or with a different wallet. unfortunately i am currently homeless/unemployed so i cant even try a different wallet as I don’t have the gas fees. so as of now its happening with only unstoppable domains. i can say that it happens no mater what type of mint i try i.e batch one of one , one of one token, burn redeem, not sure if that helps

[fuax_fuax]

switched to a coinbase wallet seems to want to work but now im having trouble with it registering/accepting the in wallet sign

[fuax_fuax]

I’ve tried a ton of stuff, but I’m still hitting the exact same roadblock.

I attached console screenshots that should hopefully give you a better idea of what’s going on with this stubborn issue. Since I’m getting pretty fed up, I’m definitely pressing pause on any more deployment attempts until we get this thing fixed.

Keep me in the loop, please! I was really hoping to have this deployed by the New Year. Thanks for your help— Fuax