feat: Add CARR configs and logo

[ltyu]

Description

Backward compatibility

Testing

Summary by CodeRabbit

• New Features

  • Added CARR token support across Arbitrum, BSC, Polygon, Solana, and Carrchain with native, collateralized, and synthetic variants.
  • Enabled cross-chain routing and token mappings for CARR to support consistent transfers and decimals.
  • Included token metadata and logo for improved identification in UIs.

• Chores

  • Published a minor version bump reflecting the new CARR configurations.

[changeset-bot]

🦋 Changeset detected

Latest commit: 551abba

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

[github-actions]

Check Warp Deploy Summary

Warp Route ID	Status
CARR/carrchain	❌
DOG/base-optimism	✅
ES/eclipse	✅
KLC/arbitrum-bsc-kalychain-polygon	✅
OORT/bsc-ethereum-oortmainnet	✅
RCADE/arbitrum-bsc	✅
SEDA/base-ethereum	✅
SOLX/nitro	✅
SUPR/base-ethereum-ink-optimism-superseed	✅
TAIKO/taiko	✅

Last updated: 2025-10-06 17:19:56 UTC

[coderabbitai]

📝 Walkthrough

Walkthrough

Adds a changeset noting “Add CARR configs and logo,” plus two new YAML files introducing CARR warp-route token configurations and deployment metadata for Arbitrum, BSC, Carrchain, Polygon, and Solana mainnet.

Changes

Cohort / File(s)	Summary
Release metadata \.changeset/two-plants-appear.md	New changeset: minor bump for @hyperlane-xyz/registry with note “Add CARR configs and logo.”
CARR warp route configs deployments/warp_routes/CARR/carrchain-config.yaml	New YAML: defines six CARR-related token entries (native, synthetic, collateral) with address/denom, chainName, decimals, logoURI, name, symbol, standard, coinGeckoId/collateralAddressOrDenom where present, and cross-chain connections mapping tokens across Arbitrum, Polygon, Solana, Carrchain, and BSC.
CARR deployment metadata deployments/warp_routes/CARR/carrchain-deploy.yaml	New deployment config: per-chain deployment entries (owners, token addresses where applicable, types: native/collateral/synthetic, Solana foreignDeployment and gas) for Arbitrum, BSC, Carrchain, Polygon, Solana mainnet.

Sequence Diagram(s)

sequenceDiagram
  autonumber
  actor User
  participant SourceChain
  participant WarpRouteConfig as "Warp Route\nConfig (CARR)"
  participant BridgeRouter
  participant DestChain

  Note over WarpRouteConfig: Token entries (native / collateral / synthetic), decimals, owners, connections

  User->>SourceChain: Initiate CARR transfer
  SourceChain->>WarpRouteConfig: Lookup token mapping & decimals
  alt Native or Collateral
    SourceChain->>BridgeRouter: Lock/escrow per deployment config
  else Synthetic
    SourceChain->>BridgeRouter: Burn synthetic per config
  end
  BridgeRouter-->>DestChain: Cross-chain message to mint/release
  DestChain->>WarpRouteConfig: Validate mapping and decimals
  DestChain-->>User: Deliver CARR on destination

Loading

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Suggested reviewers

• Mo-Hussain
• xeno097
• ameten

Poem

A wee config file rolled out on the moor,
Tokens and logos tied to each door.
Chains all linked, owners penned neat,
Bridges set up for every fleet.
Now CARR’s charted — ready to meet. 🧭✨

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description Check	⚠️ Warning	The pull request description includes the required section headings but leaves them empty with only placeholder comments, so there is no actual summary, backward compatibility statement, or testing information.	Please complete each section by providing a brief summary of the changes, confirming backward compatibility, and describing how the new configs and deployments were tested.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title Check	✅ Passed	The title clearly and concisely states the primary change of adding CARR configuration files and a logo, matching the main content of the pull request without any extra noise or ambiguity.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch ltyu/carrchain

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between b544084 and 551abba.

📒 Files selected for processing (1)

• deployments/warp_routes/CARR/carrchain-deploy.yaml (1 hunks)

🧰 Additional context used

🪛 Checkov (3.2.334)

deployments/warp_routes/CARR/carrchain-deploy.yaml

[high] 19-20: IBM Cloud IAM Key

(CKV_SECRET_7)

🪛 Gitleaks (8.28.0)

deployments/warp_routes/CARR/carrchain-deploy.yaml

[high] 6-6: Detected a Generic API Key, potentially exposing access to various services and sensitive operations.

(generic-api-key)

---

[high] 13-13: Detected a Generic API Key, potentially exposing access to various services and sensitive operations.

(generic-api-key)

---

[high] 19-19: Detected a Generic API Key, potentially exposing access to various services and sensitive operations.

(generic-api-key)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

• GitHub Check: check-warp-deploy

---

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

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between b0c6749 and edd7ac0.

⛔ Files ignored due to path filters (1)

• deployments/warp_routes/CARR/logo.svg is excluded by !**/*.svg

📒 Files selected for processing (3)

• .changeset/two-plants-appear.md (1 hunks)
• deployments/warp_routes/CARR/carrchain-config.yaml (1 hunks)
• deployments/warp_routes/CARR/carrchain-deploy.yaml (1 hunks)

🧰 Additional context used

🪛 Checkov (3.2.334)

deployments/warp_routes/CARR/carrchain-deploy.yaml

[high] 23-24: IBM Cloud IAM Key

(CKV_SECRET_7)

🪛 Gitleaks (8.28.0)

deployments/warp_routes/CARR/carrchain-deploy.yaml

[high] 8-8: Detected a Generic API Key, potentially exposing access to various services and sensitive operations.

(generic-api-key)

---

[high] 17-17: Detected a Generic API Key, potentially exposing access to various services and sensitive operations.

(generic-api-key)

---

[high] 23-23: Detected a Generic API Key, potentially exposing access to various services and sensitive operations.

(generic-api-key)

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between edd7ac0 and b544084.

📒 Files selected for processing (2)

• deployments/warp_routes/CARR/carrchain-config.yaml (1 hunks)
• deployments/warp_routes/CARR/carrchain-deploy.yaml (1 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• deployments/warp_routes/CARR/carrchain-config.yaml

🧰 Additional context used

🪛 Checkov (3.2.334)

deployments/warp_routes/CARR/carrchain-deploy.yaml

[high] 23-24: IBM Cloud IAM Key

(CKV_SECRET_7)

🪛 Gitleaks (8.28.0)

deployments/warp_routes/CARR/carrchain-deploy.yaml

[high] 8-8: Detected a Generic API Key, potentially exposing access to various services and sensitive operations.

(generic-api-key)

---

[high] 17-17: Detected a Generic API Key, potentially exposing access to various services and sensitive operations.

(generic-api-key)

---

[high] 23-23: Detected a Generic API Key, potentially exposing access to various services and sensitive operations.

(generic-api-key)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

• GitHub Check: check-warp-deploy