Replies: 6 comments 1 reply
-
well, i know that in computer science, the term "streaming" is used to refer to a continuous process, not a discrete one (like how tranches would unlock money). but for our branding, can't we also refer to it as "streaming"? if we decide not to refer to
wouldn't using both "merkle" and "lockup" keywords be redundant, as a merkle distributor implies that the funds are frozen within it? and this is what |
Beta Was this translation helpful? Give feedback.
-
We could. Let's discuss it here: sablier-labs/v2-core#708
I gotta open a separate discussion about that. Many implications.
No. Merkle is just the name of the guy who invented Merkle trees. Worldwide, very few computer scientists associate this name with crypto airdrops.
Merkle != Merkle distributor |
Beta Was this translation helpful? Give feedback.
-
i forgot to mention that if we decide to do so (refer to unlocked tranches as streaming), then it would be totally okay to leave the contract name as it is now, |
Beta Was this translation helpful? Give feedback.
-
Ok. In this case, let's first settle the API of the |
Beta Was this translation helpful? Give feedback.
-
@razgraf, do you have any thoughts on this following our call yesterday? I'm slightly more inclined to call it |
Beta Was this translation helpful? Give feedback.
-
Closing. |
Beta Was this translation helpful? Give feedback.
-
Implementing LockupTranched means that the
MerkleStreamer
contract will not handle just streaming models, but also discrete, delineated ones.In light of that, It makes most sense to rename
MerkleStreamer
toMerkleLockup
.Side note - we've previously discussed this here. But, at the time, we didn't know about LockupTranched.
Beta Was this translation helpful? Give feedback.
All reactions