feat: add missed signature for OKX

[myz1237]

Which Jira task belongs to this PR?

https://lifi.atlassian.net/browse/LF-10597

Why did I implement it this way?

I got an error from our BE when testing okx dex: Signature Allowlist] Unknown signature: 0x0d5f0e3b, chain: 1, contract: 0x7D0CcAa3Fac1e5A943c5168b6CEd828691b46B36 0x0d5f0e3b is uniswapV3SwapTo, another function to do swap

Checklist before requesting a review

• I have performed a self-review of my code
• This pull request is as small as possible and only tackles one problem
• I have added tests that cover the functionality / test the bug
• I have updated any required documentation

Checklist for reviewer (DO NOT DEPLOY and contracts BEFORE CHECKING THIS!!!)

• I have checked that any arbitrary calls to external contracts are validated and or restricted
• I have checked that any privileged calls (i.e. storage modifications) are validated and or restricted
• I have ensured that any new contracts have had AT A MINIMUM 1 preliminary audit conducted on by <company/auditor>

[coderabbitai]

Walkthrough

The pull request modifies the sigs.json file by adding a new signature entry, specifically 0x0d5f0e3b, to the existing list of signatures. This addition occurs after the unchanged signature 0x03b87e5f. The change is limited to updating the list and does not impact any existing functionality or logic.

Changes

File	Change Summary
config/sigs.json	Added new signature 0x0d5f0e3b to the list of signatures.

Possibly related PRs

• config: addresses and signatures for sushiswap dex agg #818: Modifies config/sigs.json by adding new signatures, directly related to the main PR.
• config: add signature for openocean #839: Adds a new signature to config/sigs.json, relevant to the changes in the main PR.
• config: add addresses and signatures for bebop #844: Updates config/sigs.json by adding a new signature, establishing a direct connection.
• fix: correct okx sign #876: Modifies config/sigs.json by adding a signature, relevant to the main PR's changes.

Suggested labels

AuditNotRequired

Suggested reviewers

• 0xDEnYO

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 207f863 and 9d84423.

📒 Files selected for processing (1)

• config/sigs.json (1 hunks)

🔇 Additional comments (2)

config/sigs.json (2)

153-154: LGTM! The signature addition looks correct.

The new signature follows the established format and is properly placed in the JSON array.

---

153-154: Verify signature uniqueness and correctness

Let's verify that the new signature is unique and corresponds to the correct function.

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[lifi-action-bot]

Test Coverage Report

Line Coverage: 76.10% (1675 / 2201 lines)
Function Coverage: 82.78% ( 351 / 424 functions)
Branch Coverage: 35.62% ( 192 / 539 branches)
Test coverage (76.10%) is above min threshold (76%). Check passed.