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

Draft: Prevent locking funds when using sendMessage with the target is an EOA and value > 0 #266

Closed

Conversation

0x6e616d
Copy link
Member

@0x6e616d 0x6e616d commented Sep 11, 2024

  • In the L1XDM contract, we prevent sending ETH to this contract when using sendMessage function
  • In the L2XDM contract, we prevent sending the native token and the _target is an EOA when using sendMessage function, because in the relayMessage, the _target must transfer the native token when that is called.

@0x6e616d 0x6e616d requested review from nguyenzung and rlgns98kr and removed request for nguyenzung September 11, 2024 07:22
@0x6e616d 0x6e616d self-assigned this Sep 11, 2024
Copy link
Member

@rlgns98kr rlgns98kr left a comment

Choose a reason for hiding this comment

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

Please don't make changes in the contracts.
We are all preparing the external audit (resolving test code in contracts and NAT spec...)

@0x6e616d
Copy link
Member Author

Please don't make changes in the contracts. We are all preparing the external audit (resolving test code in contracts and NAT spec...)

These changes are from the internal audit. Related to this problem we discussed before

@0x6e616d 0x6e616d changed the title Prevent locking funds when using sendMessage with the target is an EOA and value > 0 Draft: Prevent locking funds when using sendMessage with the target is an EOA and value > 0 Sep 11, 2024
@0x6e616d
Copy link
Member Author

0x6e616d commented Sep 11, 2024

I changed it to the Draft PR. We will decide when the external audit report is finished.

@theo-learner theo-learner marked this pull request as draft September 12, 2024 02:15
Copy link
Contributor

This PR is stale because it has been open 14 days with no activity. Remove stale label or comment or this will be closed in 5 days.

@github-actions github-actions bot added the Stale label Sep 27, 2024
@0x6e616d 0x6e616d closed this Oct 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants