feat(warp-routes): Deployed USD1 warp route bsc <> eni

[xeno097]

Description

Adds deployment artifacts for USD1 route between eni and bsc

Backward compatibility

• yes

Testing

• Locally on the ui
  • https://explorer.hyperlane.xyz/message/0x468cc238b107f9e05cdfe765f0a4a07aa5d1ab10273b31e087bf80a0a8338844
  • https://explorer.hyperlane.xyz/message/0xebeb1c43975d5a7d2f2eef8612484e00a05cfbb0ee3679c19323b9def7ddcfcf

Summary by CodeRabbit

• New Features
  • USD1 warp route between BSC and ENI networks deployed and available.
  • World Liberty Financial USD (USD1) added on BSC as collateral and on ENI as a synthetic asset with token metadata and logo.
  • Routing and per-chain fee configurations for the USD1 route have been added and activated.

[coderabbitai]

📝 Walkthrough

Walkthrough

This PR adds a minor release changeset and deploys a new USD1 warp route between BSC and ENI by adding configuration and deployment YAMLs that define USD1 as collateral on BSC and synthetic on ENI, including token details and fee settings.

Changes

Cohort / File(s)	Summary
Release Metadata \.changeset/wicked-kids-applaud.md	Adds a changeset recording a minor release and noting deployment of the USD1 warp route (bsc ⇄ eni).
Warp Route Config & Deployment deployments/warp_routes/USD1/eni-config.yaml, deployments/warp_routes/USD1/eni-deploy.yaml	New YAMLs adding USD1 token entries: BSC as EvmHypCollateral with collateralAddressOrDenom, 18 decimals, connections and metadata; ENI as EvmHypSynthetic with connections to Ethereum/BSC, 18 decimals, tokenFee config (fee contract on bsc at 8 bps) and overall routing fee settings.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

A wee route stitched 'twixt chain and shore,
USD1 travels, wallets roar,
Collateral set, fees not sour,
BSC to ENI — steady power,
A tiny bridge, all green and sure.

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly summarizes the main change: deploying a USD1 warp route between bsc and eni chains, which directly aligns with all the files added in this changeset.
Description check	✅ Passed	The description follows the template structure with all required sections: Description summarizes the USD1 deployment, Backward compatibility is explicitly stated as 'yes', and Testing includes specific explorer links validating the deployment.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch xeno/usd1-eni

Tip

Try Coding Plans. Let us write the prompt for your AI agent so you can ship faster (with fewer bugs).
Share your feedback on Discord.

---

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

[hyper-gonk]

Check Warp Deploy Summary

Warp Route ID	On-Chain	Config Sync
USD1/eni	✅	✅

Last updated: 2026-02-26 14:21:51 UTC

[coderabbitai]

🧹 Nitpick comments (1)

deployments/warp_routes/USD1/eni-config.yaml (1)

4-4: Minor observation: coinGeckoId only on the BSC entry.

The coinGeckoId: usd1 field is present on the BSC token but not the ENI one. Now, that's probably fine if the registry only needs it on one entry per route - just makin' sure that's intentional and not somethin' that wandered off when nobody was lookin'.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@deployments/warp_routes/USD1/eni-config.yaml` at line 4, The ENI token entry
is missing the coinGeckoId field that exists on the BSC entry; if the registry
expects a coinGeckoId for each route token, add coinGeckoId: usd1 to the ENI
entry to match the BSC configuration (ensure you update the ENI token block
where coinGeckoId is absent); if it was intentionally omitted, add a clear
comment in the ENI entry explaining why coinGeckoId is not present to avoid
confusion.

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Nitpick comments:
In `@deployments/warp_routes/USD1/eni-config.yaml`:
- Line 4: The ENI token entry is missing the coinGeckoId field that exists on
the BSC entry; if the registry expects a coinGeckoId for each route token, add
coinGeckoId: usd1 to the ENI entry to match the BSC configuration (ensure you
update the ENI token block where coinGeckoId is absent); if it was intentionally
omitted, add a clear comment in the ENI entry explaining why coinGeckoId is not
present to avoid confusion.

---

ℹ️ Review info

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 3fb7401 and dfa7924.

📒 Files selected for processing (1)

• deployments/warp_routes/USD1/eni-config.yaml