feat: add ETH/paradex & ETH/paradexsepolia warp route#1387
Conversation
Check Warp Deploy Summary
Last updated: 2026-02-12 15:43:05 UTC |
|
Warning Rate limit exceeded
⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. 📝 WalkthroughWalkthroughThis PR adds configuration and deployment files for ETH warp routes on Paradex and Paradex Sepolia networks. Five new YAML files define token routing specifications and deployment metadata across Ethereum, Mode, and Paradex chains, along with a changeset entry for version tracking. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~12 minutes Poem
🚥 Pre-merge checks | ✅ 2 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing touches🧪 Generate unit tests (beta)
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. Comment |
There was a problem hiding this comment.
Actionable comments posted: 3
🤖 Fix all issues with AI agents
In `@deployments/warp_routes/ETH/paradex-config.yaml`:
- Around line 24-32: Add a missing connections array to the paradex config
entry: update the paradex entry (the mapping that contains name: Ether and
standard: StarknetHypCollateral) to include a connections field listing the
networks that reference it (e.g., "mode" and "ethereum") so the topology is
bidirectional; ensure the field name is connections and its value is an array of
the network keys that should connect back to paradex.
In `@deployments/warp_routes/ETH/paradex-deploy.yaml`:
- Line 1: Remove the leading blank line at the very start of paradex-deploy.yaml
and reformat the file with Prettier (run prettier --write) so the YAML matches
the project's formatting rules and CI stops failing; ensure there are no extra
leading/trailing blank lines and commit the rewritten file.
In `@deployments/warp_routes/ETH/paradexsepolia-config.yaml`:
- Line 20: The YAML uses an invalid standard value "StarknetHypDexCollateral"
for the standard field; change the value of the standard key from
"StarknetHypDexCollateral" to the valid "StarknetHypCollateral" so it matches
other Starknet token configs and passes schema validation (update the standard:
entry referencing "StarknetHypDexCollateral" to "StarknetHypCollateral").
Description
Backward compatibility
Testing
Summary by CodeRabbit