feat: Deploy Everclear ETH bridge

[larryob]

Description

Add Everclear ETH warp route. See hyperlane-xyz/hyperlane-monorepo#7350 for config generation.

Backward compatibility

Yes

Testing

We can send ETH: https://explorer.hyperlane.xyz/message/0x2a7f7402291c58fdc858194ec4259c883b95c9ba87369b97d7c7d02f24a053b1

The command that generated that transfer is:

 yarn hyperlane warp send \
--origin ethereum --destination optimism \
--warp /Users/tosinalabi/hyperlane-registry/deployments/warp_routes/ETH/mainnet-everclear-config.yaml \
--amount 1000000000000000 \
--key $(mykey) \
--registry http://localhost:3333

Summary by CodeRabbit

• New Features
  • Configured Everclear cross-chain bridge enabling asset routing across 16+ networks including Arbitrum, Avalanche, Base, Ethereum, Polygon, Optimism, and others with unified token mappings, fee structures, and bridge parameters.

[changeset-bot]

⚠️ No Changeset found

Latest commit: c357363

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

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

[github-actions]

Check Warp Deploy Summary

Warp Route ID	Status
ETH/mainnet-everclear	❌
EZETH/renzo-prod	✅
PZETH/berachain-ethereum-swell-unichain-zircuit	✅
PZETHSTAGE/berachain-ethereum-swell-unichain-zircuit	✅
TIA/arbitrum-celestia-neutron	✅
TIA/mantapacific-neutron	❌

Last updated: 2025-11-12 17:27:25 UTC

[paulbalaji]

heads up we can't merge this PR til:

1. SDK release with this change is released fix(sdk): loosen xerc20 deploy config validation hyperlane-monorepo#7367
2. registry is updated with newer SDK after 1)
3. this branch is updated with latest registry main after 2)

[coderabbitai]

📝 Walkthrough

Walkthrough

Two new YAML configuration files define the Everclear cross-chain routing system for ETH mainnet. The config file catalogs tokens across 16 chains with their mappings and metadata. The deploy file specifies network-specific fee structures, bridge addresses, and asset routing configurations for the same networks.

Changes

Cohort / File(s)	Summary
Everclear ETH Mainnet Configuration deployments/warp_routes/ETH/mainnet-everclear-config.yaml	Introduces token catalog defining cross-chain token representations across ink, mode, avalanche, mantle, scroll, bsc, arbitrum, base, zircuit, polygon, sonic, unichain, optimism, linea, ethereum, and zksync with decimals, names, standards, symbols, and connection mappings.
Everclear ETH Mainnet Deployment deployments/warp_routes/ETH/mainnet-everclear-deploy.yaml	Introduces deployment schema with network-specific everclearBridgeAddress, fee parameters, output asset mappings, and cryptographic signatures across all 16 supported networks, including owner and WETH address configurations.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

• Consistency verification: Ensure token addresses and chain names match across both configuration files
• Network completeness: Verify all 16 networks are consistently represented in both config and deploy specifications
• Fee parameter validation: Check that bridge addresses and fee structures align with network deployments
• Connection mappings: Validate that token connections in config accurately reference corresponding networks and assets

Suggested reviewers

• xeno097
• Xaroz

Poem

🌍 Sixteen chains now bound as one,
Everclear routes—the deed is done,
From ink to zk, the tokens flow,
Cross-chain bridges, layer by layer grow. ✨

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'feat: Deploy Everclear ETH bridge' directly summarizes the main change—deploying a new Everclear ETH warp route across multiple chains.
Description check	✅ Passed	The description covers all required template sections: a clear summary of the change with a reference link, explicit backward compatibility confirmation, and comprehensive testing evidence with command details.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch deploy-everclear

---

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.}

[coderabbitai]

Actionable comments posted: 2

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 257e473 and c357363.

📒 Files selected for processing (2)

• deployments/warp_routes/ETH/mainnet-everclear-config.yaml (1 hunks)
• deployments/warp_routes/ETH/mainnet-everclear-deploy.yaml (1 hunks)

🧰 Additional context used

🪛 GitHub Actions: ci

deployments/warp_routes/ETH/mainnet-everclear-config.yaml

