Common Errors

A list of common issues developers encounter when building and how to fix them.

Bug found? Email us, DM us on twitter or message full-time developer support on Discord.

Signatures were not sorted before being passed in - To fix this error, make sure to short sigs before passing them into requireDeployerOnly. You can do this by calling sigs.sort() before passing them in. It is also possible to run into this error if the hash that was signed was not the correct hash.

Signature failed to be recovered. ercrecover returned the zero address. To fix this error, make sure to pass in enough valid signatures that sign the hash in the sigs array.

Invalid Hash - To fix this error, ensure that hash is equal to hashAddDeployer().

Invalid Hash - To fix this error, ensure that hash is equal to hashRemoveDeployer().

Threshold must be greater than 1 - To fix this error, ensure that threshold is greater than 1.

Invalid Hash - To fix this error, make sure that hash is equal to keccak256(abi.encodePacked(_threshold)).

Invalid Hash - To fix this error, make sure that hash is equal to keccak256(abi.encodePacked(child, data, _nonce, block.chainid)).

Invalid Nonce, nonce must be 1 greater than the current nonce - To fix this error, ensure that _nonce is equal to the current nonce + 1.

Call to child failed - To fix this error, check to see what is causing the call to the child to fail.

Invalid Hash - To fix this error, ensure that hash is equal to keccak256(abi.encodePacked(_salt, _creationCode)).

Invalid Address, cannot be the zero address - To fix this error, ensure that _deployer is not equal to the zero address.

Invalid Address, cannot be the zero address - To fix this error, ensure that _funWalletImpAddress is not equal to the zero address.

Invalid Address, cannot be the zero address - To fix this error, ensure that _feeOracle is not equal to the zero address.

Invalid Address, cannot be the zero address - To fix this error, ensure that _walletInit is not equal to the zero address.

Unable to generate the address from this deployerSalt - To fix this error, make sure that FunWalletFactoryV1 has not already been deployed from the given create3deployer contract. If it has been, change FunWalletFactoryV1 to FunWalletFactoryV2 or another version.

Generated the wrong address from this deployerSalt - To fix this error, make sure that FunWalletFactoryV1 has not already been deployed from the given create3deployer contract. If it has been, consider changing FunWalletFactoryV1 to FunWalletFactoryV2 or another version.

Call to initialize failed on the deployed proxy - To fix this error, make sure the initializerCallData is formatted correctly.

To fix this error, ensure that the function is called from the deployer address.

The previous commit has not expired - To fix this error, wait for the previous commit with this commitKey to expire. This should take at most 10 minutes.

The hash at the commitKey does not match keccak256(abi.encode(seed, owner, initializerCallData)) - To fix this error, ensure the seed, owner, and initializerCallData are hashed and stored in commits at the corresponding commitKey.

The new owner of the funwallet must match data.newFunWalletOwner from loginData - To fix this error, make sure the owner set in loginData matches the owner address returned from the tweet.

The address of the new _oracle must not be the zero address - To fix this error, ensure that _oracle is not the zero address.

Invalid Child Address - To fix this error, ensure the caller is a contract deployed from the Create3Deployer.

Invalid Target Code Hash - To fix this error, ensure the caller is a contract targeted as an ERC1967ProxyData contract.

Invalid Contract Implementation Address - To fix this error, make sure you have the minimum threshold amount of valid signatures.

Invalid Signature Amount - To fix this error, make sure you have the minimum threshold amount of valid signatures.

Invalid Signature Amount - To fix this error, make sure you have the minimum threshold amount of valid signatures.

Unable to commit with a previously used commit hash - To fix this error, make sure you are not reusing someone else's commit hash. If there are conflicts, just regenerate the seed randomly.

Threshold can't be greater than deployers length - To fix this error, make sure the threshold value is not 0.

msg.sender must equal funwalletfactory - To fix this error, ensure you are calling this function from the FunWalletFactory contract.

funwalletfactory address cannot be set to 0 - To fix this error, make sure you are passing in the valid funwalletfactory address.

Seed has already been used - To fix this error, make sure you are not using an existing salt.

Cannot set the fee oracle address to 0 - To fix this error, make sure you are using the correct address for the fee oracle.

Invalid Address, cannot be the zero address - To fix this error, make sure _entryPoint is not equal to the zero address.

Value not equal to msg.value - To fix this error, make sure msg.value is equal to the value parameter.

