From 972d1f37dc9b2667ab62a2036dbba4b9679ebd61 Mon Sep 17 00:00:00 2001 From: Asa Oines Date: Thu, 20 Jul 2023 20:10:47 +0000 Subject: [PATCH] GITBOOK-242: Fix URLs --- SUMMARY.md | 4 +- apis-and-sdks/hooks/README.md | 4 +- protocol/sovereign-consensus/README.md | 2 +- .../sovereign-consensus/aggregation-ism-1.md | 54 --------------- .../sovereign-consensus/aggregation-ism.md | 44 +++++++----- protocol/sovereign-consensus/routing-ism.md | 46 +++++++++++++ protocol/sovereign-consensus/wormhole-ism.md | 2 +- resources/addresses.md | 67 ++++++++----------- resources/glossary.md | 2 +- 9 files changed, 106 insertions(+), 119 deletions(-) delete mode 100644 protocol/sovereign-consensus/aggregation-ism-1.md create mode 100644 protocol/sovereign-consensus/routing-ism.md diff --git a/SUMMARY.md b/SUMMARY.md index 3e11497..f59455a 100644 --- a/SUMMARY.md +++ b/SUMMARY.md @@ -72,8 +72,8 @@ * [Interchain security modules](protocol/sovereign-consensus/README.md) * [Interface](protocol/sovereign-consensus/interchain-security-modules.md) * [Multisig ISM](protocol/sovereign-consensus/multisig-ism.md) - * [Routing ISM](protocol/sovereign-consensus/aggregation-ism.md) - * [Aggregation ISM](protocol/sovereign-consensus/aggregation-ism-1.md) + * [Routing ISM](protocol/sovereign-consensus/routing-ism.md) + * [Aggregation ISM](protocol/sovereign-consensus/aggregation-ism.md) * [Optimistic ISM](protocol/sovereign-consensus/optimistic-ism.md) * [Wormhole ISM](protocol/sovereign-consensus/wormhole-ism.md) * [Hook ISM](protocol/sovereign-consensus/hook-ism.md) diff --git a/apis-and-sdks/hooks/README.md b/apis-and-sdks/hooks/README.md index 2198cfa..745601e 100644 --- a/apis-and-sdks/hooks/README.md +++ b/apis-and-sdks/hooks/README.md @@ -8,7 +8,7 @@ description: Use native or third-party bridges as "hooks" for your dispatch call Developers can use the Hooks API to secure their messages either through native bridges like for Optimism or use other third-party bridge vendors. -There are cases where you may feel the MultisigISM or your own configured ISM security isn't sufficient for your application and instead you want the security of a native bridge like Optimism or a third-party vendor like Wormhole. You can opt-in to such do so with hooks without leaving the purview of the Mailbox interface and needing a bridge-specific implementation. Hooks can also be used as routes specified for the [aggregation-ism-1.md](../../protocol/sovereign-consensus/aggregation-ism-1.md "mention"). +There are cases where you may feel the MultisigISM or your own configured ISM security isn't sufficient for your application and instead you want the security of a native bridge like Optimism or a third-party vendor like Wormhole. You can opt-in to such do so with hooks without leaving the purview of the Mailbox interface and needing a bridge-specific implementation. Hooks can also be used as routes specified for the [aggregation-ism.md](../../protocol/sovereign-consensus/aggregation-ism.md "mention"). Hooks come in a pair of contracts, the `IMessageHook` on the source chain and `HookISM` on the destination chain. `IMessageHook` provides you the `postDispatch` method which you can call after `IMailbox.dispatch` providing the destination domain and the messageId. You pass on the `messageId` as payload to configured external provider (defined by the hook) which interacts with the corresponding `HookISM` contract on the destination chain. If the ISM can verify the validity of the messageId, the message can be delivered successfully by the relayer. @@ -161,7 +161,7 @@ All ERC-5164 compatible bridge vendors have to implement contracts `IMessageDisp The `ERC-5164` hook calls the dispatchMessage function on the `IMessageDispatcher` which send messages to IMessageExecutor at the specified toChainId. The executor contract has the special access to write to the `ERC5164ISM` contract, setting the messageId in the `verifiedMessageId`'s mapping to the original source chain sender (ie. the user). The relayer carries just the message with no metadata, waiting for the bridge provider to prove the validity and transport the message to the destination chain and the message delivery is then verified. -This open interface allows any third party bridge provider like Wormhole or Telepathy to implement the interface and be supported by the ERC5164Hook out-of-the-box. This is especially useful if you want the reliability and security of a diverse set of bridge vendors by using the [aggregation-ism-1.md](../../protocol/sovereign-consensus/aggregation-ism-1.md "mention"). +This open interface allows any third party bridge provider like Wormhole or Telepathy to implement the interface and be supported by the ERC5164Hook out-of-the-box. This is especially useful if you want the reliability and security of a diverse set of bridge vendors by using the [aggregation-ism.md](../../protocol/sovereign-consensus/aggregation-ism.md "mention"). ```mermaid %%{ init: { diff --git a/protocol/sovereign-consensus/README.md b/protocol/sovereign-consensus/README.md index 57da69d..98987e1 100644 --- a/protocol/sovereign-consensus/README.md +++ b/protocol/sovereign-consensus/README.md @@ -18,7 +18,7 @@ For example, application developers that want increased sovereignty over interch ISMs act as "security [legos](https://en.wikipedia.org/wiki/Lego)". Developers can mix and match different ISMs together to encode a security model that best fits their needs. -For example, application developers that want additional security could deploy an [aggregation-ism-1.md](aggregation-ism-1.md "mention") that requires verification by both a [multisig-ism.md](multisig-ism.md "mention") configured with validators from the Hyperlane community, **and** a [wormhole-ism.md](wormhole-ism.md "mention") that verifies that a quorum of the [Wormhole](https://wormhole.com/) validator set verified the message. +For example, application developers that want additional security could deploy an [aggregation-ism.md](aggregation-ism.md "mention") that requires verification by both a [multisig-ism.md](multisig-ism.md "mention") configured with validators from the Hyperlane community, **and** a [wormhole-ism.md](wormhole-ism.md "mention") that verifies that a quorum of the [Wormhole](https://wormhole.com/) validator set verified the message. ### Customize diff --git a/protocol/sovereign-consensus/aggregation-ism-1.md b/protocol/sovereign-consensus/aggregation-ism-1.md deleted file mode 100644 index 8e995bb..0000000 --- a/protocol/sovereign-consensus/aggregation-ism-1.md +++ /dev/null @@ -1,54 +0,0 @@ ---- -description: Aggregate security from multiple ISMs ---- - -# Aggregation ISM - -Developers can use an `AggregationISM` to combine security from multiple ISMs. Simply put, an `AggregationISM` requires that `m` of `n` ISMs verify a particular interchain message. - -## Interface - -`AggregationISMs` must implement the `IAggregationIsm` interface. - -```solidity -// SPDX-License-Identifier: MIT OR Apache-2.0 -pragma solidity >=0.6.11; - -import {IInterchainSecurityModule} from "../IInterchainSecurityModule.sol"; - -interface IAggregationIsm is IInterchainSecurityModule { - /** - * @notice Returns the set of modules responsible for verifying _message - * and the number of modules that must verify - * @dev Can change based on the content of _message - * @param _message Hyperlane formatted interchain message - * @return modules The array of ISM addresses - * @return threshold The number of modules needed to verify - */ - function modulesAndThreshold(bytes calldata _message) - external - view - returns (address[] memory modules, uint8 threshold); -} - -``` - -## Configure - -The hyperlane-monorepo contains an `AggregationISM` implementation that application developers can deploy off-the-shelf, specifying their desired configuration. - -Developers can configure, for each origin chain, a set of `n` ISMs, and the number of ISMs needed to verify a message. - -`AggregationISMs` can aggregate the security of any ISMs. For example, users can deploy a [multisig-ism.md](multisig-ism.md "mention") with their own validator set, and deploy an `AggregationISM` that aggregates that ISM with the Hyperlane default ISM. - -The [hyperlane-deploy repo](https://github.com/hyperlane-xyz/hyperlane-deploy) contains the tooling and instructions needed to deploy and configure an `AggregationISM`. - -## Customize - -The hyperlane-monorepo contains an abstract `AggregationISM` implementation that application developers can fork. - -Developers simply need to implement the `modulesAndThreshold()` function. - -By creating a custom implementation, application developers can tailor the security provided by a `AggregationISM` to the needs of their application. - -For example, a custom implementation could require that low value messages be verified by a [multisig-ism.md](multisig-ism.md "mention"), and require that high value messages _also_ be verified by a [wormhole-ism.md](wormhole-ism.md "mention"). diff --git a/protocol/sovereign-consensus/aggregation-ism.md b/protocol/sovereign-consensus/aggregation-ism.md index f9f64b0..8e995bb 100644 --- a/protocol/sovereign-consensus/aggregation-ism.md +++ b/protocol/sovereign-consensus/aggregation-ism.md @@ -1,46 +1,54 @@ --- -description: Smarter interchain security models +description: Aggregate security from multiple ISMs --- -# Routing ISM +# Aggregation ISM -Developers can use a `RoutingISM` to delegate message verification to a different ISM. This allows developers to change security models based on message content or application context. +Developers can use an `AggregationISM` to combine security from multiple ISMs. Simply put, an `AggregationISM` requires that `m` of `n` ISMs verify a particular interchain message. ## Interface -`RoutingISMs` must implement the `IRoutingIsm` interface. +`AggregationISMs` must implement the `IAggregationIsm` interface. ```solidity -interface IRoutingIsm is IInterchainSecurityModule { +// SPDX-License-Identifier: MIT OR Apache-2.0 +pragma solidity >=0.6.11; + +import {IInterchainSecurityModule} from "../IInterchainSecurityModule.sol"; + +interface IAggregationIsm is IInterchainSecurityModule { /** - * @notice Returns the ISM responsible for verifying _message + * @notice Returns the set of modules responsible for verifying _message + * and the number of modules that must verify * @dev Can change based on the content of _message - * @param _message Formatted Hyperlane message (see Message.sol). - * @return module The ISM to use to verify _message + * @param _message Hyperlane formatted interchain message + * @return modules The array of ISM addresses + * @return threshold The number of modules needed to verify */ - function route(bytes calldata _message) + function modulesAndThreshold(bytes calldata _message) external view - returns (IInterchainSecurityModule); + returns (address[] memory modules, uint8 threshold); } + ``` ## Configure -The hyperlane-monorepo contains a `RoutingISM` implementation, `DomainRoutingIsm`, that application developers can deploy off-the-shelf, specifying their desired configuration. +The hyperlane-monorepo contains an `AggregationISM` implementation that application developers can deploy off-the-shelf, specifying their desired configuration. -This ISM simply switches security models depending on the origin chain of the message. A simple use case for this is to use different [multisig-ism.md](multisig-ism.md "mention") validator sets for each chain. +Developers can configure, for each origin chain, a set of `n` ISMs, and the number of ISMs needed to verify a message. -Eventually, you could imagine a `DomainRoutingIsm` routing to different light-client-based ISMs, depending on the type of consensus protocol used on the origin chain. +`AggregationISMs` can aggregate the security of any ISMs. For example, users can deploy a [multisig-ism.md](multisig-ism.md "mention") with their own validator set, and deploy an `AggregationISM` that aggregates that ISM with the Hyperlane default ISM. -The [hyperlane-deploy repo](https://github.com/hyperlane-xyz/hyperlane-deploy) contains the tooling and instructions needed to deploy and configure a `DomainRoutingIsm`. +The [hyperlane-deploy repo](https://github.com/hyperlane-xyz/hyperlane-deploy) contains the tooling and instructions needed to deploy and configure an `AggregationISM`. ## Customize -The hyperlane-monorepo contains an abstract `RoutingISM` implementation that application developers can fork. +The hyperlane-monorepo contains an abstract `AggregationISM` implementation that application developers can fork. -Developers simply need to implement the `route()` function. +Developers simply need to implement the `modulesAndThreshold()` function. -By creating a custom implementation, application developers can tailor the security provided by a `RoutingISM` to the needs of their application. +By creating a custom implementation, application developers can tailor the security provided by a `AggregationISM` to the needs of their application. -For example, a custom implementation could change security models based on the contents of the message or the state of the application receiving the message. +For example, a custom implementation could require that low value messages be verified by a [multisig-ism.md](multisig-ism.md "mention"), and require that high value messages _also_ be verified by a [wormhole-ism.md](wormhole-ism.md "mention"). diff --git a/protocol/sovereign-consensus/routing-ism.md b/protocol/sovereign-consensus/routing-ism.md new file mode 100644 index 0000000..f9f64b0 --- /dev/null +++ b/protocol/sovereign-consensus/routing-ism.md @@ -0,0 +1,46 @@ +--- +description: Smarter interchain security models +--- + +# Routing ISM + +Developers can use a `RoutingISM` to delegate message verification to a different ISM. This allows developers to change security models based on message content or application context. + +## Interface + +`RoutingISMs` must implement the `IRoutingIsm` interface. + +```solidity +interface IRoutingIsm is IInterchainSecurityModule { + /** + * @notice Returns the ISM responsible for verifying _message + * @dev Can change based on the content of _message + * @param _message Formatted Hyperlane message (see Message.sol). + * @return module The ISM to use to verify _message + */ + function route(bytes calldata _message) + external + view + returns (IInterchainSecurityModule); +} +``` + +## Configure + +The hyperlane-monorepo contains a `RoutingISM` implementation, `DomainRoutingIsm`, that application developers can deploy off-the-shelf, specifying their desired configuration. + +This ISM simply switches security models depending on the origin chain of the message. A simple use case for this is to use different [multisig-ism.md](multisig-ism.md "mention") validator sets for each chain. + +Eventually, you could imagine a `DomainRoutingIsm` routing to different light-client-based ISMs, depending on the type of consensus protocol used on the origin chain. + +The [hyperlane-deploy repo](https://github.com/hyperlane-xyz/hyperlane-deploy) contains the tooling and instructions needed to deploy and configure a `DomainRoutingIsm`. + +## Customize + +The hyperlane-monorepo contains an abstract `RoutingISM` implementation that application developers can fork. + +Developers simply need to implement the `route()` function. + +By creating a custom implementation, application developers can tailor the security provided by a `RoutingISM` to the needs of their application. + +For example, a custom implementation could change security models based on the contents of the message or the state of the application receiving the message. diff --git a/protocol/sovereign-consensus/wormhole-ism.md b/protocol/sovereign-consensus/wormhole-ism.md index b80ef60..aaedcc4 100644 --- a/protocol/sovereign-consensus/wormhole-ism.md +++ b/protocol/sovereign-consensus/wormhole-ism.md @@ -14,4 +14,4 @@ This ISM requires that 13 of the 19 [Wormhole guardians](https://wormhole.com/ne ## Compose -Developers can compose a Wormhole ISM with a [multisig-ism.md](multisig-ism.md "mention")using an [aggregation-ism-1.md](aggregation-ism-1.md "mention") to require that m of n Hyperlane validators **and** 13-of-19 Wormhole guardians verify a message. +Developers can compose a Wormhole ISM with a [multisig-ism.md](multisig-ism.md "mention")using an [aggregation-ism.md](aggregation-ism.md "mention") to require that m of n Hyperlane validators **and** 13-of-19 Wormhole guardians verify a message. diff --git a/resources/addresses.md b/resources/addresses.md index cebadb7..8f63f39 100644 --- a/resources/addresses.md +++ b/resources/addresses.md @@ -1,14 +1,14 @@ -duplicate definition - NotCrossChainCall() ---- -description: Hyperlane core contract addresses ---- - # Contract addresses -{% tabs %} +### duplicate definition - NotCrossChainCall() + +### description: Hyperlane core contract addresses + +## Contract addresses +{% tabs %} {% tab title="Mainnet" %} -### Mailbox +#### Mailbox | Network | Address | Explorer | | --------- | -------------------------------------------- | --------------------------------------------------------------------------------------------------------------------- | @@ -22,10 +22,10 @@ description: Hyperlane core contract addresses | Moonbeam | `0x35231d4c2D8B8ADcB5617A638A0c4548684c7C70` | [View on moonscan.io](https://moonscan.io/address/0x35231d4c2D8B8ADcB5617A638A0c4548684c7C70) | | Gnosis | `0x35231d4c2D8B8ADcB5617A638A0c4548684c7C70` | [View on gnosisscan.io](https://gnosisscan.io/address/0x35231d4c2D8B8ADcB5617A638A0c4548684c7C70) | - -### DefaultIsmInterchainGasPaymaster +#### DefaultIsmInterchainGasPaymaster Read about this [here](../build-with-hyperlane/guides/developers/paying-for-interchain-gas/which-igp-to-use-and-understanding-gas-amounts.md#when-using-the-default-ism-for-most-applications) + | Network | Address | Explorer | | --------- | -------------------------------------------- | --------------------------------------------------------------------------------------------------------------------- | | Celo | `0x56f52c0A1ddcD557285f7CBc782D3d83096CE1Cc` | [View on celoscan.io](https://celoscan.io/address/0x56f52c0A1ddcD557285f7CBc782D3d83096CE1Cc) | @@ -38,10 +38,10 @@ Read about this [here](../build-with-hyperlane/guides/developers/paying-for-inte | Moonbeam | `0x56f52c0A1ddcD557285f7CBc782D3d83096CE1Cc` | [View on moonscan.io](https://moonscan.io/address/0x56f52c0A1ddcD557285f7CBc782D3d83096CE1Cc) | | Gnosis | `0x56f52c0A1ddcD557285f7CBc782D3d83096CE1Cc` | [View on gnosisscan.io](https://gnosisscan.io/address/0x56f52c0A1ddcD557285f7CBc782D3d83096CE1Cc) | - -### InterchainGasPaymaster +#### InterchainGasPaymaster Advanced use - [read here](../build-with-hyperlane/guides/developers/paying-for-interchain-gas/which-igp-to-use-and-understanding-gas-amounts.md#when-using-a-custom-ism-advanced) + | Network | Address | Explorer | | --------- | -------------------------------------------- | --------------------------------------------------------------------------------------------------------------------- | | Celo | `0x6cA0B6D22da47f091B7613223cD4BB03a2d77918` | [View on celoscan.io](https://celoscan.io/address/0x6cA0B6D22da47f091B7613223cD4BB03a2d77918) | @@ -54,8 +54,7 @@ Advanced use - [read here](../build-with-hyperlane/guides/developers/paying-for- | Moonbeam | `0x6cA0B6D22da47f091B7613223cD4BB03a2d77918` | [View on moonscan.io](https://moonscan.io/address/0x6cA0B6D22da47f091B7613223cD4BB03a2d77918) | | Gnosis | `0x6cA0B6D22da47f091B7613223cD4BB03a2d77918` | [View on gnosisscan.io](https://gnosisscan.io/address/0x6cA0B6D22da47f091B7613223cD4BB03a2d77918) | - -### MultisigIsm +#### MultisigIsm | Network | Address | Explorer | | --------- | -------------------------------------------- | --------------------------------------------------------------------------------------------------------------------- | @@ -69,8 +68,7 @@ Advanced use - [read here](../build-with-hyperlane/guides/developers/paying-for- | Moonbeam | `0xf3b1F415740A26568C45b1c771A737E31C198F09` | [View on moonscan.io](https://moonscan.io/address/0xf3b1F415740A26568C45b1c771A737E31C198F09) | | Gnosis | `0xC343A7054838FE9F249D7E3Ec1Fa6f1D108694b8` | [View on gnosisscan.io](https://gnosisscan.io/address/0xC343A7054838FE9F249D7E3Ec1Fa6f1D108694b8) | - -### InterchainQueryRouter +#### InterchainQueryRouter | Network | Address | Explorer | | --------- | -------------------------------------------- | --------------------------------------------------------------------------------------------------------------------- | @@ -84,8 +82,7 @@ Advanced use - [read here](../build-with-hyperlane/guides/developers/paying-for- | Moonbeam | `0xf1CFA9D0d4191441b1D121144f4027e63bbAE591` | [View on moonscan.io](https://moonscan.io/address/0xf1CFA9D0d4191441b1D121144f4027e63bbAE591) | | Gnosis | `0xA376b27212D608324808923Add679A2c9FAFe9Da` | [View on gnosisscan.io](https://gnosisscan.io/address/0xA376b27212D608324808923Add679A2c9FAFe9Da) | - -### InterchainAccountRouter +#### InterchainAccountRouter | Network | Address | Explorer | | --------- | -------------------------------------------- | --------------------------------------------------------------------------------------------------------------------- | @@ -99,8 +96,7 @@ Advanced use - [read here](../build-with-hyperlane/guides/developers/paying-for- | Moonbeam | `0xE50DEa401eD22aBc75559d411b9cfF819c324D3b` | [View on moonscan.io](https://moonscan.io/address/0xE50DEa401eD22aBc75559d411b9cfF819c324D3b) | | Gnosis | `0xe9E3444DDD80c50276c0Fcf316026f6d7fEc2c47` | [View on gnosisscan.io](https://gnosisscan.io/address/0xe9E3444DDD80c50276c0Fcf316026f6d7fEc2c47) | - -### ValidatorAnnounce +#### ValidatorAnnounce | Network | Address | Explorer | | --------- | -------------------------------------------- | --------------------------------------------------------------------------------------------------------------------- | @@ -114,18 +110,16 @@ Advanced use - [read here](../build-with-hyperlane/guides/developers/paying-for- | Moonbeam | `0x9bBdef63594D5FFc2f370Fe52115DdFFe97Bc524` | [View on moonscan.io](https://moonscan.io/address/0x9bBdef63594D5FFc2f370Fe52115DdFFe97Bc524) | | Gnosis | `0x9bBdef63594D5FFc2f370Fe52115DdFFe97Bc524` | [View on gnosisscan.io](https://gnosisscan.io/address/0x9bBdef63594D5FFc2f370Fe52115DdFFe97Bc524) | - -### LiquidityLayer +#### LiquidityLayer | Network | Address | Explorer | | --------- | -------------------------------------------- | ----------------------------------------------------------------------------------------------- | | Ethereum | `0x9954A0d5C9ac7e4a3687f9B08c0FF272f9d0dc71` | [View on etherscan.io](https://etherscan.io/address/0x9954A0d5C9ac7e4a3687f9B08c0FF272f9d0dc71) | | Avalanche | `0xEff8C988b9F9f606059c436F5C1Cc431571C8B03` | [View on snowtrace.io](https://snowtrace.io/address/0xEff8C988b9F9f606059c436F5C1Cc431571C8B03) | - - {% endtab %} + {% tab title="Testnet" %} -### Mailbox +#### Mailbox | Network | Address | Explorer | | -------------- | -------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------- | @@ -139,10 +133,10 @@ Advanced use - [read here](../build-with-hyperlane/guides/developers/paying-for- | Arbitrumgoerli | `0xCC737a94FecaeC165AbCf12dED095BB13F037685` | [View on goerli.arbiscan.io](https://goerli.arbiscan.io/address/0xCC737a94FecaeC165AbCf12dED095BB13F037685) | | Sepolia | `0xCC737a94FecaeC165AbCf12dED095BB13F037685` | [View on sepolia.etherscan.io](https://sepolia.etherscan.io/address/0xCC737a94FecaeC165AbCf12dED095BB13F037685) | - -### DefaultIsmInterchainGasPaymaster +#### DefaultIsmInterchainGasPaymaster Read about this [here](../build-with-hyperlane/guides/developers/paying-for-interchain-gas/which-igp-to-use-and-understanding-gas-amounts.md#when-using-the-default-ism-for-most-applications) + | Network | Address | Explorer | | -------------- | -------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------- | | Alfajores | `0xF90cB82a76492614D07B82a7658917f3aC811Ac1` | [View on alfajores.celoscan.io](https://alfajores.celoscan.io/address/0xF90cB82a76492614D07B82a7658917f3aC811Ac1) | @@ -155,10 +149,10 @@ Read about this [here](../build-with-hyperlane/guides/developers/paying-for-inte | Arbitrumgoerli | `0xF90cB82a76492614D07B82a7658917f3aC811Ac1` | [View on goerli.arbiscan.io](https://goerli.arbiscan.io/address/0xF90cB82a76492614D07B82a7658917f3aC811Ac1) | | Sepolia | `0xF987d7edcb5890cB321437d8145E3D51131298b6` | [View on sepolia.etherscan.io](https://sepolia.etherscan.io/address/0xF987d7edcb5890cB321437d8145E3D51131298b6) | - -### InterchainGasPaymaster +#### InterchainGasPaymaster Advanced use - [read here](../build-with-hyperlane/guides/developers/paying-for-interchain-gas/which-igp-to-use-and-understanding-gas-amounts.md#when-using-a-custom-ism-advanced) + | Network | Address | Explorer | | -------------- | -------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------- | | Alfajores | `0x8f9C3888bFC8a5B25AED115A82eCbb788b196d2a` | [View on alfajores.celoscan.io](https://alfajores.celoscan.io/address/0x8f9C3888bFC8a5B25AED115A82eCbb788b196d2a) | @@ -171,8 +165,7 @@ Advanced use - [read here](../build-with-hyperlane/guides/developers/paying-for- | Arbitrumgoerli | `0x8f9C3888bFC8a5B25AED115A82eCbb788b196d2a` | [View on goerli.arbiscan.io](https://goerli.arbiscan.io/address/0x8f9C3888bFC8a5B25AED115A82eCbb788b196d2a) | | Sepolia | `0x8f9C3888bFC8a5B25AED115A82eCbb788b196d2a` | [View on sepolia.etherscan.io](https://sepolia.etherscan.io/address/0x8f9C3888bFC8a5B25AED115A82eCbb788b196d2a) | - -### MultisigIsm +#### MultisigIsm | Network | Address | Explorer | | -------------- | -------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------- | @@ -186,8 +179,7 @@ Advanced use - [read here](../build-with-hyperlane/guides/developers/paying-for- | Arbitrumgoerli | `0x47384E33E67007B7fE4326fb096Bdf9CbA7AB6E4` | [View on goerli.arbiscan.io](https://goerli.arbiscan.io/address/0x47384E33E67007B7fE4326fb096Bdf9CbA7AB6E4) | | Sepolia | `0xD3d062a5dcBA85ae863618d4c264d2358300c283` | [View on sepolia.etherscan.io](https://sepolia.etherscan.io/address/0xD3d062a5dcBA85ae863618d4c264d2358300c283) | - -### InterchainQueryRouter +#### InterchainQueryRouter | Network | Address | Explorer | | -------------- | -------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------- | @@ -200,8 +192,7 @@ Advanced use - [read here](../build-with-hyperlane/guides/developers/paying-for- | Arbitrumgoerli | `0x5b1E05e1fdDBc0f3d31c4E634ff4D5d84A56deEe` | [View on goerli.arbiscan.io](https://goerli.arbiscan.io/address/0x5b1E05e1fdDBc0f3d31c4E634ff4D5d84A56deEe) | | Sepolia | `0x507C18fa4e3b0ce6beBD494488D62d1ed0fB0555` | [View on sepolia.etherscan.io](https://sepolia.etherscan.io/address/0x507C18fa4e3b0ce6beBD494488D62d1ed0fB0555) | - -### InterchainAccountRouter +#### InterchainAccountRouter | Network | Address | Explorer | | -------------- | -------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------- | @@ -215,8 +206,7 @@ Advanced use - [read here](../build-with-hyperlane/guides/developers/paying-for- | Arbitrumgoerli | `0x3C636ccC50222a9eb54849C7a622D60a40928a5E` | [View on goerli.arbiscan.io](https://goerli.arbiscan.io/address/0x3C636ccC50222a9eb54849C7a622D60a40928a5E) | | Sepolia | `0x9cA4A31af0f3a8fe2806599467912809D3e17ECB` | [View on sepolia.etherscan.io](https://sepolia.etherscan.io/address/0x9cA4A31af0f3a8fe2806599467912809D3e17ECB) | - -### ValidatorAnnounce +#### ValidatorAnnounce | Network | Address | Explorer | | -------------- | -------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------- | @@ -230,8 +220,7 @@ Advanced use - [read here](../build-with-hyperlane/guides/developers/paying-for- | Arbitrumgoerli | `0x3Fc742696D5dc9846e04f7A1823D92cb51695f9a` | [View on goerli.arbiscan.io](https://goerli.arbiscan.io/address/0x3Fc742696D5dc9846e04f7A1823D92cb51695f9a) | | Sepolia | `0x3Fc742696D5dc9846e04f7A1823D92cb51695f9a` | [View on sepolia.etherscan.io](https://sepolia.etherscan.io/address/0x3Fc742696D5dc9846e04f7A1823D92cb51695f9a) | - -### LiquidityLayer +#### LiquidityLayer | Network | Address | Explorer | | ---------- | -------------------------------------------- | ------------------------------------------------------------------------------------------------------------------- | @@ -240,7 +229,5 @@ Advanced use - [read here](../build-with-hyperlane/guides/developers/paying-for- | Mumbai | `0x2abe0860D81FB4242C748132bD69D125D88eaE26` | [View on mumbai.polygonscan.com](https://mumbai.polygonscan.com/address/0x2abe0860D81FB4242C748132bD69D125D88eaE26) | | Bsctestnet | `0x2abe0860D81FB4242C748132bD69D125D88eaE26` | [View on testnet.bscscan.com](https://testnet.bscscan.com/address/0x2abe0860D81FB4242C748132bD69D125D88eaE26) | | Alfajores | `0x2abe0860D81FB4242C748132bD69D125D88eaE26` | [View on alfajores.celoscan.io](https://alfajores.celoscan.io/address/0x2abe0860D81FB4242C748132bD69D125D88eaE26) | - - {% endtab %} {% endtabs %} diff --git a/resources/glossary.md b/resources/glossary.md index 2b826e2..41c8b3b 100644 --- a/resources/glossary.md +++ b/resources/glossary.md @@ -18,7 +18,7 @@ Example agents include [validators](../operators/validators/ "mention") and [rel Aggregation ISM -The [aggregation-ism-1.md](../protocol/sovereign-consensus/aggregation-ism-1.md "mention") is a type of interchain security module that aggregates security from many [sovereign-consensus](../protocol/sovereign-consensus/ "mention") (ISMs) by requiring that `m` of `n` ISMs verify a particular interchain message. +The [aggregation-ism.md](../protocol/sovereign-consensus/aggregation-ism.md "mention") is a type of interchain security module that aggregates security from many [sovereign-consensus](../protocol/sovereign-consensus/ "mention") (ISMs) by requiring that `m` of `n` ISMs verify a particular interchain message.