Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

add network explorer #236

Closed
kremalicious opened this issue Mar 5, 2021 · 3 comments · May be fixed by #242
Closed

add network explorer #236

kremalicious opened this issue Mar 5, 2021 · 3 comments · May be fixed by #242
Assignees
@md00ux
Labels
Priority: Low Type: Enhancement New feature or request

Comments

@kremalicious
Copy link
Contributor

Is your feature request related to a problem? Please describe.
At the moment transactions happening within barge can only be inspected via scripts, or with externally running tools. When using the market to run against barge, it's often critical to see transactions by linking to some explorer.

Describe the solution you'd like
Find an open source explorer we can run as additional block in barge. This is then pointed against the local running ganache node & network.

Describe alternatives you've considered
We could give instructions on how to find transactions somehow in barge, or have instructions how to run an explorer outside of barge.

Additional context
With oceanprotocol/ocean.js#643, a new explorerUri config item already exists. Once we arrive at oceanprotocol/market#413 the question arises what to do with transactions links when using the market with barge.
@alexcos20
Copy link
Member

@md00ux - take a look at blockscout. it should work out of the box

@md00ux
Copy link
Contributor

md00ux commented Apr 6, 2021

barge feature/blockscout branch has Blockscout included.

@alexcos20 alexcos20 mentioned this issue Apr 13, 2021
Open
@trentmc
Copy link
Member

trentmc commented May 11, 2023

This issue is a "nice to have". It's two years old. Even though there's a solution, it seems not enough of a priority to bother to fix. So, closing.

@trentmc trentmc closed this as completed May 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@md00ux md00ux

Labels
Priority: Low Type: Enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Feature/blockscout oceanprotocol/barge
4 participants
@kremalicious @trentmc @alexcos20 @md00ux