execute() needs to be overridden - To fix this error, ensure you are overriding the execute method in your module.

The approveData's first four bytes must be the approve() function selector - To fix this error, change approveData so that the first four bytes are bytes4(keccak256('approve(address,uint256)')).

_wethAddr cannot be the zero address - To fix this error, make sure _wethAddr is not set to the zero address.

_router cannot be the zero address - To fix this error, ensure _router is not set to the zero address.

msg.sender does not have enough WETH - To fix this error, make sure msg.sender has a WETH balance greater than or equal to amount.

Approve failed - To fix this error, ensure you have correctly formatted the approve function.

Withdrawing a zero balance - You are trying to withdraw from Aave, but you don't have a balance.

Approve failed - The token you tried to approve has failed.

Approval Failed - You are trying to withdraw from Aave, but you don't have a balance.

Router cannot be the zero address - Make sure you are not passing the zero address when initializing the module.

Quoter cannot be the zero address - Make sure you are not passing the zero address when initializing the module.

feepercent must be less than or equal to 100% - To fix this error, ensure _feepercent is less than or equal to 10 ** _decimals.

ETH transfer failed - To fix this error, investigate why the ETH withdrawal failed. It is likely because amount was greater than the ETH balance in the FeePercentOracle.

Chainlink aggregator price must be greater than 0 - To fix this error, retry the call and ensure the price is greater than 0.

Chainlink aggregator updatedAt must be greater than 0 - To fix this error, retry the call and ensure updatedAt is greater than 0.

Chainlink aggregator answeredInRound must be greater than or equal to roundId - To fix this error, retry the call and ensure answeredInRound is greater than or equal to roundId.

socialHandles, loginTypes, seeds, and owners lengths must match - To fix this error, ensure all arrays passed into this function are the same length.

The seed from Twitter cannot be empty - To fix this error, make sure the seed you post on Twitter is not empty {}.

The address from Twitter cannot be 0 - To fix this error, ensure the address you post on Twitter for the new owner is not the zero address. Otherwise, you would be unable to claim ownership of the FunWallet.

The seed from Twitter cannot be empty - To fix this error, make sure the seed you post on Twitter is not empty {}.

The address from Twitter cannot be 0 - To fix this error, ensure the address you post on Twitter for the new owner is not the zero address. Otherwise, you would be unable to claim ownership of the FunWallet.

The seed from Twitter cannot be empty - To fix this error, make sure the seed you post on Twitter is not empty {}.

The address from Twitter cannot be 0 - To fix this error, ensure the address you post on Twitter for the new owner is not the zero address. Otherwise, you would be unable to claim ownership of the FunWallet.

Entrypoint address cannot be the zero address - To fix this error, ensure the entrypoint address is not the zero address.

msg.sender must be from the entrypoint - To fix this error, make sure msg.sender is from the entrypoint.

The ith delegate call failed - To fix this error, ensure the calldata for data[i] is a valid call.

batchActions consumed more ETH than allocated by msg.value - To fix this error, increase the amount of msg.value passed to this function.

The withdrawal has not been unlocked - To fix this error, wait until block.number is greater than the unlockBlock for the sender and ensure unlockBlock[sender] is nonzero.

The balances of the sender must be greater than the withdrawal amount - To fix this error, decrease the amount you are trying to withdraw.

The userOp.paymasterAndData must have a length of 40 - To fix this error, change the paymasterAndData field in the userOp to have a length of 40.

The verificationGasLimit must be greater than COST_OF_POST in GaslessPaymaster - To fix this error, increase the verificationGasLimit in the userOp.

The sponsor's ETH is not locked for use - To fix this error, ensure the sponsor's ETH is locked using lockDeposit().

The sponsor needs to approve the spender - To fix this error, ensure you approve the spender using setSpenderWhitelistMode() or setSpenderBlacklistMode(), and the sponsor's list mode is set to whitelist mode or blacklist mode using setListMode().

The sponsor does not have sufficient ETH in the paymaster to cover this operation - To fix this error, make sure you stake enough ETH from the sponsor's address using addDepositTo().

msg.value must be greater than or equal to the amount - To fix this error, ensure that msg.value is greater than or equal to amount.

The ith delegate call failed - To fix this error, ensure the calldata for data[i] is a valid call.

batchActions consumed more ETH than allocated by msg.value - To fix this error, increase the amount of msg.value passed to this function.

