eth-bytecode-db
service is responsible for retrieving the contract details and for contract verification.
CHAIN_ID
value and check you are using the Blockscout hosted eth-bytecode-db
service. To do this, specify the following ENV variables in your Blockscout instance:
eth-bytecode-db
has read access to the Verifier Alliance database and can retrieve stored data.
API_SENSITIVE_ENDPOINTS_KEY
environment variable. If needed, Blockscout can generate and share it with you. This allows the Vera application service to trigger the lookup for verified contracts. Contracts are not verified directly when stored in the Vera database, so the instance must retrieve them for verification. Generally, the instance performs this retrieval on-demand when someone accesses the contract page. This process does not require any special access rights but has a timeout to prevent abuse. The API_SENSITIVE_ENDPOINTS_KEY
allows the use of a special /api/v2/import/smart-contracts/{address}
endpoint, bypassing the timeout limitation. The Vera application service uses this private endpoint to enforce the contract lookup on the instance. If not installed, the contract will remain unverified from the instance’s point of view and will be verified later only when someone accesses the contract page.
API_SENSITIVE_ENDPOINTS_KEY
GET http://proxy-verifier.services.blockscout.com/api/v1/chains