3 Commits (8127fa5aac5e1e74f4bf9b7633dd2a5c46362d15)

Author	SHA1	Message	Date
Asa Oines	f8d645e580	Add RoutingIsm (#1985) ... ### Description This PR adds `IRoutingIsm` and three implementations: - AbstractRoutingIsm, which folks building RoutingIsms can inherit from - DomainRoutingIsm, which routes based on message origin - InterchainAccountIsm, which routes based on the ISM in the InterchainAccountMessage ### Drive-by changes - Some related testing changes ### Related issues - Fixes #1521 ### Backward compatibility _Are these changes backward compatible?_ Yes _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
Asa Oines	f5a74006ec	Add non-struct API for IQS and ICA middlewares (#1989) ... ### Description This PR adds functions to the ICA and IQS middlewares that do not take complex types. These simpler interfaces lower the barrier to entry for users, especially for those using tooling that does not support structs well (e.g. etherscan, tally) ### Drive-by changes - Rename destinationDomain -> destination - Remove messageId from InterchainCallDispatched, rename to RemoteCallDispatched ### Related issues None ### Backward compatibility _Are these changes backward compatible?_ Yes _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
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