…perlane-xyz#2646)

### Description

just opening for image for now

### Drive-by changes

<!--
Are there any minor or drive-by changes also included?
-->

### Related issues

<!--
- Fixes #[issue number here]
-->

### Backward compatibility

<!--
Are these changes backward compatible? Are there any infrastructure
implications, e.g. changes that would prohibit deploying older commits
using this infra tooling?

Yes/No
-->

### Testing

<!--
What kind of testing have these changes undergone?

None/Manual/Unit Tests
-->

---------

Co-authored-by: Daniel Savu <23065004+daniel-savu@users.noreply.github.com>

…z#2543)

### Description

This PR sets chain signer keys in the external secret.
related to
hyperlane-xyz#2458

### Drive-by changes

<!--
Are there any minor or drive-by changes also included?
-->

### Related issues

<!--
- Fixes #[issue number here]
-->

### Backward compatibility

<!--
Are these changes backward compatible? Are there any infrastructure
implications, e.g. changes that would prohibit deploying older commits
using this infra tooling?

Yes/No
-->

### Testing

<!--
What kind of testing have these changes undergone?

None/Manual/Unit Tests
-->

Co-authored-by: josedev-union <josedev-union@users.noreply.github.com>
Co-authored-by: Nam Chu Hoai <nambrot@googlemail.com>

### Description

Adds addresses of the rc validator keys for solana, nautilus and their
testnet counterparts

### Drive-by changes

<!--
Are there any minor or drive-by changes also included?
-->

### Related issues

<!--
- Fixes #[issue number here]
-->

### Backward compatibility

<!--
Are these changes backward compatible? Are there any infrastructure
implications, e.g. changes that would prohibit deploying older commits
using this infra tooling?

Yes/No
-->

### Testing

<!--
What kind of testing have these changes undergone?

None/Manual/Unit Tests
-->

…yperlane-xyz#2647)

### Description

This change adds the possibility to configure a subfolder inside an S3
bucket, to avoid having to spin up an entire bucket for hyperlane.

### Drive-by changes

Nothing

### Related issues

None, chatted about it on Slack with @nambrot 

### Backward compatibility

Yes

I made the field optional in the `RawCheckpointSyncerConf` so that
current config are still valid and will continue to read/write at the
root of the bucket. That being said, I'm new to this code so I hope I
got it right

### Testing

None

---------

Co-authored-by: Nam Chu Hoai <nambrot@googlemail.com>

### Description

Process user used in Dockerfile can now read and write to any volume
mounted under the `/data/` directory.

### Drive-by changes

N/A

### Related issues

Fixes: 2691

### Backward compatibility

Yes

### Testing

Manual

I've built the image locally and tested that we can mount any kind of
docker volume under the `/data/` directory

### Description

This does two things:
1) It parses the agent-specific configs for the relayer, validator, and
scraper.
2) It removes the rigid structures that had been in place for parsing
that were called out earlier and instead parses the serde json values
directly.

This PR does not cut over to the new versions just yet. That can happen
once we start integrating it into the testing and deployment pipelines.

### Drive-by changes

- Derive more was added and used where it made sense
- The old config macro was removed

### Related issues

- Progress on hyperlane-xyz#2215 

### Backward compatibility

Yes

### Testing

None

### Description
 
Depends on hyperlane-xyz#2583

Indexes IGP payments related to the relayer's data pda address. Unless
this address is specified in the config (`sealevel.relayer_account `),
no filtering is applied and all IGP payments are stored in the local
database.

<!--
What's included in this PR?
-->

### Drive-by changes

- Sets `HYP_BASE_GASPAYMENTENFORCEMENT` in `run-locally` for the
relayer, to test that it correctly indexes the IGP payment before
submitting the message
- A new config section (`sealevel`) is added to the relayer
- The `MessageIndexer` trait is replaced with
`SequenceIndexer<HyperlaneMessage>`, renaming `fetch_count_at_tip` to
`sequence_at_tip`. `SequenceIndexer` is now common to both the message
and igp indexers.
- The `parse_addr` macro is modified so it can be reused when parsing
the sealevel relayer address config too
- `rust/utils/sealevel-test.bash` is included because I was using it to
test locally, but I can remove it if the sealevel e2e test already does
all the steps there @mattiecnvr
- Performs a `try_into` conversion that can be removed once
hyperlane-xyz#2610 is done

