chore: add TIA warp route between celestiatestnet and edentestnet and update eden's rpc

[blasrodri]

Add TIA warp route between celestiatestnet and edentestnet and update eden's rpc

Summary by CodeRabbit

• New Features

  • Added TIA warp route connectivity between Celestia testnet and Eden testnet.

• Updates

  • Updated Eden Testnet RPC endpoint to HTTPS for enhanced security and reliability.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[changeset-bot]

🦋 Changeset detected

Latest commit: a0ec663

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 introduces a new TIA warp route connecting Celestia Testnet and Eden Testnet. The Eden Testnet RPC endpoint gets upgraded to HTTPS with a fresh host address, and corresponding deployment and configuration files are added for the cross-chain token bridge.

Changes

Cohort / File(s)	Summary
Changeset .changeset/gold-nails-build.md	Documents a minor version release for the registry package with updates to the TIA warp route and Eden's RPC endpoint
Chain Metadata chains/edentestnet/metadata.yaml	Updates RPC endpoint from HTTP to HTTPS, changing the host from rpc-evreth-sequencer-edennet-1-testnet.binary.builders to ev-reth-eden-testnet.binarybuilders.services
TIA Warp Route Configuration deployments/warp_routes/TIA/celestiatestnet-edentestnet-config.yaml	Adds token configuration for TIA bridge between Celestia Testnet (CosmosNativeHypCollateral) and Eden Testnet (EvmHypSynthetic) with connection mappings
TIA Warp Route Deployment deployments/warp_routes/TIA/celestiatestnet-edentestnet-deploy.yaml	Specifies deployment metadata including decimals, ownership, and proxy admin settings for both chains

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

• Verify token addresses match across config and deployment files
• Confirm RPC endpoint is functional and properly formatted (HTTPS protocol)
• Check that collateral/synthetic token types are correctly assigned (CosmosNativeHypCollateral vs. EvmHypSynthetic)

Possibly related PRs

• update native token to TIA (18 decimals) for Eden #1236: Updates edentestnet metadata to rename native token to TIA alongside related chain configuration changes
• add celestia arabica + edentestnet #1150: Modifies edentestnet chain metadata and adds Celestia testnet registry entries with similar scope

Suggested reviewers

• christopherbrumm
• paulbalaji

Poem

🌉 Across the chains, TIA takes flight,
From Celestia's cosmic light to Eden's height,
An HTTPS bridge, so sturdy and true,
Layers of networks, all woven through! 🧅

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The PR description lacks the required template sections with substantive content; it only provides a summary statement without filling in Description, Backward compatibility, and Testing sections.	Complete the description template by providing details for each section: elaborate on the changes, confirm backward compatibility, and describe any testing performed with Hyperlane tooling.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Title check	✅ Passed	The title directly and accurately summarizes the main changes: adding a TIA warp route between two testnet chains and updating Eden's RPC endpoint.

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

Tip

📝 Customizable high-level summaries are now available in beta!

You can now customize how CodeRabbit generates the high-level summary in your pull requests — including its content, structure, tone, and formatting.

• Provide your own instructions using the high_level_summary_instructions setting.
• Format the summary however you like (bullet lists, tables, multi-section layouts, contributor stats, etc.).
• Use high_level_summary_in_walkthrough to move the summary from the description to the walkthrough section.

Example instruction:

"Divide the high-level summary into five sections:

1. 📝 Description — Summarize the main change in 50–60 words, explaining what was done.
2. 📓 References — List relevant issues, discussions, documentation, or related PRs.
3. 📦 Dependencies & Requirements — Mention any new/updated dependencies, environment variable changes, or configuration updates.
4. 📊 Contributor Summary — Include a Markdown table showing contributions:
   | Contributor | Lines Added | Lines Removed | Files Changed |
5. ✔️ Additional Notes — Add any extra reviewer context.
   Keep each section concise (under 200 words) and use bullet or numbered lists for clarity."

Note: This feature is currently in beta for Pro-tier users, and pricing will be announced later.

---

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: 1

🧹 Nitpick comments (1)

deployments/warp_routes/TIA/celestiatestnet-edentestnet-config.yaml (1)

1-21: Confirm provider reliability and warp route setup.

The warp route configuration ties together nicely with your deploy.yaml file—token metadata, standards, and addresses all align. Just want to make sure you've validated that the new RPC provider (binary builders) is reliable since you're switching Eden's endpoint over to it. If there are any concerns there, it might be worth keeping a close eye on this deployment.

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between c8c4e57 and 1d84cdb.

📒 Files selected for processing (4)

• .changeset/gold-nails-build.md (1 hunks)
• chains/edentestnet/metadata.yaml (1 hunks)
• deployments/warp_routes/TIA/celestiatestnet-edentestnet-config.yaml (1 hunks)
• deployments/warp_routes/TIA/celestiatestnet-edentestnet-deploy.yaml (1 hunks)

🧰 Additional context used

🧠 Learnings (1)

📚 Learning: 2025-11-20T11:01:47.506Z

Learnt from: paulbalaji
Repo: hyperlane-xyz/hyperlane-registry PR: 1240
File: deployments/warp_routes/USDSC/usdsc-config.yaml:15-24
Timestamp: 2025-11-20T11:01:47.506Z
Learning: In Hyperlane warp route configurations, the token identifier format is `<protocol>|<chain>|<address>`, not `<from_chain>|<to_chain>|<address>`. The `connections` field specifies the destination token, where the protocol indicates the protocol type (e.g., "ethereum" for EVM chains), the chain is the destination chain name, and the address is the token address. For example, `ethereum|ethereum|0x...` means connecting to a token on the ethereum chain using the ethereum protocol, and `ethereum|soneium|0x...` means connecting to a token on the soneium chain using the ethereum protocol.
<!-- [add_learning]
In the Hyperlane registry, multiple EVM-compatible chains like ethereum, soneium, bsc, linea all use "ethereum" as their protocol type in warp route token identifiers.

Applied to files:

• deployments/warp_routes/TIA/celestiatestnet-edentestnet-config.yaml

🔇 Additional comments (3)

.changeset/gold-nails-build.md (1)

1-5: Looks good.

The changeset follows the standard format and your description makes sense with what's happening in the other files—adding the TIA route and updating the RPC endpoint.

deployments/warp_routes/TIA/celestiatestnet-edentestnet-deploy.yaml (1)

1-15: Configuration looks solid.

The deployment settings are properly configured—Celestia side has the collateral token using the native utia denom, Eden side has the synthetic wrapped token with appropriate EVM ownership, and decimals are consistent across both chains. ProxyAdmin is set up too, which is the right call for the EVM side.

deployments/warp_routes/TIA/celestiatestnet-edentestnet-config.yaml (1)

3-7: Verify the Celestia token address representation.

The cross-references look consistent—your Eden token on line 13 matches the connection target on line 7, and the Celestia token on line 3 matches the connection target on line 16. The connection identifiers follow the right format (protocol|chain|address).

One thing to double-check: that long hex string on line 3 for the Celestia addressOrDenom—is that the correct representation for a Cosmos asset, or should it be using a different format? Just want to make sure it's intentional and will resolve properly.

Also applies to: 13-16