What

Add a new stellar contract info hash subcommand that outputs the SHA-256 hash of a contract's Wasm. The source can be a local .wasm file or a deployed contract ID/alias on a network. The two flags are mutually exclusive:

stellar contract info hash --wasm path/to/file.wasm
stellar contract info hash --id CDSJWGUPY...
stellar contract info hash --id my-alias --network testnet

The hash is printed as a hex string to stdout so it can be captured into shell variables.

$ stellar contract info hash --wasm target/wasm32v1-none/release/auth.wasm
6e5ca0a5beee928ce7796abd4daa35c00d01eca176a295e53b4995831db95eb2

$ stellar contract info hash --id auth
6e5ca0a5beee928ce7796abd4daa35c00d01eca176a295e53b4995831db95eb2

$ stellar contract info hash --id $(stellar contract alias show auth 2> /dev/null)
6e5ca0a5beee928ce7796abd4daa35c00d01eca176a295e53b4995831db95eb2

$ stellar contract info hash --id $(stellar contract id asset --asset native)
❌ error: cannot fetch wasm for contract because the contract is a network built-in asset contract that does not have a downloadable code binary

Why

Closes #1877. Retrieving the Wasm hash of a deployed contract previously required either chaining curl, jq, and stellar xdr decode, or scraping informational stderr logs from unrelated commands — neither convenient for scripting.

For the --id path the implementation reads ContractExecutable::Wasm(hash) directly from the contract instance ledger entry rather than downloading the full Wasm blob, so it's a single RPC round trip with a small payload.

Known limitations

A Stellar Asset Contract has no Wasm and therefore no hash; using --id against a SAC errors out.