-
Notifications
You must be signed in to change notification settings - Fork 48
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
LockupTranched: a new Lockup contract with sharply delineated chunks #787
Comments
Just wanted to let you know that I've implemented the POC and did benchmarks (see Now it is up to decide if it worth implementing here. |
Awesome, thanks @andreivladbrg, will review later. |
Kudos, @andreivladbrg, for the benchmark you have prepared here. I think it is as clear as day that we should move forward with
These gas optimizations are due to LT making it possible to have half as many segments as LD. But LT is more efficient even when the number of segments is equal. @razgraf could you give us the green light? |
Sounds good! |
Great, thanks. @andreivladbrg, you can move forward with implementing Note: we should first merge #798 |
I will, but currently I am working on making a huge refactor for core, that it would be very beneficial as the https://github.com/andreivladbrg/refactor-core/ saying it now, it may take a while |
That's fine but please create a discussion/ proposal prior to a PR |
As discussed here: https://github.com/sablier-labs/company-discussions/discussions/19
Tasks:
LockupDynamic
:withdraw
function inLockupTranched
beLockupTranched
is worth itNote: we will keep using the same terminology, i.e.,
streams
andstreamedAmountOf
. Related: #708 (comment)The text was updated successfully, but these errors were encountered: