Replies: 3 comments
-
hello @Niet-Pham , your env microservice has two, I will help you fix it and please try it
try use this |
Beta Was this translation helpful? Give feedback.
-
for more communication please join discord blockscout |
Beta Was this translation helpful? Give feedback.
-
Sorry for reopening the discussion, but I'm having some trouble building Blockscout using docker pull ghcr.io/blockscout/blockscout:latest.
However, when I verify using a manually deployed local build, I don’t encounter this issue. Can anyone help me fix or resolve this problem? |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi everyone! I'm having some trouble verifying a smart contract on Blockscout that's connected to my local zkSync network.
This is my backend env
As far as I know, when navigating to the contract verification page, it calls the API http://localhost:3000/api/v2/smart-contracts/verification/config to fetch all available compiler versions.

However, when the CHAIN_TYPE=zksync environment variable is set, that API attempts to fetch compiler versions from the third-party endpoint https://eth-bytecode-db.services.blockscout.com/api/v2/zkysnc-verifier/solidity/versions, which returns null.
On the other hand, when CHAIN_TYPE=zksync is not set, it uses the endpoint https://eth-bytecode-db.services.blockscout.com/api/v2/verifier/solidity/versions, which correctly returns a list of Solidity compiler versions.
I’m not sure if I misconfigured something.
What is the correct setup to verify smart contracts on Blockscout (with a local zkSync network), and how can I make sure it fetches both solc and zksolc compiler versions correctly in the UI?
Beta Was this translation helpful? Give feedback.
All reactions