### Related issues

- Fixes hyperlane-xyz#2501


### Backward compatibility

<!--
Are these changes backward compatible? Are there any infrastructure
implications, e.g. changes that would prohibit deploying older commits
using this infra tooling?

Yes/No
-->

### Testing

<!--
What kind of testing have these changes undergone?
-->
e2e tests but the pipeline is failing, likely fixed by
hyperlane-xyz#2602

---------

Co-authored-by: Trevor Porter <trkporter@ucdavis.edu>

…p transfers in tooling (hyperlane-xyz#2700)

### Description

Sadly, there's no programmatic way to submit transactions to Squads via
an API or anything. As a workaround, if `-k` is passed a Pubkey and not
a path to a Keypair as the payer, transactions will instead be logged in
a base58 serialized format that can then be copied into Squads.
Instructions for exactly how to do this are found in our Notion

So this includes:
* Allow for the payer to just be a Pubkey without a Keypair
* Some commands & functions to allow for ownership transfer

### Drive-by changes

* There was a whole directory
`rust/chains/hyperlane-sealevel/src/solana` that somehow got into main,
I deleted this
* Cleaned up some logs to be formatted more nicely

### Related issues

part of hyperlane-xyz/issues#545

### Backward compatibility

backward compatible

### Testing

Transferred ownership of devnet

---------

Co-authored-by: Daniel Savu <23065004+daniel-savu@users.noreply.github.com>

### Description

- Add support for multi-protocol to the HelloWorld app and Kathy service
- Create a new MultiProtocolCore

### Related issues

hyperlane-xyz#2503

### Backward compatibility

Yes

### Testing

- Tested new Kathy abstraction on existing EVM while we wait for
Sealevel Kathy to be unblocked
- Tested using local config stubs for both EVM and Sealevel

### Description

- Migrating `SealevelTokenAdapter` to monorepo for providing a common abstraction
- Common serialization code under `sdk/sealevel`

### Related issues

- hyperlane-xyz#2652 

### Backward compatibility

Yes

### Testing

Manual

---------

Co-authored-by: J M Rossy <jm.rossy@gmail.com>

### Description

- Script to monitor token balances for Nautilus-Zebec-Solana warp route
(hardcoded)
- Helm command to deploy warp route monitoring script to Kubernetes

### Drive-by changes

- Updated default version to testnet3 for kathy and liquidity-layer

### Related issues

- issue hyperlane-xyz/issues#549

### Backward compatibility

Yes

### Testing

Manual

### Description

- Currently if you do keyboard interrupt while running the deploy
script, none of the already deployed addresses get written to the
artifacts.
- Register a SIGINT handler in the `deployWithArtifacts` script

### Drive-by changes

None

### Related issues

None

### Backward compatibility

Yes

### Testing

Manual

### Description
Tooling to get / set gas oracle data for sealevel, part of
hyperlane-xyz/issues#568

The PR adds two IGP oracle commands. If the values to be set are
specified, then the command performs a write using the key configured.
Otherwise, it performs a read. Unsure whether this is the best UX, happy
to change it.

Usage example:
```bash
# Get gas values
cargo run --bin hyperlane-sealevel-client igp destination-gas-overhead --environments-dir ./sealevel/environments --environment testnet3 --chain-name solanadevnet --remote-domain 88002

# Set gas values. Note the added `--gas-overhead 159736` flag
cargo run --bin hyperlane-sealevel-client igp destination-gas-overhead --environments-dir ./sealevel/environments --environment testnet3 --chain-name solanadevnet --remote-domain 88002 --gas-overhead 159736
```

There's also a small warp route util added to read the destination gas:
```bash
 cargo run --bin hyperlane-sealevel-client warp-route destination-gas --program-id 84DAG9VX5CvefQrBUGh9Gp66kmkat2voaM4MB2YwpGW1 --destination-domain 88002
 ```

<!--
What's included in this PR?
-->

### Drive-by changes

<!--
Are there any minor or drive-by changes also included?
-->

### Related issues

<!--
- Fixes #[issue number here]
-->

### Backward compatibility

<!--
Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling?

Yes/No
-->

### Testing
Manual
<!--
What kind of testing have these changes undergone?

None/Manual/Unit Tests
-->

### Description
Fixes a current deployment issue due to some changes in the infra
deployment.

Also caught an error in the schema for the matching list type and
updated it.

)

