I've been reading as much around this as possible, but cannot verify a contract which relies on openzeppelin imports, because the compiled bytecode differs from the deployed bytecode.
I deployed an ERC721 contract using REMIX, I didn't verify it immediately on Etherscan, I only tried to verify it after a few weeks. Meantime, the Remix on my browser was updated once after the deployment. Not sure will this has an effect on the bytecode.
I didn't change any of the code in the contract. I compile with
The methods that I've tried to verify the contract:
- Directly on Etherscan (flattened contract)
- Using Hardhat (flattened and unflattened contract)
- Using Remix with a plugin called "ETHERSCAN - CONTRACT VERIFICATION"
Deploying a new contract is not an option for me, I was wondering is there anyone or company providing services of reversing the bytecode to see what went wrong (I will provide the source code), so that it can be rectified and get the contract verified?
or what other options do I have?