I am deploying a crowdsale smart contract. I deployed it on testnet.bscscan.com earlier.I had to change the name of the token , so I just changed the name and tried to verify the crowdsale contract which automatically verified my token contract in past times, But it does not verify the token contract now. I tried to deploy a same contract of previous code. Still got the problem.

I deployed it on ropsten.etherscan.io. Sill the same problem.

I also tried to verify the contract separately but got ERR_CODE_2.

Contract address of previous token: 0x39b8d1a24dbfddc655592e6f1f55e246c79c5be2

Crowdsale address of previous token : 0x19eeD596ECDED92C5267385A2FE06C90Dd89b0B4

Contract address of new token : 0x8271a0794067e1F918E17fC3aFB22988E8E41e4f

Crowdsale address of new token : 0x3D4C8A91E93886a43BeD38322091CA643A5F87D2

Please if anyone can help. It means a lot to me


I don't think anyone could tell what's the difference in the expected and actual bytecodes without going into crazy compiler-level detail. Simple changes like adding a new line in the code could result in a different bytecode. Changing comments doesn't make a difference though. You change or remove any comment (remove the line entirely, reducing the number of total lines) without it impacting the resultant bytecode.

  • I did not changed any line, just replaced the name. Jun 12 at 5:30
  • Replacing the name is enough to change the resultant bytecode. Jun 12 at 5:48
  • It depends on what you specifically did the first time you deployed the renamed contract. Maybe try re-deploying it and see if you get the same bytecode. Jun 12 at 5:49
  • Other things that could affect the bytecode are compiler version and whether optimizer is enabled. Jun 12 at 5:51

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.