Fully support this. At a minimum, I think controllers and wasm hash should be easily obtainable on chain.
Currently also, if we make the canister_status call, the error already includes half the information we need. This is obviously hacky and a workaround, as we’re doing string manipulation to extract principal ids from the error response, but still goes to show its silly to block that info or not provide it in another way
1 Like