Tony Arcieri

Nice, that looks quite promising! So, would it be helpful to have a stateful `Cipher` object which could be reused for the legacy modes, but is only one-shot for the...

Yeah, it would probably involve `Cipher` creating stateful `Encryptor`/`Decryptor` objects which are themselves enums over the various possible modes

Yes, I'll be doing an overhaul of how keys are loaded in #388, and can look at supporting multiple softsign keys as part of that.

Note that when I start working on #60, one of the things I wanted to do was change those key IDs to be a [tendermint::chain::Id](https://docs.rs/tendermint/0.2.0/tendermint/chain/id/struct.Id.html), or potentially a list of...

Yeah, we should definitely support hot config reloads. Feel free to open an issue. I'd also be +1 for including some identifier for the public key in each config entry.

@jleni FWIW, the KMS already implements option 1, and the `yubihsm` crate internally handles reconnecting ala option 2, namely the signing operation in Signatory will attempt to (re)connect to the...

My personal preference for Rust testing (not sure how it fits into this workflow) is to test on the minimum supported Rust version (i.e. for KMS), along with the latest...

I think if you can set up some sort of timer to go off every 6 weeks, that should be fairly close.

Regarding building Cosmos SDK-compatible transactions from Rust, it looks like the [`deep_space` crate](https://github.com/althea-net/deep_space) is capable of this, but is a bit rough around the edges.

@jleni would it be possible to compose and upload some sort of ACL which can be displayed on the device, confirmed, and then stored to enable subsequent "sign without confirmation"...