hyperlane-monorepo

Author SHA1 Message Date

Author	SHA1	Message	Date
Yorke Rhodes	c5c217f8ea	feat: embed package version in deployed bytecode (#4518 ) ### Description Embed NPM package version in all deployed contracts bytecode. Follows [similar pattern to published CLI version](`3010e36ec9/typescript/cli/src/version.ts (L0-L1)`). Should not be conflated with `Mailbox.VERSION` used for message encoding. ### Drive-by Changes Unfixes solidity NPM package version from typescript packages ### Backward compatibility No, only applies to new deployments or upgrades ### Testing Tested [changeset glob](https://changesets-docs.vercel.app/fixed-packages#using-glob-expressions) ```ts console.log(micromatch(['@hyperlane-xyz/sdk', '@hyperlane-xyz/core', '@hyperlane-xyz/cli'], ['@hyperlane-xyz/!(core)\|*'])); ['@hyperlane-xyz/sdk', '@hyperlane-xyz/cli'] ``` Added test that version function is on ABI	2 months ago
Kunal Arora	76619d0729	feat: Hyperlane AVS contracts (#3651 ) ### Description - Implements `IServiceManager` for the `ECDSAServiceManagerBase` which has a single quorum - `HyperlaneServiceManager` (HSM), the main AVS contract for registering/deregistering operators and enrolling/unenrolling into challengers - the HSM has a mutable slasher so that once the EL slasher is live, we can set it for your AVS too to enable freezing operators. - EnumerableMapEnrollment for a enumerable map of enrollment statuses for each operator and challenger Update: I switched the ECDSAServiceManager i had written earlier to steven's PR here: https://github.com/Layr-Labs/eigenlayer-middleware/pull/234. The differences are: - events for (de)registering Notes - `hardhat yarn` tries looking for all imports (including the ones from submodules) as npm libraries , eg. @eigenlayer/core. ### Drive-by changes - none ### Related issues - fixes https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/3590, ### 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 -->	7 months ago

Yorke Rhodes

feat: embed package version in deployed bytecode (#4518 )

### Description

Embed NPM package version in all deployed contracts bytecode. Follows
[similar pattern to published CLI
version](3010e36ec9/typescript/cli/src/version.ts (L0-L1)).

Should not be conflated with `Mailbox.VERSION` used for message
encoding.

### Drive-by Changes

Unfixes solidity NPM package version from typescript packages

### Backward compatibility

No, only applies to new deployments or upgrades

### Testing

Tested [changeset
glob](https://changesets-docs.vercel.app/fixed-packages#using-glob-expressions)
```ts
console.log(micromatch(['@hyperlane-xyz/sdk', '@hyperlane-xyz/core', '@hyperlane-xyz/cli'], ['@hyperlane-xyz/!(core)|*']));
['@hyperlane-xyz/sdk', '@hyperlane-xyz/cli']
```

Added test that version function is on ABI

2 months ago

Kunal Arora

76619d0729

feat: Hyperlane AVS contracts (#3651 )

### Description

- Implements `IServiceManager` for the `ECDSAServiceManagerBase` which
has a single quorum
- `HyperlaneServiceManager` (HSM), the main AVS contract for
registering/deregistering operators and enrolling/unenrolling into
challengers
- the HSM has a mutable slasher so that once the EL slasher is live, we
can set it for your AVS too to enable freezing operators.
- EnumerableMapEnrollment for a enumerable map of enrollment statuses
for each operator and challenger

Update: I switched the ECDSAServiceManager i had written earlier to
steven's PR here:
https://github.com/Layr-Labs/eigenlayer-middleware/pull/234. The
differences are:
 - events for (de)registering

Notes

- `hardhat yarn` tries looking for all imports (including the ones from
submodules) as npm libraries , eg. @eigenlayer/core.

### Drive-by changes

- none

### Related issues

- fixes https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/3590,

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

7 months ago

2 Commits (14e4719f00be336cd7b7b74a342d212fe6a2c0a4)