The home for Hyperlane core contracts, sdk packages, and other infrastructure
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
hyperlane-monorepo/rust/sealevel/environments/mainnet2/multisig-ism-message-id/solana/rc/multisig-config.json

65 lines
1.2 KiB

Helloworld program and tooling (#2744) ### Description * HelloWorld program added to `rust/sealevel/programs/helloworld` * Some changes to the Sealevel tooling * Refactored the old warp-route-specific deploy management into a more generic framework for idempotently deploying and managing router apps in Sealevel * Added helloworld deploy tooling * Added ISM & owner checking to this router deployment tooling * Added `--require-tx-approval` to prevent txs from being called without first prompting * Added a bunch of new commands for creating txs with certain instructions that were needed along the way -- e.g. setting an ISM, deploying a specific multisig ISM (previously only one would be deployed as a part of `core deploy` * Added a command for configuring multisig ISMs, `multisig-ism-message-id configure`, that takes in a JSON file of multisig ISM configs and applies them onchain * A bit of cleanup / refactor - e.g. removed some old commands like `mailbox receive` * Added foreignDeployments into `RouterApp` * Because RouterApp takes in `contractsMap: HyperlaneContractsMap<Factories>,`, which require attached contracts, a new `readonly foreignDeployments: ChainMap<Address> = {},` is added to the constructor * These foreignDeployments are considered in the return value of `remoteChains(chainName: string)`, but not in `chains()` -- this means that `chains()` now concretely means "chains that can be deployed to / interacted with and that there is an entry in `contractsMap` for, and `remoteChains(chainName: string)` returns any and all remote chains, regardless of whether they can be deployed to / interacted with * Added complete ISM support to the HyperlaneRouterChecker * when checking the ISM, if there's not a match and the ISM is a config, then the ISM will be deployed * Also added RouterViolation, before it'd just throw if there was a violation * Updated the Helloworld, IGP, and core tooling to work when AEE deployments are also configured * Moved to Routing ISM -> Aggregation ISM -> Merkle / Message ID multisig setup Some things to note: * atm there are a few places that have a TODO saying to remove something after some multisig txs are executed, I plan to revisit these after we get some sigs * I've deployed the mainnet sealevel version of helloworld, but haven't been able to enroll it in the EVM chains yet. Waiting for some multisig activity here ### Drive-by changes ### Related issues #2502 ### Backward compatibility I believe it should all be backward compatible ### Testing Deployed, ran checkers, etc
1 year ago
{
"celo": {
"type": 3,
"threshold": 1,
"validators": [
"0xe7a82e210f512f8e9900d6bc2acbf7981c63e66e"
]
},
"ethereum": {
"type": 3,
"threshold": 1,
"validators": [
"0xaea1adb1c687b061e5b60b9da84cb69e7b5fab44"
]
},
"avalanche": {
"type": 3,
"threshold": 1,
"validators": [
"0x706976391e23dea28152e0207936bd942aba01ce"
]
},
"polygon": {
"type": 3,
"threshold": 1,
"validators": [
"0xef372f6ff7775989b3ac884506ee31c79638c989"
]
},
"bsc": {
"type": 3,
"threshold": 1,
"validators": [
"0x0823081031a4a6f97c6083775c191d17ca96d0ab"
]
},
"arbitrum": {
"type": 3,
"threshold": 1,
"validators": [
"0x1a95b35fb809d57faf1117c1cc29a6c5df289df1"
]
},
"optimism": {
"type": 3,
"threshold": 1,
"validators": [
"0x60e938bf280bbc21bacfd8bf435459d9003a8f98"
]
},
"moonbeam": {
"type": 3,
"threshold": 1,
"validators": [
"0x0df7140811e309dc69638352545151ebb9d5e0fd"
]
},
"gnosis": {
"type": 3,
"threshold": 1,
"validators": [
"0x15f48e78092a4f79febface509cfd76467c6cdbb"
]
}
}