This repository was archived by the owner on May 12, 2025. It is now read-only.
Open
Conversation
adrienmo
force-pushed
the
blockscout_poc
branch
from
2b46ac9 to
9644c20
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
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.
📝 Summary
This adds a modified version of blockscout blockchain explorer to the dev environment docker-compose file.
Now, when running
make devnet-uptwo additional containers will be started:blockscoutandpostgres. After few seconds, the explorer should be ready and can be accessed at:http://localhost:4000In the blockscout repository, the setup with the docker-compose file starts 9 containers. Those extra containers represent extra features, such as UML visualization of solidity classes, smart contract verification, statistics, ... It also splits the backend and the frontend and put a proxy in front. In the context of a dev environment, I took a lightweight approach to have the minimum needed for the task of displaying the blockchain transactions locally and removed everything that was not needed for this task.
suave-gethexposes 2 new fields for transactions, namelywrappedandconfidentialComputeResult, those 2 new fields are now exposed in the modified version of blockscout.📚 References
blockscoutforsuave-geth