The two milestones for SabVM

[PaulRBerg]

See the milestones tab.

Broadly speaking, there will be two stages in the development of the SabVM:

Genesis

• MNTs
• Streaming opcodes, but they work only for EOAs
• No smart contract deployments besides NTs
• The NT deployments are permissioned; only us (Sablier Labs) can deploy them

Odyssey

• Custom smart contract deployments are possible, but they are still permissioned (only Sablier Labs can deploy)
• The CALL opcodes work for smart contracts and NTs
• The streaming opcodes work for smart contracts
• Eventually, deployments become permissionless

[razgraf]

In the Genesis milestone, the "Streaming opcodes" item feels a bit too specific given the active research still required (i.e. opcodes vs. precompiles). Might be worth renaming it to something more general.

At the same time, the list focuses a bit too much on the MNT aspect so it could either be:

1. Modified into a milestone set for SabVM's MNT only ..or
2. Modified to include things like
   • Stream storage and data structure
   • Growth management (How to prevent Unbounded Computational Growth (UCG)? #57) and graph optimizations
   • CRON-architecture (a.k.a. the scheduler Research Substrate's pallet-scheduler #65 or solvency watcher)
   • Other things that have to be implemented from scratch

[PaulRBerg]

the active research still required (i.e. opcodes vs. precompiles). Might be worth renaming it to something more general.

It is definitely the case that there will be special opcodes for streaming in the V<. The discussion re precompiles is about how those opcodes are exposed in Solidity.

Modified into a milestone set for SabVM's MNT only ..or

I like this idea - having an MNT-only milestone makes sense given how important they are.

[PaulRBerg]

Modified to include things like

Will review later this part