feat: Add ink, monad, xlayer for ezeth

[ltyu]

Description

This PR adds Ink, Monad, and Xlayer for EZETH

Backward compatibility

Testing

Summary by CodeRabbit

• New Features
  • Added support for Ink, Monad, and Xlayer networks for EZETH token configurations.
  • Expanded warp route connections across production and staging environments to include the new supported networks.

[changeset-bot]

🦋 Changeset detected

Latest commit: 50f7a90

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@hyperlane-xyz/registry	Minor

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[coderabbitai]

📝 Walkthrough

Walkthrough

This PR expands the EZETH restaked ETH ecosystem by integrating three new chains—Ink, Monad, and Xlayer—into both production and staging configurations. The changeset documents this minor version bump for the registry package, adding token connections and address mappings across multiple deployment layers.

Changes

Cohort / File(s)	Change Summary
Changeset Documentation .changeset/smooth-roses-travel.md	Adds minor version bump for @hyperlane-xyz/registry with changelog entry documenting the addition of Ink, Monad, and Xlayer support for EZETH.
Production Configuration deployments/warp_routes/EZETH/renzo-prod-config.yaml	Introduces ink, monad, and xlayer tokens (with their respective addresses) and establishes comprehensive connections between these chains and existing supported networks (arbitrum, base, berachain, blast, bsc, ethereum, fraxtal, line, mode, optimism, plasma, sei, swell, taiko, unichain, worldchain).
Staging Configuration deployments/warp_routes/EZETHSTAGE/renzo-stage-config.yaml	Mirrors production changes by adding ink, monad, and xlayer token definitions and chain connections to the staging environment, with corresponding address/denom blocks and expanded connection matrices.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

• Production config file: The addition of three new token definitions with extensive connection mappings requires verification that all chain connections are correctly configured and aligned with the staging version.
• Consistency verification: Ensure that ink, monad, and xlayer token addresses and connections are consistent across production and staging configs.
• Connection completeness: Validate that the connection matrix for each new chain includes all necessary routes and that existing connections weren't accidentally modified.

Possibly related PRs

• feat: sep 29 chain deploys #1168: Adds Ink/Monad/Xlayer tokens and connections to EZETH deployment configs; this PR directly implements the chain infrastructure these token configurations reference.
• feat: ousdt v3 extension #974: Both PRs modify warp_routes token configurations and registry changesets with related chain and token additions, particularly around ink token connectivity.

Suggested reviewers

• paulbalaji
• xeno097

Poem

Like layers in an onion (or perhaps a swamp),
Three new chains now join the EZETH romp—
Ink, Monad, Xlayer find their place,
Through configs prod and stage embrace. 🧅✨

Pre-merge checks and finishing touches

❌ Failed checks (2 warnings)

Check name	Status	Explanation	Resolution
Description Check	⚠️ Warning	While the description has the proper three-section structure from the template, two of the three substantive sections are left completely empty with only placeholder comments. The Description section is present and provides a brief summary, but the Backward Compatibility section contains only a "Yes/No" prompt with no answer, and the Testing section has only the template question without any response. This leaves critical information gaps that the template was designed to capture.
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	You can run @coderabbitai generate docstrings to improve docstring coverage.

✅ Passed checks (1 passed)

Check name	Status	Explanation
Title Check	✅ Passed	The title "feat: Add ink, monad, xlayer for ezeth" directly and specifically describes the main change in this PR. The raw summary confirms that the changeset adds support for these three chains in multiple EZETH configuration files, making the title a clear and concise representation of the work. It's not vague or overly broad—it tells reviewers exactly what was added without unnecessary noise.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch ltyu/EZETH/ink-monad-xlayer

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 721d717 and 9255bf5.

📒 Files selected for processing (3)

• .changeset/smooth-roses-travel.md (1 hunks)
• deployments/warp_routes/EZETH/renzo-prod-config.yaml (17 hunks)
• deployments/warp_routes/EZETHSTAGE/renzo-stage-config.yaml (17 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

• GitHub Check: check-warp-deploy

🔇 Additional comments (5)

.changeset/smooth-roses-travel.md (1)

1-5: LGTM—clean and straightforward.

The changeset format looks good, and the changelog message accurately captures the intent of adding new chain support.

deployments/warp_routes/EZETHSTAGE/renzo-stage-config.yaml (1)

192-215: Collateral address uniformity—needs a quick sanity check.

All three new chains (ink, monad, xlayer) in the stage config share the same collateral address: 0x06232BC2a4388695a2C5A6C8e1F67743B9e6cc51. While this might be correct if all three wrap the same underlying asset, it's worth verifying this is intentional and not another copy-paste artifact.

Also applies to: 273-299, 489-515

deployments/warp_routes/EZETH/renzo-prod-config.yaml (3)

200-227: Address mismatch between stage and prod configs for the same chains.

The production config uses different token addresses than the stage config:

• Ink: Stage uses 0x836088259A6c273F6dB7BB2C3ba74Ad046CC1ea9, Prod uses 0x698f0Acd19F4795B6C187d5187E1d0b62f6e257b
• Monad: Stage uses 0x6642D0E1d28C337305A99d91E528D6B155beCbe1, Prod uses 0x7A911b0bD4F067FB8DAFF734A78E7A72865100d8
• Xlayer: Stage uses 0x6642D0E1d28C337305A99d91E528D6B155beCbe1, Prod uses 0xB0A73DBA15454B3f84CeC0f88CFc7D88B6De59B3

While different environments typically do use different addresses, the duplication issue in stage config (monad/xlayer) raises questions about whether these prod addresses were properly vetted. Cross-reference with deployment documentation to ensure these are the correct production addresses.

Also applies to: 284-311, 508-535

---

200-227: Shared collateral address across all three new chains—verify this is intentional.

Like in the stage config, all three new chains in production share the same collateral address: 0x2416092f143378750bb29b79eD961ab195CcEea5. This could be correct (same underlying asset), but it's worth confirming this isn't a copy-paste artifact, especially given the stage config already has this pattern.

Also applies to: 284-311, 508-535

---

369-395: Asymmetric branding change on Sei—stage config unchanged.

The Sei entry in production was rebranded: name changed from "Renzo Restaked ETH" to "Restaked ETH on Sei" and symbol from "ezETH" to "redETH". However, the stage config (EZETHSTAGE) still uses the old naming. This asymmetry might be intentional (stage vs prod naming conventions), but it's worth confirming these should diverge or if the stage config also needs the rebrand.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[github-actions]

Check Warp Deploy Summary

Warp Route ID	Status
EZETH/renzo-prod	❌
EZETHSTAGE/renzo-stage	❌

Last updated: 2025-11-04 21:29:52 UTC