You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
DuplicateA valid issue that is a duplicate of an issue with `Has Duplicates` labelMediumA Medium severity issue.RewardA payout will be made for this issue
Protocol incompatibility with smart contract wallets
Summary
Because of using tx.origin throughout the protocol, it limits the functionality of the protocol to EOA wallets without supporting Safe Wallets or other Smart Wallets.
Vulnerability Detail
In every single external function of the core contract, it uses tx.origin as user address, as follows:
DuplicateA valid issue that is a duplicate of an issue with `Has Duplicates` labelMediumA Medium severity issue.RewardA payout will be made for this issue
KupiaSec
Medium
Protocol incompatibility with smart contract wallets
Summary
Because of using
tx.origin
throughout the protocol, it limits the functionality of the protocol to EOA wallets without supporting Safe Wallets or other Smart Wallets.Vulnerability Detail
In every single external function of the core contract, it uses
tx.origin
as user address, as follows:Using
tx.origin
as user address does limit functionality of the protocol because it does not support smart contract wallets.Impact
Limitation of the protocol functionality of only supporting EOAs.
Code Snippet
https://github.com/sherlock-audit/2024-08-velar-artha/blob/18ef2d8dc0162aca79bd71710f08a3c18c94a36e/gl-sherlock/contracts/core.vy#L166
https://github.com/sherlock-audit/2024-08-velar-artha/blob/18ef2d8dc0162aca79bd71710f08a3c18c94a36e/gl-sherlock/contracts/core.vy#L202
https://github.com/sherlock-audit/2024-08-velar-artha/blob/18ef2d8dc0162aca79bd71710f08a3c18c94a36e/gl-sherlock/contracts/core.vy#L241
Tool used
Manual Review
Recommendation
Instead of using
tx.origin
as user address, the api contract should pass the user address to the core contract, for example as follows:Duplicate of #82
The text was updated successfully, but these errors were encountered: