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: paymaster problems #957

Merged
merged 2 commits into from
Dec 31, 2024
Merged

fix: paymaster problems #957

merged 2 commits into from
Dec 31, 2024

Conversation

Marchand-Nicolas
Copy link
Collaborator

@Marchand-Nicolas Marchand-Nicolas commented Dec 31, 2024

Summary by CodeRabbit

  • Bug Fixes
    • Improved transaction metadata hash processing for registration calls to ensure correct data formatting.

Copy link

vercel bot commented Dec 31, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
app-starknet-id ✅ Ready (Inspect) Visit Preview 💬 Add feedback Dec 31, 2024 9:04am
sepolia-app-starknet-id ✅ Ready (Inspect) Visit Preview 💬 Add feedback Dec 31, 2024 9:04am

@Marchand-Nicolas Marchand-Nicolas added the 🚧 In progress do not merge Pull Request in progress, please do not merge label Dec 31, 2024
Copy link
Contributor

coderabbitai bot commented Dec 31, 2024

Walkthrough

The pull request modifies the getFreeRegistrationCalls function in the registrationCalls.ts file. The key change involves how the txMetadataHash is processed before being included in the calldata array. The new implementation first converts txMetadataHash to a decimal and then to a hexadecimal string, altering the format of the txMetadataHash in the calldata array, which may influence its interpretation by the contract.

Changes

File Change Summary
utils/callData/registrationCalls.ts Updated getFreeRegistrationCalls function to change the processing of txMetadataHash from direct hexadecimal conversion to a two-step conversion: first to decimal and then to a hexadecimal string.

Sequence Diagram

sequenceDiagram
    participant Caller
    participant getFreeRegistrationCalls
    participant Contract

    Caller->>getFreeRegistrationCalls: Call with parameters
    getFreeRegistrationCalls->>getFreeRegistrationCalls: Convert txMetadataHash
    Note over getFreeRegistrationCalls: hexToDecimal(txMetadataHash)
    Note over getFreeRegistrationCalls: numberToStringHex(decimalValue)
    getFreeRegistrationCalls->>Contract: Prepare calldata with processed txMetadataHash
Loading

The sequence diagram illustrates the transformation of txMetadataHash within the getFreeRegistrationCalls function before preparing the contract call, highlighting the new conversion process.


📜 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 8f05c55 and 714f6c1.

📒 Files selected for processing (1)
  • utils/callData/registrationCalls.ts (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • utils/callData/registrationCalls.ts

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>, 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 generate docstrings to generate docstrings for this PR. (Beta)
  • @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.

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: 0

🧹 Nitpick comments (1)
utils/callData/registrationCalls.ts (1)

Line range hint 229-240: Well-structured parameter formatting pattern for contract interactions.

The function demonstrates a consistent architectural pattern for parameter formatting in contract interactions:

  • Domain parameters use numberToStringHex
  • Signatures are mapped with numberToStringHex
  • Metadata hash now follows the same pattern

This consistency improves maintainability and reduces the likelihood of parameter formatting mismatches.

Consider documenting this parameter formatting pattern in the codebase to ensure future contract interactions follow the same approach.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 9182a1a and 8f05c55.

📒 Files selected for processing (1)
  • utils/callData/registrationCalls.ts (1 hunks)
🔇 Additional comments (1)
utils/callData/registrationCalls.ts (1)

237-237: LGTM! The metadata hash conversion aligns with parameter formatting pattern.

The change improves consistency by ensuring the metadata hash follows the same formatting pattern as other parameters in the calldata array (using numberToStringHex). This alignment with the established pattern likely resolves the paymaster issues.

Let's verify the consistency of metadata handling across the codebase:

✅ Verification successful

The metadata hash conversion is correctly implemented and consistent with the codebase patterns

Based on the codebase analysis, the change to wrap hexToDecimal(txMetadataHash) with numberToStringHex is verified to be correct for the following reasons:

  1. The pattern of converting metadata hashes using hexToDecimal is consistently used across the codebase for contract interactions, as seen in multiple files:

    • utils/callData/registrationCalls.ts
    • utils/callData/autoRenewalCalls.ts
    • Components like registerDiscount.tsx, freeRegisterCheckout.tsx
  2. The numberToStringHex conversion is commonly used for formatting parameters in contract calls, particularly in registration and renewal functions, ensuring consistent parameter formatting.

  3. The change aligns with how other metadata hashes are processed in similar contract interactions throughout the codebase, maintaining consistency in how contract parameters are formatted.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Search for other instances of metadata hash processing in contract calls
# to confirm this change aligns with the established pattern

ast-grep --pattern 'hexToDecimal($hash)'

# Also check for similar parameter processing patterns
ast-grep --pattern 'numberToStringHex($param)'

Length of output: 91


Script:

#!/bin/bash
# Let's try a broader search for hexToDecimal and numberToStringHex usage
rg "hexToDecimal|numberToStringHex" -A 2 -B 2

# Also search for metadata hash handling patterns
rg "metadataHash" -A 2 -B 2

Length of output: 40905

Copy link
Contributor

@fricoben fricoben left a comment

Choose a reason for hiding this comment

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

lgtm

@fricoben fricoben merged commit 8f3a996 into testnet Dec 31, 2024
4 checks passed
fricoben pushed a commit that referenced this pull request Dec 31, 2024
* Fix: Add distinct warning for expired domains

* Fix: Add distinct warning for expired domains

* Fix: Add distinct warning for expired domains

* Fix: Add distinct warning for expired domains

* add distinct warning for expired domains

* expiring soon checks if enbaled auto renewal

* removing space

* fix: paymaster problems (#957)

* fix: paymaster problems

* add comment

---------

Co-authored-by: Aroso Emmanuel <emmanueladedejiaroso@gmail.com>
Co-authored-by: Aroso Emmanuel  Adedeji <57766083+emarc99@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🔥 Ready for review This pull request needs a review
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants