Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: deposit ERC-20 #160

Merged
merged 4 commits into from
Jul 10, 2024
Merged

fix: deposit ERC-20 #160

merged 4 commits into from
Jul 10, 2024

Conversation

fadeev
Copy link
Member

@fadeev fadeev commented Jul 5, 2024

Fix deposit to always include a recipient address in the message when depositing ERC-20, because of zeta-chain/node#2435

Summary by CodeRabbit

  • New Features

    • Improved handling of deposit transactions, including updated handling of recipient and message parameters and refined data encoding.
  • Refactor

    • Renamed options.sourceChain to options.chain.
    • Changed recipient from optional to required parameter.
    • Updated internal data composition and transaction object handling for deposits.
  • Bug Fixes

    • Adjusted the bytesToBool function formatting and parameter alignment for better clarity.

@fadeev fadeev requested review from andresaiello, lucas-janon and a team as code owners July 5, 2024 13:59
Copy link
Contributor

coderabbitai bot commented Jul 5, 2024

Walkthrough

The recent changes involve updates to the deposit function in deposit.ts for better handling of transaction parameters and data encoding. Additionally, the parameter structure and formatting in BytesHelperLib.sol have been improved for clarity. The enhancements mainly focus on renaming, variable declarations, and refining data assignments and transaction setups.

Changes

File Change Summary
contracts/BytesHelperLib.sol Formatted bytesToBool function's parameters and alignment for clarity.
packages/client/src/deposit.ts Updated deposit function including renaming, handling, and encoding process.
packages/tasks/src/deposit.ts Modified depositTask function to set recipient as a required parameter.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant Client
    participant CustodyContract

    User->>Client: Call deposit(options)
    Client->>Client: Process options (rename sourceChain to chain, encode recipient and message)
    Client->>CustodyContract: Call deposit(recipient, erc20, value, data)
    CustodyContract-->>Client: Transaction Response
    Client-->>User: Response
Loading

Poem

Amid the code where bytes do play,
Variables dance in a clearer way.
Transactions seamless, data neat,
In the blockchain rhythm, we compete.
Let's toast these changes with delight,
For smoother flows, through day and night!


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
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>.
    • 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 generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @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 as 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.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration 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.

@fadeev
Copy link
Member Author

fadeev commented Jul 5, 2024

Depositing gas:

npx hardhat cctx 0x42ad6c066b9a5eb348b757ca001a080c3c93adfd80f460065d078a7526785e25

Depositing ERC-20:

npx hardhat cctx 0x330a276ee99638ad00128c177a64f800be4eb4fa56fc738266c0fade51750c12

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 3

Outside diff range and nitpick comments (2)
packages/client/src/deposit.ts (1)

15-15: Update the function documentation to reflect the changes.

The documentation for the options.recipient parameter should be updated to indicate that it is now required.

- * @param options.recipient - Recipient address for the deposit. If not provided,
- * the deposit is made to the signer's address.
+ * @param options.recipient - Recipient address for the deposit. This parameter is required.
packages/tasks/src/deposit.ts (1)

151-151: Update the function documentation to reflect the changes.

The documentation for the recipient parameter should be updated to indicate that it is now required.

-  .addParam("recipient", "Recipient address")
+  .addParam("recipient", "Recipient address (required)")
Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 3ada76c and 323ebc8.

Files selected for processing (3)
  • contracts/BytesHelperLib.sol (2 hunks)
  • packages/client/src/deposit.ts (4 hunks)
  • packages/tasks/src/deposit.ts (2 hunks)
Files skipped from review due to trivial changes (1)
  • contracts/BytesHelperLib.sol
Additional context used
Biome
packages/client/src/deposit.ts

[error] 95-106: This else clause can be omitted because previous branches break early.

Unsafe fix: Omit the else clause.

(lint/style/noUselessElse)

Additional comments not posted (1)
packages/client/src/deposit.ts (1)

42-42: Ensure consistent parameter naming.

The parameter sourceChain has been renamed to chain. Ensure that all references to sourceChain are updated to chain.

Verification successful

Consistent parameter naming verified.

All references to sourceChain have been successfully updated to chain. No instances of sourceChain were found in the codebase.

Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify all references to `sourceChain` are updated to `chain`.

# Test: Search for the old parameter name. Expect: No occurrences of `sourceChain`.
rg --type typescript 'sourceChain'

Length of output: 69


Script:

#!/bin/bash
# Description: Verify all references to `sourceChain` are updated to `chain`.

# Test: Search for the old parameter name. Expect: No occurrences of `sourceChain`.
rg 'sourceChain'

Length of output: 918

fadeev and others added 2 commits July 5, 2024 17:24
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
@zeta-chain zeta-chain deleted a comment from coderabbitai bot Jul 5, 2024
@zeta-chain zeta-chain deleted a comment from coderabbitai bot Jul 5, 2024
Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 3

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 323ebc8 and fafaa0f.

Files selected for processing (1)
  • packages/client/src/deposit.ts (4 hunks)
Additional context used
Biome
packages/client/src/deposit.ts

[error] 94-105: This else clause can be omitted because previous branches break early.

Unsafe fix: Omit the else clause.

(lint/style/noUselessElse)

packages/client/src/deposit.ts Show resolved Hide resolved
packages/client/src/deposit.ts Show resolved Hide resolved
@zeta-chain zeta-chain deleted a comment from coderabbitai bot Jul 5, 2024
@fadeev fadeev merged commit 1cfaebb into main Jul 10, 2024
6 checks passed
@fadeev fadeev deleted the deposit-erc20 branch July 10, 2024 03:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants