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: [ALC-LA2-4] revert when transferring to 0 address #49

Merged

Conversation

jaypaik
Copy link
Collaborator

@jaypaik jaypaik commented Apr 4, 2024

Following the recommendation to guard against address(0) transfers.

@@ -21,14 +21,10 @@ abstract contract BaseLightAccount is BaseAccount, TokenCallbackHandler, UUPSUpg
CONTRACT_WITH_ADDR
}

/// @dev The length of the array does not match the expected length.
Copy link
Collaborator Author

Choose a reason for hiding this comment

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

These were self-explanatory, so removing to be consistent with errors in BaseLightAccountFactory.

@jaypaik jaypaik requested a review from a team April 4, 2024 21:23
Copy link
Collaborator

@howydev howydev left a comment

Choose a reason for hiding this comment

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

LGTM

Base automatically changed from 04-04-fix_ALC-LA2-2_revert_on_malformed_signature to develop April 5, 2024 20:09
@jaypaik jaypaik force-pushed the 04-04-fix_ALC-LA2-4_revert_when_transferring_to_0_address branch 2 times, most recently from d8958c7 to 985a246 Compare April 5, 2024 20:41
@jaypaik jaypaik force-pushed the 04-04-fix_ALC-LA2-4_revert_when_transferring_to_0_address branch from 985a246 to 680aafd Compare April 5, 2024 20:48
@jaypaik jaypaik merged commit 90af2ae into develop Apr 5, 2024
2 checks passed
@jaypaik jaypaik deleted the 04-04-fix_ALC-LA2-4_revert_when_transferring_to_0_address branch April 5, 2024 20: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