Commits on Apr 18, 2019

1. Implement chain-specific keyrings (closes #231, #111) …

   Moves from a single global keyring to chain-specific keyrings, where
   keys/signers can be potentially shared across chains if desired.
   
   This enables true multitenancy for supporting multiple chains with a
   single KMS instance, and reloves lingering questions around the access
   control model, namely that each connection has an associated chain ID,
   and signing operations are isolated to that chain's keyring.

   

   tony-iqlusion committed Apr 18, 2019
   Copy the full SHA

   3f80083 View commit details

   Browse the repository at this point in the history