-
Notifications
You must be signed in to change notification settings - Fork 179
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
[Flow EVM] reducing the scope of deposit to COAs only #5280
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #5280 +/- ##
=======================================
Coverage 55.60% 55.61%
=======================================
Files 1003 1003
Lines 96785 96785
=======================================
+ Hits 53818 53824 +6
+ Misses 38894 38892 -2
+ Partials 4073 4069 -4
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
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.
👍
/// Deposits the given vault into the EVM account with the given address | ||
access(all) | ||
fun deposit(from: @FlowToken.Vault) { | ||
InternalEVM.deposit( | ||
from: <-from, | ||
to: self.bytes | ||
) | ||
} | ||
|
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.
Maybe also update the FLIP to reflect this change, both in the Cadence code, and also by adding a line or two that explains the rational (can just copy the description of the linked issue).
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.
the FLIP is updated with changes on the Cadence code side but I'll add a small explainer why its only available on the COAs.
closes #5227