Configuring Security
Customize interchain security using ISMs
Developers can take control of interchain security using Interchain Security Modules.
An Interchain Security Module (ISM) is a smart contract that is responsible for verifying messages from a remote chain. ISMs must implement the
IInterchainSecurityModule interface.// SPDX-License-Identifier: MIT OR Apache-2.0
pragma solidity >=0.6.11;
interface IInterchainSecurityModule {
/**
* @notice Returns an enum that represents the type of security model
* encoded by this ISM.
* @dev Relayers infer how to fetch and format metadata.
*/
function moduleType() external view returns (uint8);
/**
* @notice Defines a security model responsible for verifying interchain
* messages based on the provided metadata.
* @param _metadata Off-chain metadata provided by a relayer, specific to
* the security model encoded by the module (e.g. validator signatures)
* @param _message Hyperlane encoded interchain message
* @return True if the message was verified
*/
function verify(bytes calldata _metadata, bytes calldata _message)
external
returns (bool);
}
interface ISpecifiesInterchainSecurityModule {
function interchainSecurityModule()
external
view
returns (IInterchainSecurityModule);
}
To specify the ISM they would like to use, developers may implement the
ISpecifiesInterchainSecurityModule interface in any contract that receives interchain messages.If no ISM is specified, or if the specified ISM is the null address, the default
MultisigIsm will be used.Relayer support for ISMs other than the
MultisigIsm are coming soon™️. It is recommended to use the default ISM for now, or if you're permissionlessly deploying Hyperlane, the MultisigIsms you've deployed.Last modified 7d ago