Common Verification Errors
Last updated
Last updated
"Compiled contract deployment bytecode does NOT match the transaction deployment bytecode"
The submitted source code does not match the contract code deployed on chain.
Common causes include using a different compiler version or enabling optimisation runs.
For an exact match to be found, both source code and compiler settings specified have to exactly match the deployment conditions, for the same bytecode to be reproduced.
"Solidity Compilation Error: Identifier not found or not unique"
A compilation issue occured due to syntax errors in your Solidity source code.
Consider debugging your contract with any compiler such as or and reference the error from Solidity's .
"Unable to locate ContractCode at 0x539a277b12a3f6723f4c1769edb11b0be7c214da
The contract has not been deployed at the specific address at the specific chain.
Check the contract address you've deployed, if your contract deployment transaction has succeeded or if the specified is correct.
"Library was required but suitable match not found"
Double check on your library names ( case sensitive such as "PRBMath" ) or ensure that a matching library name and library address is provided.
"Unable to locate ContractName , did you specify the correct Contract Name ?"
A match was not found with the name of the contract specified when multiple files are provided.
Ensure that you have provided the correct contract name to be matched against, and making sure you submit the main contract name not its dependencies.
"Compiled contract deployment bytecode does NOT match the transaction deployment bytecode"
The compilation of your submitted source code does not match the deployment bytecode, ie the constructor arguments plus general initialisation code and runtime bytecode.
Similar solution as above, do take into account constructor arguments as well below.
"Please check if the correct constructor argument was entered"
if your contract utilized the constructor keyword, you should provide it in hex format. Otherwise, leave this field empty as it is.
"Please check if the correct bytecodehash was specified via standard-json verification."
Other submission formats such as single file or multifile do not support changing this setting, and will use the compiler defaults.
"This contract already Similar Matches the deployed ByteCode at 0x4200000000000000000000000000000000000042"
"Invalid or not supported solc version, see https://uniscan.xyz/solcversions for list"
This error is thrown when you specify to use an invalid or unsupported version of the Solidity Compiler ie. below v0.4.11-nightly.2017.3.15+.
"Source code already verified"
If you think this might be a mistake, do check if you've submitted verification to the right explorer/chain, a contract that is verified on Uniscan is not automatically verified on other explorers.
"Source "@openzeppelin/contracts/ERC20.sol" not found: File import callback not supported"
The chain you've specified does not have an Uniscan-like explorer.
"This could be a temporary error, please retry or contact us (Error Code 10001/10002/10003)"
A was used in your contract deployment, but was not specified, misspelt or using the wrong library address.
You may reference your original deployment's constructor arguments or determine it from the .
The settings of your submitted source code differs from the settings of your original contract deployment, such as being set to ipfs or none.
Submit your contract verification using the solc json input format, and accordingly there.
This error indicates that the contract has already been verified via to another contract.
Kindly to us at this point of time to have this updated to Full Match if required.
Do if you need to verify a contract below this supported version such as to prove you deployed the first NFT!
An has been obtained, get back to having your !
This error is thrown when contracts reference imports from external sources, such as libraries or Github links.
Consider your source code into a single file, or use the Solidity Standard Json Input format that comes with tools such as to resolve these external imports.
Check the chainId used against our .
Something went wrong on our end, which could include downtime or windows.
Please retry this in a while or if this continues to persist!
