Skip to content

feat: preview katana in USDC FPWR for polygon team - #1115

Open
haggis-hyperlane wants to merge 1 commit into
nexusfrom
haggis/preview-katana-usdc-fpwr
Open

feat: preview katana in USDC FPWR for polygon team#1115
haggis-hyperlane wants to merge 1 commit into
nexusfrom
haggis/preview-katana-usdc-fpwr

Conversation

@haggis-hyperlane

Copy link
Copy Markdown
Contributor

Summary

Adds the USDC FPWR (USDC/eclipsemainnet) token set to src/consts/warpRoutes.yaml with katana connections enabled, so the polygon team can test routes to/from katana via this PR's Vercel preview before the matching change lands in the registry.

Background

  • USDC FPWR was extended to katana on 2026-04-20 via hyperlane-monorepo#8505 and hyperlane-registry#1446.
  • The router on katana (0x680e8ECB908A2040232ef139A0A52cbE47b9F15B) is fully enrolled with all 15 peer chains (verified via cast call ... "domains()").
  • However, the merged registry config (deployments/warp_routes/USDC/eclipsemainnet-config.yaml) left katana's connections empty and every other chain's katana connection line commented out — so Nexus correctly hides katana.

What this PR does

Copies the FPWR token set from the registry config with all katana connection lines uncommented into src/consts/warpRoutes.yaml. The merge layer in src/features/warpCore/warpCoreConfig.ts deduplicates by (chainName, addressOrDenom), with local entries overriding registry entries (objMerge replaces array fields by default), so katana becomes routable in the Vercel preview without a registry change.

Test plan

  • Wait for Vercel preview to deploy
  • Confirm katana appears as both an origin and destination for USDC on the preview
  • Share preview URL with the polygon team to validate

Do not merge

This is a temporary preview. Should be superseded by a registry-side fix that uncomments the katana lines in eclipsemainnet-config.yaml, after which this file should be reverted to tokens: [].

Adds the USDC FPWR (USDC/eclipsemainnet) token set to
src/consts/warpRoutes.yaml with katana connections enabled, so the
polygon team can test routes to/from katana via this PR's Vercel
preview before the matching change lands in the registry.

Copied from hyperlane-registry deployments/warp_routes/USDC/eclipsemainnet-config.yaml
with all katana connection lines uncommented. Local entries override
registry entries on (chainName, addressOrDenom) match via the dedupe
in src/features/warpCore/warpCoreConfig.ts.

Onchain enrollment is already complete (router
0x680e8ECB908A2040232ef139A0A52cbE47b9F15B is enrolled with all 15
peers, verified via cast). Do not merge — should be superseded by a
registry-side fix.
@vercel

vercel Bot commented May 21, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
hyperlane-warp-template Ready Ready Preview, Comment May 21, 2026 2:25pm
4 Skipped Deployments
Project Deployment Actions Updated (UTC)
injective-bridge Ignored Ignored May 21, 2026 2:25pm
nexus-bridge Ignored Ignored May 21, 2026 2:25pm
ousdt-bridge Ignored Ignored May 21, 2026 2:25pm
trump-bridge Ignored Ignored May 21, 2026 2:25pm

Request Review

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.

1 participant