Token decimals must be greater than 0 - To fix this error, change the decimals in the token using setTokenData().

The token is not unlocked for withdrawal - To fix this error, call unlockTokenDepositAfter().

You are withdrawing more tokens than you have in balance - To fix this error, call getTokenBalance() to check your token balance and ensure amount is less than that.

The token is not unlocked for withdrawal - To fix this error, call unlockTokenDepositAfter() with ETH as the token.

You are withdrawing more Ether than you have in balance - To fix this error, call getTokenBalance() with ETH as the token to check your balance and ensure amount is less than that.

The call to the token oracle failed - To fix this error, check the token oracle and call setTokenData() to change the oracle if it is broken.

Failed to reimburse the paymaster with tokens via permitTransfer() - To fix this error, make sure you have permitted the paymaster to spend your tokens.

Spender doesn't have enough tokens - To fix this error, ensure you have enough tokens in the token paymaster via addTokenDepositTo().

The paymasterAndData length must be 60 - To fix this error, make sure to set the paymasterAndData length to 60.

The verificationGasLimit must be greater than COST_OF_POST - To fix this error, ensure you set the userOp's verificationGasLimit to be greater than COST_OF_POST.

The sponsor must lock their ETH - To fix this error, ensure the sponsor has locked their ETH by calling lockTokenDeposit() from the sponsor address.

The account must lock their tokens - To fix this error, ensure the user of the token paymaster has locked their tokens by calling lockTokenDeposit() from their address.

The sponsor ETH balance must be greater than maxCost - To fix this error, ensure the sponsor's ETH balance is greater than maxCost.

The sponsor must approve the spender - To fix this error, make sure the sponsor has approved the spender by calling setSpenderWhitelistMode() or setSpenderBlacklistMode(), and the sponsor's list mode is set to whitelist mode or blacklist mode using setListMode().

The sponsor must have approved the token to the paymaster - To fix this error, make sure the sponsor has approved the token to the paymaster by calling setTokenWhitelistMode() or setTokenBlacklistMode(), and the sponsor's list mode is set to whitelist mode or blacklist mode using setTokenListMode().

The permitted token must be equal to the token you are trying to pay with if using permit - To fix this error, ensure the permitted token is equal to the token you are trying to pay with if using permit.

The permitted transfer recipient must be the token paymaster - To fix this error, ensure you permit the token paymaster to spend your tokens.

The permitted transfer amount must be greater than or equal to maxTokenCost - To fix this error, ensure the permitted transfer amount is greater than or equal to maxTokenCost.

If permit was not used, make sure the token paymaster was approved to spend tokens by the sponsor or enough tokens were deposited into the TokenPaymaster - To fix this error, ensure the token paymaster was approved (approve()) to spend tokens by the sponsor or enough tokens were deposited into the TokenPaymaster via addTokenDepositTo().

Ensure msg.value is greater than or equal to amount - To fix this error, ensure that msg.value is greater than or equal to amount.

Sponsor cannot be the zero address - To fix this error, ensure the sponsor is not the zero address.

Target cannot be the zero address - To fix this error, ensure the target is not the zero address.

Token address cannot be the zero address - To fix this error, ensure the token address is not the zero address.

Spender address cannot be the zero address - To fix this error, ensure the spender address is not the zero address.

The token oracle cannot be the zero address - To fix this error, ensure the token oracle is not the zero address.

The tokenAddress cannot be the zero address - To fix this error, ensure the tokenAddress is not the zero address.

The token decimals must be greater than 0 - To fix this error, ensure the token decimals are greater than 0.

The Chainlink aggregator cannot be the zero address - To fix this error, ensure the Chainlink aggregator is not the zero address.

The token doesn't exist in tokens - To fix this error, ensure the token address is not the zero address.

The tokenListIndex doesn't match with the tokenAddress - To fix this error, ensure the token at tokenList[tokenListIndex] matches the tokenAddress.

Cannot recursively call batchActions from within batchActions - To fix this error, ensure you are not recursively calling batchActions from within batchActions.

Cannot recursively call batchActions from within batchActions - To fix this error, ensure you are not recursively calling batchActions from within batchActions.

Invalid Permit transfer amount - To fix this error, ensure your permit transfer transfers the correct amount of tokens.

Invalid amount of tokens transferred - The likely cause of this error is using a deflationary token that charges a tax when you transfer tokens. To fix this error, make sure you are transferring the correct amount of tokens and accounting for the tax/deflation.

