Skip to content

feat: add USDnr (Nerona USD) warp route between Ethereum and Fluent#1476

Open
Khrafts wants to merge 1 commit intohyperlane-xyz:mainfrom
m0-foundation:feat/add-usdnr
Open

feat: add USDnr (Nerona USD) warp route between Ethereum and Fluent#1476
Khrafts wants to merge 1 commit intohyperlane-xyz:mainfrom
m0-foundation:feat/add-usdnr

Conversation

@Khrafts
Copy link
Copy Markdown
Contributor

@Khrafts Khrafts commented Apr 14, 2026

Uses the EvmM0Portal standard.

Description

Example: Add USDnr warp route on Ethereum <-> Fluent

Backward compatibility

Yes

Testing

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented Apr 14, 2026

📝 Walkthrough

Walkthrough

A changeset entry and warp route configuration file were added to support a new USDnr token bridge between Ethereum and Fluent chains. The configuration specifies token metadata, decimal precision, and cross-chain connection mappings using the EvmM0Portal standard.

Changes

Cohort / File(s) Summary
USDnr Warp Route Addition
.changeset/quick-terms-begin.md, deployments/warp_routes/USDnr/usdnr-config.yaml
Introduced changeset documentation and YAML configuration for a new USDnr (Nerona USD) warp route. Configuration defines token parameters for Ethereum and Fluent chains, including collateral addresses, 6-decimal precision, metadata (name, symbol, logo URI), and bidirectional chain connections.
🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Description check ⚠️ Warning The description is incomplete. While it mentions the EvmM0Portal standard and the basic change, the Testing section is entirely empty with only a comment placeholder, lacking actual testing details. Fill in the Testing section with details about whether the new config and deployment addresses were tested with Hyperlane tooling or CLI.
✅ Passed checks (2 passed)
Check name Status Explanation
Title check ✅ Passed The title accurately summarizes the main change: adding a USDnr warp route between Ethereum and Fluent, which aligns perfectly with the changeset additions.
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.


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

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

Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🧹 Nitpick comments (1)
deployments/warp_routes/warpRouteConfigs.yaml (1)

11104-11127: Drop this manual warpRouteConfigs.yaml edit from the PR.

This index file is CI-generated after merge, so hand-editing it here is unnecessary and can cause avoidable conflicts with other route additions.

Based on learnings: In the hyperlane-xyz/hyperlane-registry repo, deployments/warp_routes/warpRouteConfigs.yaml is automatically updated by a CI job that runs after a PR is merged, so manual edits are not required.

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@deployments/warp_routes/warpRouteConfigs.yaml` around lines 11104 - 11127,
This PR should remove the manual edits to the CI-generated
warpRouteConfigs.yaml: delete the added USDnr/usdnr token entries (the block
defining USDnr/usdnr with tokens and both ethereum and fluent entries) and any
other hand-modifications to deployments/warp_routes/warpRouteConfigs.yaml so the
file remains untouched in the PR; the CI job will regenerate and merge the
canonical changes after PR merge.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In @.changeset/quick-terms-begin.md:
- Line 5: Update the release note text in .changeset/quick-terms-begin.md by
correcting the chain name capitalization from "FLuent" to "Fluent" in the line
containing "Add USDnr (Nerona USD) warp route between Ethereum and FLuent using
EvmM0Portal standard" so the sentence reads with "Fluent" for consistent,
searchable release notes.

---

Nitpick comments:
In `@deployments/warp_routes/warpRouteConfigs.yaml`:
- Around line 11104-11127: This PR should remove the manual edits to the
CI-generated warpRouteConfigs.yaml: delete the added USDnr/usdnr token entries
(the block defining USDnr/usdnr with tokens and both ethereum and fluent
entries) and any other hand-modifications to
deployments/warp_routes/warpRouteConfigs.yaml so the file remains untouched in
the PR; the CI job will regenerate and merge the canonical changes after PR
merge.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: a14aa9a7-08c9-4f21-8c93-d584ead125e4

📥 Commits

Reviewing files that changed from the base of the PR and between 9ba14fe and 21d5594.

⛔ Files ignored due to path filters (1)
  • deployments/warp_routes/USDnr/logo.svg is excluded by !**/*.svg
📒 Files selected for processing (3)
  • .changeset/quick-terms-begin.md
  • deployments/warp_routes/USDnr/usdnr-config.yaml
  • deployments/warp_routes/warpRouteConfigs.yaml

'@hyperlane-xyz/registry': patch
---

Add USDnr (Nerona USD) warp route between Ethereum and FLuent using EvmM0Portal standard
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

Fix chain name capitalization in release note text.

On Line 5, FLuent should be Fluent to keep release notes polished and searchable.

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In @.changeset/quick-terms-begin.md at line 5, Update the release note text in
.changeset/quick-terms-begin.md by correcting the chain name capitalization from
"FLuent" to "Fluent" in the line containing "Add USDnr (Nerona USD) warp route
between Ethereum and FLuent using EvmM0Portal standard" so the sentence reads
with "Fluent" for consistent, searchable release notes.

@nambrot nambrot enabled auto-merge April 14, 2026 17:26
@nambrot nambrot disabled auto-merge April 15, 2026 19:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants