Simon Warta

The tx hash is simply `sha256(txBytes)`, so you don't need to decode it at all in order to get the hash.

> Why has no one replied? GitHub is not a support channel and unfortunately there is no reliable support channel for CosmJS right now. Questions are answered depending on availablility...

This issue seems to be specific for that query. Which Cosmos SDK version are you using in your backend? What value do you get returned in `total` in the response?

Right now, CosmJS uses Wasm internally for crypto. We may migrate away from that at some point, but cannot easily do that short term. Did you see this? https://stackoverflow.com/questions/48523118/wasm-module-compile-error-in-chrome-extension

This is discussed here: https://bugs.chromium.org/p/chromium/issues/detail?id=1173354. I do not yet understand all the details and have no immediate solution.

Did you debug the content of `query` and `address`? The code looks correct.

Right now `makeMultisignedTx` hardcodes `SIGN_MODE_LEGACY_AMINO_JSON` for all signers. This is an implementation limitation that was used to get something working and it allows Ledger signing. In theory it would be...

> That should be enough to prove that our custom message works with **SIGN_MODE_LEGACY_AMINO_JSON** right? Unfortunately no. We have seen 2 examples in the wild where Amino JSON signing with...

No, the structure of that JSON is similar but not equal to the structure you need (see `makeSignDoc`/`StdSignDoc`). There is no shortcut.

@mikedotexe please note that ADR-036 is not finalized. The current state seems to be completely discareded. Nobody is owning the spec process right now. This is one of a million...