Context
The CLI today is light on read commands — most of its value lives in scaffolding. Adding chains list and chains show <chain> exposes registry data directly through the CLI, giving developers a quick way to look up chain metadata without leaving the terminal.
What to build
Two new commands:
w3-kit chains list — prints a table of all chains in the registry (name, chain ID, native currency).
w3-kit chains show <chain> — prints full metadata for a single chain (RPC URLs, block explorer, bridge addresses, gas oracle, etc.) accepting either chain name or chain ID.
Both should reuse the registry as the source of truth (no hardcoded data in the CLI).
Acceptance criteria
Pointers
- Related issue: cli
--json flag (will pair well with these commands)
- Related: registry chain data structure
Complexity
🟢 Good first issue
Context
The CLI today is light on read commands — most of its value lives in scaffolding. Adding
chains listandchains show <chain>exposes registry data directly through the CLI, giving developers a quick way to look up chain metadata without leaving the terminal.What to build
Two new commands:
w3-kit chains list— prints a table of all chains in the registry (name, chain ID, native currency).w3-kit chains show <chain>— prints full metadata for a single chain (RPC URLs, block explorer, bridge addresses, gas oracle, etc.) accepting either chain name or chain ID.Both should reuse the registry as the source of truth (no hardcoded data in the CLI).
Acceptance criteria
w3-kit chains listoutputs a clean table to stdoutw3-kit chains show <chain>accepts name or chain ID--helpoutputPointers
--jsonflag (will pair well with these commands)Complexity
🟢 Good first issue