Fund streams from a common pool #18
Replies: 3 comments
-
Hi @bensacc thank you for this suggestion! We've chosen an individualized architecture for now, to reduce race-conditions on which streams get funded first, along with some other advantages @smol-ninja might be able to speak of more in-depth. In the meantime, have you tried our batch top-up feature? It allows you to select streams and top-up all of them in a single transaction.
|
Beta Was this translation helpful? Give feedback.
-
ah, I see. Yes, actually, this does work well for now, and into the future for us. I'm just imagining some point at which we might have a sufficiently large number of streams that even this becomes a bit unwieldy. One solution could be to just divide the pool equally across streams (i.e. X number of streams, each gets stream get topped up by (pool funding/x, possibly using the batching above under the hood?). Anyway, for now, yes, the batch function is definitely helpful. |
Beta Was this translation helpful? Give feedback.
-
Hi @bensacc, as Razgraf mentioned, the main reason for not implementing the shared pool was to prevent first-come-first-withdraw race among stream recipients. Additionally, the pooled approach could also introduce architectural complexity. That said, I understand that topping up multiple streams can be very tedious. To address this, we introduced the To improve this experience, we could explore adding an option in the UI where, during a batch top-up, you specify a total amount and then automatically distribute it based on predefined criteria like "allocate equally to selected streams" or "pay off only the debt", like you proposed. This would enable us to offer the same experience as shared pool without navigating away from our current architecture. Would this be solving your problem? |
Beta Was this translation helpful? Give feedback.
-
Hello, possibly this is already a feature and I just haven't figured it out, but as an organization that has started using Sablier for payroll, it would be super helpful to be able to fund all of our streams from a common pool, as opposed to invoking the 'Top Up' function for each individually. At some point, this may become unmanageable for us (which would be a shame, otherwise this is working great for us!).
Beta Was this translation helpful? Give feedback.
All reactions