I’m getting a transaction hash error while setting up my NFT project
I’ve been working on launching an NFT collection using a popular GitHub template. Everything seemed to be going smoothly until I hit this roadblock.
When I execute the contract deployment command, the process runs for about 30 minutes before throwing this error:
ERROR CAUGHT: FAILED: Cannot locate transaction with hash: 0x8c47a2b9863f71d428e5bc93a672b804f12e8ab7269c483d117a6c592746f89b
I’ve double-checked all my configuration settings and made sure all required fields are properly filled out. The deployment process takes quite a while before failing, which makes me wonder if this is expected behavior or if something is actually wrong.
Has anyone else encountered this type of transaction lookup failure during NFT contract deployment? Is the extended processing time normal, or should I be looking for a different issue in my setup?
Had the same problem when I deployed my NFT collection. That “transaction hash not found” error usually means your original transaction got replaced or dropped. After 30 minutes, it probably timed out and got purged from the mempool. Deployment scripts suck at handling transaction replacements - they keep looking for the original hash even when a new transaction replaced it. Check your wallet’s transaction history for any pending or failed transactions around that time. You might find the successful one there. Next time, start with higher gas to avoid this mess. Also consider using a deployment script with better error handling. Remix IDE works way better than most CLI tools for this stuff.
your transaction prolly got dropped from the mempool - happens when you set gas too low or the network’s swamped. bump your gas price up 20-30% and try again. also, double-check your RPC endpoint isn’t flaky - free ones often timeout on big deployments.
that’s a weird error! 30 minutes before failing is definitely unusual - most deployments either bomb immediately or finish in a few minutes.
what network are you using? mainnet, polygon, testnet? and are you deploying with hardhat or truffle?
the transaction hash error is strange because it means the transaction got submitted but then disappeared. could be network congestion or your rpc provider timing out.
check that transaction hash on etherscan (or whatever block explorer you’re using). sometimes the transaction actually goes through but your deployment script loses track.
what are your gas settings? if you set gas price too low during busy periods, transactions get stuck in the mempool forever before getting dropped.
which github template are you using? some have known issues with certain network configs that could cause this.