Should the VM enable 1-to-n streams?

[PaulRBerg]

Superfluid offers Instant Distributions whereby a single stream can percolate to N recipients.

I'm skeptical that:

1. This feature is worth it in either Genesis or Odyssey
2. It's worth baking it into the VM (with a STREAMCREATEMULTIPLE opcode)

A 0xSplits-like contract could enable this feature by redistributing the incoming streams. See the Solidity fork spec I wrote.

[PaulRBerg]

Relaying the comment left by @IaroslavMazur on Notion on February 3, 2024:

There seems to be a disconnect between the question at hand - and the proposed opcodes (at least, judging by their names).

If my understanding is correct, the question hints at a one-to-many Stream (single instance), while the proposed opcodes would create multiple Streams: either one by one - or all together. Superfluid’s IDA Index, basically, creates a one-to-many “SuperStream” (and not many independent Streams), as well.

Now, if we think abstractly in terms of providing the underlying functionality (i.e. streaming assets to different recipients, in different proportions), then, if we implement SabVM such that Streams are connected to their sender’s and recipient’s balances directly (i.e. w/o requiring them to deposit and withdraw, respectively), then, the problem is being addressed by default.