-
Notifications
You must be signed in to change notification settings - Fork 7
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
BugFix: Termed Payments #2479
Comments
I can think of two solutions. Ones feels convoluted and one involves updating the contracts....again.. Option 1Make payment start date Then we can filter out any payments that out tied to that particular EndDateTs, since the changes of two payment end date + time being the same will be unlikely. Option 2Probably the better one. is we just tie the stream to the hat/term via the Thoughts @decentdao/engineering? |
Option 3 Get streams based on creator (safe), not recipient. |
That would solve the outside Decent, Sablier problem. hmmm Then we would tie the payment to term via termEndDateTs and nominee of a particular role. that could work. I think it still leaves open the possibility of streams showing up on incorrect roles, since we still really aren't tying it to the HatId in anyway and currently the TermEndDateTs, is set to the beginning of the Date selected. maybe I need to think more. probably unlikely. |
Saw I originally put that in the code for the DatePicker but maybe needs more thought on which to choose endOfDay or beginning of Day or current time of day |
I'll be working on getting this straighten out tonight when I get back to it. So I think my plan is to
@decentdao/engineering any final thoughts leave here for me tonight before I go to do this |
So uncovered an issue with tying termed roles to the payments.
Currently when we retrieve regular role payments, we do this via the recipient, its smart account address, which is unique to the role.
For termed roles its the nominee who is the recipient. So what does this mean.
Currently when retrieving the payments, I'm creating a set of recipients created from all the terms nominees of a hat. The problem that it will now pull ANY Sablier payments of that address. This includes those created in other termed hats that nominee has worn and streams that happen outside of our UI.
The text was updated successfully, but these errors were encountered: