chore: Add Outbetestnet chain to Hyperlane registry (chainId 512512)

[benachyv]

Description

Add Outbe chain to the Hyperlane registry.

• name: outbetestnet
• displayName: Outbe Testnet
• chainId: 512512
• domainId: 512512
• protocol: ethereum
• rpcUrls: https://eth.p.outbe.net
• nativeToken: Outbe (18 decimals)

Core contracts:
domainRoutingIsmFactory: "0x1da7be0a2853B8e29df356d440aD9C4FB4d7deb0"
interchainAccountRouter: "0xe1f073901b6104ca5f93c817374D8d2cCF03DE1F"
mailbox: "0xAe6E952f092d5a944582E3E99a529aE8E97b077c"
merkleTreeHook: "0xE3AACA7b77c9C6B1791631AC12E592Bf8E01FB90"
proxyAdmin: "0xc01459C72F7E0eF80a54014Dd1985aF9Fb69a178"
staticAggregationHookFactory: "0x88060b27FA13c94D26929857Af4410cF009EDc9B"
staticAggregationIsmFactory: "0x559B52978C117514f84a45F325Fc67C6CEAfF3F2"
staticMerkleRootMultisigIsmFactory: "0xA7ffB9eEC28B64fe1495403922567Ac44cEF0272"
staticMerkleRootWeightedMultisigIsmFactory: "0x7a954D5659661aEa3672518cBCaD884384a5D6D1"
staticMessageIdMultisigIsmFactory: "0x2fdD5B36eAc3cA988af43F06e15e99f07C1C5e82"
staticMessageIdWeightedMultisigIsmFactory: "0x1AdEf7A458A7AF02626C7F82Cace41F4B8A99A50"
testRecipient: "0x945C85Ac7C4cBb6fB2E17d121648e69b221515f5"
validatorAnnounce: "0x4894B9F1F525c94bB5b38AD243EA82EeD43aA4b2"

Files added:

• chains/outbe/metadata.yaml
• chains/outbe/addresses.yaml
• chains/outbe/logo.svg

---

Backward compatibility

✅ Yes — this is an additive change (adds a new chain).
No existing configs are modified.

---

Testing

✅ Verified using Hyperlane CLI with local registry:

hyperlane core read --chain outbetestnet --registry ./chains


<!-- This is an auto-generated comment: release notes by coderabbit.ai -->

## Summary by CodeRabbit

* **New Features**
  * Added support for Outbe Testnet, a new Ethereum-compatible testnet network. Users can now configure and interact with this network through the application.

<!-- end of auto-generated comment: release notes by coderabbit.ai -->

[changeset-bot]

⚠️ No Changeset found

Latest commit: 942d838

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

[coderabbitai]

📝 Walkthrough

Walkthrough

A new Outbe testnet chain configuration is introduced through two YAML files. The first defines contract address mappings for various infrastructure components, and the second specifies chain metadata including chain ID 512512, RPC endpoint, and native token details (COEN with 18 decimals).

Changes

Cohort / File(s)	Summary
Outbe Testnet Configuration chains/outbetestnet/addresses.yaml, chains/outbetestnet/metadata.yaml	Adds chain configuration for new Outbe testnet with contract address mappings (mailbox, routers, hooks, ISMs) and chain metadata (ID 512512, domain ID 512512, Ethereum protocol, test RPC endpoint, COEN native token)

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Suggested reviewers

• paulbalaji
• yjamin
• xeno097

Poem

Like onions have layers, so do chains grow tall,
Outbe testnet joins the fold, configuration and all,
Addresses mapped, metadata neat,
A swamp of contracts, now complete. 🧅⛓️

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
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 (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	The pull request description follows the required template structure and includes all three mandatory sections. The Description section provides comprehensive details about the Outbe chain being added, including name, chainId, protocol, and all relevant contract addresses. The Backward compatibility section clearly confirms the change is additive with no modifications to existing configs. The Testing section demonstrates verification using Hyperlane CLI with the appropriate command, showing the chain configuration has been validated with actual tooling.
Title Check	✅ Passed	The PR title "Add Outbetestnet chain to Hyperlane registry (chainId 512512)" directly and accurately summarizes the main change across both modified files. The title captures the primary action (adding a new chain), the specific chain being added (Outbetestnet), and the destination (Hyperlane registry), with the chainId serving as a helpful distinguishing detail. It's clear, concise, and follows conventional commit format without unnecessary fluff—a teammate reviewing the git history would immediately grasp what this pull request does. The title encompasses the addition of both the metadata.yaml and addresses.yaml files as part of the larger chainRegistry expansion.

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

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

---

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

🧹 Nitpick comments (2)

chains/outbetestnet/metadata.yaml (2)

1-1: Clear out that Cyrillic text in the comment.

Line 1 has some Russian text ("для Intent Framework") that looks like it got left behind from a template. Better to keep comments clean and in English so everyone can read what this block does.

Apply this diff to clean up the comment:

-# Minimal Chain Config для Intent Framework
+# Minimal Chain Config

---

8-9: Remove extra blank lines for cleaner formatting.

There are a couple of blank lines here (8-9) before the rpcUrls section. Nothing breaks, but trimming them would tidy things up a bit. Like draining a swamp—sometimes you just gotta remove what's not needed.

Apply this diff to remove the extra spacing:

 isTestnet: true
-
-
 rpcUrls:

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 0aaf81a and 6451e66.

⛔ Files ignored due to path filters (1)

• chains/outbetestnet/logo.svg is excluded by !**/*.svg

📒 Files selected for processing (2)

• chains/outbetestnet/addresses.yaml (1 hunks)
• chains/outbetestnet/metadata.yaml (1 hunks)

🔇 Additional comments (2)

chains/outbetestnet/addresses.yaml (1)

1-13: All contract addresses present and properly formatted.

Everything here layers together nicely—all 13 contract addresses are accounted for and formatted consistently with the 0x prefix and checksummed hex. No structural issues to worry about.

chains/outbetestnet/metadata.yaml (1)

3-20: Chain metadata structure and values look solid.

The configuration is all there and correct: chainId and domainId both match the spec (512512), name aligns with the file path (outbe), protocol is ethereum, and the RPC endpoint, native token (COEN, 18 decimals), and block confirmations all match what's documented in the PR. The structure itself is valid YAML with no schema violations.