Simon Warta

Please see https://medium.com/confio/authz-and-ledger-signing-an-executive-summary-8754a0dc2a88 for a high level overview of the current limitation. (Props for the work here by the way!)

I hear rumors of 1-2 months, but I'm not involved in Cosmos SDK development. Certainly this summer.

Which message types exactly do you need? This issue was pulled out and is still open: https://github.com/cosmos/cosmjs/issues/1092 Which networks migrated to 0.46 already?

CosmWasm team would heavily appreciate this. Once you have one, please register at https://github.com/CosmWasm/advisories#notification-list via PR.

I don't care much about the `m/`. I think it is good to display but not critical. The main problem is `44` vs. `44'` and `118` vs. `118'`. Those are...

By the way, CosmJS can do this for you: ```ts import { pathToString, Slip10RawIndex } from "@cosmjs/crypto"; const path = [ Slip10RawIndex.hardened(44), Slip10RawIndex.hardened(118), Slip10RawIndex.hardened(0), Slip10RawIndex.normal(0), Slip10RawIndex.normal(6), ]; console.log(pathToString(path)); // m/44'/118'/0'/0/6...

> I suppose we should split out something like a rand feature from the std feature that toggles on rand_core/std at the very least. What is important for me here...

> If you have any suggestions regarding what we can do in order to properly activate RNG features for WASM users, that would be helpful. I'll think about what that...

> I would argue that it's the Rust handling of the `wasm32-unknown-unknown` target is at fault here. It never should've been an `std` target. Good question: Is std and entropy...

> Also I would argue that instead of relying on user-written JS code to pass entropy to WASM you should prefer using `getrandom` either way (unless you bother with wrapping...