Open Kankalius opened 1 year ago
Any update on this? seeing same logs
Hi, @3commascapital Could you please share the bytecode of the contract you are trying to verify as well as the sources you are using for verification (json preferred)?
@Kankalius Could you also share those details, please?
Could you please share the bytecode of the contract you are trying to verify as well as the sources you are using for verification (json preferred)?
Good morning everybody, we are currently running BlockScout 5.2.0 beta and the current build of the Smart-Contract-Verifier. Both are running on the same Server (Ubuntu 20.04 Server LTS with current updates applied).
I want to verify a contract within the BlockSCout UI and therefore go to it's code tab and start a new verification. It doesn's matter if i use flattened code or a JSON file, both get me the message, that "no contract could be verified with the provided data". The compilers are correctly downloaded to /tmp/solidity-compilers and /tmp/vypr-compilers and are selectable within the UI's drop down list.
Looking in the journalctl of both Services doesn't show me any errors regarding that verification.
Can anybody please help me to find the right logs and infos, why the verification failed?
I attached the BlockSCout "env_vars.env" file, as well as the toml config file of the verifier and also how the services are configured within systemd.
verifier_toml.txt verifier_service.txt _profile.txt env_vars.txt explorer_service.txt
I highly appreciate your help. Thank you very much!