Co-authored-by: Trevor Porter <trkporter@ucdavis.edu>
Co-authored-by: Nam Chu Hoai <nambrot@googlemail.com>

Removes some unnecessary logs from the sealevel igp indexing fn. Also
instruments the eta calculator in response to
hyperlane-xyz#2723

### Description

<!--
What's included in this PR?
-->

### Drive-by changes

<!--
Are there any minor or drive-by changes also included?
-->

### Related issues

<!--
- Fixes #[issue number here]
-->

### Backward compatibility

<!--
Are these changes backward compatible? Are there any infrastructure
implications, e.g. changes that would prohibit deploying older commits
using this infra tooling?

Yes/No
-->

### Testing

<!--
What kind of testing have these changes undergone?

None/Manual/Unit Tests
-->

### Description

<!--
What's included in this PR?
-->

### Drive-by changes

<!--
Are there any minor or drive-by changes also included?
-->

### Related issues

<!--
- Fixes #[issue number here]
-->

### Backward compatibility

<!--
Are these changes backward compatible? Are there any infrastructure
implications, e.g. changes that would prohibit deploying older commits
using this infra tooling?

Yes/No
-->

### Testing

<!--
What kind of testing have these changes undergone?

None/Manual/Unit Tests
-->

### Description

- Build on hyperlane-xyz#2684, migrates the EvmAdapter and missing utils from the warp UI
- Remove the token App as it's unused and redundant with adapters
- Add IGP serialization code for hyperlane-xyz#2546 
- Simplify multi-protocol adapters in SDK
- Make token adapters extend base adapters
- Move token serialization code to token package

### Drive-by changes

- Update Sepolia RPC which was causing errors

### Related issues

hyperlane-xyz#2652 

### Backward compatibility

Yes

### Testing

Tested these in warp UI

---------

Co-authored-by: Yorke Rhodes <yorke@hyperlane.xyz>

Simplify mailbox and make interfaces payable

Update version constant

Keep message ID events

