Geth-specific Blockscout version + internal txs + verifier #2145
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Below is a summarization created by an LLM (gpt-4-0125-preview). Be mindful of hallucinations and verify accuracy.
Why
The changes introduce support for specifying a blockchain node's chain ID when setting up a local Blockscout stack, enabling enhanced compatibility with different blockchain networks. Additionally, the introduction of a smart contract verifier service in the Blockscout docker-compose setup enhances the framework's capabilities in verifying smart contract interactions.
What
BlockScoutUpcommand to acceptchain-idas an argument, allowing users to specify the chain ID of the blockchain node Blockscout will index.BlockScoutUpfunction to accept and setchainIDenvironment variable, enhancing compatibility with different blockchain networks.BlockScoutDownandObservabilityDownto remove Blockscout and observability resources more thoroughly by deleting respective directories.sc-verifierfor smart contract verification.backendservice to use the Geth variant for Ethereum JSONRPC and to enable the smart contract verifier service.