Add blockchain explorer (blockscout) #47
Open
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-up
two additional containers will be started:blockscout
andpostgres
. After few seconds, the explorer should be ready and can be accessed at:http://localhost:4000
In 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-geth
exposes 2 new fields for transactions, namelywrapped
andconfidentialComputeResult
, those 2 new fields are now exposed in the modified version of blockscout.📚 References
blockscout
forsuave-geth