-
Notifications
You must be signed in to change notification settings - Fork 242
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
[ETHEREUM-CONTRACTS] overhaul of SuperTokenV1Library & legacy lib deprecation #2032
Conversation
Changelog ReminderReminder to update the CHANGELOG.md for any of the modified packages in this PR.
|
bd182c5
to
2cb23d9
Compare
analysis of the lib interface:
|
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## dev #2032 +/- ##
==========================================
- Coverage 88.35% 88.09% -0.27%
==========================================
Files 112 109 -3
Lines 7009 6793 -216
Branches 965 978 +13
==========================================
- Hits 6193 5984 -209
+ Misses 814 807 -7
Partials 2 2
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚨 Try these New Features:
|
XKCD Comic RelifLink: https://xkcd.com/2032 |
distributeToPool
todistribute
(name nomore occupied by IDA)updateMemberUnits
(and variants) because it doesn't belong to the token interface. (1)setCFAFlowRate
andsetCFAFlowRateFrom
. Note that the naming differs from thesetFlowrate
in the CFA forwarder because of the changed context.getFlowRate
andgetFlowInfo
to be agreement independentflowX
andtransferX
, which abstract the receivers dimension (1:1 or 1:n) (2)VestingSchedulerV2
andFlowScheduler
to useSuperTokenV1Library
instead of the deprecatedCFAv1Library
VestingScheduler
(v1)IInstantDistributionAgreementV1
Not done: renaming of SuperTokenV1Library to SuperTokenLib. Would cause too much breakage across repos and documentation to be worth it. Would be nice to have it as alias.
(1) it doesn't belong into the GDA interface either, probably is duplicated there in order to make it batchable when we didn't yet have batch call support for arbitrary call targets. See #2033
(2) naming
flow
andtransfer
was considered. Shadowing the pre-existingERC20.transfer
may be dangerous in this context, thus the suffix for clear distinction.