Hydrex

[Siddharth2207]

Motivation

Hydrex Dex

Checks

By submitting this for review, I'm confirming I've done the following:

• made this PR as small as possible
• unit-tested any new functionality
• linked any relevant issues or PRs
• included screenshots (if this involves a front-end change)

Summary by CodeRabbit

• New Features
  • Added Hydrex as a supported liquidity provider, enabling integration with the routing system for pool data fetching operations.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

This PR integrates Hydrex as a new liquidity provider by creating a HydrexProvider class that extends AlgebraV2BaseProvider, registering it in the LiquidityProviders enum, and including it in both DataFetcher and RainDataFetcher initialization flows.

Changes

Cohort / File(s)	Summary
New Hydrex Provider Implementation packages/sushi/src/router/liquidity-providers/Hydrex.ts	New TypeScript class extending AlgebraV2BaseProvider with provider-specific constants (factory, initCodeHash, poolDeployer, tickLens) for the BASE chain. Implements getType() and getPoolProviderName() methods.
Provider Registration packages/sushi/src/router/liquidity-providers/LiquidityProvider.ts	Added Hydrex entry to the LiquidityProviders enum and included it in the UniV3LiquidityProviders array to expose it as a supported provider.
Data Fetcher Integration packages/sushi/src/router/data-fetcher.ts, packages/sushi/src/router/rain/RainDataFetcher.ts	Imported HydrexProvider and included it in the provider initialization arrays to enable pool data fetching participation.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

• rainlanguage/sushiswap#40: Adds a similar liquidity provider class following the same registration pattern across DataFetcher and LiquidityProvider files.
• rainlanguage/sushiswap#32: Modifies the provider initialization flow in RainDataFetcher that this PR also updates.

Suggested labels

new dex

Suggested reviewers

• hardyjosh

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The title 'Hydrex' is vague and generic, failing to convey meaningful information about what the changeset accomplishes.	Provide a more descriptive title that explains the main change, such as 'Add Hydrex liquidity provider support' or 'Integrate Hydrex DEX as liquidity provider'.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
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 docstrings

---

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