You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be handy for devs to be able to retrieve the wasm hash of a contract.
What would you like to see?
$ stellar contract info wasm-hash --network testnet --contract-id CDSJWGUPY2HFHYNLT3EZX7YGJ4X7YMWPQWHHGNKB6IVH6WRXAJFI7627
283f8e42a3585aa3a511c06c7d09a94d66762773cdf493cc4afc455d7b68adcf
What alternatives are there?
There are some other ways to get the Wasm hash that a contract ID is deployed with.
Using RPC + XDR
The RPC and any XDR decode can be used to manually retrieve the details, however this is not convenient for a developer needing the value at the command line. For example:
I'm pretty sure there are some commands in the cli where the wasm hash is outputted when retrieving the wasm for other purposes. I can't remember which one it is at the moment, but these commands exist for other purposes an the hash is only outputted in informational stderr logs, which is not accessible for scripting.
The text was updated successfully, but these errors were encountered:
Good point. wasm-hash would remove the most ambiguity and be consistent with option names --wasm-hash that are littered throughout the cli. I've updated the title to match.
What problem does your feature solve?
It would be handy for devs to be able to retrieve the wasm hash of a contract.
What would you like to see?
What alternatives are there?
There are some other ways to get the Wasm hash that a contract ID is deployed with.
Using RPC + XDR
The RPC and any XDR decode can be used to manually retrieve the details, however this is not convenient for a developer needing the value at the command line. For example:
Using log output
I'm pretty sure there are some commands in the cli where the wasm hash is outputted when retrieving the wasm for other purposes. I can't remember which one it is at the moment, but these commands exist for other purposes an the hash is only outputted in informational stderr logs, which is not accessible for scripting.
The text was updated successfully, but these errors were encountered: