deployERC20Contract under "thirdweb/deploys" returns error 410 Gone from disk cache #8609
Description
Hi Team,
I'm encountering an issue when using the deployERC20Contract function (or similar deploy functions) from the thirdweb deploys/pre-built contracts section.
The deployment process attempts to fetch the contract metadata from the following IPFS URL:
However, this request is failing with HTTP 410 Gone (from disk cache).
This prevents the successful deployment of ERC20 contracts via the thirdweb dashboard/CLI/SDK.
Steps to Reproduce:
- Go to the thirdweb dashboard or use the SDK/CLI to deploy a pre-built ERC20 contract.
- Initiate the deployment process for an ERC20 token.
- Observe the network requests – the metadata fetch to the above IPFS CID returns 410 Gone.
try {
setLoading(true);
const contractAddress = await deployERC20Contract({
chain: chainIdToChain(state.chainID),
client: client,
account: account,
type: "TokenERC20",
params: {
name: state.contractName,
description: state.description,
symbol: state.contractSymbol,
saleRecipient: state.firstSharesRecipient,
platformFeeBps: BigInt(state.platformFeePercentage * 100),
platformFeeRecipient: state.platformFeeRecipient,
defaultAdmin: account.address,
external_link: "",
image: uploadedS3Url,
trustedForwarders: [],
},
});
Expected Behavior:
The metadata should be successfully fetched from IPFS, allowing the contract deployment to proceed.
Additional Context:
- This appears to affect the standard ERC20 pre-built implementation.
- The 410 Gone status typically indicates the resource has been intentionally removed or is no longer available on the gateway.
- Date observed: January 2026
Could the team please investigate if this metadata CID needs to be updated, repinned, or if there's an issue with the IPFS gateway (ipfscdn.io)?
Thanks for your help!
