ic-query
ic-query provides the icq executable for read-only Internet Computer
metadata queries.
icq currently supports NNS and SNS metadata queries: registry version,
subnet catalog lookup, node/provider/operator/data-center inventory, topology
reports, and deployed SNS listings.
Install
From this checkout:
From crates.io after publication:
Commands
Use icq nns <family> help, icq nns topology <report> help, or
icq sns <command> help for command options.
Most commands support text output by default and JSON output with
--format json:
Cache
The NNS subnet, node, provider, operator, data-center, and topology commands
use project-local cache files under .icq/. Refresh commands fetch current
mainnet registry data and replace the matching cache atomically:
List/info commands populate their component cache on first use and print the API endpoint they are calling before creating it. Refresh commands force a fresh fetch and replace the matching cache.
Development
This repository pins the local toolchain to Rust 1.96.0 while declaring
Rust 1.91.0 as the crate MSRV.
The combined local gate is:
Release version bumps are available after the release contents are committed and the worktree is clean:
Each target runs make test, bumps Cargo.toml and Cargo.lock, validates the
package, commits the release version, and creates an annotated vX.Y.Z tag.
Integration
icq is a standalone metadata lookup tool. Orchestration, deployment, and
application repositories can call the CLI when they need IC metadata instead of
linking registry adapters directly. For one integration example, see
Canic.
Status
The command namespace is intentionally small:
nnsis implemented.sns list,sns info,sns token, andsns neuronsare implemented for deployed mainnet SNS instances.- Additional IC query families can be added without coupling query code to deployment tooling.