[error] 1-1: YAML arrays should be sorted by specified keys. (hyperlane/sort-yaml-arrays)

⏰ 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

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

Fix YAML array sorting to resolve pipeline failure.

The build's already blowin' up because the connections arrays aren't sorted by chain name. The hyperlane/sort-yaml-arrays linter's caught this right proper-like. Each token's connections array needs to be alphabetically sorted by the destination chain name (the middle part of ethereum|{chain}|address).

For example, the first token (ink, lines 5-20) currently has connections ordered as: mode, avalanche, mantle, scroll, bsc... but they should be alphabetically: arbitrum, avalanche, base, bsc, ethereum, linea, mantle, mode, optimism, polygon, scroll, sonic, unichain, zircuit, zksync.

This sorting applies to all 16 token entries. Without fixing this, the PR won't pass CI.

Generate a script to verify the connections are properly sorted:

---

🏁 Script executed:

#!/bin/bash
# Verify connections arrays are sorted alphabetically by chain name

# Extract all connection entries and check sorting
rg -A 100 'connections:' deployments/warp_routes/ETH/mainnet-everclear-config.yaml | \
  rg 'ethereum\|' | \
  sed 's/.*ethereum|\([^|]*\).*/\1/' | \
  sort | uniq -c | wc -l

# Expected: 15 unique chains (all except the source chain in each token entry)
# If chains appear in wrong order within any token entry, linter will fail

Length of output: 99

---

🏁 Script executed:

#!/bin/bash
# Find the YAML config file for Everclear

fd -type f "mainnet-everclear-config.yaml" --search-path . 2>/dev/null | head -20

# Also search for any YAML files in warp_routes directory
echo "=== Searching for warp_routes directory ==="
fd -type d "warp_routes" --search-path . 2>/dev/null | head -10

# Search for any everclear-related YAML files
echo "=== Searching for everclear YAML files ==="
fd -type f ".*everclear.*\\.yaml" --search-path . 2>/dev/null | head -20

Length of output: 86

---

🏁 Script executed:

#!/bin/bash
# Check if there are ANY YAML files in the repo to understand structure

echo "=== All YAML files in repo ==="
find . -type f -name "*.yaml" -o -name "*.yml" 2>/dev/null | head -30

echo "=== Directory structure (first 2 levels) ==="
ls -la | head -20

echo "=== Check for deployments directory ==="
ls -la deployments 2>/dev/null || echo "No deployments directory"

Length of output: 2618

---

🏁 Script executed:

#!/bin/bash
# Find everclear config in warp_routes
echo "=== Looking for everclear config in warp_routes ==="
find deployments/warp_routes -type f -name "*everclear*" 2>/dev/null

echo "=== Listing warp_routes subdirectories (first 20) ==="
ls deployments/warp_routes | head -20

echo "=== Check if ETH directory exists ==="
ls -la deployments/warp_routes/ETH 2>/dev/null | head -20 || echo "ETH directory not found"

echo "=== Check for mainnet config in ETH ==="
find deployments/warp_routes/ETH -name "*mainnet*" 2>/dev/null || echo "No mainnet files found"

Length of output: 2539

---

🏁 Script executed:

#!/bin/bash
# Extract connections arrays and check their sorting order

echo "=== Extracting connections for each token ==="

python3 << 'PYEOF'
import yaml
import re

with open('deployments/warp_routes/ETH/mainnet-everclear-config.yaml', 'r') as f:
    data = yaml.safe_load(f)

if 'tokens' in data:
    for idx, token in enumerate(data['tokens']):
        chain = token.get('chainName', 'unknown')
        connections = token.get('connections', [])
        
        if connections:
            # Extract chain names from token strings like "ethereum|mode|0x..."
            chains_in_order = []
            for conn in connections:
                if 'token' in conn:
                    parts = conn['token'].split('|')
                    if len(parts) >= 2:
                        chains_in_order.append(parts[1])
            
            # Check if sorted
            chains_sorted = sorted(chains_in_order)
            is_sorted = chains_in_order == chains_sorted
            
            print(f"\nToken {idx+1} - Chain: {chain}")
            print(f"  Current order: {chains_in_order}")
            print(f"  Sorted order:  {chains_sorted}")
            print(f"  Is sorted: {is_sorted}")
            
            if not is_sorted:
                print(f"  ❌ UNSORTED - Needs fixing")
            else:
                print(f"  ✓ Properly sorted")
