Inspect Sigil from your terminal.
The source workspace includes sigil-cli. Use explicit endpoints and chain IDs, and begin with read-only node and query commands.
Run from a Sigil source checkout
With a Rust toolchain and the workspace dependencies installed, run the CLI from the Sigil repository root. This builds the local CLI; it does not install an unverified remote binary.
cargo run --manifest-path node/Cargo.toml -p sigil-cli --bin sigil-cli -- --helpRead node identity
The node info command calls sigil_getNodeInfo. Pass --rpc-url explicitly because the CLI default targets localhost.
cargo run --manifest-path node/Cargo.toml -p sigil-cli --bin sigil-cli -- \
--rpc-url 'https://rpc.sigil.ml/rpc' \
--chain-id 'sigil-mainnet-1' node infoRead-only commands
Use the same global endpoint and chain-ID flags with these subcommands. Replace DID and hash placeholders with records from the selected network.
| Item | Details |
|---|---|
| node info | Node version and chain identity. |
| node peers | Node peer information. |
| status | Synchronization status. |
| query block | Latest block window. |
| query block --height 1 | A block at an explicit height. |
| query balance <DID> | Balance and nonce for an account. |
| query tx <HASH> | A transaction by hash. |
Before transaction commands
A command appearing in --help is not a guarantee that the selected network enables its transaction path. Check the matching specification, network policy, signer, nonce, and fee first. Keep private signing material out of command history and logs.
Track the interface, then the release.
A dated documentation record. Network deployment and software release status should be checked independently.
Small examples. Real requests.
Copy a client, inspect a block, and verify a receipt. Each example reads public state without signing or submitting a transaction.