feat: add SOL/incentiv warp routes artifacts

[Xaroz]

Description

This PR adds SOL/incentiv warp route and update transactionOverrides for incentiv

Backward compatibility

Yes

Testing

Solana -> Incentiv
Incentiv -> Solana

Summary by CodeRabbit

• New Features

  • Added Solana (SOL) token support on the Incentiv chain with complete warp route configuration and deployment setup.

• Chores

  • Updated transaction override settings for the Incentiv chain with gas price configuration.
  • Version bump for registry package.

[changeset-bot]

🦋 Changeset detected

Latest commit: 9949e7c

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

Check Warp Deploy Summary

Warp Route ID	Status
ETH/ethereum-radix	❌
LITKEY/litchain	❌
MAGIC/arbitrum-abstract-ronin	✅
SMOL/arbitrum-abstract-ethereum-solanamainnet	✅
SOL/incentiv	✅
USDC/radix	✅
USDT/ethereum-radix	❌
WBTC/ethereum-radix	❌

Last updated: 2025-11-03 21:58:38 UTC

[coderabbitai]

📝 Walkthrough

Walkthrough

This PR adds Solana warp route configuration for the Incentiv chain, including token mappings between Solana mainnet and Incentiv, deployment specifications, and updates Incentiv chain metadata with transaction gas price overrides.

Changes

Cohort / File(s)	Summary
Changeset & Metadata .changeset/two-monkeys-drive.md, chains/incentiv/metadata.yaml	Declares minor version bump for registry package and adds transactionOverrides with explicit gas price (60000000000) to Incentiv chain configuration.
SOL Warp Route Configurations deployments/warp_routes/SOL/incentiv-config.yaml, deployments/warp_routes/SOL/incentiv-deploy.yaml	Introduces token and deployment configs establishing bidirectional Solana ↔ Incentiv warp route with EvmHypSynthetic and SealevelHypNative standards, including chain addresses, decimal specifications, and owner accounts.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

• Verify wallet addresses and configuration values (owner accounts, token addresses) are correctly formatted
• Confirm decimal precision (9) aligns with token specifications for both chains
• Check that token mappings and connections between Solana mainnet and Incentiv are bidirectional and properly referenced

Possibly related PRs

• #1168: Modifies Incentiv chain configuration (metadata and deployment artifacts), overlapping scope with this PR's chain setup updates.
• #948: Adds SOL warp-route token configurations under the same deployment directory, following similar configuration patterns.
• #1200: Introduces comparable Incentiv deployment artifacts with changesets, demonstrating parallel configuration patterns for different tokens.

Suggested reviewers

• xeno097
• ltyu

Poem

🧅 Like layers, this one's got structure—
Sol and Incentiv, bound together tight,
Gas prices set, addresses in place,
Config upon config, all sittin' just right.

Pre-merge checks and finishing touches

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and concisely summarizes the main changes: adding SOL/incentiv warp route artifacts, which aligns with the core modifications across the changeset, deployment configs, and metadata files.
Description check	✅ Passed	The description covers all required template sections: a summary of changes, backward compatibility confirmation, and testing evidence with explorer links demonstrating cross-chain message delivery.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch xaroz/sol-incentiv

---

📜 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 f13734a and 9949e7c.

📒 Files selected for processing (4)

• .changeset/two-monkeys-drive.md (1 hunks)
• chains/incentiv/metadata.yaml (1 hunks)
• deployments/warp_routes/SOL/incentiv-config.yaml (1 hunks)
• deployments/warp_routes/SOL/incentiv-deploy.yaml (1 hunks)

⏰ 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

🔇 Additional comments (5)

.changeset/two-monkeys-drive.md (1)

1-5: Changeset is structured properly.

The message clearly describes what's being added, and the minor version bump aligns with the PR's backward-compatible nature. Looks like the right layer of abstraction here.

chains/incentiv/metadata.yaml (1)

27-28: Verify the gasPrice override value against Incentiv's actual network conditions.

The 60 Gwei override looks reasonable on its face, but it'd be good to confirm this matches what's happening on-chain. Might want to cross-check with actual transaction patterns on Incentiv to make sure we're not over or underpaying.

deployments/warp_routes/SOL/incentiv-config.yaml (2)

3-21: Bidirectional connections look good, but verify both token addresses are actually deployed.

The cross-chain references are properly set up—each token knows about its counterpart on the other chain. But we should confirm that both addresses are live and deployed before this merges:

• Incentiv: 0xfaC24134dbc4b00Ee11114eCDFE6397f389203E3
• Solana: AYnRuLKV6Tqtibt7iA6DGCCACnRjy4nAhC8b5nPscsYs

The PR description mentions testing links, so I assume you've already validated these on-chain. Just making sure we're not adding phantom routes.

---

1-1: Schema reference is consistent across warp route files.

The yaml-language-server schema pointer at line 1 matches the pattern used elsewhere in the warp routes directory, which is good for IDE validation.

deployments/warp_routes/SOL/incentiv-deploy.yaml (1)

1-14: Address consistency verified — no issues found.

The Solana address AYnRuLKV6Tqtibt7iA6DGCCACnRjy4nAhC8b5nPscsYs matches perfectly across both files. It appears in the deploy file as the foreignDeployment value and in the config file as both a token reference and addressOrDenom entry. This deployment has all its layers lined up properly.

---

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