hyperlane-monorepo

Commit Graph

Author	SHA1	Message	Date
Daniel Savu	8e44bc1b81	feat: sealevel merkle indexer + e2e (#3053 ) Depends on https://github.com/hyperlane-xyz/hyperlane-monorepo/pull/3048 Fixes https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/3046 Fixes https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/2754	12 months ago
Yorke Rhodes	1d18549755	Merge main to v3 (#2812 )	1 year ago
Trevor Porter	3f3306c35e	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

Author

SHA1

Message

Date

Daniel Savu

8e44bc1b81

feat: sealevel merkle indexer + e2e (#3053 )

Depends on https://github.com/hyperlane-xyz/hyperlane-monorepo/pull/3048

Fixes https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/3046
Fixes https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/2754

12 months ago

Yorke Rhodes

1d18549755

Merge main to v3 (#2812 )

1 year ago

Trevor Porter

3f3306c35e

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

2 Commits (94e6ca21eebeed715bf15b70b3d0381ca545bdb2)