-
Notifications
You must be signed in to change notification settings - Fork 1
fix(erc4626): accept Sky/Spark referral deposit/mint overloads (ENG-3841) #31
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
Open
ajag408
wants to merge
2
commits into
main
Choose a base branch
from
feat/eng-3841-erc4626-referral-deposit
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
one scope question on this overload: since it is added to the shared
ERC4626_ABI,deposit/mint(..., uint16 referral)becomes accepted for every supported generic vault, not only sky/spark, the new test also validates it against theeulerfixture...should this be gated by protocol/selector so generic vaults that do not support this overload keep rejecting it?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good question. considered gating it, and went accept-everywhere deliberately. Reasoning:
Security-wise the overload is inert. Everything that protects funds on the 2-arg path runs identically on the 3-arg path: tx.to must be a whitelisted vault, from == user, receiver == user (or the declared receiverAddress), amount > 0, no ETH value, and the byte-exact tamper re-encode. The extra arg is a uint16 — it can't encode an address or redirect anything. On Sky/Spark it only feeds a Referral event for ops attribution
For vaults that don't implement the overload, the tx just reverts on-chain — selector 0x9b8d6d38 doesn't exist on a vanilla ERC-4626, so no state changes and no funds move. A reverting deposit to a whitelisted vault is the same exposure class as any failed deposit. (If a whitelisted vault had a malicious fallback that swallowed unknown selectors, we'd have a bigger problem than this overload. The whitelist already assumes vault contracts are what they claim.)
Strict protocol specific comparison is possible but doesn't provide added security benefit and any protocols extending support to this referral code param will need a Shield update/result in false blocks.