Simon Warta

Looking at the new title, I just want to make sure we are on the same page: - Salt is randomly generated, not configured at encryption time - It is...

> we will get `not an app specific` salt, but `encryption specific salt` Exactly. Better salting with no configuration. > and it should be a part of encrypted result It...

The steps are done as follows: 1. User provides password string, possibly low entropy 2. The KDF turns this string into a byte series using a hard to bruteforce algorithm...

> What do you think about to code that? Does't looks like I have a lot of time for that. So far I only see two tests. Without a (draft)...

Nice start, but no implementation in #906. I started working on this myself now. It's a bit tricky becasue of the API design that allows KDF execution on a different...

Hi @youngjoon-lee, which of those two use cases do you have? 1. Multiple signatures because you use multiple messages in one transaction (e.g. Alice sends to Bob and Bob sends...

> My use case is none of 1 or 2. Actually, my use case is similar as 1. I see. Yeah, I consider it a variant of 1. Multiple messsages...

Re-opening as the request is very valid. We can implement a solution that includes the use case described here but supports a multi-machine setup ad well. Many of the changes...

#854 implements the ability to use different sequences for different signers. While this is not enough to close this ticket, it is an important step that allows you to maintain...

> As far as I understand is BaseAccount type not supported [..] CosmJS only supports connecting to Tendermint RPC for all current backends. The clients from @cosmjs/stargate need to be...