2 Commits (ced19e7efeb177d1543e8188ebf87762adddb902)

Author	SHA1	Message	Date
Asa Oines	e8d90775f7	Add Aggregation ISM (#1737) ... ### Description This PR introduces the Aggregation ISM, which requires interchain messages to be verified by an m-of-n ISM set. This PR also introduces a new MultisigISM, which does not make use of the "commitment" optimization in its metadata. The previous MultisigISM has been moved to LegacyMultisigISM. Both AggregationISM and MultisigISM have abstract contracts that require `valuesAndThreshold` implementations. This PR implements versions with static m-of-n sets, using the EIP-3448 MetaProxy standard. These implementations are intended to be combined with a future RoutingISM implementation to replace LegacyMultisigISM. ### Drive-by changes - genhtml in solidity code coverage ### Related issues - Fixes #1522 ### Backward compatibility _Are these changes backward compatible?_ Yes ### Testing _What kind of testing have these changes undergone? Unit Tests	2 years ago
Asa Oines	7f5d50ee9c	Interoperable Interchain Accounts (#1832) ... ### Description This PR introduces a version of Interchain Accounts that is fully interoperable with any compatible contract deployed on a remote chain. Rather than follow the previous `Router` pattern in which destination contracts were hard coded by the deployer, this version allows the user to optionally specify which destination contract should receive the interchain account message. In order to make this secure, interchain accounts are additionally name spaced by ISM and origin router. **Note that this is not feature-complete until paired with a RoutingISM that switches based on the ISM included in the message** ### Drive-by changes - Creates the `IRouter` and `IHyperlaneConnectionClient` interfaces - Moves middleware interfaces into their own directory - Moves middleware libs into their own directory - Changes `InterchainCallMessage` -> `InterchainQueryMessage` now that it's unused by anything else ### Related issues - Fixes #1747 - Fixes #1969 ### Backward compatibility _Are these changes backward compatible?_ No _Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling?_ None ### Testing _What kind of testing have these changes undergone?_ Unit Tests	2 years ago
Yorke Rhodes	af52ae9823	Remove unused commitment fn (#1511)	2 years ago
Asa Oines	4fc474ed55	Smaller MultisigMetadata (#1394)	2 years ago
Asa Oines	41493f5cc2	Add Multisig ISM (#1193)	2 years ago