The groupId count must be equal to the groups length - To fix this error, ensure the number of groupIds equals the number of groups.

Invalid Auth Type - To fix this error, ensure the auth type is correct.

Does not have enough balance of tokens - To fix this error, ensure you have enough tokens to permit transfer.

Cannot withdraw to address zero - To fix this error, ensure you are not withdrawing to address zero.

To fix this error, ensure that the target you are calling is included in the merkle root of allowed targets verified by the rule. If this doesn't work, verify that you are using the correct merkle root implementation.

To fix this error, confirm that the selector you are calling is part of the merkle root of allowed selectors verified by the rule. If this doesn't work, verify that you are using the correct merkle root implementation.

To fix this error, ensure that the ownerId is neither 0 nor an existing owner.

To fix this error, make sure the ruleId is not 0.

To fix this error, ensure that the rule you are using has a deadline that has already passed.

To fix this error, make sure the rule has been added to the role.

To fix this error, make sure the value for the execution call is less than the specified limit.

To fix this error, ensure that the fee value for the execution call is less than the specified limit.

To fix this error, make sure the fee recipient is included in the rule fee merkle root.

To fix this error, ensure the fee token is included in the rule fee merkle root.

To fix this error, ensure the rule you are trying to use actually exists.

To fix this error, make sure the user is a member of the specified role.

To fix this error, ensure the feeRecipientTokenMerkleRootHash is not zero.

To fix this error, make sure the targetSelectorMerkleRootHash is not zero.

To fix this error, ensure that the wallet has been initialized with the validation contract.

The entrypoint cannot be the zero address - To fix this error, ensure the entrypoint is not the zero address.

The msg.sender cannot be the address of the Funwallet contract - To fix this error, make sure the msg.sender is not the address of the Funwallet contract.

The function must be called from the Funwallet proxy - To fix this error, ensure msg.sender == funwallet.

The new entrypoint address cannot be the zero address - To fix this error, make sure the new entrypoint address is not the zero address.

Not enough ETH in the Funwallet - To fix this error, ensure the Funwallet has more than the amount of ETH you are trying to deposit.

Withdrawing ETH from the entrypoint failed - To fix this error, retry the operation and make sure you have a balance greater than the amount in the entrypoint.

Make sure a FunwalletFactory deployed the module - To fix this error, make sure msg.sender is the module.

The msg.sender must be the entrypoint - To fix this error, make sure msg.sender is the entrypoint.

The ETH transfer failed - To fix this error, retry the operation and make sure you have a balance greater than the amount in the wallet.

The developer ETH transfer failed - To fix this error, retry the operation and ensure you have a balance greater than the amount in the wallet.

The FunOracle ETH transfer failed - To fix this error, retry the operation and ensure you have a balance greater than the amount in the wallet.

The WalletValidations contract has already been initialized - Don't call initValidations() more than once.

Make sure there are more than zero validations - To fix this error, ensure there are more than zero validations, and the number of validation contract addresses is equal to the number of initCallData elements.

Make sure there are no duplicate validation contract addresses - To fix this error, ensure there are no duplicate validation contract addresses in validationData.

Make sure the signature length is greater than 0 - To fix this error, ensure the signature length is greater than 0.

Make sure the number of validations is greater than zero - To fix this error, ensure the number of validations is greater than zero.

The validation failed - To fix this error, ensure the validation contract returns true.

The validation was incorrectly formatted - To fix this error, ensure the validation contract address is not the zero address, the validation is valid, and the address is not the zero address.

The previous validation must be linked to this validation - To fix this error, ensure the previous validation is linked to this validation when adding or removing the validation.

You must have more than zero validations to get validations - To fix this error, ensure there is a nonzero amount of validations.

The caller must be this wallet - To fix this error, ensure you are calling addValidation() from your Funwallet.

The caller must be this wallet - To fix this error, ensure you are calling removeValidation() from your Funwallet.

The caller must be this wallet - To fix this error, ensure you are calling updateValidation() from your Funwallet.

Invalid Permit Signature - To fix this error, make sure you have a valid permit signature.

All batch inputs must have the same length - To fix this error, ensure all batch inputs have the same length.

No Validations in the wallet - To fix this error, ensure the wallet has validation contracts.

Make sure you are calling either execFromEntryPoint() or execFromEntryPointWithFee() from your Funwallet.

Don't call this function.