Use mailbox callback to authenticate messages in hooks where necessary (hyperlane-xyz#2609)

Co-authored-by: Kunal Arora <55632507+aroralanuk@users.noreply.github.com>

- IGP as a standalone hook, implementing postDispatch to call payForGas
directly
- Setting a DEFAULT_GAS_USAGE if metadata not specified and
message.senderAddress() as refund address if not specified.

- None

Fixes hyperlane-xyz/issues#511

Yes, same interface as the previous IGP but for Mailbox V3

Unit Tests

---------

Co-authored-by: Yorke Rhodes <yorke@hyperlane.xyz>

…-xyz#2632)

- Updated the OP Stack tests for the Mailbox V3 transient storage
version
- Allowing OPStackHook to send msg.value at the time of message delivery
(uses bit masking)
- Added LibBit library, will be useful for all the auth hooks which can
send `msg.value`

- None

- Fixes breaking OP Stack tests for
hyperlane-xyz/issues#513
- Also fixes
hyperlane-xyz#2410

No

Unit tests

---------

Co-authored-by: Yorke Rhodes <yorke@hyperlane.xyz>

Remove e2e and add yarn build to CI

Adding protocol fees (hyperlane-xyz#2640)

- Adding protocol fee as a hook

- None

V3

Yes

Fuzz tests

---------

Co-authored-by: Yorke Rhodes <yorke@hyperlane.xyz>

- fixes GasRouter expectRevert message
- added TestMerkleRootHook for proof() and fixes MerkleRootMultisig test
- fixes ERC5164 tests post v3 changes

- added contract name to mailbox and abstractHook error messages
- removed unnecessary tests for "message too large"
- downgrade slither in actions to 0.3.0 because of their recent "missing
inheritance" bug on main

- V3

Yes

Unit tests

- `quoteDispatch` added to `IPostDispatchHook` interface and the
relevant hooks:
     - StaticProtocolFee
     - OPStackHook
     - InterchainGasPaymaster
     - MerkleTreeHook
     - PausableHook (no tests)
     - DomainRoutingHook (no tests)
     - ConfigFallbackDomainRoutingHook
     - ConfigurableDomainRoutingHook (no tests)

- `expectEmit` -> `expectCall`

- Quote in V3

Yes

Uint tests

Fixes hyperlane-xyz#2004

### Description

- AggregationHook for v3

### Drive-by changes

None

### Related issues

v3

hyperlane-xyz/issues#514

### Backward compatibility

Yes

### Testing

Always be fuzzing

- V3 compatible ERC20, ERC721 and all their extensions

- Painstakingly migrating hardhat tests to foundry tests for all
variants

- fixes hyperlane-xyz/issues#577

Yes

whole lotta unit tests and poor man's version of integration tests

---------

Signed-off-by: -f <kunalarora1729@gmail.com>
Co-authored-by: Yorke Rhodes <yorke@hyperlane.xyz>

Fixes hyperlane-xyz/issues#591

### Description

- Removed contracts-bedrock contracts dependency from eth-optimism
(which was forcing us to use 0.8.15)
- Added local minimal interfaces for the CrossDomainMessenger contract

### Drive-by changes

None

### Related issues

None

### Backward compatibility

Yes

### Testing

Unit tests

---------

Signed-off-by: -f <kunalarora1729@gmail.com>
Co-authored-by: Yorke Rhodes <yorke@hyperlane.xyz>

### Description

Includes newly deployed Nautilus warps to not enforce gas payments
between

### Drive-by changes

n/a

### Related issues

Related hyperlane-xyz/issues#566

### Backward compatibility

yes

### Testing

Deployed

### Description

the `debug!` logs either are not occurring very often, or are not
displayed at all in the gcp logs

<!--
What's included in this PR?
-->

### Drive-by changes

<!--
Are there any minor or drive-by changes also included?
-->

### Related issues

<!--
- Fixes #[issue number here]
-->

### Backward compatibility

<!--
Are these changes backward compatible? Are there any infrastructure
implications, e.g. changes that would prohibit deploying older commits
using this infra tooling?

Yes/No
-->

### Testing

<!--
What kind of testing have these changes undergone?

None/Manual/Unit Tests
-->

### Description
Getter and setter for the warp route igp
<!--
What's included in this PR?
-->

### Drive-by changes

<!--
Are there any minor or drive-by changes also included?
-->

### Related issues

- Fixes hyperlane-xyz/issues#571

### Backward compatibility

<!--
Are these changes backward compatible? Are there any infrastructure
implications, e.g. changes that would prohibit deploying older commits
using this infra tooling?

Yes/No
-->

### Testing

Manual

### Description

- Adding "InsertedIntoEvent" for standalone indexing of events by the
agents

### Drive-by changes

None

### Related issues

hyperlane-xyz#2313 

### Backward compatibility

Yes

### Testing

Unit tests

### Description

New relayer gas payment policies for testnet3 and mainnet2, based on
these rules:

- ~~leave `PJH5QAbxAqrrnSXfH3GHR8icua8CDFZmo97z91xmpvx` in the
`GasPaymentEnforcementPolicyType.None` matching list until we move its
ownership~~
- don't enforce gas payments:
  - from the helloworld router on solanadevnet
  - from solana devnet and mainnet warp routes to anything
- with the exception of `EJqwFjvVJSAxH8Ur2PYuMfdvoJeutjmH6GkoEFQ4MdSa`,
which now has an igp configured
(`HksFWQM1EXJJ5mxo2uZoMfmksXHaNhCunh71NqcQQHZ8`)
  - from the bsc/bsctestnet routers of all the warp routes
  - for interchain queries on both testnet3 and mainnet2

### Related issues

- Fixes hyperlane-xyz/issues#570

### Backward compatibility

Yes

### Testing
 None

### Description

Currently, when the validator is not signing, there is just a unhelpful
"Could not fetch metadata" log line. This indicates that no quorum could
be found at the debug level as well as adding the checkpoint syncer
information

### Backward compatibility

Yes

### Testing

Manual

)

### Description

- Adds destinationDomain to the `GasPayment` event
- recording destination domain as `destination` while reading events for
the relayer

### Drive-by changes

- none

### Related issues

- fixes hyperlane-xyz/issues#475

### Backward compatibility

No, change in event emitted and relayer indexing

### Testing

- Unit

---------

Signed-off-by: -f <kunalarora1729@gmail.com>
Co-authored-by: Yorke Rhodes <yorke@hyperlane.xyz>

## Bug 1

Closes hyperlane-xyz#2723

The relayer panic is caused by an overflow, bc of dividing by
~`6.540888459481895e-211`. On my local, the effective rate of indexing
starts at `0.61`.
```
{"timestamp":"2023-09-15T09:57:10.746276Z","level":"INFO","fields":{"message":"~~~ blocks_processed: 2508, tip_progression: 2042, elapsed: 757.10340475, old_rate: Some(0.6155037701275111), effective_rate: 0.6155037701275111"},"target":"hyperlane_base::contract_sync::eta_calculator","span":{"domain":"solanadevnet","label":"gas_payments","name":"ContractSync"},"spans":[{"domain":"solanadevnet","label":"gas_payments","name":"ContractSync"}]}
```

But then both the `blocks_processed` and the `tip_progression` are
consistently zero, which makes the `new_rate` be zero
(https://github.com/hyperlane-xyz/hyperlane-monorepo/blob/eea423ad049acfd15855465792147fb99bc8dd4d/rust/hyperlane-base/src/contract_sync/eta_calculator.rs#L41),
and over time it takes over the entire moving average window to make it
almost zero, leading to an overflow. 15 mins after that initial log, the
effective rate already became `0.00038`.

The reason for blocks_processed and tip_progression consistently being
zero after the first log is that `eta_calculator.calculate(from, tip)`
is always called with the same from and tip although it expects to get
the latest values.

### The fix

the tip wasn't being set after the sequence_and_tip query here:
https://github.com/hyperlane-xyz/hyperlane-monorepo/blob/eea423ad049acfd15855465792147fb99bc8dd4d/rust/hyperlane-base/src/contract_sync/cursor.rs#L565

And then the to and from are calculated based on it:
https://github.com/hyperlane-xyz/hyperlane-monorepo/blob/eea423ad049acfd15855465792147fb99bc8dd4d/rust/hyperlane-base/src/contract_sync/cursor.rs#L550

So even though the sync_state internal variables were kept up-to-date,
the min(...) would cause the issue.

The first PR commit fixes this.

## Bug 2

There was another bug in the eta calculator, caused by it only using
`next_block` to approximate synced state, which doesn't apply to
sequence indexing. The way the eta calculator is called had to be
changed to use abstract measures of sync progression (which could be
blocks or sequences).

The second PR commit fixes this, afaict.

…erlane-xyz#2681)

Co-authored-by: Kunal Arora <55632507+aroralanuk@users.noreply.github.com>
Fixes hyperlane-xyz/issues#559

### Description

- Consolidating IGPMetadata and OPStackMetadata to versioned
GlobalHookMetadata
- Add `supportMetadata` to `IPostDispatchHook`

 - Metadata Schema
 [0:1] variant
 [2:33] msg.value
 [34:65] Gas limit for message (IGP)
 [66:85] Refund address for message (IGP)
 [86:] Custom metadata

### Drive-by changes

None

### Related issues

- fixes hyperlane-xyz/issues#610


### Backward compatibility

No

### Testing

Unit tests

---------

Co-authored-by: Yorke Rhodes <yorke@hyperlane.xyz>

### Description

This PR introduces a feature to warp routes such that LPs can fill
transactions on local chains and get a fee for doing this.

### Drive-by changes

No.

### Related issues

hyperlane-xyz#2690 

### Backward compatibility

No

### Testing

Added Unit tests.

---------

Co-authored-by: Rohan Shrothrium <rohan.shrothrium@intellecteu.com>
Co-authored-by: Nam Chu Hoai <nambrot@googlemail.com>

hyperlane-xyz#2758)

### Description

- Some small changes to help with debugging sealevel IGP
- Turns out the GasPaymentAccount data format onchain is different from
the one in `main`. This causes IGP indexing to not work in the wild, but
it works in e2e. Because we were planning to change the IGP anyways as
we transfer ownership to Zebec, this isn't so bad - so temporarily just
not enforcing ZBC warp route Solana -> Nautilus gas payments. In
practice, we're still effectively enforcing gas payments because the
warp route will pay for gas

### Drive-by changes

- Also added the new BSC POSE addy

### Related issues

n/a

### Backward compatibility

yes

### Testing

Deployed, poked around, used cmds

### Description

- Reorganize solidity directory structure for clarity
- Updates router apps (token and helloworld) with changes from
hyperlane-xyz#2749

### Drive-by changes

- Merges the hyperlane-token package to solidity and sdk

### Backward compatibility

No (removed token package)

### Testing

- Unit Tests
- Instrumented coverage

### Description

Regular rust version and package updates.

### Drive-by changes

None

### Related issues


### Backward compatibility

Yes

### Testing

Unit Tests

Fixes hyperlane-xyz/issues#630

Fixes hyperlane-xyz/issues#629

Fixes hyperlane-xyz#2759

### Description

Caps the msg backoff instead of going to insanely large durations

### Backward compatibility

Yes

### Testing

None

### Description

- Interceptor is the pair <hook, ism>
- `MerkleTreeInterceptorDeployer` for deploying merkle root hook and the
`StaticMerkleRootMultisigIsm` on chain

### Drive-by changes

- None

### Related issues

- addresses hyperlane-xyz/issues#621

### Backward compatibility

Yes

### Testing

Manual

### Description

Because incremental merkle tree insertion complexity can change
depending on what the index in the merkle tree is, we ran into a
situation where the 200k default compute limit wasn't enough when trying
to perform a transfer remote on sealevel.

Normal cost for index 257, about 158k units:

https://explorer.solana.com/tx/4oB9b6PaaKvGMhrQS7XGmi7zBpX3GUW99sbVrSjFwm5AVT96emKF4NH6gn2y9cLMLep8wQJ9LqwJifG5QMpr4BAs

Index 255, about 245k units!:
https://explorer.solana.com/tx/3v6SbrT58smwnLdnrEFaMXowaEDmo6EpPmKFTUMe9aESo5FTExmJdr2uMH5QJW9hnZTqrB1mfFZe4Vmu75CCAyPs

The fix is to simply request more units. Solana tx fees don't actually
charge you more if you use more units. Txs have a global cap of 1.4M
units -- I'm just requesting 1M here as a balance between having lots of
units & not bricking ourselves if the max compute unit amount ever
decreases

### Drive-by changes

n/a

### Related issues

n/a

### Backward compatibility

Yes

### Testing

I tested a version of this in the UI - I went to the commit where we
published 1.5.1, and then published a 1.5.1-beta2 version with this
change and moved the UI over to it. Opening this now so we can get this
in main and move the UI over to a less sketchy version

### 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

hyperlane-xyz#2502

### Backward compatibility

I believe it should all be backward compatible

### Testing

Deployed, ran checkers, etc

### Description

- v3 uses the OverheadIgp as the default igp and removing an "inner" igp
makes it simpler to deploy and interact with
- `InterchainGasPaymaster` has a `setDestinationGasConfigs` which sets
it the overhead and the oracle.
- the gas overhead gets added it directly to the specified gasAmount.
- Downstream changes to the `typescript/*` module in the igpConfig,
checke, deployer, etc

### Drive-by changes

None

### Related issues

- precursor to hyperlane-xyz/issues#623
- related to hyperlane-xyz/issues#637
- missing changes to governor hyperlane-xyz/issues#641

### Backward compatibility

Yes

### Testing

Fuzz

### Description

- Adapter fixes from further testing of multi-protocol Kathy
- Add router address for hyperlane context helloworld
- Improve stat collection to handle cross-protocol msgs
- Re-enable actual env config for Kathy

### Drive-by changes

- Fix for transaction hash checking in utils

### Related issues

hyperlane-xyz#2503

### Backward compatibility

Yes

### Testing

Ran Kathy manually using `getCoreConfigStub` and forced stat output
Tested live in cloud with help from @tkporter 

---------

Co-authored-by: Trevor Porter <trkporter@ucdavis.edu>

### Description

It's your favourite PR coming right back... V3 agents!

Closes hyperlane-xyz/issues#561

Builds on top of
hyperlane-xyz#2742

Depends on hyperlane-xyz#2681
for e2e testing

This PR includes:
- [x] Merkle tree hook indexer
- [x] Merkle tree builder task
- [x] Update submitter to trigger retries if no proof is available yet

Slightly more detailed overview of the work here:
hyperlane-xyz#2720 (comment)

<!--
What's included in this PR?
-->

### Drive-by changes

<!--
Are there any minor or drive-by changes also included?
-->

### Related issues

<!--
- Fixes #[issue number here]
-->

### Backward compatibility

<!--
Are these changes backward compatible? Are there any infrastructure
implications, e.g. changes that would prohibit deploying older commits
using this infra tooling?

Yes/No
-->

### Testing

<!--
What kind of testing have these changes undergone?

None/Manual/Unit Tests
-->

---------

Co-authored-by: -f <kunalarora1729@gmail.com>
Co-authored-by: Trevor Porter <trkporter@ucdavis.edu>
Co-authored-by: Kunal Arora <55632507+aroralanuk@users.noreply.github.com>
Co-authored-by: Mattie Conover <git@mconover.dev>
Co-authored-by: Guillaume Bouvignies <guillaumebouvignies@gmail.com>
Co-authored-by: Yorke Rhodes <yorke@hyperlane.xyz>
Co-authored-by: Guillaume Bouvignies <guillaume.bouvignies@kurtosistech.com>

Co-authored-by: Yorke Rhodes <yorke@hyperlane.xyz>
fixes hyperlane-xyz/issues#624

fixes hyperlane-xyz/issues#574

### Description

Part of the remediations from
hyperlane-xyz#2746

---------

Co-authored-by: Trevor Porter <trkporter@ucdavis.edu>

### Description

<!--
What's included in this PR?
-->

### Drive-by changes

<!--
Are there any minor or drive-by changes also included?
-->

### Related issues

<!--
- Fixes #[issue number here]
-->

### Backward compatibility

<!--
Are these changes backward compatible? Are there any infrastructure
implications, e.g. changes that would prohibit deploying older commits
using this infra tooling?

Yes/No
-->

### Testing

<!--
What kind of testing have these changes undergone?

None/Manual/Unit Tests
-->

### Description

- Deployer changes and artifacts from testnet4 deployment

### Drive-by changes

- a single external-secrets instance lives on the cluster, and we are running testnet3 and testnet4 on the same cluster
- json parsing errors were silently swallowed, moved to `mustFromJson` to prevent this

### Drive-by changes

### Backward compatibility

Yes

### Testing

Manual

---------

Co-authored-by: Trevor Porter <trkporter@ucdavis.edu>

Per discussion in standup yesterday

### Description

- Rpc urls are super flaky, stopping the validators and relayer support
- Keeping proteustestnet artifacts / chain metadata for now

### Drive-by changes

<!--
Are there any minor or drive-by changes also included?
-->

### Related issues

<!--
- Fixes #[issue number here]
-->

### Backward compatibility

<!--
Are these changes backward compatible? Are there any infrastructure
implications, e.g. changes that would prohibit deploying older commits
using this infra tooling?

Yes/No
-->

### Testing

<!--
What kind of testing have these changes undergone?

None/Manual/Unit Tests
-->

I guess this is goodbye.

### Description

- Create new CLI package
- Upgrade prettier, typescript, and lint packages
- Update TSConfig output target to ES2020
- Migrate code from hyp-deploy repo to `typescript/cli/src`

### Related issues

Fixes hyperlane-xyz#2566
Fixes hyperlane-xyz#2786

### Backward compatibility

Yes

### Testing

Tested all commands locally
Tested core deployments with and without pre-existing addresses (artifacts)
Created e2e tests for deploying core, warp, and sending messages

---------

Co-authored-by: Nam Chu Hoai <nambrot@googlemail.com>

### Description

- fixes to deploy testnet4 for agents

### Drive-by changes

- truncating labels to length 63
- adding `.relayer` to `agentConfig.contextChainNames`

### Related issues

- for hyperlane-xyz/issues#574

### Backward compatibility

Yes

### Testing

Manual

---------

Co-authored-by: Trevor Porter <trkporter@ucdavis.edu>
Co-authored-by: Nam Chu Hoai <nambrot@googlemail.com>

### Description

- Support multiple origins in PI deployments
- Simplify ci test with single core deploy command
- Improve output format of chains list command

### Related issues

Fixes hyperlane-xyz#2813 

### Testing

Tested locally and with e2e test

### Description

- Adds E2E testing scenarios to the agents: zero, single and double
merkle tree hook insertion
- zero insertion messages are assumed to not be deliverable for now,
because that would require additional changes to e2e logic (deploying
more one `TestSendReceiver.sol` instance per destination network)
- `TestSendReceiver.sol` is extended to dynamically specify the default
hook to use
- the kathy hardhat script is extended with two params: the required and
default hooks. If these are not specified via CLI, they default to
`protocolFee` and `aggregationHook` respectively and are still set in
the mailbox, to ensure idempotency.
- sealevel tests commented out for now

### Drive-by changes

### Related issues

- Closes hyperlane-xyz/issues#561
- Closes hyperlane-xyz#2720
- Closes hyperlane-xyz#2755

### Backward compatibility

<!--
Are these changes backward compatible? Are there any infrastructure
implications, e.g. changes that would prohibit deploying older commits
using this infra tooling?

Yes/No
-->

### Testing

<!--
What kind of testing have these changes undergone?

None/Manual/Unit Tests
-->

---------

Co-authored-by: Yorke Rhodes <yorke@hyperlane.xyz>

…z#2817)

### Description

- Redeploy goerli, bsctestnet mailboxes and deps
- Fix sepolia mailbox
- Check original ISM config

### Drive-by changes

- Uses original ISM config of aggregation => routing => multisigs

### Related issues

<!--
- Fixes #[issue number here]
-->

### Backward compatibility

<!--
Are these changes backward compatible? Are there any infrastructure
implications, e.g. changes that would prohibit deploying older commits
using this infra tooling?

Yes/No
-->

### Testing

<!--
What kind of testing have these changes undergone?

None/Manual/Unit Tests
-->

---------

Co-authored-by: Nam Chu Hoai <nambrot@googlemail.com>

### Description

* polygonzkevmtestnet's validator name was too long because of the
`controller-revision-hash` label, see
kubernetes/kubernetes#64023
* Seeks to preserve the `-validator` suffix in the name, but truncates
the earlier bit - in practice this results in validator pods like
`polygonzkevmtestnet-validator-hyperlane-ag-validator-0`. This felt like
the most backward compatible change -- of course we could consider
trying to get a name like
`polygonzkevmtestnet-hyperlane-agent-validator-0` but this would break
backward compatibility more dramatically because we'd need to change all
the other validator pods. Imo we should just really avoid long chain
names or consider a more breaking change to our infra

### Drive-by changes

n/a

### Related issues

n/a

### Backward compatibility

Mostly

### Testing

Deployed

Fixes hyperlane-xyz/issues#635

### Description

Somehow missed that in
https://github.com/hyperlane-xyz/hyperlane-monorepo/pull/2784/files#diff-c74afa5055013fc40d4626107d9d086be0f21e87907784532f71e8bfe2e1b02bR38

### Description

Fixes the alfajores IGP contract to the one actually used on-chain.

### Drive-by changes

Removed the old testnet_config.json in rust/config

Co-authored-by: Yorke Rhodes <yorke@hyperlane.xyz>

### Description

- removing `.relayers` from `Values.hyperlane.chains` in external
secrets
- redeploying helloworld on `goerli,sepolia,bsctestnet` and running
kathy on k8s

### Drive-by changes

none

### Related issues

none

### Backward compatibility

yes

### Testing

Manual

…to edge cases (hyperlane-xyz#2836)

### Description

* hyperlane-xyz#532 wasn't
actually fully closed out - finality_blocks was used still for indexing.
Sadly testnet4 infra wasn't configuring finality blocks anymore, so we
weren't indexing only finalized blocks. Moved fully to reorg_period
* Refactored `checkpoint_submitter` in light of races revealed by the
above ^ problem. It used to assume that message indexing and the
`latest_checkpoint()` call would align with one another, and wasn't
resilient to the tree already being past the correctness checkpoint. A
couple situations were possible before that aren't now:
a. Indexing is ahead of the latest_checkpoint() call, which will result
in tree ingesting the new indexed messages and the tree being ahead of
the correctness checkpoint :(
b. It's possible for the tree() call that constructs the tree initially
to be made against a block that's after the next latest_checkpoint()
call, which would result in the tree being ahead of the correctness
checkpoint from the very beginning :(

### Drive-by changes

removed a function that wasn't being used anymore

### Related issues

hyperlane-xyz#532

### Backward compatibility

Removes finality blocks entirely

### Testing

Builds, e2e