PYEOF

Length of output: 6611

---

Sort the connections arrays in all 16 tokens to fix the pipeline failure.

The verification shows every single token's got its connections all jumbled up - none of 'em are sorted alphabetically by chain name. That's what's making the build stumble. The hyperlane/sort-yaml-arrays linter's rightfully complaining about this.

Each token needs its connections array sorted by the destination chain (the middle bit in ethereum|{chain}|{address}). Right now they're all in this order: ink, mode, avalanche, mantle, scroll, bsc, arbitrum, base, zircuit, polygon, sonic, unichain, optimism, linea, ethereum (and zksync where it appears). They should be alphabetically: arbitrum, avalanche, base, bsc, ethereum, ink, linea, mantle, mode, optimism, polygon, scroll, sonic, unichain, zircuit, zksync.

All 16 tokens need fixing - none of 'em are properly sorted. Once you've got these arrays in the right order, the pipeline should be happy.

🤖 Prompt for AI Agents

In deployments/warp_routes/ETH/mainnet-everclear-config.yaml around lines 2-354,
each token's connections array is not alphabetically sorted by the destination
chain (the middle segment of entries like "ethereum|{chain}|{address}"), causing
the linter/pipeline failure; for all 16 tokens, sort each connections list by
that chain name into alphabetical order (arbitrum, avalanche, base, bsc,
ethereum, ink, linea, mantle, mode, optimism, polygon, scroll, sonic, unichain,
zircuit, zksync) and replace the existing unsorted arrays with the sorted
versions so every token's connections are in the specified sequence.

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

Verify deploy file passes linting after config file is corrected.

This deployment config looks structurally sound – the network entries and nested destination chains appear properly sorted. However, since the sibling config file has linting issues, make sure this deploy file also gets validated against the hyperlane/sort-yaml-arrays rule once the config is fixed. The nested everclearFeeParams and outputAssets entries seem to follow alphabetical ordering by destination chain, which should be good.

One thing worth noting: all deadline values are consistently set to 1764547238 across all networks and fee parameters, which is the expected behavior for a coordinated deployment.

After fixing the config file sorting, run:

---

🏁 Script executed:

#!/bin/bash
# Verify deploy file passes linting
yamllint deployments/warp_routes/ETH/mainnet-everclear-deploy.yaml

Length of output: 96

---

Right then, looks like we took a wrong turn there. Let me search for that deploy file properly.

---

🏁 Script executed:

#!/bin/bash
# Find the deploy configuration file
find . -name "*mainnet-everclear-deploy.yaml" -o -name "*everclear*deploy*" 2>/dev/null | head -20

Length of output: 59

---

🏁 Script executed:

#!/bin/bash
# List what's in the deployments directory structure
ls -la deployments/warp_routes/ETH/ 2>/dev/null || echo "Directory not found, searching for warp_routes..."
find . -type d -name "warp_routes" 2>/dev/null

Length of output: 2145

---

🏁 Script executed:

#!/bin/bash
# Get file listing to understand structure
find . -path "*/deployments/*" -name "*.yaml" -type f 2>/dev/null | grep -i ever | head -10

Length of output: 119

---

🏁 Script executed:

#!/bin/bash
# Verify deploy file passes linting with correct path
yamllint ./deployments/warp_routes/ETH/mainnet-everclear-deploy.yaml

Length of output: 24623

---

Line-length violations throughout deploy file – fix formatting of cryptographic signatures.

The deploy file's got a heap of linting errors. We're looking at over 400 violations, mostly because those long cryptographic signatures are pushin' past the 80-character limit, even when they're split across multiple lines with backslashes. There's also a missin' document start marker at the top.

The issue is fundamentally about how the signature hex strings are formatted. They need to be restructured so that when continued on the next line, they don't exceed the line-length limit. Add the document start marker (---) at line 1 as well.

This is separate from the config file sorting issues – the config file's got array-ordering problems, but this deploy file's got structural formatting problems that need fixin'.