-
Notifications
You must be signed in to change notification settings - Fork 0
Open
Description
Create a simple explorer with the following requirements:
- Should focus on
anvilnodes - When necessary, should rely on the
ots_*API endpoints (see reference), which provides listing capabilities that are not typically present in an RPC node - For layout decisions, we should mostly defer to what etherscan does, since that's the familiar layout to everyone already, and to avoid reinventing the wheel
- A top-level input should allow switching the RPC URL
- The current RPC-URL should be encoded as a route component in the URL (important to enable reverse proxies to connect only to specific instances)
- when possible, components from ethui/ethui or ethui/ui should be used or adapted. If the effort is too large, we can defer this to future work
Metadata
Metadata
Assignees
Labels
No labels